With SAS/ACCESS^® Interface to Oracle, numeric variables might be incorrectly created as a NUMBER data type rather than a DOUBLE_BINARY data type when you access Oracle 12c or later and when one of the following is true:

• You specified the OR_BINARY_DOUBLE=YES option in the LIBNAME statement.
• You do not have the OR_BINARY_DOUBLE= option specified in the LIBNAME statement.

Workaround

To circumvent this issue, use the DBTYPE= data set option to set the variable defined with a DOUBLE_BINARY data type.

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

This hot fix addresses the issue where the OR_BINARY_DOUBLE=YES option is specified in the LIBNAME statement only. Otherwise, you would need to add the option to the LIBNAME statement or use the DBTYPE= workaround.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to Oracle 9.45 is available at:

A fix for this issue for SAS/ACCESS Interface to Oracle 9.44 is available at: