SQL*Loader Features
Bad,log,discard files will be generated automatically by Oracle
Load data across a network. This means that you can run the SQL*Loader client on a different system from the one that is running the SQL*Loader server.
Specify the character set of the data.
Load data from multiple datafiles during the same load session.
Load data into multiple tables during the same load session.
Manipulate the data before loading it, using SQL functions.
Generate unique sequential key values in specified columns.
Use the operating system's file system to access the datafiles.
SQL*Loader Command-Line Reference
userid -- Oracle username/password
control -- Control file name
log -- Log file name
bad -- Bad file name
data -- Data file name
discard -- Discard file name
discardmax -- Number of discards to allow
(Default all)
skip -- Number of logical records to skip
(Default 0)
load -- Number of logical records to load
(Default all)
errors -- Number of errors to allow
(Default 50)
rows -- Number of rows in conventional path bind array
or between direct path data saves
(Default: Conventional Path 64, Direct path all)
bindsize -- Size of conventional path bind array in bytes
(System-dependent default)
silent -- Suppress messages during run
(header, feedback, errors, discards, partitions, all)
direct -- Use direct path
(Default FALSE)
parfile -- Parameter file: name of file that contains
parameter specifications
parallel -- Perform parallel load
(Default FALSE)
readsize -- Size (in bytes) of the read buffer
file -- File to allocate extents from
SQL*Loader Parameters
Parameters can be grouped together in a parameter file. You could then specify the name of the parameter file on the command line using the PARFILE parameter.
Certain parameters can also be specified within the SQL*Loader control file by using the OPTIONS clause
SQL*Loader Control File
Contains mapping information between file & the table
CONTROL specifies the name of the control file that describes how to load data.
If a file extension or file type is not specified, it defaults to CTL. If omitted, SQL*Loader prompts you for the file name.
Input Data and Datafiles
Data Conversion and Datatype Specification
Discarded and Rejected Records
Log File and Logging Information
Conventional Path Loads, Direct Path Loads, and External Table Loads
Partitioned Object Support
Application Development: Direct Path Load API
Bad,log,discard files will be generated automatically by Oracle
Load data across a network. This means that you can run the SQL*Loader client on a different system from the one that is running the SQL*Loader server.
Specify the character set of the data.
Load data from multiple datafiles during the same load session.
Load data into multiple tables during the same load session.
Manipulate the data before loading it, using SQL functions.
Generate unique sequential key values in specified columns.
Use the operating system's file system to access the datafiles.
SQL*Loader Command-Line Reference
userid -- Oracle username/password
control -- Control file name
log -- Log file name
bad -- Bad file name
data -- Data file name
discard -- Discard file name
discardmax -- Number of discards to allow
(Default all)
skip -- Number of logical records to skip
(Default 0)
load -- Number of logical records to load
(Default all)
errors -- Number of errors to allow
(Default 50)
rows -- Number of rows in conventional path bind array
or between direct path data saves
(Default: Conventional Path 64, Direct path all)
bindsize -- Size of conventional path bind array in bytes
(System-dependent default)
silent -- Suppress messages during run
(header, feedback, errors, discards, partitions, all)
direct -- Use direct path
(Default FALSE)
parfile -- Parameter file: name of file that contains
parameter specifications
parallel -- Perform parallel load
(Default FALSE)
readsize -- Size (in bytes) of the read buffer
file -- File to allocate extents from
SQL*Loader Parameters
Parameters can be grouped together in a parameter file. You could then specify the name of the parameter file on the command line using the PARFILE parameter.
Certain parameters can also be specified within the SQL*Loader control file by using the OPTIONS clause
SQL*Loader Control File
Contains mapping information between file & the table
CONTROL specifies the name of the control file that describes how to load data.
If a file extension or file type is not specified, it defaults to CTL. If omitted, SQL*Loader prompts you for the file name.
Input Data and Datafiles
Data Conversion and Datatype Specification
Discarded and Rejected Records
Log File and Logging Information
Conventional Path Loads, Direct Path Loads, and External Table Loads
Partitioned Object Support
Application Development: Direct Path Load API
No comments:
Post a Comment