Re: Duplicate for standby fail
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 23 Aug 2021 17:09:52 -0400
Message-ID: <4b3942a5-3f44-a819-a355-4092eab43e94_at_gmail.com>
Date: Mon, 23 Aug 2021 17:09:52 -0400
Message-ID: <4b3942a5-3f44-a819-a355-4092eab43e94_at_gmail.com>
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;
}
class="gmail_default">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.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com-- http://www.freelists.org/webpage/oracle-l Received on Mon Aug 23 2021 - 23:09:52 CEST