@Rajendra, nope, the backup was taken back in May. The earliest archivelogs
are from June.
@Ram I know right! It's not absolutely critical. It could be recreated but
client is reluctant to do this. I was asked to see if we could get it back
open at least.
On Fri, Sep 1, 2017 at 10:54 PM, <rajendra.pande@xxxxxxx> wrote:
Do you have online redo logs from the time of backup.
I believe You will need these for recovery.
From: Ram Raman <veeeraman@xxxxxxxxx<mailto:veeeraman@xxxxxxxxx>>
Date: Friday, Sep 01, 2017, 17:50
To: merrickronan1@xxxxxxxxx <merrickronan1@xxxxxxxxx<mailto:
merrickronan1@xxxxxxxxx>>, ORACLE-L <oracle-l@xxxxxxxxxxxxx<mailto:
oracle-l@xxxxxxxxxxxxx>>
Subject: Re: Recreating Controlfile During Database Restore
haaa! talk about a DBA's nightmare.
I dont know how critical this database is to your business. I have heard
about some of my colleagues using DUDE, DUL tools from someone in Belgium
or Holland.
Oracle support couldnt help?
On Wed, Aug 30, 2017 at 2:14 PM, Ronan Merrick <merrickronan1@xxxxxxxxx<
mailto:merrickronan1@xxxxxxxxx>> wrote:
Hi Listers,
Database is 12.1.0.2 RAC on Linux.
Somebody restored the database, then discovered there are no controlfile
or archivelog backups and the archivelogs from the time of the backup are
gone.
The backup appears to have been a consistent backup. V$datafile_header
shows all files with the same checkpoint_change#. RMAN shows all files
having the same SCN in the backup.
I thought it would be possible to recreate the controlfile and open the
database but when I try to open with RESETLOGS, it fails, saying datafile 1
needs more recovery. I tried simulating recovery with CANCEL but it still
failed.
Have I missed something? Shouldn't it be possible in this case to recreate
the controlfile and open resetlogs if the backup was consistent?
Any insights would be greatly appreciated.
Regards,
Ronan
--
Please visit our website at
http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html
for important disclosures and information about our e-mail
policies. For your protection, please do not transmit orders
or instructions by e-mail or include account numbers, Social
Security numbers, credit card numbers, passwords, or other
personal information.
