IBM Support

Connection attempt to a database may return SQL0902C error with reason code "200x1232"("0100")""

Troubleshooting


Problem

When you are trying to connect to a database or restore a database from a backup, you may receive SQL0902C error from the DB2 command line as below examples: $ db2 restore database TESTDB taken at 20140906100839 SQL0902C A system error occurred. Subsequent SQL statements cannot be processed. IBM software support reason code: "200x1232"("0100")"". or $db2 connect to TESTDB SQL0902C A system error (reason code = "200x1232"("0100")"") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005

Symptom

The error normally occurs after previous failed/incomplete redirect restores. In addition to the SQL0902C error, you may also see below db2diag.log errors reported by the db2bp process:

2014-09-06-19.54.54.052569-240 I211440A450 LEVEL: Error
PID : 14155940 TID : 1 PROC : db2bp
INSTANCE: db2inst3 NODE : 000
HOSTNAME: MYHOST1
EDUID : 1
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrDrdaArAuthenticate, probe:912
MESSAGE : ZRC=0x87370014=-2026438636=SQLJR_SYSI "System Internal"
DIA8515C A system error has occurred.
DATA #1 : String, 20 bytes
DRDA AR CB IS NULL.

2014-09-06-19.54.54.076387-240 E211891A395 LEVEL: Severe
PID : 14155940 TID : 1 PROC : db2bp
INSTANCE: db2inst3 NODE : 000
HOSTNAME: MYHOST1
EDUID : 1
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrDrdaArAuthenticate, probe:912
MESSAGE : ADM2503C A datastream parsing error has been detected. A dump has
been generated.

2014-09-06-19.54.54.118112-240 I212287A842 LEVEL: Severe
PID : 14155940 TID : 1 PROC : db2bp
INSTANCE: db2inst3 NODE : 000
HOSTNAME: MYHOST1
EDUID : 1
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrDrdaArAuthenticate, probe:912
MESSAGE : ZRC=0x87370014=-2026438636=SQLJR_SYSI "System Internal"
DIA8515C A system error has occurred.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 19
sqlerrmc: 200x1232"("0100")"
sqlerrp : sqljrsec
sqlerrd : (1) 0x87370014 (2) 0x00000014 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

Cause

The db2 backend process db2bp may still hold some stalled/corrupted internal memory structure in cache after a failed/incomplete redirect restore

Resolving The Problem

1) run "db2 terminate" command to terminate the db2bp process so that clean up the stalled/corrupted memory cache.

2) Alternatively, find out the db2bp process and kill it.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Connectivity - Other","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.1;10.5;9.5;9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21683690

Page Feedback