| C7I004 for 64-bit Enabled Solaris | 
| SAS/ACCESS Interface to Oracle 9.42 | 
| Issue(s) Addressed: | Introduced: | 
   | 62366 |    ALERT -  A data integrity issue occurs after you query an Oracle view with an Oracle 12.1.0.2 server or a later server version | 
   C7I001 | 
   | 62500 |    "ERROR: Invalid sequence of commands..." occurs when you try to create a SAS® data set from an Oracle table | 
   C7I001 | 
   | 62518 |    SAS® stops responding and "ERROR: Error fetching from cursor...Exception code=6..." occurs when you try to read a wide Oracle table | 
   C7I001 | 
   | 62882 |    The DBCONINIT= and DBCONTERM= LIBNAME options are ignored on database connections that are opened for threaded Reads | 
   C7I002 | 
   | 63183 |    The date value is missing when you bulk load an Oracle table using the Direct Path API  | 
   C7I002 | 
   | 63230 |    "ERROR: The file  has too long a member name..." occurs when you try to read an Oracle table name with more than 30 bytes | 
   C7I002 | 
   | 63997 |    "ERROR: ORA" occurs when you try to read data from Oracle using DBCONINIT="exec " and DBSLICEPARM=ALL | 
   C7I003 | 
   | 58830 |    Writing an Oracle table that contains more than 4,294,967,296 rows fails and returns the error "ORA-03148: OCI_ATTR_ROW_COUNT cannot return a row count exceeding UB4MAXVAL"  | 
   C7I004 | 
   | 63971 |    An SQL query returns no data rows when you use SAS/ACCESS® Interface to Oracle | 
   C7I004 | 
   | 65898 |    A misleading SASTRACE message appears in the log when you insert a row into an Oracle table using SAS/ACCESS® Interface to Oracle with DBIDIRECTEXEC | 
   C7I004 | 
| NOTE: If you install this hot fix, you must also install hot fix B6Q099 for Base SAS 9.4_M5. | 
 | 
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |