Database Utilities (MOSC)

MOSC Banner

Inefficient SQL*Loader Process

in Database Utilities (MOSC) 3 commentsAnswered
Hello. I am looking at an existing process that uses SQL*Loader to load a file into 3 different tables. The file format is below, and consists of 3 distinct record types - CDR, PTY and CHG.

CDR|col1|col2|
PTY|col3|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|
PTY|col3|
CHG|col4|col5|
CHG|col4|col5|
PTY|col3|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|
CHG|col4|col5|

The objective of the file load is to put rows into the table loaded for each CHG row, but the table contains the columns from the CDR and PTY rows. To do this, the original developer ( from 20+ years ago ) created tables for the CDR and PTY rows and used before and after row triggers to populate the columns when the CHG rows are inserted. In order to achieve this, the "rows=1" parameter has been set, which commits after each insert. It is now taking ages to load a 24K row file due to resource constraints on the

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center