Activation fails with "DetLock: Attempting to do a non-wait lock on <table_name>" and ORA-0 (4297359)

Activate config results in error " Unable to lock "owner"."table_name"

For example;

sp_ctrl (server_name:port_num)> activate config config_name
   Unable to lock "owner"."table_name".

The *rmp* log (activation log) shows the following error:

06/15 09:36:09 ""owner"."table_name": NEW, Type is T,
06/15 09:36:09 DetLock: Attempting to do a non-wait lock on "owner"."table_name".

The event log shows that the Oracle error ORA-01031 was primarily responsible:

06/15/07 09:36 Process launched: sp_tconf (for o.source_SID) [pid = 5541]
06/15/07 09:36 Error: Unable to lock "owner"."table_name"due to ORA-01031: insufficient privileges. [sp_tconf/5541]
06/15/07 09:36 Config compilation completed: datasrc - o.source_SID; file - config_name
06/15/07 09:36 Bad config file: file - config_name; Unable to lock "owner"."table_name ".
06/15/07 09:36 Process exited sp_tconf  (for o.source_SID) [pid = 5541] - exit(1)

The activation failed due to lack of privilege or incorrect entries in paramdb.

The problem may be due to lack of privilege on the part of Shareplex user for the database.  Please check the following:

1. Check whether the paramdb file was copied from another shareplex instance. If an incorrect paramdb has been used, restore the correct paramdb.
2. If Shareplex does not have the DBA roloe, either grant the DBA role to the Shareplex or grant appropriate privilege to Shareplex user .  For example, "GRANT DBA to <shareplex_user>" or "GRANT ALL to <shareplex_user> on <object_name>", and then activate again.
3. Re-run ora-setup but make sure that the original schema is not changed as this can render the currently active config file inactive.   When prompted whether to create a new user, enter "n", then select the current shareplex user.
4. If the ora_setup also results in ORA-01031, refer to Solution # SOL20525, especially if the Shareplex has been upgraded to 5.3 recently.

Here are details on the ORA-01031:

ORA-01031: insufficient privileges

Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login.

Action: Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label.