Question & Answer
Question
After I upgrade DataDirect ODBC drivers from a version earlier than version 7.0 to version 7.0 or later, what configuration steps need to be completed?
Answer
Complete the following steps:
Ensure that the driver names that are used in the DSNs in the .odbc.ini file are updated to use the latest driver names. Before version 7.0, the names of the branded DataDirect drivers include the suffixes 23, 24 or 25.
For example, in DataDirect v6.1, the DB2 Wire Protocol driver is named VMdb225.so. Starting with DataDirect driver version 7.0, the driver names were changed to include the suffix 00. For example, the DB2 Wire Protocol driver in DataDirect version 7.0 is named VMdb200.so, and so the user would have to change VMdb225.so to VMdb200.so in the .odbc.ini file.
For all versions of InfoSphere Information Server:
If you use the ODBC Connector stage or ODBC Enterprise stage in InfoSphere DataStage jobs or use the ODBC connector for any other components, complete these steps:
- On AIX computers, set the DD_USE_SHARED_SEM environment variable to 0 and export it in the dsenv file.
- After you update the dsenv file, restart the InfoSphere Information Server engine and ASBNode Agents.
- Ensure that your library path contains ../branded_odbc/lib.
- Ensure that your permissions are the same as in the original branded_odbc.
For individual InfoSphere Information Server versions, complete these steps:
InfoSphere Information Server, Version 8.1
ODBC Connector: Apply Fix Pack 2, and then install the patch for APAR JR42587
If you use the ODBC connector, add the CC_ODBC_USE_NEW_DRIVER_MANAGER environment variable and set it to 1. More details about this environment variable and the fix for JR42587 are in the Technote ODBC Connector jobs fail, hang, or create a core dump when using the DataDirect ODBC driver manager.
ODBC Enterprise Stage: Apply Fix Pack 2, and then install the patch for APAR JR47635
JR47635 includes a fix to address a known issue with the ODBC Enterprise stage while using it with the latest DataDirect drivers.
On HP-PA-RISC operating systems, complete these steps:
(1) In the dsenv file, set the LD_PRELOAD environment variable by adding the following line, and then restart the InfoSphere Information Server engine:
LD_PRELOAD=/usr/lib/libCsup.sl /usr/lib/libstream.sl /usr/lib/libstd.sl; export LD_PRELOAD
(2) In the ${ISHOME}/ASBNode/bin/NodeAgents.sh file, comment out the following line, and then restart the node agents:
unset LD_PRELOAD
InfoSphere Information Server, Version 8.5
ODBC connector: Apply Fix Pack 3.
Fix Pack 3 includes fixes for JR42587.
If you use the ODBC connector, add the CC_ODBC_USE_NEW_DRIVER_MANAGER environment variable and set it to 1. More details about this environment variable and the fix for JR42587 are in the Technote ODBC Connector jobs fail, hang, or create a core dump when using the DataDirect ODBC driver manager.
ODBC Enterprise Stage: Apply Fix Pack 2 or Fix Pack 3.
JR39854 is included in both Fix Pack 2 and Fix Pack 3.
JR39854 includes a fix to address a known issue with the ODBC Enterprise stage while using it with the latest DataDirect drivers.
InfoSphere Information Server, Version 8.7
ODBC connector: Apply Fix Pack 2.
Fix Pack 2 includes fixes for JR42587.
If you use the ODBC connector, add the CC_ODBC_USE_NEW_DRIVER_MANAGER environment variable and set it to 1. More details about this variable and the fix for JR42587 are in the Technote ODBC Connector jobs fail, hang, or create a core dump when using the DataDirect ODBC driver manager
InfoSphere Information Server, Version 9.1 and above
No additional fixes or environment variables are needed for IS 9.1 and later (Except for the environment variable DD_USE_SHARED_SEM=0 on AIX Platform).
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21679867