Sqlldr examples

The Case Studies

Case Study 8: Loading Partitioned Tables
Case Study 9: Loading LOBFILEs (CLOBs)
Case Study 10: Loading REF Fields and VARRAYs
Case Study 11: Loading Data in the Unicode Character Set

The Case Studies
This chapter contains the following case studies:
Case Study 1: Loading Variable-Length Data on page 12-5: Loads stream format
records in which the fields are terminated by commas and may be enclosed by
quotation marks. The data is found at the end of the control file.
Case Study 2: Loading Fixed-Format Fields on page 12-8: Loads data from a
separate datafile.
Case Study 3: Loading a Delimited, Free-Format File on page 12-11: Loads data
from stream format records with delimited fields and sequence numbers. The
data is found at the end of the control file.
Case Study 4: Loading Combined Physical Records on page 12-14: Combines
multiple physical records into one logical record corresponding to one database
row.
Case Study 5: Loading Data into Multiple Tables on page 12-18: Loads data into
multiple tables in one run.
Case Study 6: Loading Data Using the Direct Path Load Method on page 12-24:
Loads data using the direct path load method.
Case Study 7: Extracting Data from a Formatted Report on page 12-28: Extracts
data from a formatted report.
Case Study 8: Loading Partitioned Tables on page 12-34: Loads partitioned
tables.
Case Study 9: Loading LOBFILEs (CLOBs) on page 12-38: Adds a CLOB column
called resume to the table emp, uses a FILLER field (res_file), and loads
multiple LOBFILEs into the emp table.
Case Study 10: Loading REF Fields and VARRAYs on page 12-43: Loads a
customer table that has a primary key as its OID and stores order items in a
VARRAY. Loads an order table that has a reference to the customer table and the
order items in a VARRAY.

12-2 Oracle Database Utilities

Case Study Files

Case Study 11: Loading Data in the Unicode Character Set on page 12-47: Loads
data in the Unicode character set, UTF16, in little-endian byte order. This case
study uses character-length semantics.

Case Study Files
The distribution media for SQL*Loader contains files for each case:
Control files (for example, ulcase5.ctl)
Datafiles (for example, ulcase5.dat)
Setup files (for example, ulcase5.sql)
If the sample data for the case study is contained in the control file, then there will
be no .dat file for that case.
If there are no special setup steps for a case study, there may be no .sql file for that
case. Starting (setup) and ending (cleanup) scripts are denoted by an S or E after the
case number.
Table 12–1 lists the files associated with each case.
Table 12–1 Case Studies and Their Related Files
Case .ctl .dat .sql
1 Yes No Yes
2 Yes Yes No
3 Yes No Yes
4 Yes Yes Yes
5 Yes Yes Yes
6 Yes Yes Yes
7 Yes Yes Yes (S, E)
8 Yes Yes Yes
9 Yes Yes Yes
10 Yes No Yes
11 Yes Yes Yes

SQL*Loader Case Studies 12-3

Tables Used in the Case Studies

Tables Used in the Case Studies
The case studies are based upon the standard Oracle demonstration database tables,
emp and dept, owned by scott/tiger. (In some case studies, additional columns
have been added.)

Contents of Table emp
(empno NUMBER(4) NOT NULL,
ename VARCHAR2(10),
job VARCHAR2(9),
mgr NUMBER(4),
hiredate DATE,
sal NUMBER(7,2),
comm NUMBER(7,2),
deptno NUMBER(2))

Contents of Table dept
(deptno NUMBER(2) NOT NULL,
dname VARCHAR2(14),
loc VARCHAR2(13))

Checking the Results of a Load
To check the results of a load, start SQL*Plus and perform a select operation from
the table that was loaded in the case study. This is done, as follows:
1. Start SQL*Plus as scott/tiger by entering the following at the system
prompt:
sqlplus scott/tiger

The SQL prompt is displayed.
2. At the SQL prompt, use the SELECT statement to select all rows from the table
that the case study loaded. For example, if the table emp was loaded, enter:
SQL> SELECT * FROM emp;

The contents of each row in the emp table will be displayed.


Case Study 1: Loading Variable-Length Data

References and Notes
The summary at the beginning of each case study directs you to the sections of this
guide that discuss the SQL*Loader feature being demonstrated.
In the control file fragment and log file listing shown for each case study, the
numbers that appear to the left are not actually in the file; they are keyed to the
numbered notes following the listing. Do not use these numbers when you write
your control files.

Case 1 demonstrates:
A simple control file identifying one table and three columns to be loaded.
Including data to be loaded from the control file itself, so there is no separate
datafile. See Identifying Data in the Control File with BEGINDATA on
page 8-11.
Loading data in stream format, with both types of delimited fields: terminated
and enclosed. See Specifying Field Length for Datatypes for Which Whitespace
Can Be Trimmed on page 9-47.

Control File for Case Study 1
The control file is ulcase1.ctl:
1) LOAD DATA
2) INFILE *
3) INTO TABLE dept
4) FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
5) (deptno, dname, loc)
6) BEGINDATA
12,RESEARCH,"SARATOGA"
10,"ACCOUNTING",CLEVELAND
11,"ART",SALEM
13,FINANCE,"BOSTON"
21,"SALES",PHILA.
22,"SALES",ROCHESTER
42,"INT'L","SAN FRAN"

Notes:

1. The LOAD DATA statement is required at the beginning of the control file.



2. INFILE * specifies that the data is found in the control file and not in an
external file.
3. The INTO TABLE statement is required to identify the table to be loaded (dept)
into. By default, SQL*Loader requires the table to be empty before it inserts any
records.
4. FIELDS TERMINATED BY specifies that the data is terminated by commas, but
may also be enclosed by quotation marks. Datatypes for all fields default to
CHAR.
5. The names of columns to load are enclosed in parentheses. Because no datatype
or length is specified, the default is type CHAR with a maximum length of 255.
6. BEGINDATA specifies the beginning of the data.

Running Case Study 1
Take the following steps to run the case study.
prompt:
sqlplus scott/tiger

2. At the SQL prompt, execute the SQL script for this case study, as follows:
SQL> @ulcase1

This prepares and populates tables for the case study and then returns you to
the system prompt.
3. At the system prompt, invoke SQL*Loader and run the case study, as follows:
sqlldr USERID=scott/tiger CONTROL=ulcase1.ctl LOG=ulcase1.log

SQL*Loader loads the dept table, creates the log file, and returns you to the
system prompt. You can check the log file to see the results of running the case
study.

Log File for Case Study 1
The following shows a portion of the log file:
Control File: ulcase1.ctl



Data File: ulcase1.ctl
Bad File: ulcase1.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

Table DEPT, loaded from every logical record.
Insert option in effect for this table: INSERT

