Data Transformation Engine Database Interface Designer Reference Guide

Database Interface Designer Reference Guide
144
Chapter 10 - Debugging and Viewing
Results
This chapter explains various troubleshooting tools available when you encounter
problems using database objects as data sources or targets for a map or when
using the Database Interface Designer to define databases and queries. Also
presented are various methods for viewing data extracted from a database or
loaded into a database.
Troubleshooting Tools
If you receive an error while attempting to generate a type tree in the Database
Interface Designer or if you run a map that uses database sources and/or targets
and receive a runtime error or do not get the expected output, use any or all of the
following troubleshooting tools:
♦ map audit log (map_name.log)
For information about the map audit log and related settings, refer to
Chapter 16 in the Map Designer Reference Guide.
♦ Database Interface Designer trace (mdq_file_name.dbl)
♦ database execution trace file (map_name.dbl)
♦ database source and target data
♦ database audit file (audit.dbl)
♦ DBMS trace utilities and SQL command tools
Database Trace Files
Use the information contained in database trace files (.dbl) as one of the primary
tools to assist in troubleshooting. These files contain detailed information
generated during Database Interface Designer activity and also during map
execution. For example:
♦ The trace file recorded for a Database Interface Designer trace contains
information about the activities taking place when generating type trees such as
database connections, SQL statements executed, and so on.