Joining two Oracle tables, one with a column data type of NUMBER and another with a column data type of BINARY_DOUBLE, causes slow performance. Performance degrades due to the data type mismatch on the join column, which is adding in the additional data type conversion overhead.

The fix is to ensure that the join column data types match exactly.

For example, "COL1" data type is a BINARY_DOUBLE, and the "CLIENTID" column is a NUMBER(19,5). To improve performance, ensure that "CLIENTID" type is BINARY_DOUBLE or ensure that "COL1" is created with a data type NUMBER. This can be done by specifying the format with precision/scale values as 19,5 or by using DBTYPE=(DII_1034='NUMBER(19,5)') .

If you are creating an Oracle table from SAS^® and you do not want to have a numeric column as a BINARY_DOUBLE, use the LIBNAME option OR_BINARY_DOUBLE=NO.

Operating System and Release Information