The Post is stopped due to the following errors (as seen in target event log):
Notice 2011-05-27 14:11:08.365000 616 3280 s:3 Poster: retry 3 for 9I DDL BCAST on "OWNER"."TABLE_NAME" (rowid:N/A) due to: ORA-00054: resoue busy and acquire with NOWAIT specified or timeout expired.. (posting from ORCL, queue Hub, to ORCL) [module opo]
Error 2011-05-27 14:11:08.338000 616 3280 s:3 Poster: OCI Error: ORA-00054: resource busy and acquire with NOWAIT specified. OWNER.TABLE_NAMEis locked by sid 102 SPLEX,sp_opst_mt.exe,AOI-HOU\M71SHORE (posting from ORCL, queue Hub, to ORCL) [module opo]
A full or partial rollback may be a culprit (in addition to the usual suspect, namely the table is locked by another session)
First rule out the most common cause and check if the table is locked by another session and either wait for that lock to be released before restarting Post.
The error can also occur if Post is currently processing a full or partial rollback. The quickest way to check this and resolve the issue (in one combined step) is to run qview –p at command prompt and then restart Post as follows:
1. sp_ctrl > status (make sure it is "stopped due to error" before exiting sp_ctrl for step # 3)
2. sp_ctrl>stop import
3. sp_ctrl>exit
4. $ qview -p ($ denotes OS prompt. If using named queues, answer the prompt with the appropriate queue name. The following is a sample screen shot when command is run)
$ qview -p
Queue <queue_name1> (y/n) <n>? n
Queue <queue_name2> (y/n) <n>? y
Current queue <queue_name2> user <queueuser_name>
Read release full rollback subqueue 5, seq 6580815286
5. Launch sp_ctrl and Post
If the above does not help, then contact Support for further investigation.
