5There are incompatibilities with Unicode support when the Merant Driver 5Manager accesses the DB2 ODBC driver on UNIX. These incompatibilities 5cause the Merant Driver Manager to use Unicode even if the application did not 5request Unicode use. This situation can lead to problems with 5components such as the Data Warehouse Center, Information Catalog Manager, and 5MQSI, which require the Merant Driver Manager to support non-IBM data 5sources. You can use an alternate DB2 ODBC driver library without 5Unicode support enabled until a permanent solution is available.
5An alternative DB2 ODBC driver library without Unicode support enabled is 5included with DB2 UDB Version 8.1 for AIX, HP-UX, and Solaris Operating 5Environment. To use this alternative library, you must create a copy of 5it, giving the copy the original DB2 ODBC driver library's name.
5To switch to the non-Unicode ODBC library on AIX, HP-UX, or the Solaris 5Operating Environment, see the following instructions. Because this is 5a manual process, you must carry it out every time you update your product, 5including after the application of successive FixPak or modification 5level.
5Procedure
5
5To create the necessary library on AIX: 5
5cp db2_36.o db2.o 5-r--r--r-- bin:bin for db2.o5
5To switch back to the original object, follow the same procedure using the 5backup file instead of the db2_36.o file.
5To create the necessary library in a Solaris Operating Environment: 5
5cp libdb2_36.so.1 libdb2.so.1 5-r-xr-xr-x bin:bin libdb2.so.1
5To switch back to the original object, follow the same procedure using the 5backup file instead of the libdb2_36.so.1 file.
5To create the necessary library on HP-UX: 5
5cp libdb2_36.sl libdb2.sl 5-r-xr-xr-x bin:bin for libdb2.sl
5To switch back to the original object, follow the same procedure using the 5backup file instead of the libdb2_36.sl file.
5Contact IBM Support if you require assistance with DB2 UDB and the Merant 5Driver Manager on other UNIX operating systems. 5