The following errors are observed during activation when objects belonging to SYS or SYSTEM schema are included in the config file:
sp_ctrl (irvsupu16:5438)> show log reverse
Info 2009-05-16 07:31:18.500741 12357 1 Activation exited with code=1, pid = 21910 (activating sid quest10g)
Error 2009-05-16 07:31:16.345624 21910 1 Compile of "config3aaaa" for sid o.quest10g failed: Error: Unable to activate config.
Error 2009-05-16 07:31:16.331225 21910 1 Compile of "config3aaaa" for sid o.quest10g failed: line 5, source object name ("SYS"."TAB$") OWNER.TABLE OWNER is SYS
Notice 2009-05-16 07:31:16.200975 21910 1 Activation: Oracle compatible parameter='10.1.0.2.0'. (activating sid quest10g) [module ocf]
Info 2009-05-16 07:31:15.075573 21910 1 Activation launched, pid = 21910 (activating sid quest10g)
This solution delves on the question of whether it is possible to replicate tables owned by SYS or SYSTEM schema.
Shareplex does not replicate SYSTEM or SYS tables (such as data dictionaries). The SYS schema owns the data dictionary, and replication of data dictionary objects to another database could cause corruption. SharePlex will return an error message if you try to activate a configuration that includes SYSTEM or SYS tables. The following illustrates this:
sp_ctrl (irvsupu16:5438)> activate config config3aaaa
line 5, source object name ("SYS"."TAB$") OWNER.TABLE OWNER is SYS
You will need to exclude such objects from the config file and activate again if the activation failed because of inclusion of such objects.
