When activating a config, it fails and you see the following errors in event_log as the "show log reverse" output shows:
01/11/07 18:08 Process exited sp_tconf (for o.CRW03) [pid = 21721] - exit(1)
01/11/07 18:08 Logging user command: splxcrr3 activate config CRR03config.file
01/11/07 18:08 Bad config file: file - CRR03config.file; Unable to lock <owner>.<tablename>, it is currently involved in a transaction.
01/11/07 18:08 Config compilation completed: datasrc - o.CRW03; file - CRR03config.file
01/11/07 18:08 Notice: Object <owner>.<tablename>locked by user <username>,session(4186),process id(11316),mode=ROW EXCLUSIVE(3),OS user appcrw03 [sp_tconf(osp)/21721]
01/11/07 18:08 Error: Unable to lock <owner>.<tablename>due to ORA-00054: resource busy and acquire with NOWAIT specified. [sp_tconf/21721]
01/11/07 18:08 Notice: Oracle supplemental logging is on. The SHAREPLEX_ROWIDMAP will not be built [sp_tconf/21721]
01/11/07 18:08 Notice: Oracle compatible parameter='10.1.0' [sp_tconf/21721]
01/11/07 18:08 Warning: 13007 - NO_UNIQUE_KEY_WITH_LOB found on object id: 4050524 [sp_tconf(osp)/21721]
01/11/07 18:08 Warning: 13007 - NO_UNIQUE_KEY_WITH_LOB found on object id: 4050524 [sp_tconf(osp)/21721]
01/11/07 18:08 Notice: New activation id 117 [sp_tconf/21721]
01/11/07 18:08 Notice: Oracle version 101 [sp_tconf(osp)/21721]
01/11/07 18:08 Compiling a configuration file: datasrc - o.CRW03; file - CRR03config.file
01/11/07 18:08 Notice: Oracle env - CRW03:/apps/crw03/oracle/product/10.1.0 [sp_tconf(pdb)/21721]
The activation process is not able to lock a table.
If using default activation, Shareplex will lock all tables at once and you may need downtime to do this. In the current situation it is not able to do so and is failing with ORA-00054. If the downtime is not feasible, then you can use "live" option in activation. Use of this option will cause Shareplex activation process sp_tconf to skip the current table and continue processing other tables and retry the failed table(s) once again for a certain # of times before giving up on them. However, this option is generally used with hot backup and reconcile option and if this is not done, it may result in out of sync on certain tables. So either get the downtime and then activate or else use "live" option with reconcile.
If this was an attempt to activate a new config file on the top of the previously active config file, you can get by for the time being by using 'live' activation for the new config file. You may want to correct the out of sync problem introduced on some tables due to this by resynchronizing the target at a later date. Please remember that since it is difficult to determine which tables went out of sync by this, a total target refresh is warranted in near future.
<p>Note: You can use live option if there are LOB tables in the config file.</p>
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center