RMAN-06053 RMAN-06025 on Standby Database

Dear community,
we have an problem on our standby database (11.2.0.3 64Bit). We use the following RMAN script on the standby side:
connect target *
crosscheck archivelog all;
crosscheck backup;
delete noprompt expired archivelog all;
delete noprompt expired backup;
recover database;
exit;In the alertlog of the standby database we found following:
Thu Sep 20 12:05:33 2012
alter database recover datafile list clear
Completed: alter database recover datafile list clear
alter database recover datafile list
1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20
Completed: alter database recover datafile list
1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20
alter database recover datafile list
241 , 242 , 243 , 244 , 245 , 246 , 247 , 248 , 249 , 250 , 251 , 252 , 253 , 254
Completed: alter database recover datafile list
241 , 242 , 243 , 244 , 245 , 246 , 247 , 248 , 249 , 250 , 251 , 252 , 253 , 254
alter database recover if needed
start until cancel using backup controlfile
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 12 slaves
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile
Thu Sep 20 12:05:58 2012
alter database recover cancel
Media Recovery Canceled
Completed: alter database recover cancel In the RMAN Logfile will be logged:
archived log for thread 2 with sequence 3693 is already on disk as file /u03/fast_recovery_area/DBDB/archivelog/2012_09_20/2_3693_766974880.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/20/2012 12:05:52
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 2 with sequence 2984 and starting SCN of 840244104 found to restore
RMAN-06025: no backup of archived log for thread 2 with sequence 2983 and starting SCN of 840041348 found to restore
RMAN-06025: no backup of archived log for thread 2 with sequence 2982 and starting SCN of 840021178 found to restore
RMAN-06025: no backup of archived log for thread 2 with sequence 2981 and starting SCN of 839974659 found to restoreCan you please help me to understand why protocoll the database these RMAN-Errors and what is false configured?
Best regards

Do you mean the backup on the primary side was not been done?No. Backups created at primary site are not available to the standby of course, so that wont see them.
The standby database is left behind and the required archivelogs for recovery are not available anymore, and it doesnt know anything about the backups.
- you can restore the archivelogs on primary site from backups then let the standby fetch and apply them - can take a lot of time
- you can make the backups made at primary site available to the standby and register the backup pieces - can be problematic with 3rd party backup solutions
- you can create and incremental backup of primary site to roll forward the standby: http://docs.oracle.com/cd/E11882_01/server.112/e10700/rman.htm#CIHIAADC

Similar Messages

Rman backup with standby database

Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance

726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance
"I scanned thru MOS but could find solutions for rman with active DG."
Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

RMAN backup of STANDBY database

I have just created a STANDBY database using Oracle 8.1.7 which I am trying to backup using RMAN. This would then not impact on the PRODUCTION database, yet still give a valid backup. The problem I am having is that contrary to what I have been told and read about the `duplicate for standby` command, it does not reset the DB_ID. This has the effect that you canot register your new STANDBY database in the RMAN catalog as it sees it as the PRODUCTION instance that was used to create it. I have found several `solutions` on Metalink, which all require the use of a `resetlogs` command, so invalidating the STANDBY database. Does anyone know of a way that I can bypass this problem and carry out valid backups of the STANDBY database ?
TIA
Mark Tindall
Email: [email protected]

Mark,
The STANDBY database must have the same DBID as the production or you could not use the backups taken at a standby
database to recover the production database.
To backup the standby database with RMAN, you must use a recovery catalog. Take at look at http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96566/rcmbackp.htm#445993
for information on how to backup the standby with RMAN.
Tammy

Can i do all rman activities on standby database

HI all
can i do all rman activities on standby database

Hi ,
Please go through the below link , for getting more familiar with managing standby using RMAN.
http://download.oracle.com/docs/cd/B14117_01/server.101/b10823/manage_ps.htm#1024052
Hope it will be helpful.
Thanks,
Balaji K.

Problem in recover physical standby database(Data Guard) by rman

Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle 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: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PM

hi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks

RMAN in standby Database

