Online Tutorials & Training Materials | STechies.com
Register Login
Advertisement

DBIF_RSQL_SQL_ERROR (SQL30081N) Jobs are failing

|| 1

DBIF_RSQL_SQL_ERROR (SQL30081N) Jobs are failing
Stechies

Hi,

Job is failing with the below short dumps:

1. Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB
Date and Time 04.10.2010 06:31:26
Database error text........: "SQL30081N A communication error has been
detected. Communication protocol being used: "TCP/IP". Communication API being
used: "SOCKETS". Location where the error was detected: "10.62.92.4".
Communication function detecting the error: "recv". Protoco"
Internal call code.........: "[RSQL/OPEN/KONP ]"

2. Runtime Errors DBIF_REPO_SQL_ERROR

Date and Time 06.10.2010 19:24:12
Database error text........: "CLI0108E Communication link failure.
SQLSTATE=40003"
Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "
Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============C ]"

Work process traice file has the below error which came today:

C *** ERROR in DB6Open[dbdb6.c, 3308] CON = 0 (BEGIN)
C &+ DbSlBegReadDB6( SQLExecute ): [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication
C &+ protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected:
C &+ "10.62.92.4". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0"
C *** ERROR in DB6Open[dbdb6.c, 3308] (END)
B ***LOG BYM=> severe DB error -30081 ; work process in reconnect status [dbsh#3 @ 1127] [dbsh 1127 ]
B ***LOG BY4=> sql error -30081 performing SEL on table KONP [dbtran#14 @ 7588] [dbtran 7588 ]
B ***LOG BY0=> SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'
B RSLT: {dbsl=99, tran=1}
B FHDR: {tab='KONP', fcode=53, mode=2, bpb=0, dbcnt=0, crsr=1,
B hold=0, keep=1, xfer=0, pkg=0, upto=0, init:b=0,
B init:p=(nil), init:#=148, wa:p=0x7000000501bc3e8, wa:#=148}
C *** ERROR in getAndBindSQLDA[dbdb6.c, 14585] CON = 0 (BEGIN)
C &+ DbSlReadDB6( SQLExtendedBind ): [IBM][CLI Driver] CLI0108E Communication link failure. SQLSTATE=40003
C &+
C &+ SELECT "UNAM", "UDAT", "UTIME", "L_DATALG", "Q_DATALG", "SDAT", "STIME", "MINOR_VERS", "MAJOR_VERS" FROM "REPOLOAD
C &+ " WHERE "PROGNAME" = ? AND "R3STATE" = ? AND "MACH" = ? WITH UR
C &+ cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, buffer_lobs=YES, op_type=18, reopt=0
C &+ ABAP location info: 'RSBTCRTE', 807
C &+
C &+ ABAP location info 'ZBW_FILL_KONPA004', 273
C &+
C *** ERROR in getAndBindSQLDA[dbdb6.c, 14585] (END)
B ***LOG BYM=> severe DB error -99999 ; work process in reconnect status [dbsh#3 @ 1127] [dbsh 1127 ]
B ***LOG BY4=> sql error -99999 performing SEL on table REPOLOAD [dbrepo#5 @ 2657] [dbrepo 2657 ]
B ***LOG BY0=> CLI0108E Communication link failure. SQLSTATE=40003 [dbrepo#5 @ 2657] [dbrepo 2657 ]
B ***LOG BY0=> CLI0108E Communication link failure. SQLSTATE=40003 [dbrepo#5 @ 2657] [dbrepo 2657 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
C *** ERROR in DB6EndTransaction[dbdb6.c, 6768] CON = 0 (BEGIN)
C &+ DbSlRollbackDB6( SQLEndTran ): [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003
C &+
C &+ ROLLBACK[FORCED][DONT_KEEP_WITH_HOLD]
C &+
C &+ ABAP location info 'ZBW_FILL_KONPA004', 273
C &+
C *** ERROR in DB6EndTransaction[dbdb6.c, 6768] (END)
B ***LOG BYM=> severe DB error -99999 ; work process in reconnect status [dbsh#3 @ 1127] [dbsh 1127 ]

Kindly suggest what can be done to resove this, as this is coming for specificly two jobs.

Regards,


Comments

  • 11 Oct 2010 12:14 pm
    Please check sm21 logs. Looks like net work issue happening in the system.

    Check with your network team.

Advertisement
Advertisement
Advertisement