Database trace for a source with errors

The example in the preceding section provided database trace information for a database source with no problems. The following is an example of information you may see when there are errors while accessing the database source.

Database type is Oracle
Status returned to engine: (0) Success
No existing connection was found.
Connection to Oracle has been established.
Interface library version 6.0(140)
Data being retrieved for input card 1.
Database adapter version 6.0(140)
Starting a database unload...
Host string: 
Userid     : demo
Password   : ****
Query      : SELECT * FROM BONUSS
Query size : 20
Output is to a buffer.
Error in: oparse

               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 withQuery) 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.