Incremental backup gives error on Standby Database.

Dear all,

I configured the RMAN scripts for full and incrementak on primary and standby. Full backup for his works very well on both sides, I'm me following error on the database waiting for incremental backups.

ORA-19648: datafile 1: incremental YVERT of start is equal to checkpoint YVERT

ORA-19640: datafile checkpoint is YVERT 1150604773 11/03/2015 time 08:14:57

Database version: 11.2.0.1.0

Configured Active DataGuard.

OS: RHEL - 5.5

I also observed that when I cancel the MRP process (using command, below) and run the backup script incremental standby it works fine without error.

(Alter basic managed recovery sleep cancel;)

Please suggest for the resolution of it.

Kind regards

Ronak Masudi

You primary and stanndby are synchronized. ? Since

ORA-19640:

DataFile checkpoint is SNA time string

Cause: This message identifies the control point data file for a data file that was too old to take an incremental backup, or the target of a gradual restoration, which could not be applied.

Action: See other error message.

Tags: Database

Similar Questions

Roll forward standby database with the incremental backup, when a data file is deleted in primary education

Hello
I'm nologging operations + deleting some files in the primary and you want to roll forward the day before using the incremental backup Yvert.
I do in particular, as the files are dropped?
I got to meet ( Doc ID 1531031.1 ) which explains how to roll forward when a data file is added.
If I follow the same steps, to make the move to restore the data file newly added, will it work in my case?
Can someone please clarify?
Thank you
San

I was wondering if reocover noredo is performed before restored controlfile, oracle will apply the incremental backup error-free files, and in this case, what would be the status of the data file in the control file.

Why do you consider to retrieve the day before first and then in the restaurant of the controlfile will lead to problems. Please read my first post on this thread - I had clearly mentioned that you would not face problems if you go with the method of deployment.

Here is a demo for you with force logging is disabled. For the first time the day before resuming and restored then the controlfile ensures:

Primary: oraprim

Standby: orastb

Tablespace DataFile of MYTS is removed on primary:

SYS @ oraprim > select force_logging in the database of v$.

FORCE_LOGGING

---------------------------------------

NO.

Currently the tablespace is to have 2 data files.

SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

FILE_NAME

-------------------------------------------------------

/U01/app/Oracle/oradata/oraprim/myts01.dbf

/U01/app/Oracle/oradata/oraprim/myts02.dbf

In standby mode, the tablespace is to have 2 data files:

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

/U01/app/Oracle/oradata/orastb/myts02.dbf

Postponement of the day before on the primary log shipping

SYS @ oraprim > alter system set log_archive_dest_state_3 = delay;

Modified system.

Dropped 1 MYTS datafile on the primary.

SYS @ oraprim > alter tablespace myts drop datafile ' / u01/app/oracle/oradata/oraprim/myts02.dbf';

Tablespace altered.

Removed some archives to create a space.

[oracle@ora12c-1 2016_01_05] $ rm - rf * 31 *.

[oracle@ora12c-1 2016_01_05] $ ls - lrt

13696 total

-rw - r - 1 oracle oinstall 10534400 5 January 18:46 o1_mf_1_302_c8qjl3t7_.arc

-rw - r - 1 oracle oinstall 2714624 5 January 18:47 o1_mf_1_303_c8qjmhpq_.arc

-rw - r - 1 oracle oinstall 526336 5 January 18:49 o1_mf_1_304_c8qjp7sb_.arc

-rw - r - 1 oracle oinstall 23552 5 January 18:49 o1_mf_1_305_c8qjpsmh_.arc

-rw - r - 1 oracle oinstall 53760 5 January 18:50 o1_mf_1_306_c8qjsfqo_.arc

-rw - r - 1 oracle oinstall 14336 Jan 5 18:51 o1_mf_1_307_c8qjt9rh_.arc

-rw - r - 1 oracle oinstall 1024 5 January 18:53 o1_mf_1_309_c8qjxt4z_.arc

-rw - r - 1 oracle oinstall 110592 5 January 18:53 o1_mf_1_308_c8qjxt34_.arc

[oracle@ora12c-1 2016_01_05] $

Current main MYTS data files:

SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

FILE_NAME

-------------------------------------------------------

/U01/app/Oracle/oradata/oraprim/myts01.dbf

Current data of MYTS standby files:

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

