Data Transformation Engine Database Interface Designer Reference Guide

Chapter 10 - Debugging and Viewing Results Database Trace Files

Database Interface Designer Reference Guide

155

The remaining lines in the database trace file display information about the

disposition of the entire database card transaction. The transaction failed after one

row was inserted. The database adapter returns an error code of -9 to the Event

Server with a corresponding error message of Failed to execute the SQL

statement. If you produced the audit log, you would see the following line in the

execution summary section:

<Message>Failed to execute the SQL statement</Message>

</TargetReport>

Subsequently, the database trace file communicates that the database adapter is

cleaning up and closing the transaction. Because the OnFailure setting was set to

Rollback for this output card, the final entry in the database trace reveals that the

transaction rollback was successful.

Database Trace for a Target - Using the Bad Data Adapter Command

(-BADDATA)

Use the Bad Data adapter command (-BADDATA) 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 that you specify and processing

continues.

The following database trace example was produced using the same map and data

as in the preceding example, now additionally using

-BADDATA.

Error in: oexec

Message : ORA-01400: cannot insert NULL into ("EVENTMGT"."MEMBERSHIP"."LASTNAME")

The following values were being inserted:

Column 1 MEMBERID : D190-0002

Column 2 FIRSTNAME : Leverling

Column 3 LASTNAME : NULL