Re: CANNOT ACTIVATE STANDBY

If you are sure the change has not been applied to the standby, you need to sever connection to the primary and run alter database activate standby database. If it has been applied, you will need to restore from a backup, or maybe flashback your standby after you activate it.

Sent from my iPad

> On Jul 14, 2016, at 6:20 AM, Nassyam Basha <nassyambasha_at_gmail.com> wrote:
>
> Hello Howard,
>
> When you say PITR of database, have you performed full database restore(i hope backup which taken prior to drop table) and then trying to recover until any particular time/scn? (or) you are trying on the present standby database?
>
>
> > ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
> > ORA-01152: file 1 was not restored from a sufficiently old backup
>
> This happens in case of the MRP is terminated instead of safe cancel, You can activate standby database any time. So start MRP and immediately cancel and then for sure you can able to active standby database.
>
> > SQL> recover database until cancel using backup controlfile;
> > ORA-00283: recovery session canceled due to errors
> > ORA-01666: control file is for a standby database
>
> This is not applicable for standby, because standby contains standby control file but not current controlfile or backup controlfile;
>
> The best practice in your case is,, gather the timestamp of scn when the table was dropped/truncated and you can use log miner, then gather the datafiles check point and database checkpoint. Ensure database scn is always less so that you can perform recovery until the point of time you prefer in order to ensure the table is available.
>
> Thank You.
>

>> On Thu, Jul 14, 2016 at 4:05 PM, Howard Latham <howard.latham_at_gmail.com> wrote:
>> Oracle 112 RH EL4 64BIT
>> 
>> I am trying to do a point in time recovery on a standby to get a table back for a developer (IT Director)
>> Anyone got any good ideas? (got a sinus headache as well!...)
>> 
>> pecify log: {<RET>=suggested | filename | AUTO | CANCEL}
>> CANCEL
>> ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
>> ORA-01152: file 1 was not restored from a sufficiently old backup
>> ORA-01110: data file 1: '/u03/oradata/OLDBARB/system01.dbf'
>> 
>> 
>> ORA-01112: media recovery not started
>> 
>> 
>> SQL> recover database until cancel using backup controlfile;
>> ORA-00283: recovery session canceled due to errors
>> ORA-01666: control file is for a standby database
>> 
>> 
>> SQL> 
>> 
>> 
>> 
>> -- 
>> Howard A. Latham

--
http://www.freelists.org/webpage/oracle-l