数据库Crash recovery过程中，出现ADM1530E错误
由于数据库断电，大批量的insert操作未提交，数据库目前的状态是能正常db2start,db2start后，观察其日志，是没有做回滚操作的，只有当我connect的时候，开始做回滚操作，但大约几分钟后，回滚操作就失败了，报了一个ADM1530E错误，数据库也down了。数据库版本信息：DB21085I This i...显示全部
由于数据库断电，大批量的insert操作未提交，
数据库目前的状态是能正常db2start,
db2start后，观察其日志，是没有做回滚操作的，
只有当我connect的时候，开始做回滚操作，但大约几分钟后，回滚操作就失败了，报了一个ADM1530E错误，数据库也down了。
数据库版本信息：
DB21085I This instance or install (instance name, where applicable:
"db2inst1") uses "64" bits and DB2 code release "SQL09079" with level
identifier "080A0107".
Informational tokens are "DB2 v9.7.0.9", "s131204", "IP23561", and Fix Pack
"9".
Product is installed at "/opt/ibm/db2/V9.7"
操作系统版本信息：
Red Hat Enterprise Linux Server release 6.3
具体日志信息如下：
2014-04-10-21.01.32.896393+480 I1937E305 LEVEL: Event
PID : 7709 TID : 140737157846816PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 :
Single node instance [0] is starting
2014-04-10-21.01.32.896751+480 I2243E1637 LEVEL: Event
PID : 7709 TID : 140737157846816PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/db2inst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFFFFFF39F0 : 2F68 6F6D 652F 6462 3269 6E73 7431 2F73 /home/db2inst1/s
0x00007FFFFFFF3A00 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFFFFFF3A10 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFFFFFF3A20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A30 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A40 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A50 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A60 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A70 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A80 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A90 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AA0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AC0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AD0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AE0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
2014-04-10-21.01.33.096177+480 E3881E347 LEVEL: Warning
PID : 7711 TID : 140737157846816PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloKADetermineNUMASupport, probe:50
DATA #1 :
Detected kernel config that is incompatible with DB2 NUMA support.
2014-04-10-21.01.33.251351+480 E4229E1430 LEVEL: Event
PID : 7715 TID : 140736892757760PROC : db2syscr
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1
START : DB2 DBM
DATA #1 : Build Level, 152 bytes
Instance "db2inst1" uses "64" bits and DB2 code release "SQL09079"
with level identifier "080A0107".
Informational tokens are "DB2 v9.7.0.9", "s131204", "IP23561", Fix Pack "9".
DATA #2 : System Info, 440 bytes
System: Linux localhost.localdomain 6 2 x86_64
CPU: total:10 online:10 Cores per socket:5 Threading degree per core:1
Physical Memory(MB): total:16081 free:15498
Virtual Memory(MB): total:24273 free:23690
Swap Memory(MB): total:8192 free:8192
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:32153
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:68719476736 shmMin:1 shmIDs:4096
shmSegments:4096 semMap:256000 semIDs:4096 semNum:256000
semUndo:256000 semNumPerID:250 semOps:32 semUndoSize:20
semMaxVal:32767 semAdjustOnExit:32767
Cur cpu time limit (seconds) = 0xFFFFFFFF
Cur file size limit (bytes) = 0xFFFFFFFF
Cur data size (bytes) = 0xFFFFFFFF
Cur stack size (bytes) = 0x00A00000
Cur core size (bytes) = 0x00000000
Cur memory size (bytes) = 0xFFFFFFFF
nofiles (descriptors) = 0x00001000
2014-04-10-21.01.33.418472+480 I5660E540 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfBufferManager::initBufferManager, probe:10
START : Starting FCM Buffer Manager
1 resource group(s).
1491 buffers allocated.
Maximum number of buffers supported is 524470.
Total buffer manager memory required for 1 logical and 0 fail-over partition(s) is 27893776 bytes.
2014-04-10-21.01.33.436432+480 I6201E546 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfChannelManager::initChannelManager, probe:10
START : Starting FCM Channel Manager
1 resource group(s).
895 channels allocated.
Maximum number of channels supported is 524470.
Total channel manager memory required for 1 logical and 0 fail-over partitions(s) is 11444248 bytes.
2014-04-10-21.01.33.447646+480 I6748E541 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfSessionManager::initSessionManager, probe:10
START : Starting FCM Session Manager
1 resource group(s).
298 sessions allocated.
Maximum number of sessions supported is 64440.
Total session manager memory required for 1 logical and 0 fail-over partitions is 7122944 bytes.
2014-04-10-21.01.33.454453+480 I7290E422 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500
START : FCM infrastructure started
FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IPv6
2014-04-10-21.01.33.463592+480 I7713E405 LEVEL: Info
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, Self tuning memory manager, stmmAttachToShmAtStartup, probe:1135
MESSAGE : Attached to STMM shared memory segment.
DATA #1 : Pointer, 8 bytes
0x00007ffff7ffb000
2014-04-10-21.01.34.608335+480 E8119E306 LEVEL: Event
PID : 7711 TID : 140737157846816PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
2014-04-10-21.02.43.672353+480 I8426E442 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30
MESSAGE : Crash Recovery is needed.
2014-04-10-21.02.52.114929+480 E8869E472 LEVEL: Event
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:1000
START : DATABASE: EASTDB : ACTIVATED: NO
2014-04-10-21.02.52.147204+480 I9342E505 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : Crash recovery started. LowtranLSN 00000282679D088A MinbuffLSN
000002825CC071ED
2014-04-10-21.02.52.162044+480 E9848E459 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : ADM1530E Crash recovery has been initiated.
2014-04-10-21.02.52.172855+480 I10308E531 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:1182
MESSAGE : numWOCB set to
DATA #1 : Hexdump, 8 bytes
0x00007FFFE9BF64E0 : 0010 0000 0000 0000 ........
2014-04-10-21.02.52.181454+480 I10840E502 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000
DATA #1 :
Using parallel recovery with 3 agents 28 QSets 84 queues and 188 chunks
2014-04-10-21.04.37.284229+480 E11343E550 LEVEL: Severe
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20
MESSAGE : ADM0503C An unexpected internal processing error has occurred. All
DB2 processes associated with this instance have been shutdown.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.
2014-04-10-21.04.38.588181+480 E11894E423 LEVEL: Error
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:21
DATA #1 : Process ID, 4 bytes
7717
DATA #2 : Hexdump, 8 bytes
0x00007FFFDC7FC3A0 : 0201 0000 0900 0000 ........
2014-04-10-21.04.38.644713+480 I12318E392 LEVEL: Severe
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
DATA #1 : Hexdump, 4 bytes
0x00007FFFDC7FBED0 : 0201 0000 ....
2014-04-10-21.04.38.659210+480 I12711E457 LEVEL: Warning
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x00007FFFDC7FBD50 : 0000 0000 ....
这个错误一直困扰我好几天，不知道论坛里有人知道如何解决吗？谢谢！收起
数据库目前的状态是能正常db2start,
db2start后，观察其日志，是没有做回滚操作的，
只有当我connect的时候，开始做回滚操作，但大约几分钟后，回滚操作就失败了，报了一个ADM1530E错误，数据库也down了。
数据库版本信息：
DB21085I This instance or install (instance name, where applicable:
"db2inst1") uses "64" bits and DB2 code release "SQL09079" with level
identifier "080A0107".
Informational tokens are "DB2 v9.7.0.9", "s131204", "IP23561", and Fix Pack
"9".
Product is installed at "/opt/ibm/db2/V9.7"
操作系统版本信息：
Red Hat Enterprise Linux Server release 6.3
具体日志信息如下：
2014-04-10-21.01.32.896393+480 I1937E305 LEVEL: Event
PID : 7709 TID : 140737157846816PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 :
Single node instance [0] is starting
2014-04-10-21.01.32.896751+480 I2243E1637 LEVEL: Event
PID : 7709 TID : 140737157846816PROC : db2start
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/db2inst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFFFFFF39F0 : 2F68 6F6D 652F 6462 3269 6E73 7431 2F73 /home/db2inst1/s
0x00007FFFFFFF3A00 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFFFFFF3A10 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFFFFFF3A20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A30 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A40 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A50 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A60 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A70 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A80 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3A90 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AA0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AC0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AD0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFFFFF3AE0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
2014-04-10-21.01.33.096177+480 E3881E347 LEVEL: Warning
PID : 7711 TID : 140737157846816PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloKADetermineNUMASupport, probe:50
DATA #1 :
Detected kernel config that is incompatible with DB2 NUMA support.
2014-04-10-21.01.33.251351+480 E4229E1430 LEVEL: Event
PID : 7715 TID : 140736892757760PROC : db2syscr
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1
START : DB2 DBM
DATA #1 : Build Level, 152 bytes
Instance "db2inst1" uses "64" bits and DB2 code release "SQL09079"
with level identifier "080A0107".
Informational tokens are "DB2 v9.7.0.9", "s131204", "IP23561", Fix Pack "9".
DATA #2 : System Info, 440 bytes
System: Linux localhost.localdomain 6 2 x86_64
CPU: total:10 online:10 Cores per socket:5 Threading degree per core:1
Physical Memory(MB): total:16081 free:15498
Virtual Memory(MB): total:24273 free:23690
Swap Memory(MB): total:8192 free:8192
Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:32153
msgNumberOfHeaders:65536 msgMaxQueueSize:65536
msgMaxSegmentSize:16 shmMax:68719476736 shmMin:1 shmIDs:4096
shmSegments:4096 semMap:256000 semIDs:4096 semNum:256000
semUndo:256000 semNumPerID:250 semOps:32 semUndoSize:20
semMaxVal:32767 semAdjustOnExit:32767
Cur cpu time limit (seconds) = 0xFFFFFFFF
Cur file size limit (bytes) = 0xFFFFFFFF
Cur data size (bytes) = 0xFFFFFFFF
Cur stack size (bytes) = 0x00A00000
Cur core size (bytes) = 0x00000000
Cur memory size (bytes) = 0xFFFFFFFF
nofiles (descriptors) = 0x00001000
2014-04-10-21.01.33.418472+480 I5660E540 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfBufferManager::initBufferManager, probe:10
START : Starting FCM Buffer Manager
1 resource group(s).
1491 buffers allocated.
Maximum number of buffers supported is 524470.
Total buffer manager memory required for 1 logical and 0 fail-over partition(s) is 27893776 bytes.
2014-04-10-21.01.33.436432+480 I6201E546 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfChannelManager::initChannelManager, probe:10
START : Starting FCM Channel Manager
1 resource group(s).
895 channels allocated.
Maximum number of channels supported is 524470.
Total channel manager memory required for 1 logical and 0 fail-over partitions(s) is 11444248 bytes.
2014-04-10-21.01.33.447646+480 I6748E541 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqkfSessionManager::initSessionManager, probe:10
START : Starting FCM Session Manager
1 resource group(s).
298 sessions allocated.
Maximum number of sessions supported is 64440.
Total session manager memory required for 1 logical and 0 fail-over partitions is 7122944 bytes.
2014-04-10-21.01.33.454453+480 I7290E422 LEVEL: Event
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500
START : FCM infrastructure started
FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IPv6
2014-04-10-21.01.33.463592+480 I7713E405 LEVEL: Info
PID : 7717 TID : 140736892757760PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, Self tuning memory manager, stmmAttachToShmAtStartup, probe:1135
MESSAGE : Attached to STMM shared memory segment.
DATA #1 : Pointer, 8 bytes
0x00007ffff7ffb000
2014-04-10-21.01.34.608335+480 E8119E306 LEVEL: Event
PID : 7711 TID : 140737157846816PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
2014-04-10-21.02.43.672353+480 I8426E442 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30
MESSAGE : Crash Recovery is needed.
2014-04-10-21.02.52.114929+480 E8869E472 LEVEL: Event
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:1000
START : DATABASE: EASTDB : ACTIVATED: NO
2014-04-10-21.02.52.147204+480 I9342E505 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : Crash recovery started. LowtranLSN 00000282679D088A MinbuffLSN
000002825CC071ED
2014-04-10-21.02.52.162044+480 E9848E459 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : ADM1530E Crash recovery has been initiated.
2014-04-10-21.02.52.172855+480 I10308E531 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:1182
MESSAGE : numWOCB set to
DATA #1 : Hexdump, 8 bytes
0x00007FFFE9BF64E0 : 0010 0000 0000 0000 ........
2014-04-10-21.02.52.181454+480 I10840E502 LEVEL: Warning
PID : 7717 TID : 140737115055872PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : EASTDB
APPHDL : 0-7 APPID: *LOCAL.db2inst1.140410130241
AUTHID : DB2INST1
EDUID : 20 EDUNAME: db2agent (EASTDB) 0
FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000
DATA #1 :
Using parallel recovery with 3 agents 28 QSets 84 queues and 188 chunks
2014-04-10-21.04.37.284229+480 E11343E550 LEVEL: Severe
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20
MESSAGE : ADM0503C An unexpected internal processing error has occurred. All
DB2 processes associated with this instance have been shutdown.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.
2014-04-10-21.04.38.588181+480 E11894E423 LEVEL: Error
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:21
DATA #1 : Process ID, 4 bytes
7717
DATA #2 : Hexdump, 8 bytes
0x00007FFFDC7FC3A0 : 0201 0000 0900 0000 ........
2014-04-10-21.04.38.644713+480 I12318E392 LEVEL: Severe
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
DATA #1 : Hexdump, 4 bytes
0x00007FFFDC7FBED0 : 0201 0000 ....
2014-04-10-21.04.38.659210+480 I12711E457 LEVEL: Warning
PID : 7715 TID : 140736892757760PROC : db2wdog 0
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x00007FFFDC7FBD50 : 0000 0000 ....
这个错误一直困扰我好几天，不知道论坛里有人知道如何解决吗？谢谢！收起