Column Name Position Len Term Encl Datatype
------------------------------ ---------- ----- ---- ---- ---------------------
1) DEPTNO FIRST * , O(") CHARACTER
DNAME NEXT * , O(") CHARACTER
2) LOC NEXT * , O(") CHARACTER

Table DEPT:
7 Rows successfully loaded.
0 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.

Space allocated for bind array: 49536 bytes(64 rows)
Read buffer bytes: 1048576

Total logical records skipped: 0
Total logical records read: 7
Total logical records rejected: 0
Total logical records discarded: 0
.
.
.
Elapsed time was: 00:00:01.53
CPU time was: 00:00:00.20

Notes:


Case Study 2: Loading Fixed-Format Fields

1. Position and length for each field are determined for each record, based on
delimiters in the input file.
2. The notation O(") signifies optional enclosure by quotation marks.

A separate datafile. See Specifying Datafiles on page 8-8.
Data conversions. See Datatype Conversions on page 9-24.
In this case, the field positions and datatypes are specified explicitly.

The control file is ulcase2.ctl.
1) LOAD DATA
2) INFILE 'ulcase2.dat'
3) INTO TABLE emp
4) (empno POSITION(01:04) INTEGER EXTERNAL,
ename POSITION(06:15) CHAR,
job POSITION(17:25) CHAR,
mgr POSITION(27:30) INTEGER EXTERNAL,
sal POSITION(32:39) DECIMAL EXTERNAL,
comm POSITION(41:48) DECIMAL EXTERNAL,
5) deptno POSITION(50:51) INTEGER EXTERNAL)

Notes:

1. The LOAD DATA statement is required at the beginning of the control file.
2. The name of the file containing data follows the INFILE parameter.
3. The INTO TABLE statement is required to identify the table to be loaded into.
4. Lines 4 and 5 identify a column name and the location of the data in the datafile
to be loaded into that column. empno, ename, job, and so on are names of
columns in table emp. The datatypes (INTEGER EXTERNAL, CHAR, DECIMAL
EXTERNAL) identify the datatype of data fields in the file, not of corresponding
columns in the emp table.
5. Note that the set of column specifications is enclosed in parentheses.



Datafile for Case Study 2
The following are a few sample data lines from the file ulcase2.dat. Blank fields
are set to null automatically.
7782 CLARK MANAGER 7839 2572.50 10
7839 KING PRESIDENT 5500.00 10
7934 MILLER CLERK 7782 920.00 10
7566 JONES MANAGER 7839 3123.75 20
7499 ALLEN SALESMAN 7698 1600.00 300.00 30
7654 MARTIN SALESMAN 7698 1312.50 1400.00 30
7658 CHAN ANALYST 7566 3450.00 20
7654 MARTIN SALESMAN 7698 1312.50 1400.00 30

Take the following steps to run the case study. If you have already run case study 1,
you can skip to Step 3 because the ulcase1.sql script handles both case 1 and case
2.
prompt:
sqlplus scott/tiger

SQL> @ulcase1

the system prompt.

SQL*Loader loads the table, creates the log file, and returns you to the system
prompt. You can check the log file to see the results of running the case study.
Records loaded in this example from the emp table contain department
numbers. Unless the dept table is loaded first, referential integrity checking
rejects these records (if referential integrity constraints are enabled for the emp
table).



Data File: ulcase2.dat


Number to load: ALL
Number to skip: 0
Errors allowed: 50

Table EMP, loaded from every logical record.
Insert option in effect for this table: INSERT

------------------------------ ---------- ----- ---- ---- ---------------------
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

Table EMP:




Case Study 3: Loading a Delimited, Free-Format File

.
.
.

Loading data (enclosed and terminated) in stream format. See Delimited Fields
on page 9-30.
Loading dates using the datatype DATE. See Datetime and Interval Datatypes
on page 9-16.
Using SEQUENCE numbers to generate unique keys for loaded data. See Setting
a Column to a Unique Sequence Number on page 9-60.
Using APPEND to indicate that the table need not be empty before inserting new
records. See Table-Specific Loading Method on page 8-34.
Using Comments in the control file set off by two hyphens. See Comments in
the Control File on page 8-4.

This control file loads the same table as in case 2, but it loads three additional
columns (hiredate, projno, and loadseq). The demonstration table emp does
not have columns projno and loadseq. To test this control file, add these columns
to the emp table with the command:
ALTER TABLE emp ADD (projno NUMBER, loadseq NUMBER);

The data is in a different format than in case 2. Some data is enclosed in quotation
marks, some is set off by commas, and the values for deptno and projno are
separated by a colon.
1) -- Variable-length, delimited, and enclosed data format
LOAD DATA
2) INFILE *
3) APPEND
INTO TABLE emp
4) FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"'
(empno, ename, job, mgr,



5) hiredate DATE(20) "DD-Month-YYYY",
sal, comm, deptno CHAR TERMINATED BY ':',
projno,
6) loadseq SEQUENCE(MAX,1))
7) BEGINDATA
8) 7782, "Clark", "Manager", 7839, 09-June-1981, 2572.50,, 10:101
7839, "King", "President", , 17-November-1981,5500.00,,10:102
7934, "Miller", "Clerk", 7782, 23-January-1982, 920.00,, 10:102
7566, "Jones", "Manager", 7839, 02-April-1981, 3123.75,, 20:101
7499, "Allen", "Salesman", 7698, 20-February-1981, 1600.00,
(same line continued) 300.00, 30:103
7654, "Martin", "Salesman", 7698, 28-September-1981, 1312.50,
(same line continued) 1400.00, 3:103
7658, "Chan", "Analyst", 7566, 03-May-1982, 3450,, 20:101

Notes:

