On a gateway environment, there is a very rare issue where a
connect to a database might fail and db will be marked bad -
"DBMarkedBad"
Symptom:
2012-05-21-21.17.02.219088+540 I3046859A529 LEVEL: Severe
PID : 10813612 TID : 39889 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE_DB
APPHDL : 0-57898 APPID: *LOCAL.DB2.120521121713
AUTHID : DB2INST1
EDUID : 39889 EDUNAME: db2agent (idle)
FUNCTION: DB2 UDB, base sys utilities, sqleIndCoordInit,
probe:100
RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific
control block."
2012-05-21-21.17.02.219240+540 I3047389A421 LEVEL: Severe
PID : 10813612 TID : 39889 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
EDUID : 39889 EDUNAME: db2agent (idle)
FUNCTION: DB2 UDB, base sys utilities,
sqleIndCoordProcessRequest, probe:100
MESSAGE : Sqlcode =
DATA #1 : Hexdump, 4 bytes
0x0A000000293FE63C : FFFF 8A7F
....
:
:
2012-05-21-21.17.02.220984+540 I3051255A1175 LEVEL: Error
PID : 10813612 TID : 20100 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE_DB
APPHDL : 0-57897 APPID:
127.0.0.1.40894.120521121711
AUTHID : DB2INST1
EDUID : 20100 EDUNAME: db2agent (SAMPLE_DB)
FUNCTION: DB2 UDB, ABP, ABPIcoordAgent::spawnIcoordAgent,
probe:200
MESSAGE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific
control block."
CALLED : DB2 UDB, base sys utilities,
sqeIcoordCB::DispatchIndependentDBAgent
RETCODE : ZRC=0x80A90442=-2136406974=ABP_NO_AGENT
"Maximum number of connections reached."
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30081 sqlerrml:
37
sqlerrmc: 32 * 0 TCP/IP SOCKETS 127.0.0.1 send
sqlerrp : SQLESBCN
sqlerrd : (1) 0x81360012 (2) 0x00000012 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2012-05-21-21.17.02.221215+540 I3052431A1026 LEVEL: Error
PID : 10813612 TID : 20100 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE_DB
APPHDL : 0-57897 APPID:
127.0.0.1.40894.120521121711
AUTHID : DB2INST1
EDUID : 20100 EDUNAME: db2agent (SAMPLE_DB)
FUNCTION: DB2 UDB, ABP, abpSpawnDaemon, probe:100
CALLED : DB2 UDB, ABP, ABPServices::spawnDaemon
RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific
control block."
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30081 sqlerrml:
37
sqlerrmc: 32 * 0 TCP/IP SOCKETS 127.0.0.1 send
sqlerrp : SQLESBCN
sqlerrd : (1) 0x81360012 (2) 0x00000012 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
:
:
2012-05-21-21.17.02.222665+540 E3054019A960 LEVEL:
Critical
PID : 10813612 TID : 20100 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE_DB
APPHDL : 0-57897 APPID:
127.0.0.1.40894.120521121711
AUTHID : DB2INST1
EDUID : 20100 EDUNAME: db2agent (SAMPLE_DB)
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::MarkDBBad, pro
be:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"DBMarkedBad". The instance may have been shutdown as
a result.
"Automatic" FODC (First Occurrence Data Capture) has
been invoked and
diagnostic information has been recorded in directory
"/log/db2inst1/db2dump/FODC_DBMarkedBad_2012-05-21-21.17.02.2215
12_00
00/". Please look in this directory for detailed
evidence about what
happened and contact IBM support if necessary to
diagnose the
problem. |
