Kevin Knaus wrote:

> Why does my transaction log fill up, (there are 15, 4 meg primary logs),
> during an unrecoverable LOAD, during the DELETE phase? And what is the
> DELETE phase? There are two indexes defined on the table being loaded
> and they are being built at the end of the LOAD.

After the load tool adds the file to the table (using under-the-covers
apis, rather than sql) it checks for constraint violations (type,
length, whatever). These violations are deleted with standard sql.

If you've got a bad load file (offsets wrong, values wrong, whatever) it
can take almost forever for the load tool to complete: the deletes are
slow as heck compared to the load. And they use the logs.

To get around this I usually set warninglimit to 1 - so that a single
invalid row will cancel the entire load, and have added a last step to
our etl processes to perform pretty bullet-proof checking of the
validity of the data file.

ken

DB2 & UDB email list listserv db2-l LazyDBA home page