Following error messages are seen when running a repair:
sp_ctrl> repair "OWNER"."TABLE_NAME"
repair " OWNER "." TABLE_NAME "
Cannot open object cache for active config
See the event_log for details
The above error messages can also show up for compare. The resolution applies to both compare and repair.
The object cache for Capture did not get created yet.
The repair command needs to refer to the Capture object cache file for gathering information about the structure of the object. An object cache file contains structural information of the tables in replication, something similar to what Oracle stores in its data dictionary. When a config file is activated, it will create object cache file for various processes like activation process (sp_tconf or sp_conf), Capture (sp_ocap), Read (sp_ordr), etc. In our case the probable cause is that the Capture object cache did not get created for some reasons.
Find out the activation ID for current activation:
You can issue "list config" to get details on the active configuration as follows:
sp_ctrl > list config
File Name State Datasource
-------------------------------------------------- ----------
test.config Active o.SID
Last Modified At: 12-Sep-08 01:19 Size: nnnn Internal Name: .conf.22
The activation id is 22 as shown above.
You can then issue "show config" on source sp_ctrl and if Capture is not yet replicating from the most current activation, you will see the messages as below:
sp_ctrl> show config
Capture is not yet replicating the most recent activation
Re-issue this command when capture's replication is current
If Capture is current, you will see the current activation id also show up in "show config" as it did in "list config". You can then issue another repair.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center