Hi all,

I am getting the following error in the db2diag.log

PID : 282632 TID : 1 PROC : db2agntp 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:10
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(R) Support for further
assistance.

what may be the cause of the error.......and the solution.....


Any help.....


Thanks and Regards

Meena.s

We need more information. What is your DB2 version and OS? Are there any other messages in db2diag.log around the same time of this message? In my experience, there are other messages that indicate the problem. This one is just stating that due to some error DB2 is shutting down.

Andy

We are using DB2 V 8.1 and fixpak 9 and OS AIX-5.2. In db2diag.log along with the above error mentioned, the following messages occurs..

PID : 301294 TID : 1 PROC : db2agent (idle) 0
INSTANCE: db2inst1 NODE : 000 DB:***
APPHDL : 0-776 APPID: *LOCAL.db2inst1.070130191124
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:20
DATA #1 : Signal Number Recieved, 4 bytes
11
DATA #2 : Siginfo, 64 bytes
0x2FF1B6A0 : 0000 000B 0000 0000 0000 0032 0000 0000 ...........2....
0x2FF1B6B0 : 0000 0000 B000 000F 0000 0000 0000 0000 ................
0x2FF1B6C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF1B6D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

PID : 301294 TID : 1 PROC : db2agent (idle) 0
INSTANCE: db2inst1 NODE : 000 DB : ***
APPHDL : 0-776 APPID: *LOCAL.db2inst1.070130191124
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler, probe:50
MESSAGE : DIA0505I Execution of a component signal handling function has begun.

Any help.

Thanks
Meena.s

The solution is given in the message: Contact IBM(R) Support for further
assistance.

Such messages could appear if you killed DB2 processes manually. You may have additional messages before the one you cited that may give a better indication on what went wrong.

In your case, you got a SIGSEGV. You should have a trap file (named txxxx.yyy) which shows a stack trace indicating where the trap occured. If it relates to a UDF or SP, you can possibly change that routine to run as FENCED. If it is no routine, contact IBM support.