Skip to main content

DIAGNOSTICS REPLICATE

Use  DIAGNOSTICS REPLICATE to identify replication failures

Abstract

Replication Manager provides direct administrator control from your web browser for remote configuration, management, and monitoring. Quickly log in and check the status of multiple replication environments from a central location. An embedded web browser serves up all replication data and access to central troubleshooting logs.

The configuration option DIAGNOSTICS REPLICATE enables FairCom DB to log messages to CTSTATUS.FCS when a file that is being created or opened matches the filename specified for the REPLICATE keyword, and it does not meet replication requirements. This is useful in the initial setup to determine unexpected replication failures.

Example 1. Sample output

The SetSystemConfigurationOption() API function can be used to turn this diagnostic option on and off at run time.

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: None of the indexes for the file mark.dat qualify as a replication unique key:

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: index 1 is not unique

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: index 1 supports null keys

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: index 2 is not unique

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: index 3 is not unique

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: index 3 supports null keys

Mon Apr 09 10:48:21 2012

 - User# 00014  REPLICATE_DIAG: index 3 contains a SRLSEG segment