5
5
5Merant Driver Manager incompatibility (UNIX)
5There are incompatibilities with Unicode support when the Merant Driver
5Manager accesses the DB2 ODBC driver on UNIX. These incompatibilities cause the
5Merant Driver Manager to use Unicode even if the application did not request
5Unicode use. This situation can lead to problems with components such as the
5Data Warehouse Center, Information Catalog Manager, and MQSI, which require
5the Merant Driver Manager to support non-IBM data sources. You can use an
5alternate DB2 ODBC driver library without Unicode support enabled until a permanent
5solution is available.
5An alternative DB2 ODBC driver library without Unicode support enabled
5is included with DB2 Universal Database (UDB) Version 8.1 for AIX,
5HP-UX, and Solaris Operating Environment. To use this alternative library,
5you must create a copy of it, giving the copy the original DB2 ODBC driver
5library's name.
5
5Note:
5The alternative (_36) library contains the
5Unicode functions required by the DB2 JDBC driver. Using this library allows
5JDBC applications, including WebSphere(R) Application Server, to work successfully
5with DB2 UDB.
5To switch to the non-Unicode ODBC library on AIX, HP-UX, or the Solaris Operating Environment,
5see the following instructions. Because this is a manual process, you must
5carry it out every time you update your product, including after the application
5of successive FixPaks or modification levels.
5
5Procedure
5
5
5- AIX
5-
5
To create the alternate library on AIX:
5
5- As the instance owner, shut down all database instances using the db2stop force command.
5- Using the DB2 administration server (DAS) instance ID, shut down the DAS instance
5using the db2admin stop force command.
5- Back up the original db2.o file in the /usr/lpp/db2_81/lib directory.
5- Using root authority, issue the slibclean command.
5- Copy file db2_36.o to backup file db2.o, ensuring that ownership and permissions
5remain consistent. Use the following commands:
5
cp db2_36.o db2.o
5-r--r--r-- bin:bin for db2.o
5To switch back to the original object, follow the same procedure
5using the backup file instead of the db2_36.o file.
5
5- Solaris Operating Environment
5-
5
To create the alternate library in a Solaris Operating Environment:
5
5- As the instance owner, shut down all database instances using the db2stop force command.
5- Using the DB2 administration server (DAS) instance ID, shut down the DAS instance
5using the db2admin stop force command.
5- Back up the original libdb2.so.1 file in
5the /opt/IBMdb2/V8.1/lib directory.
5- Copy file libdb2_36.so.1 to backup file libdb2.so.1, ensuring that ownership and permissions
5remain consistent. Use the following commands:
5
cp libdb2_36.so.1 libdb2.so.1
5-r-xr-xr-x bin:bin libdb2.so.1
5- Issue the db2iupdt <instance> command for
5each database instance and the dasupdt <das_instance> command for the DAS instance.
5To switch back to the original object, follow the same procedure
5using the backup file instead of the libdb2_36.so.1 file.
5
5- HP-UX PA-RISC
5-
5
To create the alternate library on HP-UX PA-RISC:
5
5- Shut down all database instances using the db2stop
5force command.
5- Shut down the DB2 administration server (DAS) instance using the db2admin stop force command.
5- Back up the original libdb2.sl file in the /opt/IBMdb2/V8.1/lib directory.
5- Copy file libdb2_36.sl to backup file libdb2.sl, ensuring that the ownership and permissions
5remain consistent. Use the following command to ensure the consistency:
5
cp libdb2_36.sl libdb2.sl
5-r-xr-xr-x bin:bin for libdb2.sl
5- Issue the db2iupdt <instance> command for
5each database instance and the dasupdt <das_instance> command for the DAS instance.
5To switch back to the original object, follow the same procedure
5using the backup file instead of the libdb2_36.sl file.
5
5- HP-UX on IA64
5-
5
To create the alternate library on HP-UX on IA64:
5
5- Shut down all database instances using the db2stop
5force command.
5- Shut down the DB2 administration server (DAS) instance using the db2admin stop force command.
5- Back up the original libdb2.so file in the /opt/IBMdb2/V8.1/lib directory.
5- Copy file libdb2_36.so to backup file libdb2.so, ensuring that the ownership and permissions
5remain consistent. Use the following command to ensure the consistency:
5
cp libdb2_36.so libdb2.so
5-r-xr-xr-x bin:bin for libdb2.so
5- Issue the db2iupdt <instance> command for
5each database instance and the dasupdt <das_instance> command for the DAS instance.
5To switch back to the original object, follow the same procedure
5using the backup file instead of the libdb2_36.so file.
5
5- Other UNIX Operating Systems
5-
5
Contact IBM Support if you require assistance with DB2 UDB and the
5Merant Driver Manager on other UNIX operating systems.
5
5
[ Top of Page |Previous Page | Next Page | Contents ]