/U01/app/Oracle/oradata/orastb/myts02.dbf

Gap is created:

SYS @ orastb > select the process, status, sequence # v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.

--------- ------------ ----------

ARCH. CLOSING 319

ARCH. CLOSING 311

CONNECTED ARCH 0

ARCH. CLOSING 310

MRP0 WAIT_FOR_GAP 312

RFS IDLE 0

RFS IDLE 0

RFS IDLE 0

RFS IDLE 320

9 selected lines.

Backup incremental RMAN is taken elementary school.

RMAN > incremental backup of the format of database of SNA 2686263 ' / u02/bkp/%d_inc_%U.bak';

From backup 5 January 16

using the control file of the target instead of recovery catalog database

the DISC 2 channel configuration is ignored

the DISC 3 channel configuration is ignored

configuration for DISK 4 channel is ignored

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 41 type device = DISK

channel ORA_DISK_1: starting full datafile from backup set

channel ORA_DISK_1: specifying datafile (s) in the backup set

Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oraprim/system01.dbf

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/sysaux01.dbf 00003

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/undotbs01.dbf 00004

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/users01.dbf 00006

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/myts01.dbf 00057

channel ORA_DISK_1: starting total, 1-January 5, 16

channel ORA_DISK_1: finished piece 1-January 5, 16

piece handle=/u02/bkp/ORAPRIM_inc_42qqkmaq_1_1.bak tag = TAG20160105T190016 comment = NONE

channel ORA_DISK_1: complete set of backups, time: 00:00:02

Backup finished on 5 January 16

Saved controlfile on primary:

RMAN > backup current controlfile to Eve format ' / u02/bkp/ctl.ctl';

Cancel recovery in standby mode:

SYS @ orastb > alter database recover managed standby database cancel;

Database altered.

Recover the day before by using the above backup items

RMAN > recover database noredo;

From pick up to 5 January 16

the DISC 2 channel configuration is ignored

the DISC 3 channel configuration is ignored

configuration for DISK 4 channel is ignored

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 26 type of device = DISK

channel ORA_DISK_1: from additional data file from the restore backup set

channel ORA_DISK_1: specifying datafile (s) to restore from backup set

destination for the restoration of the data file 00001: /u01/app/oracle/oradata/orastb/system01.dbf

destination for the restoration of the data file 00003: /u01/app/oracle/oradata/orastb/sysaux01.dbf

destination for the restoration of the data file 00004: /u01/app/oracle/oradata/orastb/undotbs01.dbf

destination for the restoration of the data file 00006: /u01/app/oracle/oradata/orastb/users01.dbf

destination for the restoration of the data file 00057: /u01/app/oracle/oradata/orastb/myts01.dbf

channel ORA_DISK_1: backup /u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak piece reading

channel ORA_DISK_1: room handle=/u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak tag = TAG20160105T190016

channel ORA_DISK_1: restored the backup part 1

channel ORA_DISK_1: restore complete, duration: 00:00:01

Finished recover to 5 January 16

Restored the controlfile and mounted the day before:

RMAN > shutdown immediate

dismounted database

Instance Oracle to close

RMAN > startup nomount

connected to the database target (not started)

Oracle instance started

Total System Global Area 939495424 bytes

Bytes of size 2295080 fixed

348130008 variable size bytes

583008256 of database buffers bytes

Redo buffers 6062080 bytes

RMAN > restore controlfile eve of ' / u02/ctl.ctl ';

From 5 January 16 restore

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 20 type of device = DISK

channel ORA_DISK_1: restore the control file

channel ORA_DISK_1: restore complete, duration: 00:00:01

output file name=/u01/app/oracle/oradata/orastb/control01.ctl

output file name=/u01/app/oracle/fast_recovery_area/orastb/control02.ctl

Finished restore at 5 January 16

RMAN > change the editing of the database;

Statement processed

output channel: ORA_DISK_1

Now the data file does not exist on the standby mode:

SYS @ orastb > alter database recover managed standby database disconnect;

Database altered.

SYS @ orastb > select the process, status, sequence # v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.

--------- ------------ ----------

CONNECTED ARCH 0

CONNECTED ARCH 0

CONNECTED ARCH 0

ARCH. CLOSING 329

RFS IDLE 0

RFS IDLE 330

RFS IDLE 0

