Just a word or warning, 'cos we've fell foul of something that's caused us to lose data !

We've been happilly loading data using nzload with the maxerrors options set to 0, believing this meant that nzload should fail if any errors were encountered.

However with maxerrors set to 0 nzload is indicating a successful load (i.e. no error messages or nonzero exit codes from nzload) even if records have failed to load successfully, in our case because the input data for a column was larger than the column size in the table being loaded.

In fairness, the documentation does not indicate that 0 is a valid value, but I have raised an incident with support to request that nzload should not accept the value 0 if it is not valid, or it should treat 0 the same as 1, where 1 is documented as causing nzload to fail if at least 1 error is encountered.

I believe that treating 0 as allowing errors is very dangerous, since in our case it caused us to inadvertantly lose data.

I just wanted to post this here to make everyone else aware to make sure you don't make the same mistake as us