Object cache files are lost from time to time or there are object cache file related errors encountered by SharePlex. This article attempts to specify some of the obvious reasons for these.
There are a number of reasons that can result in loss of object cache files including Post object cache files. Some of the common ones are:
Queue corruption causing loss of messages.
Removal of messages from queue (by qview utility) to get past some issues that cause errors or problems with SharePlex processes.
The updating of object cache can be a frequent process as these files are updated whenever a new activation is done or a DDL is performed on a replicated object. Since these files are in a state of flux, any OS or system problems can result in corruption of these files.
Disk full situations also result in loss of such files.
Capture object cache files fail to get created if the SharePlex internal tables on source database have residual entries from the past installations that failed to get removed as ora_cleansp was not run prior to installing a brand new SharePlex instance.
When a compare is run, it sends a token message from source called compare marker for the purpose of establishing a common reference point to do a read consistent comparison of source and target tables. Normally when compare exits, this token message is already processed by Post queue prior to the exit of compare. At times it may still be stuck due to some glitch in compare. This results in Post object cache not updated on target which results in the Post errors due to inconsistent object cache.
