Re: SQL Loader - Direct path loading of a sequence number

I found the following the in 10g Utilities manual Ch 11 Conventional and Direct Path Loads section Restrictions on Using Direct Path Loads. Notice the last restriction.

>>

The following conditions must be satisfied for you to use the direct path load method:

Tables are not clustered.

Tables to be loaded do not have any active transactions pending.

To check for this condition, use the Oracle Enterprise Manager command MONITOR TABLE to find the object ID for the tables you want to load. Then use the command MONITOR LOCK to see if there are any locks on the tables.

For versions of the database prior to Oracle9i, you can perform a SQL*Loader direct path load only when the client and server are the same version. This also means that you cannot perform a direct path load of Oracle9i data into a database of an earlier version. For example, you cannot use direct path load to load data from a release 9.0.1 database into a release 8.1.7 database.

Beginning with Oracle9i, you can perform a SQL*Loader direct path load when the client and server are different versions. However, both versions must be at least release 9.0.1 and the client version must be the same as or lower than the server version. For example, you can perform a direct path load from a release 9.0.1 database into a release 9.2 database. However, you cannot use direct path load to load data from a release 10.0.0 database into a release 9.2 database.

The following features are not available with direct path load:

Loading a parent table together with a child table

Loading BFILE columns

Use of CREATE SEQUENCE during the load. This is because in direct path loads there is no SQL being generated to fetch the next value since direct path does not generate INSERT statements. <<

Use a conventional load.
HTH -- Mark D Powell -- Received on Wed May 17 2006 - 09:02:35 CDT