How to Solve :
Oracle database error code ORA-01157 – cannot identify/lock data file string – see DBWR trace file
Oracle Database Error Code ORA-1157 Description :
cannot identify/lock data file string – see DBWR trace file
Error 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.
How to Solve :
Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 1157, 01157, 1157, about oracle ORA-01157 error, cannot identify/lock data file string - see DBWR trace file, help ORA-01157 about, How to Solve Oracle Database Error ORA-01157, ORA-01157 error code, ORA-01157 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 1157 error code, oracle ORA-01157 example
1 Comment
1 Comment
Recent Entries
- Oracle database error code ORA-29959 – error in the execution of the string routine for one or more of the index partitions
- Oracle database error code ORA-31601 – Function string cannot be called now that fetch has begun.
- Oracle database error code ORA-29958 – fatal error occurred in the execution of ODCIINDEXCREATE routine
- Oracle database error code ORA-31600 – invalid input value string for parameter string in function string
- Oracle database error code ORA-29957 – cannot create a function-based domain index on a string table
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
Search Oracle Error Codes and Descriptions:
1 Comment Already
Similar Errors
Please Leave Your Comments Below