|
Problem IC62720
|
Status: Closed |
When issuing db2start, db2sysc may trap if a NULL handle is accessed |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When issuing db2start, db2sysc may trap if a NULL handle is
accessed. Call stack might look like below,
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002AADB3A48F07 ossDumpStackTraceEx + 0x01f7
(/opt/IBM/db2/lib/libdb2osse.so.1)
0x00002AADB3A449DA _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00b4
(/opt/IBM/db2/lib/libdb2osse.so.1)
0x00002AADB3A44AA1 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009
(/opt/IBM/db2/lib/libdb2osse.so.1)
0x00002AADAFEAA1E9 sqlo_trce + 0x0425
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAFEEC34A sqloEDUCodeTrapHandler + 0x0138
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAD682C10 address: 0x00002AADAD682C10 ; dladdress:
0x00002AADAD675000 ; offset in lib: 0x000000000000DC10 ;
(/lib64/libpthread.so.0)
0x00002AADB435A00D fgets + 0x002d
(/lib64/libc.so.6)
0x00002AADAFED2BF6 sqloPRegProfileRemoveOld + 0x02ea
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAFEEA444 address: 0x00002AADAFEEA444 ; dladdress:
0x00002AADAD78D000 ; offset in lib: 0x000000000275D444 ;
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAEC3BE30 address: 0x00002AADAEC3BE30 ; dladdress:
0x00002AADAD78D000 ; offset in lib: 0x00000000014AEE30 ;
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAEC3A4CF sqloRunInstance + 0x00cb
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00000000004079B2 DB2main + 0x0a3e
(db2sysc)
0x00002AADAEC3D20D _Z16sqloEDUMainEntryPcj + 0x000f
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAEC3E0FB sqloEDUEntry + 0x0827
(/opt/IBM/db2/lib/libdb2e.so.1)
0x00002AADAD67B143 address: 0x00002AADAD67B143 ; dladdress:
0x00002AADAD675000 ; offset in lib: 0x0000000000006143 ;
(/lib64/libpthread.so.0)
0x00002AADB43BC74D __clone + 0x006d
(/lib64/libc.so.6) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB v95 and v97 installed systems *
****************************************************************
* PROBLEM DESCRIPTION: *
* When issuing db2start, db2sysc may trap if a NULL handle is *
* *
* accessed. Call stack might look like below, *
* *
* -----FUNC-ADDR---- ------FUNCTION + OFFSET------ *
* 0x00002AADB3A48F07 ossDumpStackTraceEx + 0x01f7 *
* *
* (/opt/IBM/db2/lib/libdb2osse.so.1) *
* 0x00002AADB3A449DA _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + *
* *
* 0x00b4 *
* *
* (/opt/IBM/db2/lib/libdb2osse.so.1) *
* 0x00002AADB3A44AA1 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + *
* 0x0009 *
* *
* (/opt/IBM/db2/lib/libdb2osse.so.1) *
* 0x00002AADAFEAA1E9 sqlo_trce + 0x0425 *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAFEEC34A sqloEDUCodeTrapHandler + 0x0138 *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAD682C10 address: 0x00002AADAD682C10 ; dladdress: *
* *
* 0x00002AADAD675000 ; offset in lib: 0x000000000000DC10 ; *
* *
* (/lib64/libpthread.so.0) *
* 0x00002AADB435A00D fgets + 0x002d *
* (/lib64/libc.so.6) *
* 0x00002AADAFED2BF6 sqloPRegProfileRemoveOld + 0x02ea *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAFEEA444 address: 0x00002AADAFEEA444 ; dladdress: *
* *
* 0x00002AADAD78D000 ; offset in lib: 0x000000000275D444 ; *
* *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAEC3BE30 address: 0x00002AADAEC3BE30 ; dladdress: *
* *
* 0x00002AADAD78D000 ; offset in lib: 0x00000000014AEE30 ; *
* *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAEC3A4CF sqloRunInstance + 0x00cb *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00000000004079B2 DB2main + 0x0a3e *
* (db2sysc) *
* 0x00002AADAEC3D20D _Z16sqloEDUMainEntryPcj + 0x000f *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAEC3E0FB sqloEDUEntry + 0x0827 *
* *
* (/opt/IBM/db2/lib/libdb2e.so.1) *
* 0x00002AADAD67B143 address: 0x00002AADAD67B143 ; dladdress: *
* *
* 0x00002AADAD675000 ; offset in lib: 0x0000000000006143 ; *
* *
* (/lib64/libpthread.so.0) *
* 0x00002AADB43BC74D __clone + 0x006d *
* (/lib64/libc.so.6) *
****************************************************************
* RECOMMENDATION: *
* Upgrading to DB2 UDB v97fp1 fixes this problem. *
**************************************************************** |
| Local Fix: |
No local fix is available. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 UDB v95fp5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.08.2009
18.01.2010
18.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP5,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