MRP0 APPLYING_LOG 330

8 selected lines.

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

Hope that gives you a clear picture. You can use this to roll forward day before using the SNA roll forward Eve physical database using RMAN incremental backup | Shivananda Rao

-Jonathan Rolland

Application of incremental backup on Standby to resolve the gap newspaper archive

Hello
I have a database of primary and Standby database both in ASM. Recently, my archive logs has been deleted and I'm trying to recover my database pending with the primary SNA-based incremental backup. But I face the error when I recover the database pending with the incremental backup, made in the primary database below.
RMAN > recover database noredo;

To go back to November 6, 13
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 21 type of device = DISK
channel ORA_DISK_1: from additional data file from the restore backup set
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
destination for the restoration of the data file 00001: +STDBY/11gdb/datafile/system.258.8059
21881
destination for the restoration of the data file 00002: +STDBY/11gdb/datafile/sysaux.259.8059
21967
destination for the restoration of the data file 00003: +STDBY/11gdb/datafile/undotbs1.260.80
5922023
destination for the restoration of the data file 00004: +STDBY/11gdb/datafile/users.261.80592
2029
channel ORA_DISK_1: backup/u01/incr_for_stdby_07oo9fik_1_1 item reading
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 06/11/2013 13:22:27
ORA-19870: error while restoring the backup/u01/incr_for_stdby_07oo9fik_1_1 element
ORA-19573: failed to get exclusive enqueue for datafile 1
Kind regards
007

Have you you stopped to re-apply?

Select process from v$ managed_standby, including the process as "SIR % ';

If there are processes, you must stop it.

ALTER database recover managed standby database cancel;

If the data hold is managed by broker, use DGRMRL

DGMGRL > alter database set status = APPLY-OFF;

Then try again.

If still not resolved, can paste you here your steps and scripts?

Concerning

Mr. Mahir Quluzade

Before physical deployment standby with RMAN incremental backups.

This method is available in 10g:
http://Web.Stanford.edu/dept/ITSS/docs/Oracle/10gR2/server.102/b14239/scenarios.htm#CIHIAADC
For 11g:
http://docs.Oracle.com/CD/E11882_01/server.112/e41134/RMAN.htm#SBYDB00759
For 12 c:
http://docs.Oracle.com/database/121/BRADV/rcmadvre.htm#BRADV685
According to dosc 10 g, the scenario is simple:
1. create an incremental backup to SNA required on primary and copy it in standby mode
2 save the backup in sleep mode and perform a recovery
11 g dosc, we must recreate the standby control file and update the file names before performing the recovery.
12 c introduces the new method - recovery on network, but again, we must recreate and standby control file update.
The question is: why we must create new controlfile ensures g 11 and 12 c and can we use a simple method of 10g?
Thank you.

Hello

1 why the incremental backup application does not update standby controlfile?

-Your database pending is be retrieved using the incremental backup. This does not update the eve controlfile. Your standby controlfile completely ignores the last CNS to the primary database.

2. what happens if we leave the old standby controlfile? RFS will record new logs of the primary, but will ignore them MRP? If so, can update us standby controlfile by manually applying the following log?

-Your old standby controlfile is unaware of the last CNS to the primary database.

As Mseberg said, trying things on a test computer and you will have the answers to your questions.

Kind regards

Shivananda

Duplicate the database and incremental backups
Hello

I reviewing options to maintain a test server that is "relatively" updated compared to the production server.
This is my first contact with RMAN and I went through the books, but as I have not had a chance to play with it I could have missed something.

It is an Oracle devoted to a Redhat Enterprise Linux (not sure of the complete version number) 11.2.

The test server must be writable and must be synchronized with the server in production about once or twice a month. Due to the size of the database (~ 600 GB) we are studying solutions that could make using incremental backups that are already taken on the production database.

While launching the test using RMAN DUPLICATE server seems to be honest, I'm not sure how the "sync" can be done as effectively as possible - especially because we are changing the data on the test server.

After the RMAN BACK command description, is not clear to me if this could serve to 'recover' the database of test based on the incremental backups to the 'current state' of the production database, even if the test database has been changed. After reading a few posts here, it's not seems to be the case.

A restore point would make such a possible incremental restore? Creating a (name?) point of restoration immediately after duplication, and once the tests are finished making back to the restore point and then apply the incremental backups that have accumulated since then.

