Amazon Redshift Connector Post-Upgrade Tasks
You need to perform upgrade tasks if you want to use Amazon Redshift connections from versions earlier than 30.0 in version 33.0. If you upgraded an ODBC connection from a previous version that used the 32-bit Redshift ODBC driver, you need to set the appropriate DSN name in the 64-bit Redshift ODBC driver after the upgrade.
Amazon Redshift Connector
To make client-side encryption configured for versions earlier than 30.0 to work in version 33.0, perform the following steps after the Secure Agent upgrades:
- 1. Move the US_export_policy.jar and local_policy.jar files, and cacerts files from <Secure Agent installation directory>\jre2\lib\security to <Secure Agent installation directory>\jre\lib\security.
- 2. Restart the Secure Agent.
ODBC Driver for Redshift
When you use an ODBC connection that contains the 32-bit ODBC Redshift driver to connect to Redshift from the previous version, the connection fails after the upgrade.
To ensure that the ODBC connection does not fail, perform the following tasks:
- 1. Install the 64-bit Redshift ODBC driver on the Secure Agent machine.
- 2. Create or rename the DSN with the same name as the DSN of the 32-bit Redshift ODBC driver from the previous version.