Hello all,
We want to configure RMAN in physical standby database but getting below error
[oracle@timsdr ~]$ rman catalog rmandr/rmandr@rman target system/password
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Feb 26 17:04:36 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TIMS (DBID=3639374466, not open)
connected to recovery catalog database
RMAN> show all;
RMAN configuration parameters are:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 02/26/2010 17:08:34
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN>
Standby DB is in mount mode.Pls give some idea..

catalog rmandr/rmandr@rmanIs this catalog different from the one that the Production database is registered with ?
Note : You cannot register the same database -- ie Production and Standby have the same DBID -- twice in a catalog.
Yet your catalog reports that the database is not registered.
Seemingly, Production is registered to a different catalog OR is not registered at all.
If using the same Catalog you should
a. NOT register the Standby
b. STOP recovery on the Standby
c. MOUNT STANDBY on the Standby
and then RMAN BACKUP the Standby
Once the Backup is completed, restart Recovery on the Standby.
Hemant K Chitale
http://hemantoracledba.blogspot.com

MANAGING A STANDBY DATABASE-CRITICAL

Hi All,
I had a primary database version 10.2.0.3 which i upgraded to 10.2.0.4. While upgrading the database
i turned off archiving.
After i upgraded the database and brought it up and the listener i started getting errors of
missing archive logs at the standby site.
My standby database is 10.2.0.3.
My question is
1) As i had turned archiving off at the primary site there is a gap in the archive numbers at the primary itself.
arch_1_29345_623164377.dbf
arch_1_29346_623164377.dbf
-rw-r----- 1 oracle dba 5241344 Feb 7 08:43 arch_1_29347_623164377.dbf
-rw-r----- 1 oracle dba 5241344 Feb 7 09:03 arch_1_29348_623164377.dbf
-rw-r----- 1 oracle dba 5241344 Feb 7 09:35 arch_1_29349_623164377.dbf
-rw-r----- 1 oracle dba 2781184 Feb 7 11:57 arch_1_29350_623164377.dbf
--------------------GAP------------------------AS I HAD TURNED ARCHIVING OFF----------------
-rw-r----- 1 oracle dba 5241344 Feb 7 15:57 arch_1_29561_623164377.dbf
-rw-r----- 1 oracle dba 5241344 Feb 7 15:57 arch_1_29562_623164377.dbf
-rw-r----- 1 oracle dba 5241344 Feb 7 15:57 arch_1_29563_623164377.dbf
-rw-r----- 1 oracle dba 5241344 Feb 7 15:57 arch_1_29564_623164377.dbf
I am getting errors that the standby is not in snyc with primary
when i ran query
SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS
2 FROM V$MANAGED_STANDBY;
on standby database
it says i am missing sequence # 29351 which is due to the fact that there is no sequence like that on
my primary itself.
How should i resolve this gap.
Also is it a good idea to upgrade the oracle home on my standbysite to 10.2.0.4 as i have upgraded
my primary