Another of the options seems to be to create a database of the previous day. Then when running the tests, we turn to the backup database in one instantaneous standby database open read/write and run tests. Once we have finished, we he switch back to a physical standby. This switchback to rewind the changes and recovery logs accumulated are applied as "incremental" catching up with production - which is basically what we want.

Is there another solution to this? Or use a watch of the snapshot, the most effective solution? If possible, we would like to avoid transferring the 600GB whenever we want to re - synchronize the database to test.

Thanks in advance
Thomas
Hi Tomas. I think you're right. Ensures the most effective solution in your situation of snapshot.

Roll forward standby with RMAN incremental backup when used DG broker
Hello

I'm about to use the process defined in the note: steps to roll forward a database ensures the RMAN incremental backup using during primaries and Eve are in the file [836986.1 ID] ASM system. I'm on 11.1.0.7.

However, it does not mention the DataGuard broker.
Did someone played this process when you use the broker.
The broker he manages properly?
Does it matter if the broker is upwards or downwards during the physical recovery of standby or replacement of control file?
Should the broker configuration be re-created?

Thank you.
user11993454 wrote:
Hello

I'm about to use the process defined in the note: steps to roll forward a database ensures the RMAN incremental backup using during primaries and Eve are in the file [836986.1 ID] ASM system. I'm on 11.1.0.7.

However, it does not mention the DataGuard broker.
Did someone played this process when you use the broker.
The broker he manages properly?
Does it matter if the broker is upwards or downwards during the physical recovery of standby or replacement of control file?
Should the broker configuration be re-created?

Thank you.

(1) disable the broker
(2) perform the Roll forard SNA.
(3) select the broker

Error on duplicated to standby database

Hi all

We use 10.2.0.3 on database of Oracle and oracle 10.2.0.5 for ASM.
I am trying to duplicate for standby, but I got the following errors:

Recovery Manager: Release 10.2.0.3.0 - Production on Tue Oct 18 21:57:54 2011

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: PROJDB (DBID=3454419911)
connected to auxiliary database: PROJDB (not mounted)

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13>
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: sid=539 devtype=DISK

allocated channel: c2
channel c2: sid=541 devtype=DISK

allocated channel: c3
channel c3: sid=542 devtype=DISK

allocated channel: c4
channel c4: sid=544 devtype=DISK

Starting Duplicate Db at 18-OCT-11

contents of Memory Script:
{
   set until scn  30812264289;
   restore clone standby controlfile;
   sql clone 'alter database mount standby database';
}
executing Memory Script

executing command: SET until clause

Starting restore at 18-OCT-11

channel c1: restoring control file
ORA-19625: error identifying file /tmp/PROJDB.ctl
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file  (/tmp/PROJDB.ctl)
ORA-19601: output file is control file  (+FRA)
failover to previous backup

channel c1: restoring control file
ORA-19625: error identifying file /tmp/boston.ctl
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file  (/tmp/boston.ctl)
ORA-19601: output file is control file  (+FRA)
failover to previous backup

released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/18/2011 22:04:03
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06101: no channel to restore a backup or copy of the control file

Thus, control, data files files e redo log files are in ASM.
I created rman backup to disk.
There is no control /tmp/boston.ctl and/tmp/PROJDB.ctl file. It's very strange.

The duplicate script is:

export ORACLE_SID=PROJ_STD

rman target rman/rman@PROJ auxiliary / msglog=restore_disk.log << EOF
run
{
    ALLOCATE AUXILIARY CHANNEL c1 TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL c2 TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL c3 TYPE DISK;
    ALLOCATE AUXILIARY CHANNEL c4 TYPE DISK;
     DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER
     NOFILENAMECHECK;
     release channel c1;
     release channel c2;
     release channel c3;
     release channel c4;
}
EOF

Is there any tip about this problem?

thank you very much!!!

I can share my short notes I have tested several times:

I use SYS as shown here.

http://www.Visi.com/~mseberg/duprman2.html

Change if necessary, but it works.

Best regards

mseberg

Would use this: (I connect using the catalog)

Something like this:

Target of $ORACLE_HOME/bin/rman / catalog rmancatuser/rmancatpassword@rmancatdb

