DIA0505I Execution of a component signal handling function has begun

[vijay.db]

Hi Group,

Running DB2 V8.2 Fxpack 9 in AIX 5.2, I get the following error
frequently and my instance is stopped...collected some info like: the
signal received is 11 which is SEGMENTATION VIOLATION ERROR...after
that I'm getting the entry as DIA0505I Execution of a component signal
handling function has begun, so my query is what does the DIA05051
actally mean..

My diag log entry is as follows:

2007-01-30-19.19.39.672649+000 E66265C610 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
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
Support for
further assistance.

2007-01-30-19.19.39.673125+000 E66876C711 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
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 ................

2007-01-30-19.19.39.673563+000 I67588C422 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler, probe:50
MESSAGE : DIA0505I Execution of a component signal handling function
has begun.

Kindly put all your suggestions...thanks in advance..

it's
vj_dba

[Knut Stolze]

vi******@gmail.com wrote:

Hi Group,

Running DB2 V8.2 Fxpack 9 in AIX 5.2, I get the following error
frequently and my instance is stopped...collected some info like: the
signal received is 11 which is SEGMENTATION VIOLATION ERROR...after
that I'm getting the entry as DIA0505I Execution of a component signal
handling function has begun, so my query is what does the DIA05051
actally mean..

My diag log entry is as follows:

2007-01-30-19.19.39.672649+000 E66265C610 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
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
Support for
further assistance.

2007-01-30-19.19.39.673125+000 E66876C711 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:
20
DATA #1 : Signal Number Recieved, 4 bytes
11

This tells you that you run into a SIGSEGV (segmentation violation,
segfault, ...). If you don't use some external routine that causes this (a
trap file in the DIAGPATH will show that), then it may be a problem in DB2
and you should contain IBM support to get this resolved. There is no other
way...

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[vijay.db]

On Feb 2, 2:20 am, Knut Stolze <[e-mail]:

[e-mail] wrote:

Hi Group,

Running DB2 V8.2 Fxpack 9 in AIX 5.2, I get the following error
frequently and my instance is stopped...collected some info like: the
signal received is 11 which is SEGMENTATION VIOLATION ERROR...after
that I'm getting the entry as DIA0505I Execution of a component signal
handling function has begun, so my query is what does the DIA05051
actally mean..

My diag log entry is as follows:

2007-01-30-19.19.39.672649+000 E66265C610 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
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
Support for
further assistance.

2007-01-30-19.19.39.673125+000 E66876C711 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:
20
DATA #1 : Signal Number Recieved, 4 bytes
11

This tells you that you run into a SIGSEGV (segmentation violation,
segfault, ...). If you don't use some external routine that causes this (a
trap file in the DIAGPATH will show that), then it may be a problem in DB2
and you should contain IBM support to get this resolved. There is no other
way...

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany- Hide quoted text -

- Show quoted text -

Hi Knut,

Thanks for your kind advice...I scrolled my diaglog file back and
forth but not able to find the corresponding trap file for the
process...is there any other method to find the trap file which
exactly shows why that process is killed?

Thanks
vj_dba

[Knut Stolze]

vi******@gmail.com wrote:

On Feb 2, 2:20 am, Knut Stolze <[e-mail]:

>[e-mail] wrote:

Hi Group,

Running DB2 V8.2 Fxpack 9 in AIX 5.2, I get the following error
frequently and my instance is stopped...collected some info like: the
signal received is 11 which is SEGMENTATION VIOLATION ERROR...after
that I'm getting the entry as DIA0505I Execution of a component signal
handling function has begun, so my query is what does the DIA05051
actally mean..

My diag log entry is as follows:

2007-01-30-19.19.39.672649+000 E66265C610 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
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
Support for
further assistance.

2007-01-30-19.19.39.673125+000 E66876C711 LEVEL: Severe
PID : 124534 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: db2inst1 NODE : 000 DB : MQSBK01P
APPHDL : 0-1648 APPID: *LOCAL.db2inst1.070130151548
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:
20
DATA #1 : Signal Number Recieved, 4 bytes
11

This tells you that you run into a SIGSEGV (segmentation violation,
segfault, ...). If you don't use some external routine that causes this
(a trap file in the DIAGPATH will show that), then it may be a problem in
DB2
and you should contain IBM support to get this resolved. There is no
other way...

Thanks for your kind advice...I scrolled my diaglog file back and
forth but not able to find the corresponding trap file for the
process...is there any other method to find the trap file which
exactly shows why that process is killed?

The trap file is - as the name says - a file and not an entry in the db2diag
log. Go to the directory specified in your DIAGPATH (DBM CFG parameter)
and look for a file with a name beginning with a 't'.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany