ORA-01157: cannot identify/lock data file string - see DBWR
trace file
- 1 Answers
- 5725 Views
- I also Faced
- E-Mail Answers
Answer / guest
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.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 0 No |
ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log
ORA-16169: LGWR network server invalid parameters
NNL-00285: Server has no queued system queries
ORA-38105: Delete not yet supported when Update row-migration is possible
ORA-31403: change table string already contains a column string
PLS-00115: this PRAGMA must follow the declaration of 'string'
PLW-05004: identifier string is also declared in STANDARD or is a SQL builtin
ORA-31025: Invalid document element
ORA-26055: Invalid buffer specified for direct path unload
QSM-00514: the size of must-retain summaries exceeds specified space limit
ORA-06916: CMX: error in data read (t_datain)
ORA-22613: buflen does not match the size of the scalar
Oracle Errors 
