Examples of trace logging

For example, if a Db2 Universal Database instance "dbinst02" is running on computer "server01", the RAS log file for the DB2® agent might be named as follows:

server01_ud_dbinst02_kudcma_437fc59-01.log

For long-running programs, the nn suffix is used to maintain a short history of log files for that startup of the program. For example, the kudcma program might have a series of log files as follows:

server01_ud_dbinst02_kudcma_437fc59-01.log
server01_ud_dbinst02_kudcma_437fc59-02.log
server01_ud_dbinst02_kudcma_437fc59-03.log

As the program runs, the first log (nn=01) is preserved because it contains program startup information. The remaining logs "roll." In other words, when the set of numbered logs reach a maximum size, the remaining logs are overwritten in sequence. Each time a program is started, a new timestamp is assigned to maintain a short program history. For example, if the Db2 agent is started twice, it might have log files as follows:

server01_ud_dbinst02_kudcma_437fc59-01.log
server01_ud_dbinst02_kudcma_437fc59-02.log
server01_ud_dbinst02_kudcma_437fc59-03.log

server01_ud_dbinst02_kudcma_537fc59-01.log
server01_ud_dbinst02_kudcma_537fc59-02.log
server01_ud_dbinst02_kudcma_537fc59-03.log

Each program that is started has its own log file. For example, the Db2 agent would have agent logs in this format:

server01_ud_dbinst02_kudcma_437fc59-01.log

Other logs, such as logs for collector processes and Take Action commands, have a similar syntax, as in the following example:

server01_ud_dbinst02_kudBackupDatabase_447fc59-01.log

where kudBackupDatabase is the name of a program.