Fix: ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
ORA-01110: data file 201: '+DATA'
Issue:
If you are using XML in your database and you are trying to update any XML data, then above error may come.
Fix:
1) Add below line in your parameter file and bounce the database if not there.
*.dispatchers='(PROTOCOL=TCP) (SERVICE=PRODXDB)'
2) Unlock the XDB user if locked.
SQL> alter user XDB account unlock;
3) If you have created a duplicate database or open standby database r/w mode, then source TEMP tablespaces will no more valid. drop your TEMP tablespace and create new TEMP tablespace and make it default.
e.g.,
SQL> DROP TABLESPACE TEMP INCLUDING CONTENTS AND DATAFILES;
SQL> create temporary tablespace TEMP02 tempfile '/u02/PROD/ORADATA/temp_02.dbf' size 1024M autoextend on;
SQL> alter database default temporary tablespace TEMP02;
Bounce the database. Now sure the above error will not come.
Thanks
ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
ORA-01110: data file 201: '+DATA'
Issue:
If you are using XML in your database and you are trying to update any XML data, then above error may come.
Fix:
1) Add below line in your parameter file and bounce the database if not there.
*.dispatchers='(PROTOCOL=TCP) (SERVICE=PRODXDB)'
2) Unlock the XDB user if locked.
SQL> alter user XDB account unlock;
3) If you have created a duplicate database or open standby database r/w mode, then source TEMP tablespaces will no more valid. drop your TEMP tablespace and create new TEMP tablespace and make it default.
e.g.,
SQL> DROP TABLESPACE TEMP INCLUDING CONTENTS AND DATAFILES;
SQL> create temporary tablespace TEMP02 tempfile '/u02/PROD/ORADATA/temp_02.dbf' size 1024M autoextend on;
SQL> alter database default temporary tablespace TEMP02;
Bounce the database. Now sure the above error will not come.
Thanks
This comment has been removed by a blog administrator.
ReplyDelete