Apress.Expert.Oracle.Database.Architecture.9i.and.10g.Programming.Techniques.and.Solutions.Sep.2005

662
CHAPTER 15 ■ DATA LOADING AND UNLOADING
INSERT INTO DEPT ( DEPTNO, DNAME, LOC, LAST_UPDATED, ENTIRE_LINE )
VALUES ( :DEPTNO, :DNAME, :LOC, :LAST_UPDATED, :ENTIRE_LINE );
It would then parse the input stream, assigning the values to its bind variables, and then
execute the statement. When you begin to use functions, SQLLDR incorporates them into its
INSERT statement. In the preceding example, the INSERT statement SQLLDR builds will look
like this:
INSERT INTO T (DEPTNO, DNAME, LOC, LAST_UPDATED, ENTIRE_LINE)
VALUES ( :DEPTNO, upper(:dname), upper(:loc), :last_updated,
:deptno||:dname||:loc||:last_updated );
It then prepares and binds the inputs to this statement, and executes it. So, pretty much
anything you can think of doing in SQL, you can incorporate into your SQLLDR scripts. With
the addition of the CASE statement in SQL, doing this can be extremely powerful and easy. For
example, say your input file could have dates in the following formats:
• HH24:MI:SS: Just a time; the date should default to SYSDATE.
• DD/MM/YYYY: Just a date; the time should default to midnight.
• HH24:MI:SS DD/MM/YYYY: The date and time are both explicitly supplied.
You could use a control file like this:
LOAD DATA
INFILE *
INTO TABLE DEPT
REPLACE
FIELDS TERMINATED BY ','
TRAILING NULLCOLS
(DEPTNO,
DNAME "upper(:dname)",
LOC
"upper(:loc)",
LAST_UPDATED
"case
when length(:last_updated) > 9
then to_date(:last_updated,'hh24:mi:ss dd/mm/yyyy')
when instr(:last_updated,':') > 0
then to_date(:last_updated,'hh24:mi:ss')
else to_date(:last_updated,'dd/mm/yyyy')
end"
)
BEGINDATA
10,Sales,Virginia,12:03:03 17/10/2005
20,Accounting,Virginia,02:23:54
30,Consulting,Virginia,01:24:00 21/10/2005
40,Finance,Virginia,17/8/2005