SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

708 Introduction to SAS/ACCESS Interface to Oracle 4 Chapter 25Binary Data 735Oracle Null and Default Values 735LIBNAME Statement Data Conversions 735ACCESS Procedure Data Conversions 737DBLOAD Procedure Data Conversions 738Introduction to SAS/ACCESS Interface to OracleThis section describes SAS/ACCESS Interface to Oracle. For a list of SAS/ACCESSfeatures that are available in this interface, see “SAS/ACCESS Interface to Oracle:Supported Features” on page 82.LIBNAME Statement Specifics for OracleOverviewThis section describes the LIBNAME statement that SAS/ACCESS Interface toOracle supports and includes examples. For details about this feature, see “Overview ofthe LIBNAME Statement for Relational Databases” on page 87.Here is the LIBNAME statement syntax for accessing Oracle.LIBNAME libref oracle ;Argumentslibrefspecifies any SAS name that serves as an alias to associate SAS with a database,schema, server, or group of tables and views.oraclespecifies the SAS/ACCESS engine name for the Oracle interface.connection-optionsprovide connection information and control how SAS manages the timing andconcurrence of the connection to the DBMS. Here is how these options are defined.USER=Oracle-user-namespecifies an optional Oracle user name. If the user name contains blanks ornational characters, enclose it in quotation marks. If you omit an Oracle username and password, the default Oracle user ID OPS$sysid is used, if it isenabled. USER= must be used with PASSWORD=.PASSWORD=Oracle-passwordspecifies an optional Oracle password that is associated with the Oracle username. If you omit PASSWORD=, the password for the default Oracle user IDOPS$sysid is used, if it is enabled. PASSWORD= must be used with USER=.PATH=Oracle-database-specificationspecifies the Oracle driver, node, and database. Aliases are required if youare using SQL*Net Version 2.0 or later. In some operating environments, you