DB2 - Problem description
Problem IC95532 | Status: Closed |
A 32-BIT CLI APPLICATION RUNNING WITH DB2 64-BIT ON AIX FAILS WITH ILLEGAL INSTRUCTION ERROR | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
A 32-bit CLI application running with DB2 64-bit on AIX fails with illegal instruction error when attempting to connect to the database. db2diag.log might contain below errors: 2013-02-21-22.47.51.957528-300 I14746C1399 LEVEL: Error PID : 17432734 TID : 1 PROC : t_97 INSTANCE: db2inst NODE : 000 HOSTNAME: hostname1 EDUID : 1 FUNCTION: DB2 Common, OSSe, OSSHLibrary::load, probe:80 MESSAGE : ECF=0x90000076=-1879048074=ECF_LIB_CANNOT_LOAD Cannot load the specified library DATA #1 : Hex integer, 4 bytes 0x00000009 DATA #2 : String, 39 bytes /opt/ibm/db2/v10/lib32/libdb2clixml4c.a CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0xD21FA5CC oss_log__FP9OSSLogFacUiT2UlT2N34lPPc + 0xEC [1] 0xD21FA498 ossLog + 0xB8 [2] 0xD21FD098 load__11OSSHLibraryFPCcUl + 0x2F8 [3] 0xD64ACE04 CLI_coLoadXml4cLib + 0x3A4 [4] 0xD648F138 loadXml__9rccConfigFP5sqlcaPc + 0x2D8 [5] 0xD6493758 getAltSrvrFromCache__10rccDBEntryFP7rccListP5sqlca + 0x1D8 [6] 0xD6491FC8 getEffectiveAlternateSrvList__10rccDBEntryFPcPbPP7rccListP5sqlca + 0x508 [7] 0xD5FA99CC sqleUCappConnect + 0x4A6C [8] 0xD6552FAC CLI_sqlConnect__FP15CLI_CONNECTINFOP5sqlcaP19CLI_ERRORHEADERINFO + 0xD8C [9] 0xD6704BD0 SQLConnect2__FP15CLI_CONNECTINFOPUcsT2T3T2T3T2T3Uc + 0x6F0 [10] 0xD66F55A8 SQLDriverConnect2__FP15CLI_CONNECTINFOPvPUcsT3T4PsUsUcT9P19CLI_E RRORHEADERINFO + 0x1AC8 [11] 0xD67097B0 SQLDriverConnect + 0x410 [12] 0x10000934 main + 0x274 [13] 0x10000190 __start + 0x68 2013-02-21-22.47.51.958368-300 I16146C1428 LEVEL: Error PID : 17432734 TID : 1 PROC : t_97 INSTANCE: db2inst NODE : 000 HOSTNAME: hostname1 EDUID : 1 FUNCTION: DB2 Common, OSSe, OSSHLibrary::load, probe:90 MESSAGE : ECF=0x90000076=-1879048074=ECF_LIB_CANNOT_LOAD Cannot load the specified library DATA #1 : String, 109 bytes Could not load module /opt/ibm/db2/v10/lib32/libdb2clixml4c.a(shr.o). System error: No such file or directory CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0xD21FA5CC oss_log__FP9OSSLogFacUiT2UlT2N34lPPc + 0xEC [1] 0xD21FA498 ossLog + 0xB8 [2] 0xD21FD0E0 load__11OSSHLibraryFPCcUl + 0x340 [3] 0xD64ACE04 CLI_coLoadXml4cLib + 0x3A4 [4] 0xD648F138 loadXml__9rccConfigFP5sqlcaPc + 0x2D8 [5] 0xD6493758 getAltSrvrFromCache__10rccDBEntryFP7rccListP5sqlca + 0x1D8 [6] 0xD6491FC8 getEffectiveAlternateSrvList__10rccDBEntryFPcPbPP7rccListP5sqlca + 0x508 [7] 0xD5FA99CC sqleUCappConnect + 0x4A6C [8] 0xD6552FAC CLI_sqlConnect__FP15CLI_CONNECTINFOP5sqlcaP19CLI_ERRORHEADERINFO + 0xD8C [9] 0xD6704BD0 SQLConnect2__FP15CLI_CONNECTINFOPUcsT2T3T2T3T2T3Uc + 0x6F0 [10] 0xD66F55A8 SQLDriverConnect2__FP15CLI_CONNECTINFOPvPUcsT3T4PsUsUcT9P19CLI_E RRORHEADERINFO + 0x1AC8 [11] 0xD67097B0 SQLDriverConnect + 0x410 [12] 0x10000934 main + 0x274 [13] 0x10000190 __start + 0x68 Note: This issue happens only with 32-bit CLI applications using DB2 64-bit on AIX | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * CLI application users on AIX * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix * * Pack 4) or higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.08.2013 16.10.2014 16.10.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |