on 10-02-2008 3:51 PM
Hi all,
When i try to apply Basis patch 13, database abruptly shutsdown. I pasted the db2diag.log
2008-10-02-19.21.01.588067+330 I1664780E452 LEVEL: Severe
PID : 17895 TID : 47872453238400PROC : db2loggr (GLP) 0
INSTANCE: db2glp NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgasn, probe:160
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
DATA #1 : String, 41 bytes
Logging can not continue due to an error.
2008-10-02-19.21.04.743549+330 I1665233E301 LEVEL: Event
PID : 17900 TID : 47872453238400PROC : db2pclnr 0
INSTANCE: db2glp NODE : 000
FUNCTION: DB2 UDB, trace services, pdInvokeCalloutScript, probe:20
STOP : Completed invoking /db2/db2glp/sqllib/bin/db2cos
2008-10-02-19.21.04.744280+330 E1665535E514 LEVEL: Severe
PID : 17900 TID : 47872453238400PROC : db2pclnr 0
INSTANCE: db2glp 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.
2008-10-02-19.21.04.744353+330 E1666050E971 LEVEL: Severe
PID : 17900 TID : 47872453238400PROC : db2pclnr 0
INSTANCE: db2glp NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:20
DATA #1 : Signal Number Recieved, 4 bytes
6
DATA #2 : Siginfo, 128 bytes
0x00007FFF871BA6F0 : 0600 0000 0000 0000 FAFF FFFF FFFF FFFF ................
0x00007FFF871BA700 : EC45 0000 EA03 0000 0800 0000 0000 0000 .E..............
0x00007FFF871BA710 : 589F FF4B 0081 FFFF 7DDD 2F80 FFFF FFFF X..K....}./.....
0x00007FFF871BA720 : 0400 0000 0000 0000 72BE 1380 FFFF FFFF ........r.......
0x00007FFF871BA730 : 0000 0000 0000 0000 80DE 912C 8A2B 0000 ...........,.+..
0x00007FFF871BA740 : 0100 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFF871BA750 : 0000 0000 0000 0000 52EB 1380 FFFF FFFF ........R.......
0x00007FFF871BA760 : 2000 0000 0000 0000 15BC 1080 FFFF FFFF ...............
2008-10-02-19.21.04.755212+330 E1667022E990 LEVEL: Severe
PID : 17869 TID : 47872453238400PROC : db2gds 0
INSTANCE: db2glp NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler, probe:50
DATA #1 : <preformatted>
Detected the death of an EDU with process id 17900.
The signal number that terminated this process was 6.
Look for trap files (t17900.*) in the dump directory.
CALLSTCK:
[0] 0x00002B8A251DBB63 /db2/IBM/db2/V9.1/lib64/libdb2e.so.1 + 0x156AB63
[1] 0x00002B8A23B66C10 /lib64/libpthread.so.0 + 0xDC10
[2] 0x00002B8A29DCDA23 msgrcv + 0x13
[3] 0x00002B8A251DC95E /db2/IBM/db2/V9.1/lib64/libdb2e.so.1 + 0x156B95E
[4] 0x00002B8A251DC4BB sqloInitEDUServices + 0x2E3
[5] 0x00002B8A251D9734 /db2/IBM/db2/V9.1/lib64/libdb2e.so.1 + 0x1568734
[6] 0x00002B8A251D9A9C sqloRunInstance + 0x7C
[7] 0x00000000004063AE DB2main + 0x73E
[8] 0x0000000000405C67 main + 0x2F
[9] 0x00002B8A29D2A154 __libc_start_main + 0xF4
2008-10-02-19.21.04.766963+330 I1668013E338 LEVEL: Event
PID : 17869 TID : 47872453238400PROC : db2gds 0
INSTANCE: db2glp NODE : 000
FUNCTION: DB2 UDB, trace services, pdInvokeCalloutScript, probe:10
START : Invoking /db2/db2glp/sqllib/bin/db2cos from oper system services sqloEDUCodeTrapHandler
2008-10-02-19.21.05.347681+330 I1668352E301 LEVEL: Event
PID : 17901 TID : 47872453238400PROC : db2pclnr 0
INSTANCE: db2glp NODE : 000
FUNCTION: DB2 UDB, trace services, pdInvokeCalloutScript, probe:20
STOP : Completed invoking /db2/db2glp/sqllib/bin/db2cos
2008-10-02-19.21.05.348488+330 E1668654E514 LEVEL: Severe
PID : 17901 TID : 47872453238400PROC : db2pclnr 0
INSTANCE: db2glp 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.
......
......
...
2008-10-02-19.20.56.114401+330 I1410907E490 LEVEL: Severe
PID : 18076 TID : 47872453238400PROC : db2agent (GLP) 0
INSTANCE: db2glp NODE : 000 DB : GLP
APPHDL : 0-19 APPID: *LOCAL.db2glp.081002132525
AUTHID : SAPSEB
FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:10
MESSAGE : The log state was marked bad by another process, this message is not
an indication of an error with the logger process.
2008-10-02-19.20.56.114471+330 I1411398E495 LEVEL: Severe
PID : 18076 TID : 47872453238400PROC : db2agent (GLP) 0
INSTANCE: db2glp NODE : 000 DB : GLP
APPHDL : 0-19 APPID: *LOCAL.db2glp.081002132525
AUTHID : SAPSEB
FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:10
DATA #1 : <preformatted>
Error -2045771763 when reading LSN 00000017E709F500 from log file S0000007.LOG tellMe 0 dpsAcbFlags 0 setSkipOutputBuf 0
2008-10-02-19.20.56.114540+330 I1411894E484 LEVEL: Error
PID : 18076 TID : 47872453238400PROC : db2agent (GLP) 0
INSTANCE: db2glp NODE : 000 DB : GLP
APPHDL : 0-19 APPID: *LOCAL.db2glp.081002132525
AUTHID : SAPSEB
FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:10
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
Please show some light to proceed further.
Environment: SUSE Linux with DB2[v9.1.0.4] - ERP6.0
Regards,
AGP
Edited by: Aravind G Patil on Oct 2, 2008 4:52 PM
Hi Aravind,
Have you made any recent change to the active log directory and the active logs inside (/db2/<SID>/log_dir)? Looks like this crash is related to log file issue. In some customer cases, they use NFS for the log_dir and this can pose a problem as well.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.