Rogue SQL Created with No "where" Clause From Analysis Using Redshift as Datasource (Doc ID 2961955.1)

Last updated on JULY 24, 2023

Applies to:

Symptoms

 Experiencing an odd behavior while using Amazon Redshift as datasource, where along with the main SQL query, another SQL statement is being issued with no "where" clause. This rogue SQL is not generated and have no control over it.

When the rogue SQL is sent to the database with no "where" clause, it tries to return millions of rows and causes a significant delay in getting results back for the main query.

Changes

Amazon Redshift database using the ORACLE_HOME/bi/modules/oracle.bi.datadirect.odbc/8.0.2/lib/ARrsft28.so AWS Redshift driver. Database Features were set back to default but did not change behavior.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.