DB2 Version 9.7 for Linux, UNIX, and Windows

Upgrading 32-bit database applications to run on 64-bit instances

Upgrading 32-bit database applications from a DB2® Version 8 32-bit instance to a DB2 Version 9.7 64-bit instance requires that your 32-bit database applications are linked to the appropriate shared library path to run them successfully.

You do not need to modify your 32-bit database applications if you linked them to the $INSTHOME/sqllib/lib32 shared library path on Linux and UNIX or theDB2PATH\lib\Win32 shared library path on Windows, where INSTHOME is the instance home directory and DB2PATH is the location of the DB2 copy.

About this task

Restrictions

This procedure applies only to 32-bit database applications programmed in C/C++, COBOL, FORTRAN, and REXX.

Before you begin

Ensure that you have access to a DB2 UDB Version 8 32-bit instance that you upgraded to a DB2 Version 9.7 64-bit instance that includes 32-bit shared libraries.
Ensure that the development software is at a version level that is supported by DB2 database products.
Perform the previous steps in the upgrading database applications task.

Procedure

To upgrade 32-bit database applications to run on a DB2 Version 9.7 64-bit instance:

Ensure that the library path environment variables include the correct DB2 shared library path for 32-bit libraries as shown in Table 2, so that the correct library can be loaded at runtime.
Test your 32-bit applications in a DB2 Version 9.7 testing environment. If testing is successful, you do not need to perform any additional steps. However, consider performing step 4 or 5 if they apply to your applications, to improve their support by using the correct client and shared library path.
Perform any other steps in the following upgrade tasks that apply to your applications:
- Embedded SQL applications
- CLI applications
- Java™ applications that use the IBM® Data Server Driver for JDBC and SQLJ or that use the DB2 JDBC Type 2 driver
- ADO and .NET applications
Specify the correct library path by linking or rebuilding your 32-bit applications using the DB2 shared library paths for 32-bit libraries shown in Table 1.
Optional: If you no longer have the source code to rebuild your applications or the use environmental variables is not possible, you can run the db2chglibpath command to change the DB2 shared library path to $INSTHOME/sqllib/lib32 on your application binary file as long as it has an embedded runtime path. The embedded runtime path can be changed to a new path with the same length or less.
Test your 32-bit applications to ensure that they run as expected using DB2 Version 9.7.

What to do next

After upgrading your 32-bit database applications, perform the remaining steps in the upgrading database applications task.