Release Notes

4.37 Merant Driver Manager and the DB2 UDB Version 7 ODBC Driver on UNIX

Incompatibilities have been encountered with Unicode support when the Merant Driver Manager accesses DB2's ODBC driver on UNIX. These incompatibilities result in Unicode being used by the Merant Driver Manager regardless of whether the application has requested its use. This can lead to problems with products such as the Data Warehouse Center, Information Catalog Manager, and MQSI, which require the Merant Driver Manager to support non-IBM data sources. You can use an alternate DB2 ODBC driver library without Unicode support enabled until a permanent solution is available. The affected versions of DB2 UDB include Version 7.1 with FixPak 2 or later, and Version 7.2 at any FixPak level.

An alternative DB2 ODBC driver library without Unicode support enabled was shipped with DB2 Versions 7.1 and 7.2 for AIX, HP-UX, and Solaris Operating Environment. To use this alternative library, you must create a copy of it, giving the copy the original DB2 ODBC driver library's name.

Note:

The alternative (_36) clibrary contains the Unicode functions required by the DB2 JDBC cdriver. Using this library will still allow JDBC applications, including WebSphere Application Server, to work successfully with DB2.

To switch to the non-Unicode ODBC library on AIX, HP-UX, or the Solaris Operating Environment, see the following instructions. Because this is a manual process, you must carry it out every time you update your product, including after the application of successive FixPaks.

AIX

To create the necessary library on AIX:

1. As the instance owner, shut down all database instances using db2stop force.
2. As the admin instance ID, shut down the administration server instance using db2admin stop force.
3. Back up the original db2.o under /usr/lpp/db2_<ver>_<rel>/lib.
4. As root, issue slibclean.
5. Copy db2_36.o to db2.o, ensuring that ownership and permissions remain consistent. Use the following commands:

   cp db2_36.o db2.o
   -r--r--r-- bin:bin for db2.o
   

To switch back to the original object, follow the same procedure using the backup file instead of db2_36.o.

Solaris Operating Environment

To create the necessary library:

1. As the instance owner, shut down all database instances using db2stop force.
2. As the admin instance ID, shut down the administration server instance using db2admin stop force.
3. Back up the original libdb2.so.1 under /opt/IBMdb2/V<ver>.<rel>/lib.
4. Copy libdb2_36.so.1 to libdb2.so.1, ensuring that ownership and permissions remain consistent. Use the following commands:

   cp libdb2_36.so.1 libdb2.so.1
   -r-xr-xr-x bin:bin libdb2.so.1
   

5. Issue db2iupdt <instance> for each database instance and dasiupt <das_instance>for the DAS instance.

To switch back to the original object, follow the same procedure using the backup file instead of libdb2_36.so.1.

HP-UX - Only available for FixPak 4 or later.

You must install FixPak 4 or later before attempting this workaround.

To create the necessary library on HP-UX:

1. Shut down all database instances using db2stop force.
2. Shut down the administration server instance using db2admin stop force.
3. Back up the original libdb2.sl under /opt/IBMdb2/V<ver>.<rel>/lib.
4. Copy libdb2_36.sl to libdb2.sl, ensuring that the ownership and permissions remain consistent. Use the following command to ensure the consistency:

   -r-xr-xr-x bin:bin for libdb2.sl
   

5. Issue db2iupdt <instance> for each database instance and dasiupdt <das_instance> for the DAS instance.

To switch back to the original object, follow the same procedure using the backup file instead of libdb2_36.sl.

Other UNIX Operating Systems

If you require assistance with DB2 and the Merant Driver Manager on other UNIX operating systems, please contact IBM Support.