Home » RDBMS Server » Server Utilities » allowed errors sql loader
allowed errors sql loader [message #74652] Fri, 28 January 2005 06:24 Go to next message
Messages: 68
Registered: September 2004
hello you all,

This is the log file of an sql loader import.
I see that there are 50 errors allowed. Is it possible to tell sql loader not to accept any errors?

SQL*Loader: Release - Production on Fri Nov 26 12:02:57 2004

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Control File: /export/Data.ctl File: /export/file.csv
Bad File: /export/file.bad
Discard File: none specified

(Allow all discards)

Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 64 rows, maximum of 256000 bytes
Continuation: none specified
Path used: Conventional

Thanks in advance
Re: allowed errors sql loader [message #74653 is a reply to message #74652] Fri, 28 January 2005 06:32 Go to previous message
Mahesh Rajendran
Messages: 10679
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
quoting docs
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/or rejected rows filtered out of all tables.

In all cases, SQL*Loader writes erroneous records to the bad file.
Previous Topic: migrating 7.1.6 to 10g
Goto Forum:

Current Time: Tue Dec 12 10:49:16 CST 2017

Total time taken to generate the page: 0.02964 seconds