WORKAROUND 1:
Add the oracle error to the oramsglist file and have post ignore the oracle error.
To set post to ignore this error use the following procedure.
1. Go to vardir/data/ directory
2. Edit the oramsglist file
3. Increment the error count (number) on the top of the file by one ( equals to total number of lines in the file -1 )and add a new line with the error 3124 at the bottom of the line
4. Save the file and exit
5. In sp_ctrl > set param sp_opo_cont_on_err 1
6. start post in sp_ctrl> start post
Once post is past the error the above can be unset:
1. sp_ctrl> stop post
2.sp_ctrl> status (Make sure post is stopped by user)
3. Edit the file oramsglist in the vardir/data directory, decrease the number in first line by 1, remove the message number 3124 from the file and then save the file.
4. from sp_ctrl> set param SP_OPO_CONT_ON_ERR 0
5. sp_ctrl> start post
At times the above workaround does not work. Here is the second workaround:
WORKAROUND 2:
1. For the object name provided in the event log (which is aaa.sss in our sample event log), get the object id from the source database.
2. Disable posting on this object by:
sp_ctrl>set param SP_OPO_DISABLE_OBJECT_NUM [queue <queue_name>] <value of object_id from source database>
3. Restart Post
4. Once the queue is drained, unset the above parameter by:
sp_ctrl>reset param SP_OPO_DISABLE_OBJECT_NUM [queue <queue_name>]
sp_ctrl>stop post
sp_ctrl>start post
STATUS:
This issue will be fixed in future release 7.x.
