SUMMARY
Users may encounter an issue where they are unable to successfully connect to Amazon Redshift after creating the appropriate database instance in Strategy 9.4.x or newer. To make sure that the environment is properly configured to connect to Amazon Redshift, please do the following:
- The DSN is created properly by using the "Strategy ODBC Driver for PostgreSQL Wire Protocol" from the Connectivity Wizard.
- The user should be able to connect to the database using the DSN created in the Intelligence Server and list the tables by using the command-line ODBC Test Tool.
- The database instance is created properly with "Amazon Redshift" selected as the connection type (after importing the Amazon Redshift PDS file per KB:41797 ) and the appropriate DSN, login, and other connection information is specified in the database instance.
SYMPTOM
Even with the environment configured properly (as described in the Summary), users are still unable to connect to Amazon Redshift from Strategy Developer. Specifically, when launching the Warehouse Catalog for the Amazon Redshift database instance, the user will encounter a warning message.
no available tables were found in the warehouse catalog
CAUSEThis was an issue with ODBC 3.x calls being used when retrieving the tables from the warehouse. Although ODBC 3.x is the default for database instances and is supported for use, it has lead to an issue in retrieving tables in this instance.
ACTIONPlease modify the advanced settings of the database instance to use 2.0 ODBC Calls instead of the default 3.x ODBC calls. This setting can be found by editing the database instance>Advanced tab>"ODBC Version".
