-
Title
Post stopped due to error "ORA-08006: specified row no longer exists" -
Description
Post is stopped due to ORA-08006 as the following event log entries show:
Info 2010-06-16 20:48:48.335129 3631 1 Poster launched, pid = 3631 (posting from NAME, queue queue_name, to name)
Notice 2010-06-16 20:48:51.328975 3631 24 Poster: ORA-08006: specified row no longer exists. (posting from NAME, queue queue_name, to name) [module osp]
Error 2010-06-16 20:48:51.329530 3631 24 Poster: Unexpected Oracle error: ORA-08006: specified row no longer exists. (object name: "OWNER"."TABLE_NAME") (posting from NAME, queue queue_name, to name) [module opo]
Info 2010-06-16 20:48:51.348161 29968 1 Poster exited with code=1, pid = 3631 (posting from NAME, queue queue_name, to name)
 -
Cause
One reason for seeing this post error could be a problem in post key cache and it may have caused post to encounter this problem. There may be other reasons as well.
 -
Resolution
The best way to move forward is to ignore the Oracle error by setting the parameter SP_OPO_CONT_ON_ERR to 1 and configuring the file oramsglist. See Shareplex Reference Guide chapter titled Shareplex parameters section titled Post parameterss for details. Once the problem DML is ignored, the parameter can be reset back to 0 (also detailed in the Shareplex Reference Guide). Ignoring the DML will cause out of sync on target table and Support can be contacted if this is a concern so that at least debug info is collected for investigation purposes prior to trying this workaround. The target table will need to be resync'd at a later time.
Â