1. Comments may appear anywhere in the command lines of the file, but they
should not appear in data. They are preceded with two hyphens that may
appear anywhere on a line.
2. INFILE * specifies that the data is found at the end of the control file.
3. APPEND specifies that the data can be loaded even if the table already contains
rows. That is, the table need not be empty.
4. The default terminator for the data fields is a comma, and some fields may be
enclosed by double quotation marks (").
5. The data to be loaded into column hiredate appears in the format
DD-Month-YYYY. The length of the date field is specified to have a maximum
of 20. The maximum length is in bytes, with default byte-length semantics. If
character-length semantics were used instead, the length would be in
characters. If a length is not specified, then the length depends on the length of
the date mask.
6. The SEQUENCE function generates a unique value in the column loadseq. This
function finds the current maximum value in column loadseq and adds the
increment (1) to it to obtain the value for loadseq for each row inserted.
7. BEGINDATA specifies the end of the control information and the beginning of
the data.
8. Although each physical record equals one logical record, the fields vary in
length, so that some records are longer than others. Note also that several rows
have null values for comm.



prompt:
sqlplus scott/tiger

SQL> @ulcase3

the system prompt.




Number to load: ALL
Number to skip: 0
Errors allowed: 50

Insert option in effect for this table: APPEND



Case Study 4: Loading Combined Physical Records

------------------------------ ---------- ----- ---- ---- ---------------------
EMPNO FIRST * , O(") CHARACTER
ENAME NEXT * , O(") CHARACTER
JOB NEXT * , O(") CHARACTER
MGR NEXT * , O(") CHARACTER
HIREDATE NEXT 20 , O(") DATE DD-Month-YYYY
SAL NEXT * , O(") CHARACTER
COMM NEXT * , O(") CHARACTER
DEPTNO NEXT * : O(") CHARACTER
PROJNO NEXT * , O(") CHARACTER
LOADSEQ SEQUENCE (MAX, 1)

Table EMP:

.
.
.

Combining multiple physical records to form one logical record with
CONTINUEIF; see Using CONTINUEIF to Assemble Logical Records on
page 8-28.
Inserting negative numbers.
Indicating with REPLACE that the table should be emptied before the new data
is inserted; see Table-Speciﬁc Loading Method on page 8-34.



Specifying a discard file in the control file using DISCARDFILE; see Specifying
the Discard File on page 8-14.
Specifying a maximum number of discards using DISCARDMAX; see Specifying
the Discard File on page 8-14.
Rejecting records due to duplicate values in a unique index or due to invalid
data values; see Criteria for Rejected Records on page 8-14.

The control file is ulcase4.ctl:
LOAD DATA
INFILE 'ulcase4.dat'
1) DISCARDFILE 'ulcase4.dsc'
2) DISCARDMAX 999
3) REPLACE
4) CONTINUEIF THIS (1) = '*'
INTO TABLE emp
(empno POSITION(1:4) INTEGER EXTERNAL,
mgr POSITION(27:30) INTEGER EXTERNAL,
sal POSITION(32:39) DECIMAL EXTERNAL,
comm POSITION(41:48) DECIMAL EXTERNAL,
deptno POSITION(50:51) INTEGER EXTERNAL,
hiredate POSITION(52:60) INTEGER EXTERNAL)

Notes:

1. DISCARDFILE specifies a discard file named ulcase4.dsc.
2. DISCARDMAX specifies a maximum of 999 discards allowed before terminating
the run (for all practical purposes, this allows all discards).
3. REPLACE specifies that if there is data in the table being loaded, then
SQL*Loader should delete that data before loading new data.
4. CONTINUEIF THIS specifies that if an asterisk is found in column 1 of the
current record, then the next physical record after that record should be
appended to it from the logical record. Note that column 1 in each physical
record should then contain either an asterisk or a nondata value.



The datafile for this case, ulcase4.dat, looks as follows. Asterisks are in the first
position and, though not visible, a newline character is in position 20. Note that
clark's commission is -10, and SQL*Loader loads the value, converting it to a
negative number.
*7782 CLARK
MANAGER 7839 2572.50 -10 25 12-NOV-85
*7839 KING
PRESIDENT 5500.00 25 05-APR-83
*7934 MILLER
CLERK 7782 920.00 25 08-MAY-80
*7566 JONES
MANAGER 7839 3123.75 25 17-JUL-85
*7499 ALLEN
SALESMAN 7698 1600.00 300.00 25 3-JUN-84
*7654 MARTIN
SALESMAN 7698 1312.50 1400.00 25 21-DEC-85
*7658 CHAN
ANALYST 7566 3450.00 25 16-FEB-84
* CHEN
ANALYST 7566 3450.00 25 16-FEB-84
*7658 CHIN
ANALYST 7566 3450.00 25 16-FEB-84

Rejected Records
The last two records are rejected, given two assumptions. If a unique index is
created on column empno, then the record for chin will be rejected because his
empno is identical to chan's. If empno is defined as NOT NULL, then chen's record
will be rejected because it has no value for empno.

prompt:
sqlplus scott/tiger




SQL> @ulcase4

the system prompt.


The following is a portion of the log ﬁle:
Discard File: ulcase4.dis
(Allow 999 discards)

Number to load: ALL
Number to skip: 0
Errors allowed: 50
Continuation: 1:1 = 0X2a(character '*'), in current physical record

Insert option in effect for this table: REPLACE

------------------------------ ---------- ----- ---- ---- ---------------------
HIREDATE 52:60 9 CHARACTER

Record 8: Rejected - Error on table EMP.
ORA-01400: cannot insert NULL into ("SCOTT"."EMP"."EMPNO")


Case Study 5: Loading Data into Multiple Tables

Record 9: Rejected - Error on table EMP.
ORA-00001: unique constraint (SCOTT.EMPIX) violated

Table EMP:


.
.
.

Bad File for Case Study 4
The bad file, shown in the following display, lists records 8 and 9 for the reasons
stated earlier. (The discard file is not created.)
* CHEN ANALYST
7566 3450.00 25 16-FEB-84
*7658 CHIN ANALYST
7566 3450.00 25 16-FEB-84

Loading multiple tables. See Loading Data into Multiple Tables on page 8-44.
Using SQL*Loader to break down repeating groups in a flat file and to load the
data into normalized tables. In this way, one file record may generate multiple
database rows.



Deriving multiple logical records from each physical record. See Benefits of
Using Multiple INTO TABLE Clauses on page 8-40.
Using a WHEN clause. See Loading Records Based on a Condition on page 8-36.
Loading the same field (empno) into multiple tables.

-- Loads EMP records from first 23 characters
-- Creates and loads PROJ records for each PROJNO listed
-- for each employee
LOAD DATA
BADFILE 'ulcase5.bad'
DISCARDFILE 'ulcase5.dsc'
1) REPLACE
2) INTO TABLE emp
deptno POSITION(17:18) CHAR,
mgr POSITION(20:23) INTEGER EXTERNAL)
2) INTO TABLE proj
-- PROJ has two columns, both not null: EMPNO and PROJNO
3) WHEN projno != ' '
3) projno POSITION(25:27) INTEGER EXTERNAL) -- 1st proj
2) INTO TABLE proj
4) projno POSITION(29:31 INTEGER EXTERNAL) -- 2nd proj

2) INTO TABLE proj
5) projno POSITION(33:35) INTEGER EXTERNAL) -- 3rd proj

Notes:

1. REPLACE specifies that if there is data in the tables to be loaded (emp and
proj), SQL*loader should delete the data before loading new rows.



2. Multiple INTO TABLE clauses load two tables, emp and proj. The same set of
records is processed three times, using different combinations of columns each
time to load table proj.
3. WHEN loads only rows with nonblank project numbers. When projno is
defined as columns 25...27, rows are inserted into proj only if there is a value
in those columns.
4. When projno is defined as columns 29...31, rows are inserted into proj only if
there is a value in those columns.
5. When projno is defined as columns 33...35, rows are inserted into proj only if
there is a value in those columns.

1234 BAKER 10 9999 101 102 103
1234 JOKER 10 9999 777 888 999
2664 YOUNG 20 2893 425 abc 102
5321 OTOOLE 10 9999 321 55 40
2134 FARMER 20 4555 236 456
2414 LITTLE 20 5634 236 456 40
6542 LEE 10 4532 102 321 14
2849 EDDS xx 4555 294 40
4532 PERKINS 10 9999 40
1244 HUNT 11 3452 665 133 456
123 DOOLITTLE 12 9940 132
1453 MACDONALD 25 5532 200

prompt:
sqlplus scott/tiger

SQL> @ulcase5

the system prompt.




