Oracle7 Server Utilities

**The SQL*Loader Command Line**

You can invoke SQL*Loader from the command line followed by certain keywords.

Additional Information: The command to invoke SQL*Loader is operating system-dependent. The following examples use the UNIX-based name, "sqlldr". See your Oracle operating system-specific documentation for the correct command for your system.

If you invoke SQL*Loader with no keywords, SQL*Loader displays a help screen with the available keywords and default values. The following example shows default values that are the same on all operating systems.

sqlldr

...

Valid Keywords:

	    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)

	    direct -- Use direct path

				(Default FALSE)

	   parfile -- Parameter file: name of file that contains

			     parameter specifications

	  parallel - Perform parallel load

				(Default FALSE)

	      file - File to allocate extents from

Using Command-Line Keywords

Keywords are optionally separated by commas. They are entered in any order. Keywords are followed by valid arguments.

For example, :

SQLLDR CONTROL=foo.ctl, LOG=bar.log, BAD=baz.bad, DATA=etc.dat

	USERID=scott/tiger, ERRORS=999, LOAD=2000, DISCARD=toss.dis,

	DISCARDMAX=5

Specifying Keywords in the Control File

If the command line's length exceeds the size of the maximum command line on your system, you can put some of the command-line keywords in the control file, using the control file keyword OPTIONS. See

They can also be specified in a separate file specified by the keyword PARFILE (see ). These alternative methods are useful for keyword entries that seldom change. Keywords specified in this manner can still be overridden from the command line.