dbload command log files

There are two dbload command log files: *.log and *.bad.

Note: Note that when running dbload that is in a Db2 Warehouse container (docker exec -it Db2wh dbload ...), the log file is saved within this container.

The system appends to the *.log file for every dbload command that loads the same table into the same database. The system names the log file according to the table and the database names and uses the extension .log. Consider the following example:

dbload -u admin -pw password -t member_profile -db dev -schema sales -maxErrors 10 -delim '\t'

In this example, the file name is dev.sales.member_profile.log. The -maxErrors option allows the dbload command to continue processing until 10 errors are found. The -delim '\t' option specifies the TAB delimiter.

The *.bad file contains any record that had an error. In the case of the previous sample command, the file name is dev.sales.member_profile.bad. Unlike the system behavior for the *.log file, the system overwrites the *.bad file each time that you run the dbload command for the same table and database name.

Tip: dbload follows the nzsql naming convention for log files: <database>.<schema>.<table>.<log|bad>, and not the Db2 Warehouse external tables naming convention.