My Oracle Support Banner

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:

Oracle Analytics Server - Version 2022 ( and later
Information in this document applies to any platform.


 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.


Amazon Redshift database using the ORACLE_HOME/bi/modules/ AWS Redshift driver. Database Features were set back to default but did not change behavior.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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