ORA-01157: cannot identify/lock data file 1 - see DBWR trace file

[former_member209962]

Hi Friends,

We are building a new system with production backup and doing system copy with backup restore method.

Restore is done using HP data protector after restore database is not opening

ORA-01157: cannot identify/lock data file 1 - see DBWR trace file

ORA-01110: data file 1: 'F:\ORACLE\SID\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'

SYSTEM.DATA1 this data file is available at the required location

SQL> startup

ORACLE instance started.

Total System Global Area 8824815616 bytes

Fixed Size                  2227352 bytes

Variable Size            2664268648 bytes

Database Buffers         6157238272 bytes

Redo Buffers                1081344 bytes

Database mounted.

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;

alter database open resetlogs

*

ERROR at line 1:

ORA-01157: cannot identify/lock data file 1 - see DBWR trace file

ORA-01110: data file 1: 'F:\ORACLE\SID\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'

Kindly help to resolve this issue.

Thanks

Tabrayz

[Former Member · Accepted solution]

Hi Tabrayz,

Create the controlfile, first. Please find the procudure, below;

1) Create control.sql by executing the command at the productive system, below;

alter database backup controlfile to trace resetlogs;

2) Goto "/oracle/<SID>/saptrace/usertrace" and open newly created trace file,

3) Copy lines between "STARTUP NOMOUNT" and "-- Commands to re-create incarnation table" strings. Please note that these strings will not be included, just between of them

4) Create a control.sql file and paste the SQL statement, at the 3rd step

5) Now, you can change all the paths, regarding your needs in the file

6) Now that you have a control.sql file, then you can create the control files,

7) Delete all control files on the database. They have been determined in the SPFILE or init<SID>.ora file.

😎 By the <sid>adm user

  a) sqlplus / as sysdba

  b) startup nomount

  c) @<path>/control.sql

  d) shutdown

Best regards,

Orkun Gedik

[former_member209962 · Accepted solution]

Thanks

Issue is solved after creating new controlfile

after running @control.sql it asked resetlogs and then it asked for some archive logs, once i gave required archive logs  database got open

Thank you all for your help!!!

Thanks

Tabrayz

[volker_borowski2]

Hi,

do you use new SID for copied system?

If Yes, did you create new controlfile with SET DATABASE "NEWSID" ?

Volker

[former_member209962]

Hi Volker,

SID is same and its not even allowing to recover db

Thanks

Tabrayz

[Former Member]

Hello Tabrayz,

Issue is with your control file creation, pls check.

Regards,

Medha

[Former Member]

Hi Abdul,

As i read your problem, it is the control file related issues and to resolve the same issue, you need to recreate the control file and then need to start the database again then only you can start your database in open mode.

You can file the control file creation steps and oracle errors solution.

Try this and if it'll not work for you then please do post here. We would glad to help you further.

[former_member209962]

Hi Robby,

This issue already solved and you can see its answerd .

But thanks for your inputes

Thanks

Basis