Monitoring and Troubleshooting with Trace Logs

DataCaster enables tracing of program activity to help debug problems and track issues. This trace facility is meant to be used infrequently and has a significant adverse impact on performance, and may even lead to program failure if used improperly.

Tracing for each module can be enabled at an appropriate level that generates more or less data. The higher the trace level, the more data is generated in the trace logs. Trace logs can be found in the database trace sub-directory within each database's main directory.

Extreme care must be taken in using trace files in production systems since a tremendous amount of data can be generated in a very short time. This can quickly fill up the disk and cause your application and DataCaster to fail.

Trace can be enabled either via the trace.xml configuration file in the db sub-directory of the configuration directory, or via the WebAdmin tool, which allows changing the trace level while the server is running.

Trace levels can also be changed for individual transactions via the Transaction interface. This provides some of the trace messages for specific transactions. Currently only transaction and some of the BUFFER and SQL messages use the transaction-specific trace level.

Trace Log Information

The following provides some details on some of the information logged in trace files.

• Transaction Trace Information
• BTree Trace Information
• Buffer Trace Information
• SQL Trace Information
• Transaction Log Trace Information
• Recovery Trace Information
• System Catalog Trace Information
• Network Message Trace Information