Re: Does table trigger fire on SQLLoader DIRECT load?

Kelly,

This is pasted in from the Oracle8 online docs for SQL*LOADER:

Table insert triggers are also disabled when a direct path load begins. After the rows are loaded and indexes rebuilt, any triggers that were disabled are automatically re-enabled. The log file lists all triggers that were disabled for the load. There should not be any errors re-enabling triggers.

Unlike integrity constraints, insert triggers are not reapplied to the whole table when they are enabled. As a result, insert triggers do not fire
for any rows loaded on the direct path. When using the direct path, the application must ensure that any behavior associated with insert triggers is carried out for the new rows.

kgrigg_at_acxiom.com wrote:
>
> Hello all!
> I am using SQL Loader 8.0 to load a table on an Oracle 8 server. This
> table has an after insert trigger that put data into 2 other tables based
> on the values inserted into it. I have had this work successfully using
> SQL Loader using the 'conventional' method. I tried it using the DIRECT
> method to try to speed things up, but, it doesn't appear that the trigger
> fired....can you make it work using the direct method or do I just have to
> stick with the conventional method?
>
  Received on Tue Oct 14 1997 - 00:00:00 CDT