SQL*Loader loads the tables, creates the log ﬁle, and returns you to the system


Number to load: ALL
Number to skip: 0
Errors allowed: 50


------------------------------ ---------- ----- ---- ---- ---------------------

Table PROJ, loaded when PROJNO != 0X202020(character ' ')

------------------------------ ---------- ----- ---- ---- ---------------------
PROJNO 25:27 3 CHARACTER




------------------------------ ---------- ----- ---- ---- ---------------------


------------------------------ ---------- ----- ---- ---- ---------------------

1) Record 2: Rejected - Error on table EMP.
1) ORA-00001: unique constraint (SCOTT.EMPIX) violated

1) Record 8: Rejected - Error on table EMP, column DEPTNO.
1) ORA-01722: invalid number

1) Record 3: Rejected - Error on table PROJ, column PROJNO.
1) ORA-01722: invalid number

Table EMP:
2) 9 Rows successfully loaded.
2) 3 Rows not loaded due to data errors.
2) 0 Rows not loaded because all WHEN clauses were failed.
2) 0 Rows not loaded because all fields were null.

Table PROJ:

Table PROJ:

Table PROJ:





.
.
.

Notes:

1. Errors are not encountered in the same order as the physical records due to
buffering (array batch). The bad file and discard file contain records in the same
order as they appear in the log file.
2. Of the 12 logical records for input, three rows were rejected (rows for joker,
young, and edds). No data was loaded for any of the rejected records.
3. Of the 9 records that met the WHEN clause criteria, two (joker and young) were
rejected due to data errors.
4. Of the 10 records that met the WHEN clause criteria, three (joker, young, and
edds) were rejected due to data errors.
5. Of the 9 records that met the WHEN clause criteria, three (joker, young, and
edds) were rejected due to data errors.

Loaded Tables for Case Study 5
The following are sample SQL queries and their results:
SQL> SELECT empno, ename, mgr, deptno FROM emp;
EMPNO ENAME MGR DEPTNO
------ ------ ------ ------
1234 BAKER 9999 10
5321 OTOOLE 9999 10


Case Study 6: Loading Data Using the Direct Path Load Method

2134 FARMER 4555 20
2414 LITTLE 5634 20
6542 LEE 4532 10
4532 PERKINS 9999 10
1244 HUNT 3452 11
123 DOOLITTLE 9940 12
1453 MACDONALD 5532 25

SQL> SELECT * from PROJ order by EMPNO;

EMPNO PROJNO
------ ------
123 132
1234 101
1234 103
1234 102
1244 665
1244 456
1244 133
1453 200
2134 236
2134 456
2414 236
2414 456
2414 40
4532 40
5321 321
5321 40
5321 55
6542 102
6542 14
6542 321

This case study loads the emp table using the direct path load method and
concurrently builds all indexes. It illustrates the following functions:
Use of the direct path load method to load and index data. See Chapter 11.
How to specify the indexes for which the data is presorted. See Presorting Data
for Faster Indexing on page 11-18.
The NULLIF clause. See Using the WHEN, NULLIF, and DEFAULTIF Clauses
on page 9-33.



Loading all-blank numeric fields as NULL. See Loading All-Blank Fields on
page 9-44.
In this example, field positions and datatypes are specified explicitly.

LOAD DATA
REPLACE
INTO TABLE emp
1) SORTED INDEXES (empix)
2) (empno POSITION(01:04) INTEGER EXTERNAL NULLIF empno=BLANKS,
mgr POSITION(27:30) INTEGER EXTERNAL NULLIF mgr=BLANKS,
sal POSITION(32:39) DECIMAL EXTERNAL NULLIF sal=BLANKS,
comm POSITION(41:48) DECIMAL EXTERNAL NULLIF comm=BLANKS,
deptno POSITION(50:51) INTEGER EXTERNAL NULLIF deptno=BLANKS)

Notes:

1. The SORTED INDEXES statement identifies the indexes on which the data is
sorted. This statement indicates that the datafile is sorted on the columns in the
empix index. It allows SQL*Loader to optimize index creation by eliminating
the sort phase for this data when using the direct path load method.
2. The NULLIF...BLANKS clause specifies that the column should be loaded as
NULL if the field in the datafile consists of all blanks. For more information,
refer to Using the WHEN, NULLIF, and DEFAULTIF Clauses on page 9-33.

7499 ALLEN SALESMAN 7698 1600.00 300.00 30
7566 JONES MANAGER 7839 3123.75 20
7654 MARTIN SALESMAN 7698 1312.50 1400.00 30
7658 CHAN ANALYST 7566 3450.00 20
7782 CLARK MANAGER 7839 2572.50 10
7839 KING PRESIDENT 5500.00 10
7934 MILLER CLERK 7782 920.00 10



prompt:
sqlplus scott/tiger

SQL> @ulcase6

the system prompt.
3. At the system prompt, invoke SQL*Loader and run the case study, as follows.
Be sure to specify DIRECT=true.Otherwise, conventional path is used as the
default, which will result in failure of the case study.
sqlldr USERID=scott/tiger CONTROL=ulcase6.ctl LOG=ulcase6.log DIRECT=true

SQL*Loader loads the emp table using the direct path load method, creates the
log ﬁle, and returns you to the system prompt. You can check the log ﬁle to see
the results of running the case study.



Number to load: ALL
Number to skip: 0
Errors allowed: 50
Path used: Direct




------------------------------ ---------- ----- ---- ---- ---------------------
NULL if MGR = BLANKS
NULL if SAL = BLANKS
NULL if COMM = BLANKS
NULL if EMPNO = BLANKS

The following index(es) on table EMP were processed:
index SCOTT.EMPIX loaded successfully with 7 keys

Table EMP:
Bind array size not used in direct path.
Column array rows : 5000
Stream buffer bytes: 256000

Total stream buffers loaded by SQL*Loader main thread: 2
Total stream buffers loaded by SQL*Loader load thread: 0
.
.
.


Case Study 7: Extracting Data from a Formatted Report

In this case study, SQL*Loader string-processing functions extract data from a
formatted report. This example creates a trigger that uses the last value of
unspecified fields. This case illustrates the following:
Use of SQL*Loader with an INSERT trigger. See Oracle Database Application
Developer's Guide - Fundamentals for more information about database triggers.
Use of the SQL string to manipulate data; see Applying SQL Operators to Fields
on page 9-52.
Different initial and trailing delimiters. See Specifying Delimiters on page 9-25.
Use of SYSDATE; see Setting a Column to the Current Date on page 9-60.
Use of the TRAILING NULLCOLS clause; see TRAILING NULLCOLS Clause on
page 8-38.
Ambiguous field length warnings; see Conflicting Native Datatype Field
Lengths on page 9-23 and Conflicting Field Lengths for Character Datatypes on
page 9-29.
Use of a discard file. See Specifying the Discard File in the Control File on
page 8-15.

