The sections that follow describe the files created by diagnostic data collection.
Tracking log file
The first file created is the diagnostic event tracking log file. By default, this file is created in the database directory. You can change the location of the tracking log file using one of the following methods:
Specify the directory at startup with -diagDir.
Change the value while the database is online with PROMON.
Change the value while the database is online by updating the value of the _dbparams VST field for the -diagDir parameter.
By default, the event tracking file is named, diagEvent_Tracking.csv. If you specify JSON as your output format, the file is named diagEvent_Tracking.json. You can change the file prefix (diagEvent_) using one of the following methods:
Specify the prefix at startup with -diagPrefix.
Change the value while the database is online with PROMON.
Change the value while the database is online by updating the value of the _dbparams VST field for the -diagPrefix parameter.
Event sub-directory
When a triggering event occurs, and the level is non-zero, a sub-directory is created to hold the event-specific files. The sub-directory name is constructed as follows:
The eventid is the combination of the event and an identifier. The event is the name of a triggering event, or _DbStatus to indicate that the data is being collected by a directive, and not an event. The identifier is an increasing number, that starts from 1, each time the database is brought online.
Lock table event files
For the lock table overflow triggering event, the following files are created for CSV output format, based on the level specified. For JSON output, only one file is created.
Summary (level 1)
Filename
Contents
prefixlocktable_summary.csv
Pid of all users with lock table entries, and a summary of locks held (_usrlock VST data)
Summary and detail (level 2)
Filename
Contents
prefixlocktable_summary.csv
Pid of all users with lock table entries, and a summary of locks held (_usrlock VST data)
prefixlocktable_detail.csv
Contents of the _lock VST by user
prefixtransaction_detail.csv
Contents of the _trans VST by user
BI threshold event files
For the BI threshold triggering event, the following files are created for CSV output format, based on the level specified. For JSON output, only one file is created.
Summary (level 1)
Filename
Contents
prefixBILogging_summary.csv
The size of each BI file
Cluster size and BI block size
Oldest transaction id
All Pids with an active transaction
Summary and detail (level 2)
Filename
Contents
prefixBILogging_summary.csv
The size of each BI file
Cluster size and BI block size
Oldest transaction id
All Pids with an active transaction
prefixBILogging_detail.csv
Contents of the _logging VST
prefixtransaction_detail.csv
Contents of the _trans VST by user
Syserror event files
For the syserror triggering event, the following file is created for CSV output format. The files are the same, regardless of the level. For JSON output, only one file is created.
Pid of all users with lock table entries, and a summary of locks held (_usrlock VST data)
1 The file contents are the same as those provided during lock table overflow, so the same file name is used.
DiagComplete file
The DiagComplete file is not a data file, but a processing indicator. When a triggering event occurs, you can specify an amount of time to pause after collecting the data and processing the event. If you want to cut the pause time short, create a DiagComplete file in the event sub-directory. When the presence of this file is detected, the pause is ended, regardless of remaining time.
Specify the directory at startup with -diagDir.