Re: SQL*Loader and Sequencing multiple tables

When I have had to convert data from one system into oracle, I create a junk tables containing the old data with the key which connected the data.

The Junk tables contains a column to hold the new sequence key. I then update the junk tables with the new sequence number. Then insert the junk table columns
into the target table using the new sequence key.

mcall_at_signalnet.com wrote:
: This problem relates to SQL*Loader and sequencing in multiple tables.

: I have a 400 byte input file I am trying to load into Oracle. The majority of
: the data will be placed in table 1 creating a sequence(max, 1). The second
: table should have the same sequence number from table 1 as a reference.
: (Primary key in table 1, foreign key in table 2).

: I have tried this with the 'field sequence(max, 1)' and 'field sequence(max,
: 0)' to no avail. The documentation stipulates that this is a common practice
: which I am very well aware, but shows no examples of how this is handled. We
: are running out of alternatives in that dealing with the sub-table(s) might
: have to lose the reference of the sequence number from the parent table,
: however, this to me is not good database design.

: -----== Posted via Deja News, The Leader in Internet Discussion ==-----
: http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum

--
While DSC may claim ownership of all my ideas (on or off the job),
DSC does not claim any responsibility for them. Warranty expired when you
opened this article and I will not be responsible for its contents or use.