run
{
     allocate channel c1 type disk;
     allocate channel c2 type disk;
     allocate channel c3 type disk;
     allocate channel c4 type disk;
     backup format '/ora/backup/stage/df_t%t_s%s_p%p' database;
     sql 'alter system archive log current';
     backup format '/ora/backup/stage/al_t%t_s%s_p%p' archivelog all;
     backup current controlfile for standby format '/ora/backup/stage/sb_t%t_s%s_p%p';
     release channel c1;
     release channel c2;
     release channel c3;
     release channel c4;
}
EOF

Very important

backup current controlfile to Eve format

Published by: mseberg on October 19, 2011 09:04

Published by: mseberg on October 19, 2011 09:07

How to set the incremental backup of level 1 to restore on a different database

Hello
I have a question what is annoys me all week.
I have 2 databases. ORCL and ORCL2. ORCL2 is an auxiliary ORCL database. ORCL my database is backup incrementaly Sunday level 0, other days level 1. Now, I would like to update my ORCL2 db every night to be synchronized with the ORCL database. Is this possible? I have Oracle Standard Edition, so I can't use Data guard. If you can help me I would be very thanful. Or if you could send me a link to some textbooks.
I have db Oracle 10.2.0.3 Standard Edition
Windows Server 2003 Standard edition
With respect,
Ivan

Hello Ivan,.

You can recover the database duplicate, once created each day with an incremental backup of the target database.

What you need here is a simple restore to another host without opening the database with resetlogs. RMAN: Restoring a backup RMAN to another node [ID 73974.1]

Thank you

Backups on the physics of the standby database?
I use dataguard and standby a physical database. How to assign backups on the physics of the standby database to reduce the load on the primary database.

environment: windows

Database version: 11.2.0.1.0

What are the pro and cons on the allocation of jobs of RMAN backups for the physics of the standby database?
Hello;

The backup database is an identical copy of the primary database block.

Therefore, you just save one of the two (you can choose to only save the day before, however, if you want to remove the load on the primary). But if you are uncomfortable with the primary backup, it is not necessary for the safeguarding of the day before. (Since you can recreate the primary backup before).

The only important part, is that you use the RMAN catalog. Then only known RMAN, the two are identical and can use the same backup.

Best regards

mseberg

DataGuard: MRP still in WAIT_FOR_GAP after incremental backup recover

Hello
I'm new to the dataguard configuration, and recently, I connected on a dataguard configuration to test the object.
I have deleted stupidely some archive my primary database logs, thereby breaking the standby update (due to the fact that the database has not been started for a long time, the gap is now about 130 days ).
I have to try to recover the situation re-synchronized the RCS of the day before using an incremental backup (and create eve of primary control files).
After restoration, the SNA were the same, but restarting the recovery service (MRP), it is still indicating WAIT_FOR_GAP and still waiting for my missing archive logs.
New archive logs is well shipped to the waiting however.
No idea what I missed or what should I do?
The database version is a 12.1.0.1.
DGMGRL > see Configuring
Configuration - g12dggo
Protection mode: MaxPerformance
Databases:
g12dggop - primary database
Error: ORA-16724: could not resolve the deficit for one or more databases in waiting
g12dggos - physical of the standby database
Fast-Start Failover: DISABLED
The configuration status:
ERROR
DGMGRL > validate database g12dggop
Database role: primary database
Ready for the digital switchover: Yes
Flashback Database Status:
g12dggop: Off
DGMGRL > validate database g12dggos
Role of data: physical database ensures
Primary data: g12dggop
Ready for the digital switchover: No.
Ready for failover: Yes (main stream)
Flashback Database Status:
g12dggop: Off
g12dggos: Off
Apply information in standby mode:
Apply a State: running
Apply the Lag: 143 days 14 hours 18 minutes 26 seconds
Apply the delay: 0 minutes
Database backup:
SQL > select process, sequence #, status from v$ managed_standby;
STATUS OF PROCESS SEQUENCE #.
--------- ---------- ------------
ARCH CONNECTED 0
ARCH CONNECTED 0
RFS 0 IDLE
MRP0 1965 WAIT_FOR_GAP
RFS 3526 IDLE
More small sequence of table v$ archived_log is corresponding to the last recovery made.
SQL > select sequence #, applied to the order of v$ archived_log by sequence #.
SEQUENCE # APPLIED
---------- ---------
3441 NO.
SQL > select * from v$ archived_log where sequence #= 3441; Select * from v$ archived_log where sequence #= 3441;
RECID STAMP
---------- ----------
NAME
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DEST_ID THREAD # SEQUENCE # RESETLOGS_CHANGE # RESETLOGS_TIME RESETLOGS_ID FIRST_CHANGE # FIRST_TIME NEXT_CHANGE # NEXT_TIME BLOCKS BLOCK_SIZE CREATOR
---------- ---------- ---------- ----------------- ------------------- ------------ ------------- ------------------- ------------ ------------------- ---------- ---------- -------
REGISTR STA ARC APPLIED S DEL COMPLETION_TIME DIC DIC END BACKUP_COUNT ARCHIVAL_THREAD # ACTIVATION # IS_ COM FAL END_OF_RED BIN CON_ID
------- --- --- --------- --- - ------------------- --- --- --- ------------ ---------------- ----------- --- --- --- ---------- --- ----------
1 880046905
/oravar/G12DGGO/Archiv/1_3441_865786197.dbf
2 1 1 08/12/3441 2014 16:09:57 865786197 7004011 18/05/2015 17:21:17 7005043 18/05/2015 17:29:22 509 512 ARCH
RFS NO NO YES NO A 17:28:25 05/18/2015 NO NO NO 0 1 2523036437 NO NO NO YES 0
Thank you in advance for your help!

