Data Transformation Engine Database Interface Designer Reference Guide

Chapter 10 - Debugging and Viewing Results Database Trace Files
Database Interface Designer Reference Guide
151
Message : ORA-00942: table or view does not exist
Retrieved 0 records (0 bytes).
Error returned to engine: (-17) Failed to parse SQL statement
Cleaning up and closing the transaction...
The transaction was successfully committed.
Status returned to engine: (0) Success
Commit was successful.
Database disconnect succeeded.
The key information in the database trace is in the line defining the query
(beginning with Query) and the four lines beginning with the Error in: line. In
this example, the attempt to execute the query failed because the table specified
in the query listed does not exist. This would result in a map return code of 12 and
a message of:
Source not available
Upon receiving this error, verify that the query is correct and that the table
referenced in the query exists using the Database Interface Designer or the SQL
command tool provided with your database.
Database Trace for a Valid Target
The information included in the database trace for an output (data target) is similar
to that for a database source. The following example shows the PUT > Target
settings for the first output card (which is a database) in a map called
UpdateMembershipDB.
The Update adapter command (
-UPDATE) specifies that the rows produced by the
map should update existing rows or should insert new rows, based upon the
update keys configured for the table in the Database Interface Designer. The Trace
adapter command (
-TRACE) generates the database trace information for this
output card.