If replication failures occur repeatedly, you need to examine the events in the holding cache to determine and resolve the cause of the failures. You can then either reset or clear the cache.
To dump the cache contents
To dump the contents of the cache to a text file, run the following command. Cached events are output to CacheData.txt in the \System subfolder of the CA DataMinder installation folder.
wgninfra -exec wigan/infrastruct/replication/NetworkMonitor DumpHoldingCacheData CacheData.txt
To clear the holding cache
To clear the replication cache (that is, delete the cached events), run the following command:
wgninfra -exec wigan/infrastruct/replication/NetworkMonitor ManageHoldingCacheData delete <minID> <maxID>
where <minID> and <maxID> are event identifiers in the cache dump file. All events within the specified range of identifiers will be deleted. To delete all events in the cache, specify the identifiers for the top and bottom rows in the dump file (that is, the first and last events in the cache).
To reset the holding cache
After diagnosing and resolving a replication problem, you can reset the cache. That is, you can move cached events back to the main replication queue for re-sending to the parent server. CA DataMinder provides methods to do this manually and automatically.
|
Copyright © 2014 CA.
All rights reserved.
|
|