Problem solved.

In Oracle 12 c, roll forward is more to do "by hand".

There are a few commands to RMAN done automatically, by using the primary database service (G12DGGOP_DG for me).

So back up mode:

RESTORE DATABASE SERVICE G12DGGOP_DG WITH THE HELP OF NOREDO COMPRESSED BACKUPSET SECTION SIZE 100M;

Then after restore controlfile in nomount (stop):

RESTORE CONTROLFILE EVE OF SERVICE G12DGGOP_DG;

The information comes from here:

http://allthingsoracle.com/rolling-forward-a-physical-standby-database-using-the-recover-command/

Reference on Oracle documentation:

https://docs.Oracle.com/database/121/BRADV/rcmadvre.htm#BRADV685

Thank you all for the answers and the help on this!

Ray Zin

Manuel Standby Database not in harmony with the missing archivelogs
Hello

Operating system: Solaris
DB: Oracle 11.2.0.1 EA
Do not use RAC or ASM

I have a Production database which is in archivelog mode and standby server DR.
The two servers (Prod, standby) have the same structure and exact db name/version.

We manually scp archive logs and recover them to a database of manual standby via the SQL Scripts "cron". (I.e. the value of automatic recovery on; restore database Eve ;))
Recently, we got out of sync with our log files and were not applying on the eve. As part of the maintenance of the Prod, these log files have been removed and are no longer available.
I tried several ways to 'rebuild' our database awaiting. I tried to prod Shutdown, backup all files db and scp sleep them, recreate standby controlfile and startup mount and recover the.
Whenever I try to apply a new journal archive via recover Eve, here are the errors:

ORA-00279: change 211077622 September at 27/01/2012 12:18:42 necessary to screw 1
ORA-00289: suggestion: /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
ORA-00280: change 211077622 thread 1 is in sequence #69486

ORA-00308: cannot open archived log ' / oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
ORA-27037: unable to get file status
SVR4 error: 2: no such file or directory
Additional information: 3

ORA-10879: error reported in parallel recovery slave
ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01152: 1 no file has been restored from a sufficiently old backup
ORA-01110: data file 1: ' / oradevices/PROD/oraPRODsystem1.dbf'

When I check v$ log_history, new newspapers have not been implemented.
I also tried the method 'Restore from incremental backup via YVERT' with the same results.

Is there a way to re - create own forward and ensure that the chain of the newspaper which is now defective gets fixed or reset?
Finally, I would get DataGuard here, but this isn't the case at the moment.
Thanks for your suggestions.

-Dav
If you use the backup to cold to create the database pending, check whether you have followed these steps.

1. Remove
all the data files and the database pending controlfiles.

2. create a new controlfile eve of production to standby by using the following command
"change the database create controlfile as 'Location'"; "."

3. move the controlfile back to the location of the server database of such relief as specified in the initialization parameter file.

4. replace its appropriate place that was taken through cold backup all data files.

5 startup nomount

6 change the mounting base pending;

