Recovery using Backup Control File!

Hi all!

Query:

P.S:This is a case study # 8 from Backup & Recovery by Rama Velpuri.

Consider the following scenario:

Working on Oracle v8i with OS as NT.

1.I take regular cold backups after shutting down the db which includes:

Data Files,Log Files and Control Files.

I maintain only One Copy of the Control File say Control01.dbf.

The Db is running on Archivelog mode and automatic arch enabled.

I accidently delete the only one copy of the control file as above.Since I don't have any other copy of the control file,I copied the Backup controlfile and started the DB.While opening the Db,
Oracle complained that an old controlfile was being used.

What should be the way and approach to recover the Db in such a scenario.

P.S:I do not want to create a new control file for the above recovery.


2.While IMPORTING in the Tablespace Mode, I get the following error mesg:

D:\> IMP TRANSPORT_TABLESPACE=Y TABLESPACES=BIAC FILE=D:\SERVICE\S_SUPPORT.DMP
LOHG=D:\SERVICE\TR_TS.LOG

USERNAME:amitst/amitst@test as sysdba

IMP-00009: Abnormal end of Export File.
IMP-00000: Import terminated unsuccessfully.

d:\>


Any idea what could have gone wrong.

What should be done to resolve the above error.

3.Under what scenarios,could we delete views.

Thanks&Regards,

Amit.

[
P.S:I do not want to create a new control file for the above recovery.


Amit. [/B][/QUOTE]


Ofcourse, your option will be to recover using backup controlfile. At this point .the best thing would be to recreate the controlfile.

hmm..if i understand ur qn 1) correctly u are saying your one and only controlfile was deleted
and u are using a backup copy and now oracle is complaining that it's too old rite?
I hv not encountered this before but i guess u could always perform a database reset to
start controlfile afresh.

Quote:

---

Originally posted by ngwh
[I hv not encountered this before but i guess u could always perform a database reset to
start controlfile afresh. [/B]

---

to reset database, he has to recreate the controlfile.

Yes,

Amit you have to recreate the controlfile. Otherwise how can the archivelogs be applied. as controlfile is the only place where info abt archivelogs is kept.

i don't think there is another way :(

Hi Vijay8282!

Many thanks for the vital info!

I know that by recreating control file I can open the DB.But I would like to make the other option valid what is mentioned in the book by copying the control file from an offline backup and recover database using backup controlfile.

But boss you see this way!

P.S:This is a case study # 8 from Backup & Recovery by Rama Velpuri. If you open to this case study and follow the steps mentioned therein, you would get stuck at a point wherein oracle asks for more Archived Redo log files to what has been stored in the Archived Destination and finally asks for File 1 needs media Recovery:

D:\oracle\oradata\test\system01.dbf and even after passing the command:

ALTER DATABASE OPEN RESETLOGS

the db doesn't open at all.It keeps on throwing errors!

Any help on the above would be appreciated!

Thanks&Regards,

Amit.

Quote:

---

Originally posted by vijay8282
Yes,

Amit you have to recreate the controlfile. Otherwise how can the archivelogs be applied. as controlfile is the only place where info abt archivelogs is kept.

i don't think there is another way :(

---

Archive logs are not needed here since he has not lost any datafiles. By recreating the controlfiles, all the SCNs in redo logs, datafiles are synchronized and the info recorded in the controlfile.

you need to recover the datafile. Issue a recover database until cancel and then proceed opening the database after the resetlogs option.
Post your result.

Why do u want to do recovery, if u have just lost the controlfile.
Create a new controlfile and u r done.

U need to use backup controlfile to recover only if u are not aware of the controlfile parameters and u have lost the controlfile.In that case It shall be incomplete recovery and u need to use cancel at some point of time.

As far as imp is considered, there 4 possibilities:

1) corrupted exp file
2) incompatible version of exp/imp or database.
3) incorrect block size
4) Database from where exported is not configured for transportable tablespace.