Reading data from an external data source (ODBC, Oracle, Teradata, and so on) using a PROC SQL query with a HAVING clause might produce an incorrect result.

This issue can happen in the following rare situations:

• The query contains identical column aliases in a SELECT and an in-line SELECT clause.
• The query contains a HAVING clause with this column alias. 

A result set is created. However, if you have the SAS trace option enabled, the SAS log shows a message similar to the following:

This message is an example of the error message that you receive when running against an Oracle database.

Here is example code that triggers this issue (Notice column alias COL2):

To work around the problem, use distinct aliases for the column name, as shown here:

A hot fix is planned for this issue.

Operating System and Release Information