7 restore database pending.
CPS archives newspapers sequence which is posed by the database of the production.

You can try these steps.

Block corruption on the physical Standby database

Hi all
Operating system: HP Unix
DB: 10.2.0.4
We are facing corruption block on our database of physical intelligence. The same has been detected using commands below and several blocks were found to be corrupt.
RMAN > backup validate check the logic of database;
SQL > select * from v$ database_block_corruption
As it is a basic data watch no backup is present, pulling the command below did not help
RMAN > list of corruption block restoration;
I think taking the incremental backup of the PR and the same application on DR, y at - it another way to eliminate corruption said?
Kind regards
Sphinx

You can check below link if corruption block results nologging, there is a thread already with the question.

Block corruption on the standby database

10.5.2 steps of recovery for databases physical standby

Data protection scenarios

ORA-01403: no data found on the LOGICAL standby database
Hello

Logical question of Eve:
Enterprise Edition Oracle 10.2.0.2.

M work waiting LOGIC for 1 year but still i have not had this...
I m not be countinuously no data foud errror on the logic of the standby database.

I found the table causing the problem (db_logstdby_events) and jumped this table and table instantiated using the package bwlow:

exec dbms_logstdby.instantiate_table (...)

but when I start to apply the logical waiting process it gives again some were found for the new data table:

I even tried to instantiate the table to EXPORT/IMPORT assistance over time, but the same problem same deal with.

As much as I knew abt the error that is:
Table1:
ID
10
20
30

Now if sql apply processes on standby logic tent performs the operation of (for example) updated as below

Update table1 set id = 100 where id = 50;

above request will not be completed cos he'll never find 50 values which is not in the table. That is why this error coming...

Now my concern is... no user didn't dare change/make of such changes on the logic ensures. So if there is no change in the tables, then apply it sqll should get all the values to be needded for an update...

watingggg guyssss...
Hello;

How do you know that the database pending is compatible with the primary?

Are there opportunities has one or several tables have been created on the eve before they were created on the primary? (If Yes check in DBMS_LOGSTDBY. INSTANTIATE_TABLE)

Or jump and re-instantiate the table.

Example of
```
EXEC DBMS_LOGSTDBY.SKIP('DML','EMPLOYEES','%');

EXECUTE DBMS_LOGSTDBY.INSTANTIATE_TABLE  ('YOUR_USER', 'EMPLOYEES', 'YOUR_DBLINK');
```
Best regards

mseberg

question from control_file_record_keep_time in the standby database
Hello

We used to recreate a database waiting for backup to cold after a PROD failover to STANDBY mode. (on a weekly basis)

During the synchronization of the day before with a production that we get under WARNING
-------------------------------------------------------------------------------------------------------
FAL [client]: you cannot request the gap sequence
GAP - thread 1 sequence 45217-45225
FAL [client]: all defined FAL servers have been tried.
-------------------------------------------------------------
Check that the initialization of CONTROL_FILE_RECORD_KEEP_TIME
parameter is set to a value large enough
enough to keep adequate record switch information to solve
ARCHIVELOG gaps.
-------------------------------------------------------------
In my opinion why this happens because
----------------------------------------------------------
During synchronization ARCH process detects that gap archive logs are present in the side watching or we can say that the archive requested connects
[Customer] [SERVER] FAL FAL are already transferred on transferred before failover.
So after showning this warning, it replaces the archive logs that are ever-present in the side watching.

Please me corret I if am wrong...
CONTROL_FILE_RECORD_KEEP_TIME = 7

Please help me on this so that I will no more get the warning above...

Thank you
user9085814 wrote:
Hello

We used to recreate a database waiting for backup to cold after a PROD failover to STANDBY mode. (on a weekly basis)

During the synchronization of the day before with a production that we get under WARNING
-------------------------------------------------------------------------------------------------------
FAL [client]: you cannot request the gap sequence
GAP - thread 1 sequence 45217-45225
FAL [client]: all defined FAL servers have been tried.
-------------------------------------------------------------
Check that the initialization of CONTROL_FILE_RECORD_KEEP_TIME
parameter is set to a value large enough
enough to keep adequate record switch information to solve
ARCHIVELOG gaps.
-------------------------------------------------------------
In my opinion why this happens because
----------------------------------------------------------
During synchronization ARCH process detects that gap archive logs are present in the side watching or we can say that the archive requested connects
[Customer] [SERVER] FAL FAL are already transferred on transferred before failover.
So after showning this warning, it replaces the archive logs that are ever-present in the side watching.

