Release Notes > After You Upgrade > ODBC Connector Post-Upgrade Tasks
  

ODBC Connector Post-Upgrade Tasks

When the earlier versions of the Secure Agent upgrades to version 33.0 on Windows or Linux, you need to perform some manual steps. If you use third-party drivers with the generic ODBC connection, you need to perform upgrade tasks based on the Secure Agent version from which you upgrade both on Windows and Linux.

Upgrading from 32-Bit Secure Agent to 64-Bit Secure Agent Version 33.0 on Windows

When the 32-bit Secure Agent upgrades to 64-bit Secure Agent version 33.0 on Windows, you need to restore the DSN name in the upgraded version. You must avoid changing the DSN name in the ODBC connection. You also need to manually copy any third-party libraries available from the previous version.
    1. Uninstall the 32-bit ODBC driver.
    2. Remove the DSN entry for the 32-bit ODBC driver from the Secure Agent machine.
    3. Install the 64-bit ODBC driver on the Secure Agent machine.
    4. Create the required DSN with the same name as provided in the 32-bit driver from the previous version.
    5. If you had copied any third-party driver files in the <Secure Agent installation directory>/main directory in the previous version, the Secure Agent backs up the content after the upgrade. Perform the following tasks for third-party files:
    1. a. Copy the backed-up third-party files from the following directory: <Secure Agent installation directory>/main2 directory.
    2. b. Paste the third-party files in the following directory: <Secure Agent installation directory>/*

Upgrading from 64-Bit Secure Agent Version Earlier than 30.0 to 64-Bit Secure Agent Version 33.0 on Windows

When the 64-bit Secure Agent with versions earlier than 30.0 upgrades to 64-bit Secure Agent version 33.0 on Windows, you must manually copy any third-party libraries available from the previous version and re-create the registry entries for the ODBC driver.
    1. If there are third-party driver files in the <Secure Agent installtion directory>/main/drivers directory in the previous version, the Secure Agent backs up the content after the upgrade. Perform the following tasks for third-party files:
    1. a. Copy the backed-up third-party files from the following directory: <Secure Agent installation directory>/main2/drivers directory.
    2. b. Replace the files in the following directory: <Secure Agent installation directory>/drivers/*.
    2. Re-create the registry entries for the ODBC driver and ensure that you set the correct path for the driver.

Upgrading from 64-Bit Secure Agent Version Later than 30.0 to 64-Bit Secure Agent Version 33.0 on Windows

When the 64-bit Secure Agent versions later than 30.0 upgrades to 64-bit Secure Agent version 33.0 on Windows, you must manually copy any third-party libraries available from the previous version.
  1. 1. Copy the third-party libraries from the following directory: <Secure Agent installation directory>/drivers/odbc/datadirect/win64/*
  2. 2. Replace the files in the following directory: <Secure Agent installation directory>/drivers/odbc/datadirect/r27/win64/*

Upgrading from 32-Bit Secure Agent to 64-Bit Secure Agent Version 33.0 on Linux

When the 32-bit Secure Agent upgrades to 64-bit Secure Agent version 33.0, you need to restore the DSN name in the upgraded version. You must avoid changing the DSN name in the ODBC connection. You also need to manually copy any third-party libraries available from the previous version.
    1. Uninstall the 32-bit ODBC driver.
    2. Remove the DSN entry for the 32-bit ODBC driver on the Secure Agent machine.
    3. Install the 64-bit ODBC driver on the Secure Agent machine.
    4. Create the required DSN with the same name as provided in the 32-bit driver from the previous version.
    5. Ensure that you set the ODBCINI environment variable on the Linux machine to the location of the odbc.ini file that contains the DSN entry.
    6. If you had copied any third-party driver files in the <Secure Agent installation directory>/main directory in the previous version, the Secure Agent backs up the content after the upgrade. Perform the following tasks:
    1. a. Copy the backed-up third-party files from the following directory: <Secure Agent installation directory>/main2 directory.
    2. b. Paste the third-party files in the following directory: <Secure Agent installation directory>/*
    7. If you had configured custom properties in the [ODBC] section in the <Secure Agent installation directory>/odbcinst.ini file in the previous version, the Secure Agent backs up the content in the [ODBC - R26] section after the upgrade. As the Secure Agent reads only the [ODBC] section, perform the following tasks in the odbcinst.ini file:
    1. a. Copy the custom properties from the [ODBC-R26] section.
    2. b. Paste the content into the [ODBC] section.

Upgrading from 64-Bit Secure Agent Version Earlier than 30.0 to 64-Bit Secure Agent Version 33.0 on Linux

When the 64-bit Secure Agent with versions earlier than 30.0 upgrades to 64-bit Secure Agent version 33.0 on Linux, you must manually copy any third-party libraries available from the previous version and re-create the DSN entries for the ODBC driver.
    1. If there are any third-party driver files in the <Secure Agent installation directory>/main/drivers directory in the previous version, the Secure Agent backs up the content after the upgrade. Perform the following tasks:
    1. a. Copy the backed-up third-party files from the following directory: <Secure Agent installation directory>/main2/drivers.
    2. b. Paste the third-party files in the following directory: <Secure Agent installation directory>/drivers/*
    2. Re-create the DSN entries for the ODBC driver in the odbc.ini file.
    3. Ensure that you set the correct path for the ODBC drivers.
    4. Ensure that you set the ODBCINI environment variable on the Linux machine to the location of the odbc.ini file that contains the DSN entry.
    5. If you had configured custom properties in the [ODBC] section in the <Secure Agent installation directory>/odbcinst.ini file in the previous version, the Secure Agent backs up the content in the [ODBC - R26] section after the upgrade. As the Secure Agent reads only the [ODBC] section, perform the following tasks in the odbcinst.ini file:
    1. a. Copy the custom properties from the [ODBC-R26] section.
    2. b. Paste the content into the [ODBC] section.

Upgrading from 64-Bit Secure Agent Version Later than 30.0 to 64-Bit Secure Agent Version 33.0 on Linux

When the 64-bit Secure Agent versions later than 30.0 upgrades to 64-bit Secure Agent version 33.0 on Linux, you must manually copy any third-party libraries available from the previous version.
  1. 1. Copy the third-party libraries from the following directory: <Secure Agent installation directory>/drivers/odbc/datadirect/linux/*
  2. 2. Replace the files in the following directory: <Secure Agent installation directory>/drivers/odbc/datadirect/r27/linux/*
  3. 3. If you had configured custom properties in the [ODBC] section in the <Secure Agent installation directory>/odbcinst.ini file in the previous version, the Secure Agent backs up the content in the [ODBC - R26] section after the upgrade. As the Secure Agent reads only the [ODBC] section, perform the following tasks in the odbcinst.ini file:
    1. a. Copy the custom properties from the [ODBC-R26] section.
    2. b. Paste the content into the [ODBC] section.