Database audit files

Edit online

Additional troubleshooting and diagnostic information is available in the database adapter audit. Use the Audit adapter command (-AUDIT) to create a file that records the adapter activity for each specified database activity. This command can be used for a source or target, or in a DBLOOKUP, DBQUERY, GET, or PUT function. This adapter command can be specified for individual input and output cards on a card-by-card basis or, optionally, as a global audit that encompasses all database activity for the entire map.

The default is to produce a file named audit.dbl in the directory in which the map is located. Optionally, you can append the audit information to an existing file or specify a name or the full path for the file. For more information, see the Resource Adapters documentation.

The database adapter audit file provides the following details for each database access:

  • Execution Time (Audit Time)

    This is the amount of clock time (in seconds) the database adapter takes to execute the database action (for example, the retrieval of all rows for a data source, a single instance of aDBLOOKUP function, and so on).

  • Adapter Return Code (AC)

    This is the adapter return code as a result of executing the database action.

  • Connection

    This information identifies the connection used for each database action. This can be helpful in determining ways to configure your map to minimize the number of database connections that must be made.

  • Map Name (Map)

    This is name of the compiled map file.

  • Access Type (Input Card, Function, or Output Card)

    This information identifies the type of database action (for example, whether the type is for an input card, output card, or for a DBLOOKUP, DBQUERY, GET, or PUT function).

  • Additional Information

    This information is provided (when appropriate) for each database action such as the SQL statement associated with an input card, the name of the table or stored procedure for a database target, or the SQL statement executed by any of the functions for interfacing with data in a database (for example, DBLOOKUP, DBQUERY, PUT, and GET).