Joining an information map table using the SAS Information Map LIBNAME Engine with another data source might return incorrect results. This problem can occur when you use PROC SQL in Base SAS^® or the Query Builder in SAS^® Enterprise Guide^®.

These factors might cause the code to create incorrect results:

• The SQL query pattern is used. (See below for examples.)
• The estimated size of the information map library table is greater in size than the estimated size of the joining table.
• The information map library table is joined using equijoin, or one or more columns from the information map library table are queried from a correlated subquery and the queried columns are used outside of the scope of the correlated subquery.
• The criteria for joining is a character column.

Examples of query patterns:

select * from A inner join B on A.C1 = B.C2
or
select * from A join B on A.C1 = B.C2
or
select * from A, B where A.C1 = B.C2
  where
  A or B is an information map table
  C1 and C2 are SAS character values

Examples of correlated subqueries:

 select * from A where
    ... (select * from B where A.C1 = B.C2)
  where
  B is an information map table
  C1 is a SAS character value

When these factors are part of the generated PROC SQL, the final result might contain an incorrect value.

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_M3 is available at:

A fix for this issue for Base SAS 9.3_M2 is available at: