SAP Basis Tech Supports

Symptom

Problems with DB2 Connect 9.5 FP1:
1)
After upgrading DB Connect to IBM Data Server Driver for CLI, ODBC, JDBC, SQLJ V9.5 FP1 Special Build 20615 no database connect is possible on Windows platforms; e.g. R3trans -x fails without displaying any return code.
The error does occur only if DB2 Connect EE was never installed on this box.
2)
R3trans fails with error message:
‘The ordinal 1299 could not be located in the dynamic link library DB2APP64.dll.’
In trans.log the following error message can be found:
*** ERROR => DlLoadLib: LoadLibrary(C:\usr\sap\\SYS\global\db2
\WINDOWS_AMD64\db2_clidriver\bin\db2cli64.dll) Error 182
Could not load DB2 library C:\usr\sap\\SYS\global\db2\WINDOWS_AMD64
\db2_clidriver\bin\db2cli64.dll. No database connection possible.
3)
With SAP MDM the connect to DB2 fails with:
Error: ERROR CODE = 0,
–ERROR while allocating the DB2 environment handle.
Error: DB2 Init
Error: ERROR CODE = 0,

Other terms

Db2 Connect; thin client
Reason and Prerequisites

The CLI Driver V9.5 FP1 uses authorization groups on Windows which are normally created by the DB2 Connect EE installation automatically.

Solution

Apply DB2 Connect 9.5 FP3a Special Build 21887.
If you can’t apply the fixpack immediately the following workarounds are possible:
Symptom 1:
a) Set environment variable DB2_EXTSECURITY=NO as system variable
or
b) Create groups DB2ADMNS and DB2USERS and add both groups to user SAPService .
Service SAP_ must be restarted in both cases.
Symptom 2:
Uninstall DB2 Connect EE. In addition you have to apply the workaround of symptom 1 .
Symptom 3:
See symptom 2