Creating a BEFORE INSERT Trigger
In this case study, a BEFORE INSERT trigger is required to fill in the department
number, job name, and manager's number when these fields are not present on a
data line. When values are present, they should be saved in a global variable. When
values are not present, the global variables are used.
The INSERT trigger and the global variables package are created when you execute
the ulcase7s.sql script.
The package defining the global variables looks as follows:
CREATE OR REPLACE PACKAGE uldemo7 AS -- Global Package Variables
last_deptno NUMBER(2);
last_job VARCHAR2(9);
last_mgr NUMBER(4);
END uldemo7;
/

The definition of the INSERT trigger looks as follows:
CREATE OR REPLACE TRIGGER uldemo7_emp_insert



BEFORE INSERT ON emp
FOR EACH ROW
BEGIN
IF :new.deptno IS NOT NULL THEN
uldemo7.last_deptno := :new.deptno; -- save value for later
ELSE
:new.deptno := uldemo7.last_deptno; -- use last valid value
END IF;
IF :new.job IS NOT NULL THEN
uldemo7.last_job := :new.job;
ELSE
:new.job := uldemo7.last_job;
END IF;
IF :new.mgr IS NOT NULL THEN
uldemo7.last_mgr := :new.mgr;
ELSE
:new.mgr := uldemo7.last_mgr;
END IF;
END;
/

Note: The FOR EACH ROW clause is important. If it was not
speciﬁed, the INSERT trigger would only execute once for each
array of inserts, because SQL*Loader uses the array interface.

Be sure to execute the ulcase7e.sql script to drop the INSERT trigger and the
global variables package before continuing with the rest of the case studies. See
Running Case Study 7 on page 12-31.

LOAD DATA
DISCARDFILE 'ulcase7.dis'
APPEND
INTO TABLE emp
1) WHEN (57) = '.'
2) TRAILING NULLCOLS
3) (hiredate SYSDATE,
4) deptno POSITION(1:2) INTEGER EXTERNAL(3)
5) NULLIF deptno=BLANKS,



job POSITION(7:14) CHAR TERMINATED BY WHITESPACE
6) NULLIF job=BLANKS "UPPER(:job)",
7) mgr POSITION(28:31) INTEGER EXTERNAL
TERMINATED BY WHITESPACE, NULLIF mgr=BLANKS,
ename POSITION(34:41) CHAR
TERMINATED BY WHITESPACE "UPPER(:ename)",
empno POSITION(45) INTEGER EXTERNAL
TERMINATED BY WHITESPACE,
sal POSITION(51) CHAR TERMINATED BY WHITESPACE
8) "TO_NUMBER(:sal,'$99,999.99')",
9) comm INTEGER EXTERNAL ENCLOSED BY '(' AND '%'
":comm * 100"
)

Notes:

1. The decimal point in column 57 (the salary field) identifies a line with data on it.
All other lines in the report are discarded.
2. The TRAILING NULLCOLS clause causes SQL*Loader to treat any fields that are
missing at the end of a record as null. Because the commission field is not
present for every record, this clause says to load a null commission instead of
rejecting the record when only seven fields are found instead of the expected
eight.
3. Employee's hire date is filled in using the current system date.
4. This specification generates a warning message because the specified length
does not agree with the length determined by the field's position. The specified
length (3) is used. See Log File for Case Study 7 on page 12-32. The length is in
bytes with the default byte-length semantics. If character-length semantics were
used instead, this length would be in characters.
5. Because the report only shows department number, job, and manager when the
value changes, these fields may be blank. This control file causes them to be
loaded as null, and an insert trigger fills in the last valid value.
6. The SQL string changes the job name to uppercase letters.
7. It is necessary to specify starting position here. If the job field and the manager
field were both blank, then the job field's TERMINATED BY WHITESPACE clause
would cause SQL*Loader to scan forward to the employee name field. Without
the POSITION clause, the employee name field would be mistakenly
interpreted as the manager field.



8. Here, the SQL string translates the ﬁeld from a formatted character string into a
number. The numeric value takes less space and can be printed with a variety of
formatting options.
9. In this case, different initial and trailing delimiters pick the numeric value out of
a formatted ﬁeld. The SQL string then converts the value to its stored form.

The following listing of the report shows the data to be loaded:
Today's Newly Hired Employees

Dept Job Manager MgrNo Emp Name EmpNo Salary/Commission
---- -------- -------- ----- -------- ----- -----------------
20 Salesman Blake 7698 Shepard 8061 $1,600.00 (3%)
Falstaff 8066 $1,250.00 (5%)
Major 8064 $1,250.00 (14%)

30 Clerk Scott 7788 Conrad 8062 $1,100.00
Ford 7369 DeSilva 8063 $800.00
Manager King 7839 Provo 8065 $2,975.00

prompt:
sqlplus scott/tiger

SQL> @ulcase7s

the system prompt.



SQL*Loader extracts data from the report, creates the log ﬁle, and returns you
to the system prompt. You can check the log ﬁle to see the results of running the
case study.
4. After running this case study, you must drop the insert triggers and
global-variable package before you can continue with the rest of the case
studies. To do this, execute the ulcase7e.sql script as follows:
SQL> @ulcase7e

1) SQL*Loader-307: Warning: conflicting lengths 2 and 3 specified for column
DEPTNO
table EMP

Number to load: ALL
Number to skip: 0
Errors allowed: 50

Table EMP, loaded when 57:57 = 0X2e(character '.')
Insert option in effect for this table: APPEND
TRAILING NULLCOLS option in effect

------------------------------ ---------- ----- ---- ---- ---------------------
HIREDATE SYSDATE
NULL if DEPTNO = BLANKS
JOB 7:14 8 WHT CHARACTER
NULL if JOB = BLANKS
SQL string for column : "UPPER(:job)"
MGR 28:31 4 WHT CHARACTER
NULL if MGR = BLANKS
ENAME 34:41 8 WHT CHARACTER



SQL string for column : "UPPER(:ename)"
EMPNO NEXT * WHT CHARACTER
SAL 51 * WHT CHARACTER
SQL string for column : "TO_NUMBER(:sal,'$99,999.99')"
COMM NEXT * ( CHARACTER
%
SQL string for column : ":comm * 100"

2) Record 1: Discarded - failed all WHEN clauses.
Record 2: Discarded - failed all WHEN clauses.

Table EMP:


2) Total logical records discarded: 7
.
.
.

Notes:

1. A warning is generated by the difference between the speciﬁed length and the
length derived from the position speciﬁcation.
2. There are six header lines at the top of the report: 3 of them contain text and 3 of
them are blank. All of them are rejected, as is the blank separator line in the
middle.



Partitioning of data. See Oracle Database Concepts for more information about
partitioned data concepts.
Explicitly defined field positions and datatypes.
Loading using the fixed record length option. See Input Data and Datafiles on
page 6-5.

