Usage Note 18748: ORACLE FNA support
SAS will support the use of the FNA (File Name Augmentation) facility
utilized by the SQL*Loader prior to opening its files in circumstances
where these files have not been allocated externally (via ALLOC or DD
statement).
The Oracle Bulk Loader (SQL*Loader) reads CTL and DAT files as input to
its function of loading Oracle tables. In the process, it creates a LOG
file and possibly, DISCARD and BAD files. The SAS interface allocates
and creates the CTL and DAT files before invoking the SQL*Loader, and
later opens the LOG file to echo its contents to the SAS log. The
DISCARD and BAD files are not processed, other than to pass any
specified user options across to the SQL*Loader.
The FNA facility is invoked by SQL*Loader prior to opening its files in
order to allow an installation to manage its dataset naming and
attribute functions. The installation specifies to FNA an FTYPE (CTL,
DAT, LOG, DSC or BAD), an FNAME, which may allow for dataset name
expansion and substitution of variable symbols, and an FATTR keyword
which allows dataset atributes to be specified for the SQL*Loader's
output files.
SAS will check for a file having been externally defined with a logical
filename of ORA$FNA. If found, SAS will open the file and read its
contents, storing these for later use. The file contents are not
checked for correct syntax. SAS searches for sub-entries FTYPE and
FNAME, and extracts information to allow datasets to be created with
names matching the names that SQL*Loader will generate when invoked. The
FATTR sub-entry is ignored by SAS, since it is not pertinent to any of
the SAS processing functions.
The rules for FNAME definition are as defined in the Oracle description,
i.e. the name must be enclosed in single or double quotes, and may be a
fully qualified name or subject to symbolic substitution and/or
expansion. There are a couple of minor restrictions imposed:
- The maximum logical record size of the FNA file is 255 bytes.
- Each FNAME entry must be complete within one record of the input
file. SAS does not cater for overflow from one record to the next
in tacking together the dataset name.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Oracle | z/OS | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Usage Note |
Priority: | |
Topic: | SAS Reference ==> LIBNAME Engines Data Management ==> Data Sources ==> External Databases ==> Oracle
|
Date Modified: | 2006-11-03 10:13:15 |
Date Created: | 2006-10-10 15:23:34 |