Data Transformation Engine Database Interface Designer Reference Guide
Chapter 10 - Debugging and Viewing Results Viewing Database Source and Target Data
Database Interface Designer Reference Guide
163
<TimeStamp>01:02:00 July 9, 2001</TimeStamp>
</SourceReport>
<SourceReport card="3" adapter="DB" bytes="0" adapterreturn="-9">
<Message>Failed to execute the SQL statement</Message>
<TimeStamp>01:02:00 July 9, 2001</TimeStamp>
</SourceReport>
Use this information to determine whether the query defined for input card 3
references a table or view that does not exist.
Viewing Database Source and Target Data
When debugging a map that uses database sources or targets, you cannot view
the database source or target data in the Map Designer by selecting Run Results
from the View menu. Because the data retrieved from a database for an input or
written to a database as an output is a snapshot of the data at a given time, it is
not available to the Map Designer after the map runs.
However, you can use Backup settings to capture the data retrieved from or
written to the database for debugging purposes.
Using Backup Settings
Backup settings are used to determine when, where, and how the data for a
specific card should be copied to a specified backup file. These settings are
configured in the Input Card and Output Card settings in the Map Designer and
the Event Server or in Command Settings for the Integration Flow Designer. For
more information about these settings, refer to the Map Designer Reference Guide.
Capturing Data Not Processed
The Bad Data adapter command (-BADDATA) can be used for a target (or in a PUT
function). If any inserts, updates, or procedure calls fail to execute, the data that
could not be processed is written to a file you specify and processing continues.
The
-BADDATA command can be specified:
♦ as part of the PUT > Target > Command setting for a card target
♦ as part of the command line for a database target referenced in a
RUN or PUT
function