SAS/ACCESS software fails to use table aliases correctly when you use in-line SELECT statements. As a result, you might receive error messages similar to the following:

   ERROR: ORACLE prepare error: ORA-00904: "CLASS"."SEX": invalid
          identifier. SQL statement:  select t1."NAME", t2."AGE"
          from CLASS t1, CLASS t2 where (t1."AGE" = t2."AGE") and
          (CLASS."SEX" = 'F') and (CLASS."SEX" = 'M').

   ERROR: CLI describe error: [IBM][CLI Driver][DB2/LINUX] SQL0206N
          "CLASS.SEX" is not valid in the context where it is used.
          SQLSTATE=42703

Consider the following simplified example. Note that the WHERE clauses (that were originally in the two SELECT statements) still use the table alias CLASS rather than the T1 and T2 defined aliases. This is not valid syntax in DB2, Oracle, or other databases.

This issue results in in-line views that are not persisted. The in-line views should persist for the proper scoping of the predicates. The predicate qualifiers would be correct if they were contained within the appropriate in-line view. As a result, this problem query is not passed down correctly through Implicit Pass-Through at any prior release.

If your query is critical to performance, you can work around the problem (in the short term) by using Explicit Pass-Through or predefined views in the database.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :