Message Logging
When a Replicator Server starts, it creates three log files:
replicat.log
The replicat.log file contains Replicator Server messages. This file writes its buffers after every message is logged, allowing you to see the latest logged messages in real time. Messages are appended to this file from run to run.
print.log
The print.log file contains information that normally goes to the standard output (stdout), such as error output from the DBMS Server. This file contains Replicator Server messages at its specified logging level. This file gets initialized from run to run.
Unlike replicat.log, it is possible that the print.log does not contain the latest error messages.
Note: The print.log is not created on Microsoft Windows.
commit.log
The commit.log file is the two-phase commit recovery log for the Replicator Server. This file must not be manipulated because it contains information to resolve leftover willing-to-commit transactions. If the server has been shut down cleanly and there are no willing-to-commit transactions, it is safe to delete this file. Otherwise, do not delete it. This file is initialized from run to run, unless there are incomplete two-phase commit transactions, in which case they are recovered first.
Periodically, you must shut down the servers to clean out the log files.
The Log Level (-LGL) flag controls which messages get written to the replicat.log file, while the Print Logging Level (-PTL) flag controls the messages written to the print.log. Both the -PTL and -LGL flags share various settings that indicate the message levels that are logged.
The message levels that require attention are the Level 1 error messages and the Level 3 warning messages. You are advised to set the -LGL flag to receive Level 1 through Level 3 messages.
Message Logging Levels
Message logging levels 0 through 3 are as follows.
Note: Message Levels 4 and 5 are reserved for internal use only and can be set at the request of Customer Support to troubleshoot your system.
0
SILENT
Logs no messages.
Note: The exception is DBMS Server error messages, for example, informing users of deadlock. The server continues to channel these messages to the standard output (stdout).
1
Logs ERRORS
Errors are any occurrence that causes the Replicator Server to alert you to take some action. Error messages include configuration, timeout, transmission, and fatal errors such as the inability to replicate, the issuance of an invalid database event, or the inability to complete a distributed transaction.
2
Logs ERROR and INFORMATIONAL messages
Informational messages provide normal server status information such as startup, shutdown, and the setting of flags.
3
(Default) Logs ERROR, INFORMATIONAL, and WARNING messages
Warning messages convey some information about a problem or identify an unusual situation that requires your attention, for example, an invalid startup flag in the configuration file.