Upgrading to 64-bit database clients

This topic describes how to upgrade your database clients to 64-bit and includes:

Upgrading Oracle database clients 

1. Save the TNS entry for the MVMMdatabase configuration from your 32-bit Oracle client's tnsnames.ora file.
2. Uninstall the 32-bit Oracle client.
3. Install a new 64-bit Oracle client (the same version as your 32-bit Oracle client).
4. Copy the TNS entry you saved in Step 1 to the tnsnames.ora file in the newly installed 64-bit Oracle client.
5. Verify that you have connectivity to the MVMMOracle schema, by running run sqlplus with the MVMMOracle credentials, as in the following example:
   
   sqlplus <MVMM_Oracle_user>/<MVMM_Oracle_password>@<MVMM_TNS_entry>


Upgrading DB2 database clients

The 64-bit DB2 client may already be installed. This can be verified by running the db2level command.

The following sample output indicates that the install uses 64 bits and that the MVMMservices, after Fix Pack D is installed, can access the same DB2 database because the installed 64-bit DB2 client has both 32-bit and 64-bit DB2 executables and libraries in it, and the database configuration is shared.

DB21085I  This instance or install (instance name, where applicable: "DB2")

uses "64" bits and DB2 code release "SQL11012" with level identifier "0203010F".

Informational tokens are "DB2 v11.1.2020.1393", "s1706091900", "DYN1701310100WIN64", and Fix Pack "2".

Product is installed at "C:\PROGRA~1\IBM\SQLLIB" with DB2 Copy Name "DB2COPY1".

If the output after running the db2level command indicates "32" bits is in use, perform the following steps:

1. Save the DB2 TCPIP node and DB2 database alias client configurations by running the list node directory and list db directory commands from the DB2 command line processor, and then save the MVMMTCPIP node and database alias information.
2. Uninstall the 32-bit DB2 client.
3. Install a 64-bit DB2 client (the same version as your 32-bit DB2 client).
4. Recreate the MVMMMVMMnode and database alias configuration in the newly installed 64-bit DB2 client by running the catalog tcpip node...  and catalog db...  commands and using the saved information on the MVMMTCPIP node and database alias.
5. Verify database connectivity by running the connect to <MVMM_DB_alias> user <MVMM_DB_user> using <MVMM_DB_password> command from the DB2 command line processor.

Upgrading MS SQL database clients

1. Open the 64-bit ODBC Driver Manager either by running it directly, for example, c:\windows\system32\odbcad32.exe, or through the GUI, through the Control Panel > Administrative Tools > ODBC Data Sources (64-bit) option. In the Drivers tab of the ODBC Driver Manager dialog, verify if the right version of the 64-bit SNAC/ODBC driver for SQL Server is installed. If it's not installed, install it by using the relevant installable package from Microsoft (for more details, refer to the appropriate Microsoft manual).
2. Open the 32-bit ODBC Driver Manager either by running it directly, for example, c:\windows\syswow64\odbcad32.exe, or through the GIU, through the Control Panel > Administrative Tools > ODBC Data Sources (32-bit) option. Save the information about the MVMMODBC DSN (the data source name, the database server hostname, and the database name).
3. Assuming that the right version of the SNAC/ODBC driver for SQL Server is installed (see Step 1), open the 64-bit ODBC Driver Manager, select the correct SNAC/ODBC driver for SQL Server, and re-create the 64-bit version of the MVMMODBC DSN using the same name for the MVMMODBC DSN, the saved database server name, and the saved database name. Run through the onscreen dialogs to ensure that the new ODBC DSN can connect to the database successfully.