IBM Support

ITDSv6.2 is not supported with DB2v9.7 FP5 and later

Troubleshooting


Problem

A recent change added in DB2v9.7 FP 5 will lead to a gskit collision with ITDSv6.2.

Symptom

The ibmslapd process fails to start with the following messages in:

ibmslapd.log:
03/26/12 17:44:05 GLPSRV200I Initializing primary database and its connections.
03/26/12 17:44:07 GLPRDB001E Error code -1 from function:" SQLConnect " ldapdb2b .
03/26/12 17:44:07 GLPSRV064E Failed to initialize be_config.

db2cli.log:
2012-03-26-17:44:07.native retcode = -1042; state = "HY000"; message = "[IBM][CLI Driver] SQL1042C An unexpected system error occurred. SQLSTATE=58004"

db2diag.log
2012-03-26-17.44.06.996363-300 I267903A1651 LEVEL: Event
PID : 4282 TID : 1 PROC : db2start
INSTANCE: ldapdb2 NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 40 bytes
/export/home/ldapdb2/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0xFFFFFFFF7FFF2140 : 2F65 7870 6F72 742F 686F 6D65 2F69 6473 /export/home/ldap
0xFFFFFFFF7FFF2150 : 6C64 6170 2F73 716C 6C69 622F 6164 6D2F db2/sqllib/adm/
0xFFFFFFFF7FFF2160 : 6462 3273 7461 7232 004E 4F4D 5347 0000 db2star2.NOMSG..
0xFFFFFFFF7FFF2170 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF2180 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF2190 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF21A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF21B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF21C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF21D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF21E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF21F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF2200 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF2210 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF2220 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xFFFFFFFF7FFF2230 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2012-03-26-17.44.07.618298-300 E269555A328 LEVEL: Error (OS)
PID : 4284 TID : 1 PROC : db2star2
INSTANCE: ldapdb2 NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget
OSERR : EEXIST (17) "File exists"

2012-03-26-17.44.07.716827-300 I269884A1363 LEVEL: Error
PID : 4277 TID : 1 PROC : ibmslapd
INSTANCE: ldapdb2 NODE : 000
EDUID : 1
FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:40
MESSAGE : ECF=0x90000403=-1879047165=ECF_CRYPT_UNEXPECTED_ERROR
Unexpected cryptographic error
DATA #1 : Hex integer, 4 bytes
0x00000004
DATA #2 : Hex integer, 4 bytes
0x00000000
DATA #3 : Hex integer, 4 bytes
0x00000000
DATA #4 : String, 123 bytes
ld.so.1: ibmslapd: fatal: /opt/IBM/ldap/V6.2/lib64/icc/N/icc/icclib/libicclib081.so: open failed: No such file or directory
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0xFFFFFFFF75DCDFFC ossLogSysRC + 0x508
[1] 0xFFFFFFFF75DCD3C0 ossLog + 0x58
[2] 0xFFFFFFFF77B273C0 cryptContextRealInit + 0x610
[3] 0xFFFFFFFF77B2899C cryptContextCheckAndInit + 0x8C
[4] 0xFFFFFFFF77B28BAC cryptDHInit + 0x14C
[5] 0xFFFFFFFF783943DC __1cbHsqlexSlcServerEncryptAuthenticate6FpnOdb2UCinterface_lpI_i_ + 0xDC
[6] 0xFFFFFFFF7834C440 __1cUsqlexAppAuthenticate6FpnOdb2UCinterface__i_ + 0xC10
[7] 0xFFFFFFFF7851789C __1cSsqljrDrdaArConnect6FpnOdb2UCinterface__i_ + 0xBC
[8] 0xFFFFFFFF78331CD4 __1cQsqleUCdrdaARinit6FpnOdb2UCconHandle__i_ + 0x144
[9] 0xFFFFFFFF78321404 sqleUCappConnect + 0xDCC

Cause

This behavior is the result of a collision between the ICC libraries used by ITDSv6.2 (GSKitv7) and DB2v9.7 FP5 (GSKitv8).

Details of the Crypto library change in DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows: http://www.ibm.com/support/docview.wss?uid=swg21590697

Resolving The Problem

There are two options available if you are currently running ITDSv6.2 and DB2v9.7 in your environment:

Option 1. Do not upgrade past DB2v9.7 FP4. DB2v9.7 FP4 will continue to work ITDSv6.2 since this FP level is prior to the ICC change introduced in DB2 9.7 FP 5.

Option 2. Upgrade to ITDSv6.3. ITDSv6.3 uses GSKitv8 so the collision will not occur with this combination.

[{"Product":{"code":"SSVJJU","label":"IBM Security Directory Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.2","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21591733

Page Feedback