The control file is ulcase8.ctl. It loads the lineitem table with fixed-length
records, partitioning the data according to shipment date.
LOAD DATA
1) INFILE 'ulcase8.dat' "fix 129"
BADFILE 'ulcase8.bad'
TRUNCATE
INTO TABLE lineitem
PARTITION (ship_q1)
2) (l_orderkey position (1:6) char,
l_partkey position (7:11) char,
l_suppkey position (12:15) char,
l_linenumber position (16:16) char,
l_quantity position (17:18) char,
l_extendedprice position (19:26) char,
l_discount position (27:29) char,
l_tax position (30:32) char,
l_returnflag position (33:33) char,
l_linestatus position (34:34) char,
l_shipdate position (35:43) char,
l_commitdate position (44:52) char,
l_receiptdate position (53:61) char,
l_shipinstruct position (62:78) char,
l_shipmode position (79:85) char,
l_comment position (86:128) char)

Notes:

1. Specifies that each record in the datafile is of fixed length (129 bytes in this
example).



2. Identifies the column name and location of the data in the datafile to be loaded
into each column.

Table Creation
In order to partition the data, the lineitem table is created using four partitions
according to the shipment date:
create table lineitem
(l_orderkey number,
l_partkey number,
l_suppkey number,
l_linenumber number,
l_quantity number,
l_extendedprice number,
l_discount number,
l_tax number,
l_returnflag char,
l_linestatus char,
l_shipdate date,
l_commitdate date,
l_receiptdate date,
l_shipinstruct char(17),
l_shipmode char(7),
l_comment char(43))
partition by range (l_shipdate)
(
partition ship_q1 values less than (TO_DATE('01-APR-1996', 'DD-MON-YYYY'))
tablespace p01,
partition ship_q2 values less than (TO_DATE('01-JUL-1996', 'DD-MON-YYYY'))
tablespace p02,
partition ship_q3 values less than (TO_DATE('01-OCT-1996', 'DD-MON-YYYY'))
tablespace p03,
partition ship_q4 values less than (TO_DATE('01-JAN-1997', 'DD-MON-YYYY'))
tablespace p04
)

The datafile for this case, ulcase8.dat, looks as follows. Each record is 128 bytes
in length. Five blanks precede each record in the file.
1 151978511724386.60 7.04.0NO09-SEP-6412-FEB-9622-MAR-96DELIVER IN
PERSONTRUCK iPBw4mMm7w7kQ zNPL i261OPP
1 2731 73223658958.28.09.06NO12-FEB-9628-FEB-9620-APR-96TAKE BACK RETURN



MAIL 5wM04SNyl0AnghCP2nx lAi
1 3370 3713 810210.96 .1.02NO29-MAR-9605-MAR-9631-JAN-96TAKE BACK RETURN
REG AIRSQC2C 5PNCy4mM
1 5214 46542831197.88.09.06NO21-APR-9630-MAR-9616-MAY-96NONE
AIR Om0L65CSAwSj5k6k
1 6564 6763246897.92.07.02NO30-MAY-9607-FEB-9603-FEB-96DELIVER IN
PERSONMAIL CB0SnyOL PQ32B70wB75k 6Aw10m0wh
1 7403 160524 31329.6 .1.04NO30-JUN-9614-MAR-9601 APR-96NONE
FOB C2gOQj OB6RLk1BS15 igN
2 8819 82012441659.44 0.08NO05-AUG-9609-FEB-9711-MAR-97COLLECT COD
AIR O52M70MRgRNnmm476mNm
3 9451 721230 41113.5.05.01AF05-SEP-9629-DEC-9318-FEB-94TAKE BACK RETURN
FOB 6wQnO0Llg6y
3 9717 1834440788.44.07.03RF09-NOV-9623-DEC-9315-FEB-94TAKE BACK RETURN
SHIP LhiA7wygz0k4g4zRhMLBAM
3 9844 1955 6 8066.64.04.01RF28-DEC-9615-DEC-9314-FEB-94TAKE BACK RETURN
REG AIR6nmBmjQkgiCyzCQBkxPPOx5j4hB 0lRywgniP1297

prompt:
sqlplus scott/tiger

SQL> @ulcase8

the system prompt.

SQL*Loader partitions and loads the data, creates the log ﬁle, and returns you
to the system prompt. You can check the log ﬁle to see the results of running the
case study.



File processing option string: "fix 129"


Number to load: ALL
Number to skip: 0
Errors allowed: 50

Table LINEITEM, partition SHIP_Q1, loaded from every logical record.
Insert option in effect for this partition: TRUNCATE

------------------------------ ---------- ----- ---- ---- ---------------------
L_ORDERKEY 1:6 6 CHARACTER
L_PARTKEY 7:11 5 CHARACTER
L_SUPPKEY 12:15 4 CHARACTER
L_LINENUMBER 16:16 1 CHARACTER
L_QUANTITY 17:18 2 CHARACTER
L_EXTENDEDPRICE 19:26 8 CHARACTER
L_DISCOUNT 27:29 3 CHARACTER
L_TAX 30:32 3 CHARACTER
L_RETURNFLAG 33:33 1 CHARACTER
L_LINESTATUS 34:34 1 CHARACTER
L_SHIPDATE 35:43 9 CHARACTER
L_COMMITDATE 44:52 9 CHARACTER
L_RECEIPTDATE 53:61 9 CHARACTER
L_SHIPINSTRUCT 62:78 17 CHARACTER
L_SHIPMODE 79:85 7 CHARACTER
L_COMMENT 86:128 43 CHARACTER

Record 4: Rejected - Error on table LINEITEM, partition SHIP_Q1.
ORA-14401: inserted partition key is outside specified partition










Table LINEITEM, partition SHIP_Q1:


.
.
.

Adding a CLOB column called resume to the table emp
Using a ﬁller ﬁeld (res_file)



Loading multiple LOBFILEs into the emp table

The control file is ulcase9.ctl. It loads new records into emp, including a resume
for each employee. Each resume is contained in a separate file.
LOAD DATA
INFILE *
INTO TABLE emp
REPLACE
FIELDS TERMINATED BY ','
( empno INTEGER EXTERNAL,
ename CHAR,
job CHAR,
mgr INTEGER EXTERNAL,
sal DECIMAL EXTERNAL,
comm DECIMAL EXTERNAL,
deptno INTEGER EXTERNAL,
1) res_file FILLER CHAR,
2) "RESUME" LOBFILE (res_file) TERMINATED BY EOF NULLIF res_file = 'NONE'
)
BEGINDATA
7782,CLARK,MANAGER,7839,2572.50,,10,ulcase91.dat
7839,KING,PRESIDENT,,5500.00,,10,ulcase92.dat
7934,MILLER,CLERK,7782,920.00,,10,ulcase93.dat
7566,JONES,MANAGER,7839,3123.75,,20,ulcase94.dat
7499,ALLEN,SALESMAN,7698,1600.00,300.00,30,ulcase95.dat
7654,MARTIN,SALESMAN,7698,1312.50,1400.00,30,ulcase96.dat
7658,CHAN,ANALYST,7566,3450.00,,20,NONE

Notes:

1. This is a filler field. The filler field is assigned values from the data field to
which it is mapped. See Specifying Filler Fields on page 9-6 for more
information.
2. The resume column is loaded as a CLOB. The LOBFILE function specifies the
field name in which the name of the file that contains data for the LOB field is
provided. See Loading LOB Data from LOBFILEs on page 10-22 for more
information.

Datafiles for Case Study 9
>>ulcase91.dat<<



Resume for Mary Clark

Career Objective: Manage a sales team with consistent record-breaking
performance.
Education: BA Business University of Iowa 1992
Experience: 1992-1994 - Sales Support at MicroSales Inc.
Won "Best Sales Support" award in 1993 and 1994
1994-Present - Sales Manager at MicroSales Inc.
Most sales in mid-South division for 2 years

>>ulcase92.dat<<

Resume for Monica King
Career Objective: President of large computer services company
Education: BA English Literature Bennington, 1985
Experience: 1985-1986 - Mailroom at New World Services
1986-1987 - Secretary for sales management at
New World Services
1988-1989 - Sales support at New World Services
1990-1992 - Salesman at New World Services
1993-1994 - Sales Manager at New World Services
1995 - Vice President of Sales and Marketing at
New World Services
1996-Present - President of New World Services

>>ulcase93.dat<<

Resume for Dan Miller

Career Objective: Work as a sales support specialist for a services
company
Education: Plainview High School, 1996
Experience: 1996 - Present: Mail room clerk at New World Services

>>ulcase94.dat<<

Resume for Alyson Jones

Career Objective: Work in senior sales management for a vibrant and
growing company
Education: BA Philosophy Howard Univerity 1993
Experience: 1993 - Sales Support for New World Services
1994-1995 - Salesman for New World Services. Led in
US sales in both 1994 and 1995.
1996 - present - Sales Manager New World Services. My



sales team has beat its quota by at least 15% each
year.

>>ulcase95.dat<<

Resume for David Allen

Career Objective: Senior Sales man for agressive Services company
Education: BS Business Administration, Weber State 1994
Experience: 1993-1994 - Sales Support New World Services
1994-present - Salesman at New World Service. Won sales
award for exceeding sales quota by over 20%
in 1995, 1996.

>>ulcase96.dat<<

Resume for Tom Martin

Career Objective: Salesman for a computing service company
Education: 1988 - BA Mathematics, University of the North
Experience: 1988-1992 Sales Support, New World Services
1993-present Salesman New World Services

prompt:
sqlplus scott/tiger

SQL> @ulcase9

the system prompt.



SQL*Loader loads the emp table, creates the log ﬁle, and returns you to the
study.



Number to load: ALL
Number to skip: 0
Errors allowed: 50


------------------------------ ---------- ----- ---- ---- ---------------------
EMPNO FIRST * , CHARACTER
ENAME NEXT * , CHARACTER
JOB NEXT * , CHARACTER
MGR NEXT * , CHARACTER
SAL NEXT * , CHARACTER
COMM NEXT * , CHARACTER
DEPTNO NEXT * , CHARACTER
RES_FILE NEXT * , CHARACTER
(FILLER FIELD)
"RESUME" DERIVED * EOF CHARACTER
Dynamic LOBFILE. Filename in field RES_FILE
NULL if RES_FILE = 0X4e4f4e45(character 'NONE')

Table EMP:





.
.
.

Loading a customer table that has a primary key as its OID and stores order
items in a VARRAY.
Loading an order table that has a reference to the customer table and the order
items in a VARRAY.

Note: Case study 10 requires that the COMPATIBILITY parameter
be set to 8.1.0 or higher in your initialization parameter ﬁle.
Otherwise, the table cannot be properly created and you will
receive an error message. For more information about setting the
COMPATIBILITY parameter, see Oracle Database Upgrade Guide.

LOAD DATA
INFILE *
CONTINUEIF THIS (1) = '*'
INTO TABLE customers
REPLACE
FIELDS TERMINATED BY ","
(
CUST_NO CHAR,
NAME CHAR,



ADDR CHAR
)
INTO TABLE orders
REPLACE
FIELDS TERMINATED BY ","
(
order_no CHAR,
1) cust_no FILLER CHAR,
2) cust REF (CONSTANT 'CUSTOMERS', cust_no),
1) item_list_count FILLER CHAR,
3) item_list VARRAY COUNT (item_list_count)
(
4) item_list COLUMN OBJECT
(
5) item CHAR,
cnt CHAR,
price CHAR
)
)
)
6) BEGINDATA
*00001,Spacely Sprockets,15 Space Way,
*00101,00001,2,
*Sprocket clips, 10000, .01,
*Sprocket cleaner, 10, 14.00
*00002,Cogswell Cogs,12 Cogswell Lane,
*00100,00002,4,
*one quarter inch cogs,1000,.02,
*one half inch cog, 150, .04,
*one inch cog, 75, .10,
*Custom coffee mugs, 10, 2.50

Notes:

1. This is a FILLER field. The FILLER field is assigned values from the data field
to which it is mapped. See Specifying Filler Fields on page 9-6 for more
information.
2. This field is created as a REF field. See Loading REF Columns on page 10-14 for
more information.
3. item_list is stored in a VARRAY.
4. The second occurrence of item_list identifies the datatype of each element of
the VARRAY. Here, the datatype is a COLUMN OBJECT.



5. This list shows all attributes of the column object that are loaded for the
VARRAY. The list is enclosed in parentheses. See Loading Column Objects on
page 10-1 for more information.
6. The data is contained in the control ﬁle and is preceded by the BEGINDATA
parameter.

prompt:
sqlplus scott/tiger

SQL> @ulcase10

the system prompt.

SQL*Loader loads the data, creates the log ﬁle, and returns you to the system



Number to load: ALL
Number to skip: 0
Errors allowed: 50



Continuation: 1:1 = 0X2a(character '*'), in current physical record

Table CUSTOMERS, loaded from every logical record.

------------------------------ ---------- ----- ---- ---- ---------------------
CUST_NO FIRST * , CHARACTER
NAME NEXT * , CHARACTER
ADDR NEXT * , CHARACTER

Table ORDERS, loaded from every logical record.

------------------------------ ---------- ----- ---- ---- ---------------------
ORDER_NO NEXT * , CHARACTER
CUST_NO NEXT * , CHARACTER
(FILLER FIELD)
CUST DERIVED REF
Arguments are:
CONSTANT 'CUSTOMERS'
CUST_NO
ITEM_LIST_COUNT NEXT * , CHARACTER
(FILLER FIELD)
ITEM_LIST DERIVED * VARRAY
Count for VARRAY
ITEM_LIST_COUNT

*** Fields in ITEM_LIST
ITEM_LIST DERIVED * COLUMN OBJECT

*** Fields in ITEM_LIST.ITEM_LIST
ITEM FIRST * , CHARACTER
CNT NEXT * , CHARACTER
PRICE NEXT * , CHARACTER
*** End of fields in ITEM_LIST.ITEM_LIST

*** End of fields in ITEM_LIST

Table CUSTOMERS:




Table ORDERS:


.
.
.

