Data Transformation Engine Database Interface Designer Reference Guide
Chapter 10 - Debugging and Viewing Results Database Audit Files
Database Interface Designer Reference Guide
164
♦ on the command line or in a command file. (Refer to the following example.)
The rejected record(s) is/are saved in the file specified with the
-BADDATA adapter
command (badstuff.txt in this example).
When the
-BADDATA adapter command is used and one or more rows are rejected,
the database adapter returns an adapter return code of 1 with a message of One
or more records could not be processed as shown in the following
TargetReport excerpt in the execution summary section:
<TargetReport card="1" adapter="DB" bytes="1218" adapterreturn="1">
<Message>One or more records could not be processed</Message>
<TimeStamp>22:07:32 July 9, 2001</TimeStamp>
</TargetReport>
Database Audit Files
Additional troubleshooting and diagnostic information is available in the database
adapter audit. Use the Audit adapter command (
-AUDIT) to create a file that
records the adapter activity for each specified database activity. This command can
be used for a source or target, or in a
DBLOOKUP, DBQUERY, GET, or PUT function.
This adapter command can be specified for individual input and output cards on a
card-by-card basis or, optionally, as a global audit that encompasses all database
activity for the entire map.
The default is to produce a file named audit.dbl in the directory in which the map
is located. Optionally, you can append the audit information to an existing file or