OID file / load nonrecoverable failing with full transaction log

[Justin]

I noticed several OID files that seemed to correspond to load
failures.

The OID files were located at ./userid/NODE0000/SQL0001/load/
DB200015.PID

Are these important and can they be deleted? The total disk space
used by the OID's is 38 Gig.

Is this related to execution of a load nonrecoverable?

When running this command:

db2 "load from <file>.ixf of ixf insert into <db table>
nonrecoverable"

It results in transaction log full. This is supposed to be a non-
logged transaction.

[Frederik Engelen]

Most logging happens either at the delete phase or at the index
creation phase. Usually the delete phase is the culprit. Check for any
unique constraints that you might have on that table that may cause a
large part of the records to be deleted. The delete phase is also
visible in the monitoring commands.

If I'm correct, buiding the indexes after a load is done in a single
transaction. If you drop those indexes beforehand, you have the choice
to create them in multiple transactions afterwards. If you have that
luxury of course...

Can't help you with those files off the top of my head.

--
Frederik Engelen