Oracle7 Server Utilities User's Guide | Library |
Product |
Contents |
Index |
When SQL*Loader begins execution, it creates a log file. The log file contains a detailed summary of the load.
Most of the log file entries will be records of successful SQL*Loader execution. However, errors can also cause log file entries. For example, errors found during parsing of the control file will appear in the log file.
This chapter describes the following log file entries:
The Header Section contains the following entries:
For example:
SQL*Loader: Version 7.1.3.0.0 - Production on Mon Nov 26...
Copyright (c) Oracle Corporation...
The Global Information Section contains the following entries:
If the data is in the control file, then the data file is shown as "*".
For example:
Control File: LOAD.CTL
Data File: LOAD.DAT
Bad File: LOAD.BAD
Discard File: LOAD.DSC
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 64 rows, maximum of 65536 bytes
Continuation: 1:1 = '*', in current physical record
Path used: Conventional
The Table Information Section provides the following entries for each table loaded:
For example:
Table EMP, loaded from every logical record.
Insert option in effect for this table: REPLACE
Column Name Position Len Term Encl Datatype
-------------------------------------- --- ---- ---- ---------
EMPNO 1:4 4 CHARACTER
ENAME 6:15 10 CHARACTER
JOB 17:25 9 CHARACTER
MGR 27:30 4 CHARACTER
SAL 32:39 8 CHARACTER
COMM 41:48 8 CHARACTER
DEPTNO 50:51 2 CHARACTER
Column EMPNO is NULL if EMPNO = BLANKS
Column MGR is NULL if MGR = BLANKS
Column SAL is NULL if SAL = BLANKS
Column COMM is NULL if COMM = BLANKS
Column DEPTNO is NULL if DEPTNO = BLANKS
The Datafile Information Section appears only for datafiles with data errors, and provides the following entries:
For example:
Record 2: Rejected - Error on table EMP.
ORA-00001: unique constraint <name> violated
Record 8: Rejected - Error on table EMP, column DEPTNO.
ORA-01722: invalid number
Record 3: Rejected - Error on table PROJ, column PROJNO.
ORA-01722: invalid number
The Table Load Information Section provides the following entries for each table that was loaded:
For example:
The following indexes on table EMP were processed:
Index EMPIX was left in Direct Load State due to
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
Table EMP:
7 Rows successfully loaded.
2 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
The Summary Statistics Section displays the following data:
For example:
Space allocated for bind array: 65336 bytes (64 rows)
Space allocated for memory less bind array: 6470 bytes
Total logical records skipped: 0
Total logical records read: 7
Total logical records rejected: 0
Total logical records discarded: 0
Run began on Mon Nov 26 10:46:53 1990
Run ended on Mon Nov 26 10:47:17 1990
Elapsed time was: 00:00:15.62
CPU time was: 00:00:07.76
Prev Next |
Copyright © 1996 Oracle Corporation. All Rights Reserved. |
Library |
Product |
Contents |
Index |