Please me corret I if am wrong...
CONTROL_FILE_RECORD_KEEP_TIME = 7

Please help me on this so that I will no more get the warning above...

Thank you

If you think that the problem with "CONTROL_FILE_RECORD_KEEP_TIME", it means that wrong you ;)
Oracle offering to check if the archives are out of detention, his don't say no not any problems with the parameter. If this parameter too low value and the archives are not applied within that time, then you need to adjust the value.

Now coming to the point, Archives of * 45217-45225 * Miss waiting,.

(1) check whether exist on primary or not
(2) if it is deleted, restore these backups sauvegardΘ
(3) if not accessible to the general public of these backup archives, you must perform the rollforward differential to recover your database pending, using the link below
http://www.Oracle-CKPT.com/RMAN-incremental-backups-to-roll-forward-a-physical-standby-database-2/

Newspapers do not apply to Standby Database
I'm scared, I'm back.

I now a primary database and an expectation of database and logs are shipped but not applied. Did some research and I got to the point where in my alert log I find the following when I try to start MRP:
Fri Jun 29 15:03:40 2012
modify the recovery of database managed standby database disconnect from the session
Try to start the standby recovery process thoroughly managed (SAPDS)
Fri Jun 29 15:03:40 2012
MRP0 started with pid = 29, OS id = 23272
MRP0: Background Managed Standby recovery process started (SAPDS)
has started the process of logmerger
Fri Jun 29 15:03:45 2012
Managed Standby recovery not using real time applies
Reading file ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' header (fno 2) failed with ORA-01206
Data file header 2 replay failed with ORA-01206
MRP0: Background Media Recovery terminated with error 1110
Errors in the /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc file:
ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: the file is not part of this database - bad database id
Recovery slave PR00 is previously released with the exception of 1110
Errors in the /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc file:
ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: the file is not part of this database - bad database id
MRP0: Stopping the process background Media Recovery (SAPDS)
Completed: change the recovery of database managed standby database disconnect from the session

Therefore, my question is how can I get out of this and get my logs to apply pending?
Hello again;

Do you think if I tried to repeat the duplicate?

Yes I think you should do this.

Give me a few minutes and I'll review my Word document and provide here an overview step by step as insurance.

I always clean the day before before trying another dup

OVERVIEW

Step 1 - password file FRO sleep - the primary copy and rename
Step 2 - On the remote server Directory Structure - Make sure noting is missing
Step 3 - Oracle Net Setup - entered for the CLONE in your TNSNAMES file. ORA on both servers
Step 4 - Adding SID_LIST_LISTENER (guess named listener LISTENER)
Step 5 - located in listener.ora and sqlnet.ora both servers wait times
Step 6 - settings of the auxiliary Instance initialization file
Step 7 - Set SID of the auxiliary Instance
Step 8 - create a SPFILE to the new database using a file with the INIT parameters pfile
Step 9 - shutdown and startup nomount on new Spfile (auxiliary Instance)
Step 10 - Start RMAN and run the command DUPLICATE

SID_LIST_LISTENER example of mine
```
SID_LIST_LISTENER =
   (SID_LIST =
       (SID_DESC =
       (SID_NAME = PLSExtProc)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
       (PROGRAM = extproc)
     )
       (SID_DESC =
       (global_dbname = CLONE.hostname)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
       (sid_name = CLONE)
   )
)
```
Avoid delays
```
Add these to both servers

To listener.ora
INBOUND_CONNECT_TIMEOUT_ = 120

To sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120

Then stop and start the listener.
```
RMAN

$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby

Connect should return something like this
```
connected to target database: RECOVER9 (DBID=3806912436)
connected to auxiliary database: CLONE (not mounted)
```
RMAN > current database of target duplicate for the eve of the database NOFILENAMECHECK.

INIT Extras

In order to avoid the ORA-09925 do of course the PFILE core_dump_dest value and audit_file_dest a file

Best regards

mseberg

Published by: mseberg on June 29, 2012 11:12

Incremental backup gives error on Standby Database.

Similar Questions

10.5.2 steps of recovery for databases physical standby

Maybe you are looking for