Hi,

My customer has no contract with IBM, he cannot open PMR. Could anybody help identify the bug number of this crash? Thanks a lot!

Environment: db2 V8.1.0 on AIX 5.2.
=======================================

2010-07-07-14.48.50.231359 Instance:db2inst1 Node:000
PID:1269950(db2agent (idle) 0) TID:1 Appid:C0A80104.M10C.11A981001612
oper system services sqloEDUCodeTrapHandler Probe:10 Database:PDB

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.

2010-07-07-14.48.50.337606 Instance:db2inst1 Node:000
PID:1269950(db2agent (idle) 0) TID:1 Appid:C0A80104.M10C.11A981001612
oper system services sqloEDUCodeTrapHandler Probe:20 Database:PDB

Signal number received
0000 0004 ....

PID:1269950 TID:1 Node:000 Title: siginfo_t...

0000 0004 0000 0000 0000 001e 0000 0000 ................
0000 0000 c05c a8d4 0000 0000 0000 0000 ....餐侃........
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 0000 0000 0000 0000 0000 0000 0000 ................

2010-07-07-14.48.50.452225 Instance:db2inst1 Node:000
PID:1269950(db2agent (idle) 0) TID:1 Appid:C0A80104.M10C.11A981001612
relation data serv sqlrr_signal_handler Probe:10 Database:PDB

DIA0505I Execution of a component signal handling function has begun.


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 Data:RDS AGENT CB

PID:1269950 TID:1 Node:000 Title: SQLCA
sqlcaid : SQLCA sqlcabc: 136 sqlcode: 0 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL08010
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:



Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 Data:RDS UCINTFC

PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID =
2003 5ba8 .[?

PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =


PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID->rdbcolidLen =
0000 ..

PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID->rdbname =
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 ..

PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgname =
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 ..

PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgcnstkn =
0000 0000 0000 0000 ........

PID:1269950 TID:1 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgsn =
0000 ..


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 Data:RDS NESTED APPL CB


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 Data:RDS SP REGISTERS CB


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 Data:RDS TRAN CB


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 Data:RDS NESTED TRAN CB

2010-07-07-14.48.51.062733 Instance:db2inst1 Node:000
PID:1269950(db2agent (idle) 0) TID:1 Appid:C0A80104.M10C.11A981001612
access plan manager sqlra_sqlW_raw_dump Probe:25 Database:PDB

Private workspace info dumped! Check /home/db2inst1/sqllib/db2dump/a1269950.000 for additional data.

2010-07-07-14.48.51.132354 Instance:db2inst1 Node:000
PID:1269950(db2agent (idle) 0) TID:1 Appid:C0A80104.M10C.11A981001612
access plan manager sqlra_sqlW_raw_dump Probe:25 Database:PDB

Shared workspace info dumped! Check /home/db2inst1/sqllib/db2dump/a1269950.000 for additional data.

2010-07-07-14.48.51.181305 Instance:db2inst1 Node:000
PID:1269950(db2agent (idle) 0) TID:1 Appid:C0A80104.M10C.11A981001612
relation data serv sqlrr_signal_handler Probe:20 Database:PDB

DIA0506I Execution of a component signal handling function is complete.


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 DataQLE_AGENT_PRIVATECB


Dump File:/home/db2inst1/sqllib/db2dump/12699501.000 DataQLE_AGENTCB

2010-07-07-14.49.23.023613 Instance:db2inst1 Node:000
PID:753812(db2gds 0) TID:1 Appid:none
oper system services sqloEDUSIGCHLDHandler Probe:20

PID of abnormally terminated child process:
0013 60be ..`.

2010-07-07-14.49.23.103562 Instance:db2inst1 Node:000
PID:753812(db2gds 0) TID:1 Appid:none
oper system services sqloEDUSIGCHLDHandler Probe:30

waitpid() status of abnormally terminated child process:
0004 0084 ....

2010-07-07-14.49.23.157394 Instance:db2inst1 Node:000
PID:753812(db2gds 0) TID:1 Appid:none
oper system services sqloEDUSIGCHLDHandler Probe:50

Signal that terminated the child process:
0000 0004 ....

2010-07-07-14.49.23.223165 Instance:db2inst1 Node:000
PID:753812(db2gds 0) TID:1 Appid:none
oper system services sqloEDUCodeTrapHandler Probe:10

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.

2010-07-07-14.49.23.359874 Instance:db2inst1 Node:000
PID:753812(db2gds 0) TID:1 Appid:none
oper system services sqloEDUCodeTrapHandler Probe:20

Signal number received
0000 0006 ....

PID:753812 TID:1 Node:000 Title: siginfo_t...

0000 0006 0000 0000 0000 0009 0000 0000 ................
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 0000 0000 0000 0000 0000 0000 0000 ................
0000 0000 0000 0000 0000 0000 0000 0000 ................

2010-07-07-14.49.23.733162 Instance:db2inst1 Node:000
PID:1052828(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:15

DiagData
416e 2045 4455 2063 7261 7368 6564 2e An EDU crashed.

2010-07-07-14.49.23.796118 Instance:db2inst1 Node:000
PID:1052828(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:16

DiagData
000b 8094 ....

2010-07-07-14.49.23.856029 Instance:db2inst1 Node:000
PID:1052828(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:17

DiagData
0000 0101 ....

2010-07-07-14.49.23.911730 Instance:db2inst1 Node:000
PID:1052828(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:18

DiagData
ffff ffff 

2010-07-07-14.49.23.971431 Instance:db2inst1 Node:000
PID:1052828(db2sysc 0) TID:1 Appid:none
base sys utilities sqleChildCrashHandler Probe:19

DiagData
ffff fc88 ?

2010-07-07-14.49.24.025334 Instance:db2inst1 Node:000
PID:1052828(db2sysc 0) TID:1 Appid:none
base sys utilities sqle_sys_ctlr Probe:10

DiagData
0000 0001 ....

2010-07-07-14.49.24.129228 Instance:db2inst1 Node:000
PID:1167476(db2wdog 0) TID:1 Appid:none
oper system services sqloRunInstance Probe:102

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.

2010-07-07-14.49.24.244524 Instance:db2inst1 Node:000
PID:1167476(db2wdog 0) TID:1 Appid:none
oper system services sqloRunInstance Probe:105

DiagData
0000 0102 0000 0009 ........

2010-07-07-14.49.24.298476 Instance:db2inst1 Node:000
PID:1167476(db2wdog 0) TID:1 Appid:none
base sys utilities sqleCleanupResources Probe:5

DiagData
0000 0102 ....

2010-07-07-14.49.25.752992 Instance:db2inst1 Node:000
PID:794794(db2ckpwd 0) TID:1 Appid:none
oper system services sqlorque Probe:9

Unexpected system error 0x24 has occurred.
This has been mapped to ZRC 0x83000024.

2010-07-07-14.49.25.753426 Instance:db2inst1 Node:000
PID:913564(db2ckpwd 0) TID:1 Appid:none
oper system services sqlorque Probe:9

Unexpected system error 0x24 has occurred.
This has been mapped to ZRC 0x83000024.



Jimmy

as v8 is not supported anymore - you could install latest fixpack and hope problem is corrected. with or without contract = no support for v8 anymore

This crash was due to signal #4 (SIGILL). A 32-bit instance on AIX can crash with this signal if the stack and data collide, see note #4 here:
IBM - Setting the user data limit for DB2 on AIX


This looks ok as per the trap file so ulimit(data) setting is not related to the crash. Stack traceback was not generated so there is no helpful info in the trap. A core file might contain some helpful info, but you need to go to IBM for that. In any case, follow Guy's advice and upgrade to the latest fixpak (you're still using GA which is ~8 yrs old!)

Hi all,

Thanks a lot for your replies.

I know the best way is to apply fix, but because the customer has WAS 5.0 which should be compatible with DB2, he has to test all including applications. It will be a tough job for customer to do.