Use this information to troubleshoot
multiple data center configurations, including linking between catalog
service domains.
Procedure
Problem: You need to determine
if data replication is synchronized across container servers and catalog
service domains. Solution: Run the xscmd
-c showReplicationState or xscmd.sh -c showDomainReplicationState command.
These commands display information about the status of replication
in the environment. For more information, see Monitoring with the xscmd utility.
Problem: You need to check which
catalog service domains are linked to your local catalog service domain. Solution: Run the xscmd -c showLinkedDomains command.
This command lists the foreign catalog service domains that are linking
to the local catalog service domain.
Problem: You want to detect any
configuration problems with your primary shard links to catalog service
domains, without going through the entire output of the xscmd
-c showLinkedPrimaries command. Solution: Use
the
-hc or the
--linkHealthCheck option
with this command. For example,
xscmd -c showLinkedPrimaries
-hc or
xscmd -c showLinkedPrimaries --linkHealthCheck.
The command verifies that the primary shards have the appropriate
number of catalog service domain links. The command lists any primary
shards that have the wrong number of links. If they are all linked
correctly (for example, your domain is linked to 1 other domain, then
all of the individual primary shards are expected to have 1 link),
you will get a message saying they are linked:
CWXSI0092I: All primary shards for {0} data grid and {1} map set have the correct number of links
to foreign primary shards.
If you discover problems, try
some of the following possible solutions:
- Review your network and firewall settings to ensure that the servers
that are hosting container servers in the domains can communicate
with each other.
- Review the SystemOut and FFDC logs for the primary shards with
the incorrect links for more specific error messages.
- Dismiss and re-establish the link between the domains.
- Problem: Data is missing in one or more catalog
service domains. For example, you might run the xscmd -c
establishLink command. When you look at the data for each
linked catalog service domain, the data looks different, for example
from the xscmd -c showMapSizes command.
Solution: You
can troubleshoot this problem with the xscmd -c showLinkedPrimaries command.
This command prints out each primary shard, and including which foreign
primaries are linked.
In the described scenario, you might discover
from running the xscmd -c showLinkedPrimaries command
that the first catalog service domain primary shards are linked to
the second catalog service domain primary shards, but the second catalog
service domain does not have links to the first catalog service domain.
You might consider rerunning the xscmd -c establishLink command
from the second catalog service domain to the first catalog service
domain.