-
Title
Post errors out with “Unexpected Oracle error ORA-01157 cannot identify lock data file” -
Description
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)
-
Cause
Some issues with data file as detailed below are causing this. -
Resolution
Some of the common reasons for seeing this error is, unopened data files which are mounted, lack of write permissions to that data file, among others. These usually occur during recovery. To fix the issue, make the data files available by fixing the above issues carry out one of the following as applicable:
* Open the data file in question.
* Set the write permissions on the data file based on the Operating System (different for Windows and Unix)
* If needed, check the integrity of the data file by “ALTER SYSTEM CHECK DATAFILES” and fix it
Then restart Post.
-
Additional Information
Here is the description of the ORA-01157 ORA-01157: cannot identify/lock data file string - see DBWR trace file Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified. Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.