Post was stopped due to ORA-00942 but the object name did not show up and instead the rowid was displayed in the event log as the following sample output shows:
Info 2017-03-29 13:10:11.538970 13434964 1 Poster exited with code=1, pid = 14155898 (posting from SID1, queue queue_name, to SID2)
Error 2017-03-29 13:10:09.727798 14155898 1029 s:5 Poster stopped: Internal error encountered; cannot continue (posting from SID1, queue queue_name, to SID2)
Notice 2017-03-29 13:10:09.727453 14155898 1029 s:5 Poster: Oracle error: ORA-00942: table or view does not exist rowid: AAA/s5AAHAAAN2OAAA (posting from SID1, queue queue_name, to SID2) [module opo]
Info 2017-03-29 13:09:51.295979 14155898 1 Poster launched, pid = 14155898 (posting from SID1, queue queue_name, to SID2)
The fact that the rowid has been identified in the event_log helps us track the problem table whose absence on the target is resulting in Post error. It should be noted that the rowid mentioned is from source. That rowid can be used to determine the object id of the source table as the sample output shows below:
SQL> Select DBMS_ROWID.rowid_object('AAA/s5AAHAAAN2OAAA') from dual;
Armed with the object id from source, it is possible to find out the table name corresponding to that object id (260921 in our example) on source and check if the table exists on target. If it does not, create the table on target database and restart Post.