Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / May 2006

Tip: Looking for answers? Try searching our database.

DB2 Instance Crash

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Michel Esber - 07 May 2006 01:25 GMT
Hello,

Linux RedHat 4.0 Update 2 + UDB 8 Fixpack 10.

Our instance crashed recently. I know I´d better open a PMR (I will do
it on Monday), but any suggestion as to what may be causing the error ?
Here is the diag:

2006-05-05-20.07.34.185685-180 E80748351G871      LEVEL: Severe
PID     : 5499                 TID  : 4143883968  PROC : db2gds
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler,
probe:50
DATA #1 : <preformatted>
Detected the death of an EDU with process id 5505
The signal number that terminated this process was 9
Look for trap files (t5505.*) in the dump directory
CALLSTCK:
 [0] 0x010999E8 /home/db2inst1/sqllib/lib/libdb2e.so.1 + 0x8FA9E8
 [1] 0x007987C0 /lib/tls/libpthread.so.0 + 0xB7C0
 [2] 0x0109AA0B /home/db2inst1/sqllib/lib/libdb2e.so.1 + 0x8FBA0B
 [3] 0x0109A0BC sqloInitEDUServices + 0x14C
 [4] 0x010962CE sqloRunInstance + 0x456
 [5] 0x0804CCE1 DB2main + 0x905
 [6] 0x08050E28 main + 0x1C
 [7] 0x0064AE23 __libc_start_main + 0xD3
 [8] 0x0804C111 db2gds + 0x4111
 [9] 0x00000000 (nil) + 0x0

2006-05-05-20.07.34.381169-180 E80749223G508      LEVEL: Severe
PID     : 5499                 TID  : 4143883968  PROC : db2gds
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
Support for
         further assistance.

2006-05-05-20.07.34.382716-180 E80749732G901      LEVEL: Severe
PID     : 5499                 TID  : 4143883968  PROC : db2gds
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:20
DATA #1 : Signal Number Recieved, 4 bytes
6
DATA #2 : Siginfo, 128 bytes
0xFEE384F0 : 0600 0000 0000 0000 FAFF FFFF 7B15 0000
............{...
0xFEE38500 : 0000 0000 0010 F7FF C016 AB06 0800 0000
................
0xFEE38510 : 0800 0000 8808 0000 B0FF AF95 7242 1502
............rB..
0xFEE38520 : EAFF FFFF C016 AB06 80A9 47E0 0000 0000
..........G.....
0xFEE38530 : B8FF AF95 9088 E3FE 0000 0000 0000 0000
................
0xFEE38540 : 0100 0000 B0FF AF95 4CBA 1202 0000 0100
........L.......
0xFEE38550 : 0000 0000 F2FF FFFF 0000 0000 F4BF 7500
..............u.
0xFEE38560 : 00F0 AF95 B6BA 1202 0000 0100 0000 0000
................

2006-05-05-20.07.34.349110-180 E80750634G503      LEVEL: Severe
PID     : 5494                 TID  : 4143883968  PROC : db2wdog
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:490
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.

2006-05-05-20.07.34.853035-180 I80751138G350      LEVEL: Severe
PID     : 5494                 TID  : 4143883968  PROC : db2wdog
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:500
MESSAGE : DiagData
DATA #1 : Hexdump, 8 bytes
0xFEE391BC : 0201 0000 0900 0000                        ........

2006-05-05-20.07.34.859199-180 I80751489G347      LEVEL: Severe
PID     : 5494                 TID  : 4143883968  PROC : db2wdog
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xFEE391A0 : 0201 0000                                  ....

2006-05-05-20.07.34.873572-180 I80751837G293      LEVEL: Severe
PID     : 5494                 TID  : 4143883968  PROC : db2wdog
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, base sys utilities,
sqeDomainSockePair::termSocketPair, probe:10
MESSAGE : Freeing active socket pair!

Thanks in Advance,
Serge Rielau - 07 May 2006 03:56 GMT
> Hello,
>
[quoted text clipped - 13 lines]
> The signal number that terminated this process was 9
> Look for trap files (t5505.*) in the dump directory
Signal 9?
Would kill -9 do the job?

Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Michel Esber - 08 May 2006 14:34 GMT
I have just checked my /var/log/messages and it doesn´t seem like the
kernel sent this signal to the process. So I guess someone did ...

Thanks Serge,

> > Hello,
> >
[quoted text clipped - 15 lines]
> Signal 9?
> Would kill -9 do the job?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.