Post stops with ORA‑00942; the event_log shows only the rowid, not the object name. (4300703)

Post stops with ORA‑00942; the event_log shows only the rowid, not the object name.

Post stops with ORA‑00942; the event_log shows only the rowid, not the object name.

Info     2022-03-29 13:10:11.538970 13434964 1 Poster exited with code=1, pid = 14155898  (posting from SID1, queue queue_name, to SID2)
Error    2022-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   2022-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     2022-03-29 13:09:51.295979 14155898 1 Poster launched, pid = 14155898  (posting from SID1, queue queue_name, to SID2)

SQL> Select DBMS_ROWID.rowid_object('AAA/s5AAHAAAN2OAAA') from dual;

DBMS_ROWID.ROWID_OBJECT('AAA/S5AAHAAAN2OAAA')

---------------------------------------------

                                       260921

Normally, the table name appears in the Target event_log file whenever an ORA‑00942 error is raised. However, in some cases, it may not be displayed. When this happens, the method described above is the quickest way to identify the missing table and resolve the issue.