-
Title
Activation Fails with "may not be replicated because it's neither a table or a sequence" -
Description
The activation fails with the error message indicating that the said object is neither a table nor a sequence as shown below:
Config compilation completed: datasrc - o.SID; file - config_test
config file: file - config_test; <owner>.<table_name> may not be replicated because its neither a table or a sequence. sp_tconf exit.
Process exited sp_tconf (for o.SID queue *) [pid = 2479] - exit(1) -
Resolution
Check the following:
1. If the object is indeed not a table nor a sequence, and remove it from the config file if true and then activate again.2. If the object is a clustered table, remove it from the config file and then activate again.
3. Execute the following steps to see if it resolves the problem if the object is actually a table or a sequence:
a. shutdown cop
b. unset the environment variable TWO_TASK
c. export ORACLE_SID=<value>
d. export ORACLE_HOME=<value>
e. start cop
f. run ora_setup again for the same user.
g. activate config4. If the object does not exist on source and/or target, then remove it from config file. If there is a typo in object name, correct it. (Here is the explanation of how Shareplex returns the error.The Shareplex error messages are hard coded in program code and check in the database for every object referenced in the config file to see if the object is a table or a sequence, and the activation process will error out if this is not the case. If one has objects in the config file which are non-existent in the database, Shareplex will check if they fall under the category of table or a sequence and error out if this is false. It will not parse/check to see if a non-existent object has been referenced so as to print an error to that effect.
The error most likely occurs if a config file has been inherited from another Shareplex instance with a premise that the objects in this database are same whereas it could be that some object did not exist in the database associated with the new Shareplex instance.)
5. Set the init.ora parameter O7_DICTIONARY_ACCESSIBILITY to true and activate config.
Here is the description of the parameter from Metalink:
O7_DICTIONARY_ACCESSIBILITY is intended for use when you migrate from Oracle7 to Oracle9i. It controls restrictions on SYSTEM privileges. If the parameter is set to true, access to objects in the SYS schema is allowed (Oracle7 behavior). The default setting of false ensures that system privileges that allow access to objects in any schema do not allow access to objects in SYS schema.)
6. Grant the system privilege GRANT SELECT ANY DICTIONARY to Shareplex user.