Hello,
Like I said no easy way out of this situation. First option sync both usign RMAN and section option setup from the scratch (that's might not be possbile).
You can also find similar steps under oracle documentation serach for resolving gaps manually/
Here are the steps for first option, study it and make changes to according to your needs
1. On the standby database, stop the managed recovery process
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
2. On the standby database, find the SCN which will be used for the incremental backup at the primary database:
SQL> SELECT CURRENT_SCN FROM V$DATABASE;
This will used in the rman backup command at step 2.
3. In RMAN, connect to the primary database and create an incremental backup from the
SCN derived in the previous step:
RMAN> BACKUP INCREMENTAL FROM SCN <SCN from previous step>
DATABASE FORMAT '/tmp/ForStandby_%U' tag 'FORSTANDBY';
You must create this incremental backup on disk for it to be useful. When you move
the incremental backup to the standby database, you must catalog it at the
standby as described in Oracle Database Backup and Recovery Advanced User's
Guide. Backups on tape cannot be cataloged.
4. Transfer all backup sets created on the primary system to the standby system (note that there may be
more than one backup file created). For example:
SCP /tmp/ForStandby_* standby:/tmp
5. Connect to the standby database as the RMAN target, and catalog all incremental backup pieces:
RMAN> CATALOG START WITH '/tmp/ForStandby';
6. Recover the standby database with the cataloged incremental backup:
RMAN> RECOVER DATABASE NOREDO;
7. In RMAN, connect to the primary database and create a standby control file backup:
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY FORMAT '/tmp/ForStandbyCTRL.bck';
8. Copy the standby control file backup to the standby system. For example:
SCP /tmp/ForStandbyCTRL.bck standby:/tmp
9. Shut down the standby database and startup nomount:
RMAN> SHUTDOWN;
RMAN> STARTUP NOMOUNT;
10. In RMAN, connect to standby database and restore the standby control file:
RMAN> RESTORE STANDBY CONTROLFILE FROM '/tmp/ForStandbyCTRL.bck';
11. Shut down the standby database and startup mount:
RMAN> SHUTDOWN;
RMAN> STARTUP MOUNT;
12. If the primary and standby database data file directories are identical, skip to step
13. If the primary and standby database data file directories are different,
then in RMAN, connect to the standby database, catalog the standby data files,
and switch the standby database to use the just-cataloged data files. For
example:
RMAN> CATALOG START WITH '+DATA_1/CHICAGO/DATAFILE/';
RMAN> SWITCH DATABASE TO COPY;
13. If the primary and standby database redo log directories are identical, skip to step 14. Otherwise, on the standby database, use an OS
utility or the asmcmd utility (if it is an ASM-managed database) to remove all
online and standby redo logs from the standby directories and ensure that the
LOG_FILE_NAME_CONVERT parameter is properly defined to translate log directory
paths. For example, LOG_FILE_NAME_CONVERT='/BOSTON/','/CHICAGO/'.
14. On the standby database, clear all standby redo log groups (there may be more than
3):
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 1;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 2;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
15. If you have flashback enabled:
On the standby database, restart Flashback Database:
SQL> ALTER DATABASE FLASHBACK OFF;
SQL> ALTER DATABASE FLASHBACK ON;
16. If required restart managed recovery in the standby:
On the standby database, restart recovery:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;Regards
Edited by: OrionNet on Feb 7, 2009 6:43 PM

Failed to clone DB from StandBy database

Hello,
      I need to perform a clone of Data Guard physical standby database (production) to use in preproduction. we have a full RMAN backup of standby database.
My restore is failed, i use this steps:
   * full RMAN backup of standby database
* backup control file of primary
* on a new database server, copy backup
* RMAN > restore control file (of brimary)
* RMAN > CATALOG START WITH ' Path of backup'
* crosscheck backup
* restore database
-> the restore is failed with errors messages :
   RMAN-06026: some targets not found - aborting restore
   RMAN-06023: no backup or copy of datafile 4 found to restore
   RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
I retry restore database after restoring a standby control file, it's failed with the same message.
can you help me ,please, to resolve this issue
Regards
Dj

Thank's AbuFazalMdAbbas for your reply,
RMAN > list backup : i display only 3 Piece Name
            BS Key Type LV Size       Device Type Elapsed Time Completion Time
            18364   Incr 1 36.56M     DISK        00:22:11     29-JUL-13
                    BP Key: 18364   Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
                    Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0fofu8j3_1_1
              List of Datafiles in backup set 18364
              File LV Type Ckp SCN    Ckp Time Name
              17   1 Incr 22020167729 29-JUL-13 +DATA/DB1/datafile/indx_fusion54_purge.277.753031091
              25   1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.284.762608775
              44   1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.303.799865601
              64   1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.324.809446025
            BS Key Type LV Size       Device Type Elapsed Time Completion Time
            18365   Incr 1 11.17M     DISK        00:22:12     29-JUL-13
                    BP Key: 18365   Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
                    Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0gofu8j3_1_1
              List of Datafiles in backup set 18365
              File LV Type Ckp SCN    Ckp Time Name
              18   1 Incr 22020167729 29-JUL-13 +DATA/DB1/datafile/indx_fusion54_purge.279.753031091
              26   1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.285.762622281
              45   1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.304.800028323
              65   1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.325.814713695
            BS Key Type LV Size       Device Type Elapsed Time Completion Time
            18366   Incr 1 49.25M     DISK        00:11:54     29-JUL-13
                    BP Key: 18366   Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
                    Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0hofu9sq_1_1
              List of Datafiles in backup set 18366
              File LV Type Ckp SCN    Ckp Time Name
              4    1 Incr 22021555818 29-JUL-13 +DATA/DB1/datafile/users.281.753031093
              27   1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.286.763655749
              47   1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.306.800463801
              66   1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.326.817754983
# cd <location where backup files were copied>
# ls -lrt
      ALL files (piece name in list backup) exist on file System, and it's owner by oracle
# show all
            RMAN> show all;
            using target database control file instead of recovery catalog
            RMAN configuration parameters for database with db_unique_name RSP are:
            CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
            CONFIGURE BACKUP OPTIMIZATION OFF; # default
            CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
            CONFIGURE CONTROLFILE AUTOBACKUP ON;
            CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '+RECO/ctrl_%F';
            CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
            CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
            CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
            CONFIGURE MAXSETSIZE TO UNLIMITED; # default
            CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
            CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
            CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
            CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
            CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/db/dbs/snapcf_MNTRSP.f'; # default

Issue in configuring Standby Database from Active database in 11g by RMAN

POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PM

Hello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg

Issue in creating the standby database from Active database using RMAN

Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.

Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN

How to delete archivelog with RMAN in the Primary and Standby database?

Hello,
I am working on Oracle 10gR2.
My question is :
How could I implement a automatized and secure way of:
1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED to all my standby databases?
2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
Thanks a lot for your help!

on 10G
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#CHDBEICE
Coskan Gundogar
http://coskan.wordpress.com

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Updating standby database from primary using rman

I have created a standby database using rman on my oracle linux server, now i want to update the standby from my primary database, but i didn't remember the scn which i used for creating the standby. How can i find out the scn from where i should perform the incremental backup on the primary, so that i can update my standby database with the latest information.

You simply need to find out which logs on the Primary have yet to be applied to your Standby. Have a look at this (or any Oracle Data Guard docs.): http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/manage_ps.htm#1024046
As long as the logs are available on the Primary server, then they should be sent across to the Standby server. Use the views described in the above link to check for any gaps, etc.

I got the above error while i restore the standby database using RMAN backu

Dear All,
RMAN> crosscheck archivelog all;
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
specification does not match any archive log in the recovery catalogi got the above error while i restore the standby database using RMAN backup from production.
Help need.i take the backup without catalog database.
regards,
DB

rman> list backup;
it shows lengthier but i showed only the corresponding
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3479    Full    17G        DISK        01:29:42     09-FEB-13
        BP Key: 3479   Status: AVAILABLE   Tag: 09FEB13_FULL_ESMSRV1_DB
        Piece Name: /oradatabkp/rman/esmsrv1_full_db_09feb13
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3479
File LV Type Ckp SCN    Ckp Time Name
1       Full 1759250260 09-FEB-13 /esmsrv1/dbs/system01.dbf
2       Full 1759250260 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3       Full 1759250260 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4       Full 1759250260 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5       Full 1759250260 09-FEB-13 /esmsrv1/dbs/example01.dbf
6       Full 1759250260 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7       Full 1759250260 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8       Full 1759250260 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9       Full 1759250260 09-FEB-13 /esmsrv1/dbs/users01.dbf
10      Full 1759250260 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23      Full 1759250260 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39      Full 1759250260 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3480    Full    17G        DISK        01:21:30     09-FEB-13
        BP Key: 3480   Status: EXPIRED   Tag: TAG20130209T200021
        Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_full_Feb09
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3480
File LV Type Ckp SCN    Ckp Time Name
1       Full 1759422265 09-FEB-13 /esmsrv1/dbs/system01.dbf
2       Full 1759422265 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3       Full 1759422265 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4       Full 1759422265 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5       Full 1759422265 09-FEB-13 /esmsrv1/dbs/example01.dbf
6       Full 1759422265 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7       Full 1759422265 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8       Full 1759422265 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9       Full 1759422265 09-FEB-13 /esmsrv1/dbs/users01.dbf
10      Full 1759422265 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23      Full 1759422265 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39      Full 1759422265 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3481    Full    4M         DISK        00:00:03     09-FEB-13
        BP Key: 3481   Status: AVAILABLE   Tag: TAG20130209T212205
        Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_controlfile_copy_Feb09
Controlfile Included: Ckp SCN: 1759462488   Ckp time: 09-FEB-13
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3482    Full    0          DISK        00:00:01     09-FEB-13
        BP Key: 3482   Status: AVAILABLE   Tag: TAG20130209T212212
        Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_spfile_copy_Feb09
SPFILE Included: Modification time: 08-FEB-13
ls -l /oradatabkp
root@drsrv1#ls -l /oradatabkp
total 1108672
drwxr-xr-x   2 ovsd       dba             96 Sep 27 2009 alert_bkp
-rw-r--r--   1 oracle     dba            195 Mar 15 2007 create.sql
drwxr-xr-x   2 oracle     dba           8192 Aug 7 2009 ctrl_bkp
-rw-r--r--   1 root       sys        565114880 Apr 24 2007 drsrv1.tar
drwxrwxrwx   2 root       sys             96 Jun 17 2011 drsrv2-ignitebkp
drwxr-xr-x   4 root       sys             96 Apr 24 2007 esmsrv1
-rw-r-----   1 root       sys        1613824 Feb 22 2007 esmsrv1stby.ctl
-rw-r--r--   1 esmsrv1    dba           5120 Dec 31 2009 esmtables.dmp
-rw-r--r--   1 esmsrv1    dba            538 Dec 31 2009 esmtables.log
drwxrwxrwx   4 root       sys           8192 Mar 10 2009 export
drwxr-xr-x   8 root       sys           8192 Apr 24 2007 finalbackup
-rw-r--r--   1 oracle     dba           3820 Sep 5 2008 invalid.sql
-rw-r--r--   1 esmsrv1    dba         303104 Dec 31 2009 kirdevports.dmp
-rw-r--r--   1 esmsrv1    dba            591 Dec 31 2009 kirdevports.log
drwxr-xr-x   2 root       root            96 Feb 12 2007 lost+found
-rw-r--r--   1 oracle     dba          24954 Aug 9 2009 ovcontrol-090909.ctl
drwxr-xr-x 22 root       sys           8192 Apr 24 2007 ovpi
drwxr-xr-x   2 oracle     dba           8192 Aug 7 2009 pfile_bkp
drwxrw-rw-   4 oracle     dba           8192 Feb 10 15:25 rman
drwxr-xr-x 28 root       sys           8192 Feb 1 17:15 schedbkp
drwxr-xr-x   2 oracle     dba           8192 Jul 11 2011 sdnnm
-rw-r--r--   1 esmsrv1    dba           2196 Dec 31 2009 srirdevports.log
drwxr-xr-x   2 oracle     dba             96 Mar 13 2009 statsreport
-rw-r--r--   1 oracle     dba            966 Mar 15 2007 tbs.sql
drwxr-xr-x   5 oracle     dba             96 Mar 16 2007 testov
drwxr-xr-x   2 root       sys         442368 Mar 11 2009 trendadm_files
root@drsrv1#ls -l /oradatabkp/rman
total 37244448
drwxr-xr-x   2 oracle     dba           8192 Feb 10 15:25 esmsrv1
-rw-r-----   1 oracle     dba        19068198912 Feb 9 14:21 esmsrv1_full_db_09feb13
drwxrw-rw-   2 oracle     dba           8192 Feb 9 21:36 openview
-rw-r--r--   1 oracle     dba         920442 Feb 9 21:37 rmanbkp-all.log

Standby database from RMAN backup

I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
Database : Oracle 10G R2
OS : Windows Server 2003
My backup script is
configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
SQL "ALTER SYSTEM SWITCH LOGFILE";
SQL "ALTER SYSTEM SWITCH LOGFILE";
backup database;
SQL "ALTER SYSTEM SWITCH LOGFILE";
SQL "ALTER SYSTEM SWITCH LOGFILE";
backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
For recovery of a standby database,
I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
set ORACLE_SID=NGINPROD
set dbid 820336652
STARTUP NOMOUNT
RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
RESTORE DATABASE;
Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
RMAN> recover database;
Starting recover at 16-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
starting media recovery
unable to find archive log
archive log thread=1 sequence=253340
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/16/2011 09:31:57
RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
------------------------------------------------------------------------------------------------------------------------------------------------

Here's the standard dcoumentation on the procedure :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
Hemant K Chitale

RMAN-06053 RMAN-06025 on Standby Database

Similar Messages

Maybe you are looking for