In this case study, SQL*Loader loads data from a datafile in a Unicode character set.
This case study parallels case study 3, except that it uses the character set UTF16
and a maximum length is specified for the empno and deptno fields. The data must
be in a separate datafile because the CHARACTERSET keyword is specified. This case
study demonstrates the following:
Using SQL*Loader to load data in the Unicode character set, UTF16.
Using SQL*Loader to load data in a fixed-width multibyte character set.
Using character-length semantics.
Using SQL*Loader to load data in little-endian byte order. SQL*Loader checks
the byte order of the system on which it is running. If necessary, SQL*Loader
swaps the byte order of the data to ensure that any byte-order-dependent data
is correctly loaded.



LOAD DATA
1) CHARACTERSET UTF16
2) BYTEORDER LITTLE
INFILE ulcase11.dat
REPLACE

INTO TABLE emp
3) FIELDS TERMINATED BY X'002c' OPTIONALLY ENCLOSED BY X'0022'
4) (empno INTEGER EXTERNAL (5), ename, job, mgr,
hiredate DATE(20) "DD-Month-YYYY",
sal, comm,
5) deptno CHAR(5) TERMINATED BY ":",
projno,
loadseq SEQUENCE(MAX,1) )

Notes:

1. The character set specified with the CHARACTERSET keyword is UTF16.
SQL*Loader will convert the data from the UTF16 character set to the datafile
character set. This line also tells SQL*Loader to use character-length semantics
for the load.
2. BYTEORDER LITTLE tells SQL*Loader that the data in the datafile is in
little-endian byte order. SQL*Loader checks the byte order of the system on
which it is running to determine if any byte-swapping is necessary. In this
example, all the character data in UTF16 is byte-order dependent.
3. The TERMINATED BY and OPTIONALLY ENCLOSED BY clauses both specify
hexadecimal strings. The X'002c' is the encoding for a comma (,) in UTF-16
big-endian format. The X'0022' is the encoding for a double quotation mark
(") in big-endian format. Because the datafile is in little-endian format,
SQL*Loader swaps the bytes before checking for a match.
If these clauses were specified as character strings instead of hexadecimal
strings, SQL*Loader would convert the strings to the datafile character set
(UTF16) and byte-swap as needed before checking for a match.
4. Because character-length semantics are used, the maximum length for the
empno, hiredate, and deptno fields is interpreted as characters, not bytes.



5. The TERMINATED BY clause for the deptno field is specified using the
character string ":". SQL*Loader converts the string to the datafile character set
(UTF16) and byte-swaps as needed before checking for a match.
See Also:
Handling Different Character Encoding Schemes on page 8-17
Byte Ordering on page 9-39
7782, "Clark", "Manager", 7839, 09-June-1981, 2572.50,, 10:101
7839, "King", "President", , 17-November-1981, 5500.00,, 10:102
7934, "Miller", "Clerk", 7782, 23-January-1982, 920.00,, 10:102
7566, "Jones", "Manager", 7839, 02-April-1981, 3123.75,, 20:101
7499, "Allen", "Salesman", 7698, 20-February-1981, 1600.00, 300.00, 30:103
7654, "Martin", "Salesman", 7698, 28-September-1981, 1312.50, 1400.00, 30:103
7658, "Chan", "Analyst", 7566, 03-May-1982, 3450,, 20:101

prompt:
sqlplus scott/tiger

SQL> @ulcase11

This prepares the table emp for the case study and then returns you to the
system prompt.

SQL*Loader loads the table emp, creates the log file, and returns you to the
study.



The following shows a portion of the log ﬁle for case study 11:
Character Set utf16 specified for all input.
1) Using character length semantics.
2) Byteorder little endian specified.
Processing datafile as little endian.
3) SQL*Loader running on a big endian platform. Swapping bytes where needed.



Number to load: ALL
Number to skip: 0
Errors allowed: 50


------------------------------ ---------- ----- ---- ---- ---------------------
4) EMPNO FIRST 10 , O(") CHARACTER
ENAME NEXT * , O(") CHARACTER
JOB NEXT * , O(") CHARACTER
MGR NEXT * , O(") CHARACTER
4) HIREDATE NEXT 40 , O(") DATE DD-Month-YYYY
SAL NEXT * , O(") CHARACTER
COMM NEXT * , O(") CHARACTER
DEPTNO NEXT 10 : O(") CHARACTER
4) PROJNO NEXT * , O(") CHARACTER
LOADSEQ SEQUENCE (MAX, 1)

Table EMP:




.
.
.

Notes:

1. SQL*Loader used character-length semantics for this load. This is the default if
the character set is UTF16. This means that length checking for the maximum
sizes is in characters (see item number 4 in this list).
2. BYTEORDER LITTLE was specified in the control file. This tells SQL*Loader that
the byte order for the UTF16 character data in the datafile is little endian.
3. This message only appears when SQL*Loader is running on a system with the
opposite byte order (in this case, big endian) from the datafile's byte order. It
indicates that SQL*Loader detected that the byte order of the datafile is
opposite from the byte order of the system on which SQL*Loader is running.
Therefore, SQL*Loader had to byte-swap any byte-order-dependent data (in
this case, all the UTF16 character data).
4. The maximum lengths under the len heading are in bytes even though
character-length semantics were used. However, the maximum lengths are
adjusted based on the maximum size, in bytes, of a character in UTF16. All
characters in UTF16 are 2 bytes. Therefore, the sizes given for empno and
projno (5) are multiplied by 2, resulting in a maximum size of 10 bytes.
Similarly, the hiredate maximum size (20) is multiplied by 2, resulting in a
maximum size of 40 bytes.

Loaded Tables for Case Study 11
To see the results of this execution of SQL*Loader, execute the following query at
the SQL prompt:



SQL> SELECT * FROM emp;

The results of the query look as follows (the formatting may be slightly different on
your display):
EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO PROJNO LOADSEQ
------ ------ --------- ----- --------- -------- ----- ------- ------ --------
7782 Clark Manager 7839 09-JUN-81 2572.50 10 101 1

7839 King President 17-NOV-81 5500.00 10 102 2

7934 Miller Clerk 7782 23-JAN-82 920.00 10 102 3

7566 Jones Manager 7839 02-APR-81 3123.75 20 101 4

EMPNO ENAME JOB MGR HIREDATE SAL COMM DEPTNO PROJNO LOADSEQ
------ ------ --------- ----- --------- -------- ----- ------- ------ --------

7499 Allen Salesman 7698 20-FEB-81 1600.00 300 30 103 5

7654 Martin Salesman 7698 28-SEP-81 1312.50 1400 30 103 6

7658 Chan Analyst 7566 03-MAY-82 3450.00 20 101 7

7 rows selected.

The output for the table is displayed in the character set US7ASCII, which is the
normal default character set when the NLS_LANG parameter is not deﬁned.
SQL*Loader converts the output from the database character set, which normally
defaults to WE8DEC, to the character set speciﬁed for your session by the NLS_
LANG parameter.


Sqlldr examples

More Related Content

What's hot (20)

Similar to Sqlldr examples (20)

Recently uploaded (20)

Sqlldr examples