- Install Sql Loader Oracle Client 12c
- How To Install Sql Server
- Install Sql
- Install Sql Loader Oracle Client 11g Linux
- Install Sql Developer
- Download Sql Loader
Installing the full client should provide you with the sqlldr tool but you may want to be aware that if you are loading files with a large amount of data you may want to perform the load on the server itself where the db resides.
- Oracle SQL*Loader Overview. SQL*Loader is the primary method for quickly populating Oracle tables with data from external files. It has a powerful data parsing engine that puts little limitation on the format of the data in the datafile.
- The Oracle client was previously installed by our support team. There were no registry settings, but Sqlplus, Toad, and Plsql Developer all worked. I copied Sqlldr from another server and put it in the bin directory of my localhost.
- How can I install the SQL Loader, when I have installed the Oracle Data Access Components(ODAC) for windows? I am using oracle DB 11gR2 and oracle ODAC version: 11.2.0.3. Oracle sql-loader oracleclient.
This chapter describes the command-line parameters used to invoke SQL*Loader. The following topics are discussed:
Invoking SQL*Loader
When you invoke SQL*Loader, you can specify certain parameters to establish session characteristics. Parameters can be entered in any order, optionally separated by commas. You specify values for parameters, or in some cases, you can accept the default without entering a value.
For example:
If you invoke SQL*Loader without specifying any parameters, SQL*Loader displays a help screen similar to the following. It lists the available parameters and their default values.
See Also: Command-Line Parameters for descriptions of all the command-line parameters |
Command-Line Parameters
This section describes each SQL*Loader command-line parameter. The defaults and maximum values listed for these parameters are for UNIX-based systems. They may be different on your operating system. Refer to your Oracle operating system-specific documentation for more information.
BAD (bad file)
Default: The name of the datafile, with an extension of .bad.
BAD specifies the name of the bad file created by SQL*Loader to store records that cause errors during insert or that are improperly formatted. If you do not specify a filename, the default is used. A bad file is not automatically created if there are no rejected records.
A bad file filename specified on the command line becomes the bad file associated with the first INFILE statement in the control file. If the bad file filename was also specified in the control file, the command-line value overrides it.
See Also: Specifying the Bad File for information about the format of bad files |
BINDSIZE (maximum size)
Default: To see the default value for this parameter, invoke SQL*Loader without any parameters, as described in Invoking SQL*Loader.
BINDSIZE specifies the maximum size (bytes) of the bind array. The size of the bind array given by BINDSIZE overrides the default size (which is system dependent) and any size determined by ROWS.
See Also: |
COLUMNARRAYROWS
Default: To see the default value for this parameter, invoke SQL*Loader without any parameters, as described in Invoking SQL*Loader.
Specifies the number of rows to allocate for direct path column arrays. The value for this parameter is not calculated by SQL*Loader. You must either specify it or accept the default.
See Also: |
CONTROL (control file)
Default: none
CONTROL specifies the name of the SQL*Loader control file that describes how to load the data. If a file extension or file type is not specified, it defaults to .ctl. If the filename is omitted, SQL*Loader prompts you for it.
If the name of your SQL*Loader control file contains special characters, your operating system may require that they be preceded by an escape character. Also, if your operating system uses backslashes in its file system paths, you may need to use multiple escape characters or to enclose the path in quotation marks. See your Oracle operating system-specific documentation for more information.
See Also: Chapter 8 for a detailed description of the SQL*Loader control file |
DATA (datafile)
Default: The name of the control file, with an extension of .dat.
DATA specifies the name of the datafile containing the data to be loaded. If you do not specify a file extension or file type, the default is .dat.
If you specify a datafile on the command line and also specify datafiles in the control file with INFILE, the data specified on the command line is processed first. The first datafile specified in the control file is ignored. All other datafiles specified in the control file are processed.
If you specify a file processing option when loading data from the control file, a warning message will be issued.
DATE_CACHE
Default: Enabled (for 1000 elements). To completely disable the date cache feature, set it to 0.
DATE_CACHE specifies the date cache size (in entries). For example, DATE_CACHE=5000 specifies that each date cache created can contain a maximum of 5000 unique date entries. Every table has its own date cache, if one is needed. A date cache is created only if at least one date or timestamp value is loaded that requires datatype conversion in order to be stored in the table.
The date cache feature is only available for direct path loads. It is enabled by default. The default date cache size is 1000 elements. If the default size is used and the number of unique input values loaded exceeds 1000, then the date cache feature is automatically disabled for that table. However, if you override the default and specify a nonzero date cache size and that size is exceeded, then the cache is not disabled.
You can use the date cache statistics (entries, hits, and misses) contained in the log file to tune the size of the cache for future similar loads.
DIRECT (data path)
Default: false
DIRECT specifies the data path, that is, the load method to use, either conventional path or direct path. A value of true specifies a direct path load. A value of false specifies a conventional path load.
See Also: Chapter 11, 'Conventional and Direct Path Loads' |
DISCARD (filename)
Default: The name of the datafile, with an extension of .dsc.
DISCARD specifies a discard file (optional) to be created by SQL*Loader to store records that are neither inserted into a table nor rejected.
A discard file filename specified on the command line becomes the discard file associated with the first INFILE statement in the control file. If the discard file filename is specified also in the control file, the command-line value overrides it.
See Also: Discarded and Rejected Records for information about the format of discard files |
DISCARDMAX (integer)
Default: ALL
DISCARDMAX specifies the number of discard records to allow before data loading is terminated. To stop on the first discarded record, specify one (1).
ERRORS (errors to allow)
Default: To see the default value for this parameter, invoke SQL*Loader without any parameters, as described in Invoking SQL*Loader.
ERRORS specifies the maximum number of insert errors to allow. If the number of errors exceeds the value specified for ERRORS, then SQL*Loader terminates the load. To permit no errors at all, set ERRORS=0. To specify that all errors be allowed, use a very high number.
On a single-table load, SQL*Loader terminates the load when errors exceed this error limit. Any data inserted up that point, however, is committed.
SQL*Loader maintains the consistency of records across all tables. Therefore, multitable loads do not terminate immediately if errors exceed the error limit. When SQL*Loader encounters the maximum number of errors for a multitable load, it continues to load rows to ensure that valid rows previously loaded into tables are loaded into all tables and rejected rows are filtered out of all tables.
In all cases, SQL*Loader writes erroneous records to the bad file.
EXTERNAL_TABLE
Default: NOT_USED
EXTERNAL_TABLE instructs SQL*Loader whether or not to load data using the external tables option. There are three possible values:
NOT_USED- the default value. It means the load is performed using either conventional or direct path mode.GENERATE_ONLY- places all the SQL statements needed to do the load using external tables, as described in the control file, in the SQL*Loader log file. These SQL statements can be edited and customized. The actual load can be done later without the use of SQL*Loader by executing these statements in SQL*Plus.EXECUTE- attempts to execute the SQL statements that are needed to do the load using external tables. However, if any of the SQL statements returns an error, then the attempt to load stops. Statements are placed in the log file as they are executed. This means that if a SQL statement returns an error, then the remaining SQL statements required for the load will not be placed in the log file.If you use
EXTERNAL_TABLE=EXECUTEand also use theSEQUENCEparameter in your SQL*Loader control file, then SQL*Loader creates a database sequence, loads the table using that sequence, and then deletes the sequence. The results of doing the load this way will be different than if the load were done with conventional or direct path. (For more information about creating sequences, seeCREATESEQUENCEin Oracle Database SQL Reference.)
Note that the external tables option uses directory objects in the database to indicate where all datafiles are stored and to indicate where output files, such as bad files and discard files, are created. You must have READ access to the directory objects containing the datafiles, and you must have WRITE access to the directory objects where the output files are created. If there are no existing directory objects for the location of a datafile or output file, SQL*Loader will generate the SQL statement to create one. Therefore, when the EXECUTE option is specified, you must have the CREATEANYDIRECTORY privilege. If you want the directory object to be deleted at the end of the load, you must also have the DELETEANYDIRECTORY privilege.
Note: TheEXTERNAL_TABLE=EXECUTE qualifier tells SQL*Loader to create an external table that can be used to load data and then execute the INSERT statement to load the data. All files in the external table must be identified as being in a directory object. SQL*Loader attempts to use directory objects that already exist and that you have privileges to access. However, if SQL*Loader does not find the matching directory object, it attempts to create a temporary directory object. If you do not have privileges to create new directory objects, then the operation fails.To work around this, use |
FILE (file to load into)
Default: none
FILE specifies the database file to allocate extents from. It is used only for parallel loads. By varying the value of the FILE parameter for different SQL*Loader processes, data can be loaded onto a system with minimal disk contention.
LOAD (records to load)
Default: All records are loaded.
LOAD specifies the maximum number of logical records to load (after skipping the specified number of records). No error occurs if fewer than the maximum number of records are found.
LOG (log file)
Default: The name of the control file, with an extension of .log.
LOG specifies the log file that SQL*Loader will create to store logging information about the loading process.
MULTITHREADING
Default: true on multiple-CPU systems, false on single-CPU systems
This parameter is available only for direct path loads.
By default, the multithreading option is always enabled (set to true) on multiple-CPU systems. In this case, the definition of a multiple-CPU system is a single system that has more than one CPU.
On single-CPU systems, multithreading is set to false by default. To use multithreading between two single-CPU systems, you must enable multithreading; it will not be on by default. This will allow stream building on the client system to be done in parallel with stream loading on the server system.
Multithreading functionality is operating system-dependent. Not all operating systems support multithreading.
See Also: Optimizing Direct Path Loads on Multiple-CPU Systems |
PARALLEL (parallel load)
Default: false
PARALLEL specifies whether direct loads can operate in multiple concurrent sessions to load data into the same table.
PARFILE (parameter file)
Default: none
PARFILE specifies the name of a file that contains commonly used command-line parameters. For example, the command line could read:
The parameter file could have the following contents:
Note: Although it is not usually important, on some systems it may be necessary to have no spaces around the equal sign (=) in the parameter specifications. |
READSIZE (read buffer size)
Default: To see the default value for this parameter, invoke SQL*Loader without any parameters, as described in Invoking SQL*Loader.
The READSIZE parameter is used only when reading data from datafiles. When reading records from a control file, a value of 64 kilobytes (KB) is always used as the READSIZE.
The READSIZE parameter lets you specify (in bytes) the size of the read buffer, if you choose not to use the default. The maximum size allowed is 20 megabytes (MB) for both direct path loads and conventional path loads.
In the conventional path method, the bind array is limited by the size of the read buffer. Therefore, the advantage of a larger read buffer is that more data can be read before a commit operation is required.
For example:
This example enables SQL*Loader to perform reads from the external datafile in chunks of 1,000,000 bytes before a commit is required.
Note: If theREADSIZE value specified is smaller than the BINDSIZE value, the READSIZE value will be increased. |
RESUMABLE
Default: false
The RESUMABLE parameter is used to enable and disable resumable space allocation. Because this parameter is disabled by default, you must set RESUMABLE=true in order to use its associated parameters, RESUMABLE_NAME and RESUMABLE_TIMEOUT.
See Also: |
RESUMABLE_NAME
Default: 'User USERNAME (USERID), Session SESSIONID, Instance INSTANCEID'
The value for this parameter identifies the statement that is resumable. This value is a user-defined text string that is inserted in either the USER_RESUMABLE or DBA_RESUMABLE view to help you identify a specific resumable statement that has been suspended.
This parameter is ignored unless the RESUMABLE parameter is set to true to enable resumable space allocation.
RESUMABLE_TIMEOUT
Default: 7200 seconds (2 hours)
The value of the parameter specifies the time period during which an error must be fixed. If the error is not fixed within the timeout period, execution of the statement is terminated, without finishing.
This parameter is ignored unless the RESUMABLE parameter is set to true to enable resumable space allocation.
ROWS (rows per commit)
Default: To see the default value for this parameter, invoke SQL*Loader without any parameters, as described in Invoking SQL*Loader.
Keep in mind that if you specify a low value for ROWS and then attempt to compress data using table compression, your compression ratio will probably be degraded. Oracle recommends that you either specify a high value or accept the default value when compressing data.
Conventional path loads only: ROWS specifies the number of rows in the bind array. See Bind Arrays and Conventional Path Loads.
Direct path loads only: ROWS identifies the number of rows you want to read from the datafile before a data save. The default is to read all rows and save data once at the end of the load. See Using Data Saves to Protect Against Data Loss. The actual number of rows loaded into a table on a save is approximately the value of ROWS minus the number of discarded and rejected records since the last save.
Note: TheROWS parameter is ignored when data is loaded into an Index Organized Table (IOT) or into a table containing VARRAYs, XML columns, or LOBs. This means that the load will still take place, but no save points will be done. |
SILENT (feedback mode)
When SQL*Loader begins, information about the SQL*Loader version being used appears on the screen and is placed in the log file. As SQL*Loader executes, you also see feedback messages on the screen, for example:
SQL*Loader may also display data error messages like the following:
You can suppress these messages by specifying SILENT with one or more values.
For example, you can suppress the header and feedback messages that normally appear on the screen with the following command-line argument:
Use the appropriate values to suppress one or more of the following:
HEADER- Suppresses the SQL*Loader header messages that normally appear on the screen. Header messages still appear in the log file.FEEDBACK- Suppresses the 'commit point reached' feedback messages that normally appear on the screen.ERRORS- Suppresses the data error messages in the log file that occur when a record generates an Oracle error that causes it to be written to the bad file. A count of rejected records still appears.DISCARDS- Suppresses the messages in the log file for each record written to the discard file.PARTITIONS- Disables writing the per-partition statistics to the log file during a direct load of a partitioned table.ALL- Implements all of the suppression values:HEADER,FEEDBACK,ERRORS,DISCARDS,andPARTITIONS.
Install Sql Loader Oracle Client 12c
SKIP (records to skip)
Default: No records are skipped.
SKIP specifies the number of logical records from the beginning of the file that should not be loaded.
This parameter continues loads that have been interrupted for some reason. It is used for all conventional loads, for single-table direct loads, and for multiple-table direct loads when the same number of records was loaded into each table. It is not used for multiple-table direct loads when a different number of records was loaded into each table.
If a WHEN clause is also present and the load involves secondary data, the secondary data is skipped only if the WHEN clause succeeds for the record in the primary data file.
SKIP_INDEX_MAINTENANCE
Default: false
The SKIP_INDEX_MAINTENANCE parameter stops index maintenance for direct path loads but does not apply to conventional path loads. It causes the index partitions that would have had index keys added to them to be marked Index Unusable instead, because the index segment is inconsistent with respect to the data it indexes. Index segments that are not affected by the load retain the Index Unusable state they had prior to the load.
The SKIP_INDEX_MAINTENANCE parameter:
Applies to both local and global indexes
Can be used (with the
PARALLELparameter) to do parallel loads on an object that has indexesCan be used (with the
PARTITIONparameter on theINTO TABLEclause) to do a single partition load to a table that has global indexesPuts a list (in the SQL*Loader log file) of the indexes and index partitions that the load set into Index Unusable state
SKIP_UNUSABLE_INDEXES
Default: The value of the Oracle database configuration parameter, SKIP_UNUSABLE_INDEXES, as specified in the initialization parameter file. The default database setting is TRUE.
Both SQL*Loader and the Oracle database provide a SKIP_UNUSABLE_INDEXES parameter. The SQL*Loader SKIP_UNUSABLE_INDEXES parameter is specified at the SQL*Loader command line. The Oracle database SKIP_UNUSABLE_INDEXES parameter is specified as a configuration parameter in the initialization parameter file. It is important to understand how they affect each other.
If you specify a value for SKIP_UNUSABLE_INDEXES at the SQL*Loader command line, it overrides the value of the SKIP_UNUSABLE_INDEXES configuration parameter in the initialization parameter file.
If you do not specify a value for SKIP_UNUSABLE_INDEXES at the SQL*Loader command line, then SQL*Loader uses the database setting for the SKIP_UNUSABLE_INDEXES configuration parameter, as specified in the initialization parameter file. If the initialization parameter file does not specify a database setting for SKIP_UNUSABLE_INDEXES, then the default database setting is TRUE.
A value of TRUE for SKIP_UNUSABLE_INDEXES means that if an index in an Index Unusable state is encountered, it is skipped and the load operation continues. This allows SQL*Loader to load a table with indexes that are in an Unusable state prior to the beginning of the load. Indexes that are not in an Unusable state at load time will be maintained by SQL*Loader. Indexes that are in an Unusable state at load time will not be maintained but will remain in an Unusable state at load completion.
Note: Indexes that are unique and marked Unusable are not allowed to skip index maintenance. This rule is enforced by DML operations, and enforced by the direct path load to be consistent with DML. |
STREAMSIZE
Default: To see the default value for this parameter, invoke SQL*Loader without any parameters, as described in Invoking SQL*Loader.
Specifies the size, in bytes, for direct path streams.
See Also: Specifying the Number of Column Array Rows and Size of Stream Buffers |
USERID (username/password)
Default: none
USERID is used to provide your Oracle username/password. If it is omitted, you are prompted for it. If only a slash is used, USERID defaults to your operating system login.
If you connect as user SYS, you must also specify AS SYSDBA in the connect string. For example:
Note: This example shows the entire connect string enclosed in quotation marks and backslashes. This is because the string,AS SYSDBA, contains a blank, a situation for which most operating systems require that the entire connect string be placed in quotation marks or marked as a literal by some method. Some operating systems also require that quotation marks on the command line be preceded by an escape character. In this example, backslashes are used as the escape character. If the backslashes were not present, the command line parser that SQL*Loader uses would not understand the quotation marks and would remove them.See your Oracle operating system-specific documentation for information about special and reserved characters on your system. |
Exit Codes for Inspection and Display
Oracle SQL*Loader provides the results of a SQL*Loader run immediately upon completion. Depending on the platform, SQL*Loader may report the outcome in a process exit code as well as recording the results in the log file. This Oracle SQL*Loader functionality allows for checking the outcome of a SQL*Loader invocation from the command line or script. Table 7-1 shows the exit codes for various results.
Table 7-1 Exit Codes for SQL*Loader
| Result | Exit Code |
|---|---|
| All rows loaded successfully | EX_SUCC |
| All or some rows rejected | EX_WARN |
| All or some rows discarded | EX_WARN |
| Discontinued load | EX_WARN |
| Command-line or syntax errors | EX_FAIL |
| Oracle errors nonrecoverable for SQL*Loader | EX_FAIL |
| Operating system errors (such as file open/close and malloc) | EX_FAIL |
For UNIX, the exit codes are as follows:
For Windows NT, the exit codes are as follows:
If SQL*Loader returns any exit code other than zero, you should consult your system log files and SQL*Loader log files for more detailed diagnostic information.
How To Install Sql Server
In UNIX, you can check the exit code from the shell to determine the outcome of a load. For example, you could place the SQL*Loader command in a script and check the exit code within the script:
I tried to install Oracle instant client on a redhat machine. I have instantClient basic, sdk, and sqlplus but I could not find any sqlldr. Can some one help me do it?Thanks
3 Answers
Following the information @Alex Poole provided in his comment, I was able to add the sqlldr binary to an Oracle instant client installation on redhat linux. The key is to have access to a full oracle client (or database) installation from which to obtain the sqlldr binary.
In summary here was the process I took with Oracle 11.2.0.3.0:
Install Sql
Install Oracle Instant Client
Download from oracle instant client rpms:
- oracle-instantclient11.2-basic-11.2.0.3.0-1.x86_64.rpm
- oracle-instantclient11.2-jdbc-11.2.0.3.0-1.x86_64.rpm
- oracle-instantclient11.2-devel-11.2.0.3.0-1.x86_64.rpm
- oracle-instantclient11.2-sqlplus-11.2.0.3.0-1.x86_64.rpm
Install:
yum install oracle* --nogpgcheck
Create Oracle Environment Variables
In /etc/profile.d/oracle.sh
Copy sqlldr and message file from full Oracle client/database
Try it:
We need to copy over the ulus.msb file from the Oracle database. But first we need to create the proper directory structure:
With the message file in place, try again:
Success!
Brice RoncaceBrice RoncaceSimpler alternative to the accepted answer that does not require an existing full client install to steal the sqlldr binary from:
You can download SQL loader from OTN in a separate instant client package called 'Instant Client Package - Tools: Includes Data Pump, SQL*Loader and Workload Replay Client'
Install Sql Loader Oracle Client 11g Linux
Here is the link for linux: Instant Client Downloads for Linux x86-64
Install Sql Developer
Install oracle-instantclient12.2-tools, which has sqlldr; and make sure your PATH includes /usr/lib/oracle/12.2/client64/bin.
Download Sql Loader
Adjust versions accordingly.