missing DBF file
I was clonning my DB.
I did the following steps:
1.Shutdown the source DB
2.take the backup of all the DBF files.
3.alter database backup control file to trace , of Source DB.
Now While creating the control file I missed one dbf file anyhow.
Control files are created and destination(clonned)
I gave alter database openresetlogs
DB is up.
But while working on the clonned DB, got an error , because one of the dbf file is missed.
By default oracle made a dbf file named like missing1000000, in the respective tablespace.
Now my problem is :
How can I take the DBF file which I left?I mean how can i include the reaminning dbf in my clonned DB
tricky but if you have all archive logs since that file was created you can try alter database create datafile
Originally Posted by pando
Pando, thanks for yr reply.
I am having the dbf file in the source DB.
How can I include that DB file from Source DB to the Clonned DB?
I have already applied the resetlogs command to all the DBF files in the Clonned DB.
Is it possible that I copied this file from Source to clonned in the respectice tablespace, and then start the clonned DB in mount stage , and then again issue the cooomand:
alter database open resetlogs?
Please do help me.
is there a reason you cant just start again and re-copy the files and create the control file again
Originally Posted by davey23uk
Thanks for yr reply.
Yes , I cannot shut down and recreate the DB , because I have applied around 5 patches on it and regress testing is going on from last 5 days.I am using this DB for Oracle 11i5.10.2 E-business suite.
Can be some other work around possible ?
You can try out the following
1) Backup the control file to trace (of standby)
2) shutdown the db and copy the missing datafile to its destination
3)Open the controlfile trace and you will find that one the datafile name is given as missing100....
4) Change that name to the name of the datafile you juct copied(with path of course)
5) Recreate the controlfile (backup the original one first )
6) mount the database, do recovery (if needed), open the database.
There are three kinds of lies: Lies, damned lies, and benchmarks...
Unix is user friendly. It's just very particular about who it's friends are.
Originally Posted by simply_dba
Thanks to all, the above solution works.
Click Here to Expand Forum to Full Width