An incorrect data type might be specified when you create a DBMS table with the LIBNAME statement in the SAS/ACCESS Interface to OLE DB, using either the Informix OLE DB Provider or the Oracle 10g Provider.

To demonstrate this behavior, assign the OLEDB libref to Informix or Oracle and submit a SAS DATA step to create a DBMS table.

If you submit the following OPTIONS statement to turn on SAS tracing, you can see the underlying SQL statements that are generated by the DATA step code. The CREATE TABLE statement specifies the data type INTERVAL, which is incorrect, and the SAS processing halts with errors:

   libname oleinfx oledb preserve_tab_names=yes preserve_col_names=yes 
           autocommit=yes, provider=ifxoledbc prompt=no      
           datasource='people@online20' schema=dbitest user=dbitest  
           password="{sas001}ZGJpZ3JwMQ==" ;

   data oleinfx.OLEDBInfxJob11Outx;
      attrib surrogate_key length=8 
             label='Surrogate/Retained Key';
      attrib ssn length=$9
             label='Social Security';
      attrib first_name length=$15
             label='First Name';
      attrib last_name length=$15
             label='Last Name';
      attrib address length=$50
             label='Address';
      attrib phone length=$12
             label='Phone Number';
      attrib email length=$30
             label='Email Address';
      attrib current_indicator length=8
             label='Current Indicator';
      stop;
   run;

   Debug info for creating table in the log:
      OLEDB_36: Executed:
      CREATE TABLE "dbitest"."OLEDBInfxJob11Outx" ("surrogate_key"
      float,"ssn" interval day to
      fraction(4),"first_name" varchar(15),"last_name"
      varchar(15),"address"
      varchar(50),"phone" interval
      day to fraction(4),"email" varchar(30),"current_indicator" float)

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 :