When you use SAS^® 9.4M6 (TS1M6) with Hot Fix D9T069 and run an SQL procedure query, you might see an error related to an ambiguous column reference or duplicate column name. The problem might occur under the following scenario:

• You create VIEW1 that references a database management system (DBMS) table in which the columns in the SELECT statement are renamed. Here is an example: create view1 as select var1 as var1_1, var2 as var2_1 from dblib.table1
   
• You create VIEW2 that references a different DBMS table in which the table contains one of the variables in VIEW1 but it is not being renamed. Here is an example: create view2 as select var1, var4 from dblib.table2
   
• You create VIEW3 that references a third DBMS table in which a variable that matched with one of the variables in VIEW1 is renamed to the same name. Here is an example: create view3 as select var1 as var1_1, var5, var6 from dblib.table3
   
• You create VIEW4 that joins VIEW2 and VIEW1 on the variable in common that was renamed in VIEW1 but not renamed in VIEW2 and then select the other variable in VIEW1 and rename it to the same name and include that variable in the ORDER BY clause. Here is an example: create view4 as select t2.var2_1 as var2_1 from view2 t1 inner join view1 t2 on t1.var1=t2.var2_1 order by t2.var2_1
   
• You create VIEW5 that joins VIEW3 and VIEW1 on the variable that is in common that was renamed in both views. Here is an example: create view5 as select t2.var2_1 from view3 t1 inner join view1 t2 on t1.var1_1=t2.var1_1
   
• You create a table in which you perform a full join of VIEW5 and VIEW4 on the renamed variable and create a new variable using a CASE expression in which the variable from both tables is used and give it the same name. Here is an example: create table results as select case when t1.var2_1 is missing then t2.var2_1 else t1.var2_1 end as var2_1 from view5 t1 full join view4 t2 on t1.var2_1 =t2.var2_1

Here are some of the errors that have been encountered due to this issue:

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

Operating System and Release Information

A fix for this issue for Base SAS 9.4_M6 is available at:

A fix for this issue for Base SAS 9.4_M5 is available at: