The RMS provides a tracing feature to assist the user when troubleshooting problems. Information about the internal workings of the RMS will be written to the RMS log file.
Table 10-1 lists trace flags that are useful when troubleshooting problems in the RMS.
Trace flags |
Description |
|---|---|
trace RMS_Command on |
Writes to the error log every command RMS receives. Commands can be sent from the RM plug-in, an isql session, or some other client application. This flag is useful in finding the command that caused a specific problem. |
trace Server_Command on |
Writes to the error log every command RMS sends to a monitored server. Use this flag to determine how RMS retrieves information about the replication environment. |
trace Startup on |
Adds trace messages to the RMS log file at each step of the start-up process. Use this flag to diagnose UAF start-up problems. |
trace Network_Connection on |
Adds trace messages to the RMS log file whenever a connection to a server is created. The RMS will include all connection information except the password in the trace message. Use this flag to trace network connection errors. |
The user controls the type of information that is logged by setting trace flags in the RMS. For information on the RMS trace commands and a complete list of the trace flags, see the Replication Server Reference Manual.
