This page (revision-3) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
3 26-Nov-2021 10:22 3 KB JEscott to previous
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 42 added 23 lines
If you are using SQL Loader as your feeder program, there are certain considerations that must be made for the ASCII file that the SQL Loader program will read.
You may stop providing fields at any point after the mandatory fields are provided, as all subsequent fields in the file will be treated as NULL.
Dates must be provided in the date format DD-Mon-YYYY unless you override the default date format in the SQL*Loader control file.
The control file provided separates fields by commas, and fields may be enclosed in quotes.
If a field contains a comma (such as names or descriptions) then that field MUST be enclosed within quotes.
If you place two commas beside each other (,,) then the field in the middle is treated as NULL. This has the same effect as placing double quotes beside each other (,””,).
Effective date files may leave the EXPIRY date null, and it will default to the “end of time” date.
Effective date files may leave the EFFECTIVE date null, and it will default to the “beginning of time” date.
Effective date files that have records with different effective dates will cause “date-splitting” to occur.
If you are unable or unwilling to create a comma-delimited file, you may modify the supplied control file in accordance with instructions found in the Oracle Utilities reference manual.
See the [Using SQL Loader|USING SQL LOADER] page for more information on the SQL LOADER utility.