The following messages appear in event log when Post runs into error “Unexpected Oracle error ORA-01157 cannot identify lock data file”:
Info 2018-02-28 15:58:36.401300 24022 736356224 Poster exited with code=1, pid = 80641 (posting from source_SID, queue queue_name, to target_SID)
Notice 2018-02-28 15:58:36.348292 80641 248170240 s:19 Poster: No locks found (posting from source_SID, queue queue_name, to target_SID) [module osp]
Error 2018-02-28 15:58:36.256524 80641 248170240 s:19 Poster: que/seq = 19/ 27957085260 seqno/offset = 587790/737828916 Unexpected Oracle error: ORA-01157: cannot identify/lock data file 3368 - see DBWR trace file ORA-01110: data file 3368: '+DG_target_SID_DT05/oradata/wbxeventloguser_opc_y18q1d_6061.dbf' (object name: "OWNER"."TABLE_NAME") (posting from source_SID, queue queue_name, to target_SID) [module opo]
Notice 2018-02-28 15:58:36.254938 80641 248170240 s:19 Poster: ORA-01157: cannot identify/lock data file 3368 - see DBWR trace file ORA-01110: data file 3368: '+DG_target_SID_DT05/oradata/wbxeventloguser_opc_y18q1d_6061.dbf' (posting from source_SID, queue queue_name, to target_SID) [module osp]
Info 2018-02-28 15:58:31.695876 80641 736356224 Poster launched, pid = 80641 (posting from source_SID, queue queue_name, to target_SID)
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center