I tried this, stopped dg_broker, even removed the configuration. I changed
dg_broker_start to false, in the primary db and even in standby.
I reset the dataguard parameters, but the error occurred on the retry.
I recreated the redo logs standbys, to try to avoid the error...
What I didn't do that I thought now was delete the metadata files from the
dataguard... dr*.data
tomorrow I'll check if there is any parameter that I forgot to change and
try again.
Att.
*Juliano Ribeiro*
<http://br.linkedin.com/in/supernoi>
Em seg., 23 de ago. de 2021 às 23:09, Mladen Gogala <gogala.mladen@xxxxxxxxx>
escreveu:
Juliano, did you turn off the standby in dg broker? If you didn't, dg
broker will turn on recovery as soon as it detects that the instance is in
the mounted state. You should disable the standby in the dgmgrl and turn
off log shipping.
Regards
On 8/23/21 3:43 PM, Juliano Ribeiro wrote:
Doc Oracle:*RMAN Duplicate for Standby Failing with RMAN-05535 ORA-01156
(Doc ID 2183867.1)*
Command:
run {
duplicate target database for standby from active database dorecover
nofilenamecheck;
}
Error:
Oracle Error:
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: '+DATA/<dbname>/DATAFILE/system.269.1080901629'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/18/2021 12:07:33
RMAN-05501: aborting duplication of target database
*RMAN-06136: Oracle error from auxiliary database: ORA-01156: recovery or
flashback in progress may need access to files*
Recovery Manager complete.
Thank you.
Att.
*Juliano Ribeiro*
<http://br.linkedin.com/in/supernoi>
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217https://dbwhisperer.wordpress.com
-- //www.freelists.org/webpage/oracle-l
