Error "unable to lock table "SPLEX2200"."SHAREPLEX_PARTITION" due to ORA-00942" when activating a (4297150)

When an activation was attempted, it resulted in the following error:

sp_ctrl (servername:2200)> activate config atlbkdb_2200.config
   Unable to lock table " SPLEX2200"."SHAREPLEX_PARTITION" due to ORA-00942: table or view does not exist.

The table did exist in the database as verified by user.

The login entry in the paramdb file was found to be incorrect. When examining the contents of the paramdb file, it was found to contain wrong login information for the username as shown below:

$ cat paramdb
.
.
SP_ORD_LOGIN_O.SID "579fd983ba0c16fe94160d"
SP_ORD_OWNER_O.SID "splex2100"

The username should have been splex2200 instead of splex2100. The mix-up may have been the result of the inheriting the paramdb file from another Shareplex instance.

The resolution to this issue is to comment out the login entry in this paramdb and re-run ora_setup and specify the credentials for the user SPLEX2200 (in our case). This would create new login entry for Shareplex user in the paramdb and then the activation can be done successfully. Make sure that the environment variable for SP_SYS_VARDIR is pointing to correct variable directory containing this modified paramdb before attempting another activation. One more thing that can be done prior to activating again is to run ora_cleansp on both source and target, if this is not a continuing activation. If this is a continuing activation (activation on the top of a previously active config file), then activate the config without running ora_cleansp so as to avoid any downtime on the source database.