Log File Naming

Restriction: This topic applies to Windows environments only.

Each time a location is created the XDB Server logging system creates a file named anchor.log. This file holds information on how to recover the location after a transient system failure or media failure. As work commences in the location, the logging system automatically creates a second log file named a0000000.log, which records all current transaction information necessary for transient system failure recovery.

A series of log files (beginning with a0000000.log) are automatically created by the logging system to record all data table changes since the location was created (or since logging was reset for that location). Log files are named automatically by the system according to the following convention:

xyyyyyyy.log

where the x prefix is a letter of the alphabet, and each y represents a digit of a hexadecimal number (seven digits long). The first in the series of log files built is always named a0000000.log, with the hexadecimal portion of each subsequent log file name indexed upward by one (for example, a0000001.log, a0000002.log, etc.).