Rman back up on stand by database

Hi all,
I created one stand by database. log shipping is not in place yet.
I manually copied rman files and archive files from the primary database and copied to standby.
Whenever I was trying to restore the database. it gives me below error. please see and let me know if I am doing it wrong.
Recovery Manager: Release 10.2.0.3.0 - Production on Tue Sep 28 11:20:16 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: WTFNL (DBID=3371173325, not open)
RMAN>
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 09/28/2010 11:20:16
RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file
RMAN>
Recovery Manager complete.
RAMAN backup completed.
Tue Sep 28 11:20:16 EST 2010
Thanks

Make sure from where you are giving commands...
Oracle Error :: RMAN-05021
this configuration cannot be changed for a BACKUP or STANDBY control file
Cause
The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY. The following configurations can be changed only when connected to primary database instance that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ENCRYPTION CONFIGURE DB_UNIQUE_NAME
Action
Connect to primary database instance and execute the command.

Similar Messages

Error while taking RMAN back up - RMAN-03009: failure of backup command ..

Hi Experts,
I am trying to take RMAN back up but at the end I get this error message.. I found a solution at http://www.oracle-base.com/articles/9i/RecoveryManager9i.php
But this is of oracle 9i. Can I use it on 10g too ?
So is this Step correct ?
1) First create a user to hold the recovery catalog:
a) CONNECT sys/password@w2k1 AS SYSDBA
b) GRANT connect, resource, recovery_catalog_owner TO rman;
2) Then create the recovery catalog:
a) C:>rman catalog=rman/rman@w2k1
b) RMAN> create catalog tablespace "RMAN";
c) RMAN> exit
3) Register Database
a) C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
b) RMAN> register database;
c) Existing user-created backups can be added to the catalog using: (*So far no Back up taken so I guess this step can be ignored*)
i) RMAN> catalog datafilecopy 'C:\Oracle\Oradata\TSH1.dbf';
ii) RMAN> catalog archivelog 'log1', 'log2', 'log3', ... 'logN';
4) Full Backup Configuration
RMAN> configure retention policy to recovery window of 7 days;
RMAN> configure default device type to disk;
RMAN> configure controlfile autobackup on;
RMAN> configure channel device type disk format 'C:\Oracle\Admin\W2K2\Backup%d_DB_%u_%s_%p';
5) Full back up
RMAN> run {
backup database plus archivelog;
delete noprompt obsolete;
6) RMAN> resync catalog;
Starting backup at 15-MAY-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00006 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
60430230208_DB.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\UNDOTBS01.DB
F
input datafile fno=00007 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\DM_MENTOR200
60430230208_IND.DBF
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSAUX01.DBF
input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\EXAMPLE01.DB
F
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 15-MAY-10
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
03
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
channel ORA_DISK_1: starting piece 1 at 15-MAY-10
channel ORA_DISK_1: finished piece 1 at 15-MAY-10
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\BACKUPSET\2010_05
_15\O1_MF_NCNNF_TAG20100515T045136_5YX3TTFT_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:17
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/15/2010 05:11:21
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/15/2010 05:11:
03
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
RMAN>
Thanks & Regards,
Ranjith John

Provided you consult the 10g RMAN documentation and the online error documentation: yes.
But apparently you didn't check documentation, not even the error messages!!!!! Why?
You are backing up to the Flash Recovery Area, and the error messages mean too much space is occupied.
How to configure the Flash Recovery Areea is fully documented in the Backup and Recovery manual for 10g at http://tahiti.oracle.com
READ IT.
Please do not ask a volunteer to abstract it.
Sybrand Bakker
Senior Oracle DBA

Rman Backupset size is exceeding the database size

Hi
my rman backup size is exceeding the database backup size and occupying the full mountpoint. and finally due to space issue, backup is failing.
Below is the RMAN script
run {
backup
incremental level 0
tag ASCPLVL0
database plus archivelog ;
delete noprompt backupset completed before 'sysdate - 4/24' ;
Please look into this
Regards
M. Satyanvesh

Are you using compression?
Ans: No
The size of an RMAN backup isn't always proportional to the size of the database.
Ans: yeah I know, but it should be somewhere near to database size(lets say 100gb or 150 gb variance)
How many archivelogs are you backing up with your database? This is possibly a factor in the size of your db backup.
Ans: archive log count per day is 18 and size is 34gb
Have you got a retention policy in place and do you regularly delete obsolete backups/archivelogs?
Ans: yes
Are you taking this backup as part of a backup strategy? or is this just a one off for some other purpose which would seem to be the case.
Ans: This is production systesm so its a part of backup strategy

What is the best method to revert back to 'golden' image of database

Hello,
I want to have a 'golden' image of my test database. What is the best method to keep reverting back to this 'golden' image after testers are done with testing. What I mean is I want to set up a test database for testers. Testers can insert,update, delete on objects as they like. But after the testers have completed their testing, I want to revert the database back to the 'golden' image. This 'golden' image is the state of the database before testers perform their tests. I need to revert back to the 'golden' image many times over as we have to perform many different tests.
I thought about export and import (9i database) but takes 6 hours, too long. I tried using rman and was successful the first time, (set until time; restore database; recover database; open resetlogs;). The seconde time using rman, I got error saying the set until time was before the resetlogs time. I think I would have to restore the control file before the resetlog time frame before I can recover to the set until time, again.
What is a straight forward method to have a 'golden' image so I can keep on restoring back to it? This database is a test 9i database and it is in archive log mode but it doesn't need to be. I just need a best practice method, whether it is rman, exp/imp, manual backup/restore? Something I can use time and time over again. Thank you.

If it is a Test envionment, can you just take a COLD Backup (database files
plus control files) ? How big is the database ? What platform is it on ?
eg in a COLD Backup
a. If using a script, run multiple "cp" (or cpio/tar) commands in parallel to
copy different database files
b. If using RMAN (in NOMOUNT), use multiple Chnanels.
Note : Remember to include ControlFile Backups and Restores as well.

Open stand by database to run scripts

hello all,
I am having one physical stand by database which is synchronized with production database.Now i am have some scripts which extracts data.But i want to run this scripts on stand by database which is in recovery mode.Now i want to make the stand by database in read only mode and after executing the scripts make it back to stand by database in recovery mode.My plan to make the stand by database is as follows.
SQL>connect / as sysdba
SQL>recover managed standby database cancel;
SQL>alter database open;
Now i want to make it back to physical standby database and my plan is as below.
SQL>connect / as sysdba
SQL>shutdown immediate;
SQL>alter database mount standby database;
SQL>recover managed standby database disconnect;
Will the above scripts run for my purpose.I don't have a test server to test it.
DB version:9.2.0.6
Thank You All...

First off, I would say that not having a test environment to test this sort of thing is exceptionally short-sighted. If the database is important enough to go through the effort of setting up a physical standby, it is well worth having a proper test environment so that you can test scripts before applying it to production.
Second, you will want to review the documentation for [opening a physical standby database for read-only access|http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/manage_ps.htm#1014483] which walks through a different set of steps than you have outlined here. I wouldn't dream of running the documented script on a production environment, though, without having first run it in some sort of test environment.
Justin

I need Rman Back Demo

_ hi_
i m new ORacle dabatase administrator   i need ur help frineds
i need Rman backup demo any one can tell me with rman recover demo   if i lost some thing in database please any one can send me full success Rman back demo
thanks and bestregards
kashif
Edited by: user8285127 on Dec 6, 2009 11:19 PM

user8285127 wrote:
_ hi_
i m new ORacle dabatase administrator   i need ur help frineds
i need Rman backup demo any one can tell me with rman recover demo   if i lost some thing in database please any one can send me full success Rman back demo
thanks and bestregards
kashif
Edited by: user8285127 on Dec 6, 2009 11:19 PMgo to your favorite online bookstore and locate a copy of "Oracle Database RMAN Backup and Recovery" by Hart and Freeman (Oracle Press). It is no substitute for the official docs found at tahiti.oracle.com, but is a very good supplement.

RMAN 11gr2 ORA-00308 when dulplicate database from active

Hi,
I'm trying to clone a production database (Oracle 11.2.0.3) from HP-UX IA64 to Solaris 10 (Sparc 64) (source on Filesystem, target on ASM)
the previous steps was done (same oracle software installation, same patches, sqlnet comunication, etc.)
but the RMAN fails at end of the process:
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Aug 22 09:44:34 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SIN (DBID=634625013)
connected to recovery catalog database
connected to auxiliary database: SIN (not mounted)
RMAN> run
+2> {+
+3> allocate channel c1 type disk;+
+4> allocate channel c2 type disk;+
+5> allocate channel c3 type disk;+
+6> allocate channel c4 type disk;+
+7> allocate auxiliary channel a1 type disk;+
+8> allocate auxiliary channel a2 type disk;+
+9> set newname for datafile 1 to '+DG_DATA';+
+10> set newname for datafile 2 to '+DG_DATA';+
+11> set newname for datafile 3 to '+DG_DATA';+
+12> set newname for datafile 4 to '+DG_DATA';+
+13> set newname for datafile 5 to '+DG_DATA';+
+14> set newname for datafile 6 to '+DG_DATA';+
+15> set newname for datafile 7 to '+DG_DATA';+
+16> set newname for datafile 8 to '+DG_DATA';+
+17> set newname for datafile 9 to '+DG_DATA';+
+18> set newname for datafile 10 to '+DG_DATA';+
+... to...+
+398> set newname for datafile 390 to '+DG_DATA';+
+399> set newname for datafile 391 to '+DG_DATA';+
+400> duplicate target database to "sin" from active database nofilenamecheck+
+401> DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','+DG_DATA/',+
+402> '/u11/oradata/sin/','+DG_DATA/',+
+403> '/u07/oradata/sin/','+DG_DATA/',+
+404> '/u08/oradata/sin/','+DG_DATA/',+
+405> '/u09/oradata/sin/','+DG_DATA/');+
+406> }+
+407>+
starting full resync of recovery catalog
full resync complete
allocated channel: c1
channel c1: SID=1787 device type=DISK
allocated channel: c2
channel c2: SID=2406 device type=DISK
allocated channel: c3
channel c3: SID=850 device type=DISK
allocated channel: c4
channel c4: SID=1146 device type=DISK
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=1514 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
+...+
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 22-AUG-12
contents of Memory Script:
+{+
sql clone "create spfile from memory";
+}+
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
+{+
shutdown clone immediate;
startup clone nomount;
+}+
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    7317790720 bytes
Fixed Size                     2173456 bytes
Variable Size               3808433648 bytes
Database Buffers            3489660928 bytes
Redo Buffers                  17522688 bytes
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=758 device type=DISK
contents of Memory Script:
+{+
sql clone "alter system set control_files =
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
sql clone "alter system set db_name =
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+sql clone "alter system set db_unique_name =+
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+shutdown clone immediate;+
+startup clone force nomount+
+backup as copy current controlfile auxiliary format '+DG_DATA/sin/controlfile/current.512.791978153';+
+restore clone controlfile to '+DG_DATA/sin/controlfile/current.625.791978153' from+
+'+DG_DATA/sin/controlfile/current.512.791978153';+
+sql clone "alter system set control_files =+
+''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/current.625.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+shutdown clone immediate;+
+startup clone nomount;+
+alter clone database mount;+
+}+
+executing Memory Script+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.562.791978153'' comment= ''Set by RMAN'' scope=spfile+
+sql statement: alter system set db_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+sql statement: alter system set db_unique_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+Oracle instance shut down+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+Starting backup at 22-AUG-12+
+channel c1: starting datafile copy+
+copying current control file+
+output file name=/u06/tmpapp/rmanbkps/snapcf_sin.f tag=TAG20120822T094657 RECID=49 STAMP=791977621+
+channel c1: datafile copy complete, elapsed time: 00:00:01+
+Finished backup at 22-AUG-12+
+Starting restore at 22-AUG-12+
+channel a2: skipped, AUTOBACKUP already found+
+channel a1: copied control file copy+
+Finished restore at 22-AUG-12+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.625.791978153'' comment= ''Set by RMAN'' scope=spfile+
+Oracle instance shut down+
+connected to auxiliary database (not started)+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+database mounted+
+Using previous duplicated file +DG_DATA/sin/datafile/system.666.791914845 for datafile 1 with checkpoint SCN of 46164275052+
+Using previous duplicated file +DG_DATA/sin/datafile/undotbs1.678.791913821 for datafile 2 with checkpoint SCN of 46164227408+
+...+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.498.791939115 for datafile 389 with checkpoint SCN of 46165353395+
+Using previous duplicated file +DG_DATA/sin/datafile/mytablespace.674.791914359 for datafile 390 with checkpoint SCN of 46164253329+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.499.791939115 for datafile 391 with checkpoint SCN of 46165353396+
+contents of Memory Script:+
+{+
+sql 'alter system archive log current';+
+}+
+executing Memory Script+
+sql statement: alter system archive log current+
+contents of Memory Script:+
+{+
+backup as copy reuse+
+archivelog like "/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065832.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065833.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065834.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065835.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065836.ARC" auxiliary format+
+"+DG_DATA" ;+
+catalog clone start with "+DG_DATA";+
+catalog clone datafilecopy "+DG_DATA/sin/datafile/system.666.791914845",+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.679.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.689.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.690.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.677.791914357",+
+"+DG_DATA/sin/datafile/drsys.621.791939555",+
+"+DG_DATA/sin/datafile/high_idx.663.791914889",+
+"+DG_DATA/sin/datafile/tools.507.791939555",+
+...+
+"+DG_DATA/sin/datafile/bkptemp.497.791939113",+
+"+DG_DATA/sin/datafile/med_dat.498.791939115",+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359",+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+switch clone datafile 1 to datafilecopy+
+"+DG_DATA/sin/datafile/system.666.791914845";+
+switch clone datafile 2 to datafilecopy+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821";+
+switch clone datafile 3 to datafilecopy+
+...+
+"+DG_DATA/sin/datafile/med_dat.498.791939115";+
+switch clone datafile 390 to datafilecopy+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359";+
+switch clone datafile 391 to datafilecopy+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+}+
+executing Memory Script+
+Starting backup at 22-AUG-12+
+channel c1: starting archived log copy+
+input archived log thread=1 sequence=65832 RECID=48339 STAMP=791913640+
+channel c2: starting archived log copy+
+input archived log thread=1 sequence=65833 RECID=48340 STAMP=791933223+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65834 RECID=48341 STAMP=791939052+
+channel c4: starting archived log copy+
+input archived log thread=1 sequence=65835 RECID=48342 STAMP=791962351+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.791978259 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:00:35+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65836 RECID=48343 STAMP=791977692+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 RECID=0 STAMP=0+
+channel c1: archived log copy complete, elapsed time: 00:00:51+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.791978259 RECID=0 STAMP=0+
+channel c2: archived log copy complete, elapsed time: 00:01:41+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.791978295 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:01:06+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.791978259 RECID=0 STAMP=0+
+channel c4: archived log copy complete, elapsed time: 00:01:41+
+Finished backup at 22-AUG-12+
+searching for all files that match the pattern +DG_DATA+
+List of Files Unknown to the Database+
+=====================================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+cataloging files...+
+cataloging done+
+List of Cataloged Files+
+=======================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65835.516.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+List of Files Which Where Not Cataloged+
+=======================================+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+RMAN-07518: Reason: Foreign database file DBID: 0 Database Name:+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/system.666.791914845 RECID=442 STAMP=791978374+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.678.791913821 RECID=443 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.679.791913821 RECID=444 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.689.791913821 RECID=445 STAMP=791978375+
+cataloged datafile copy+
+...+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.498.791939115 RECID=830 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/mytablespace.674.791914359 RECID=831 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.499.791939115 RECID=832 STAMP=791978408+
+datafile 1 switched to datafile copy+
+input datafile copy RECID=442 STAMP=791978374 file name=+DG_DATA/sin/datafile/system.666.791914845+
+datafile 2 switched to datafile copy+
+input datafile copy RECID=443 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.678.791913821+
+datafile 3 switched to datafile copy+
+input datafile copy RECID=444 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.679.791913821+
+datafile 4 switched to datafile copy+
+input datafile copy RECID=445 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.689.791913821+
+...+
+datafile 389 switched to datafile copy+
+input datafile copy RECID=830 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.498.791939115+
+datafile 390 switched to datafile copy+
+input datafile copy RECID=831 STAMP=791978408 file name=+DG_DATA/sin/datafile/mytablespace.674.791914359+
+datafile 391 switched to datafile copy+
+input datafile copy RECID=832 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.499.791939115+
+contents of Memory Script:+
+{+
+set until scn 46167049411;+
+recover+
+clone database+
+delete archivelog+
+;+
+}+
+executing Memory Script+
+executing command: SET until clause+
+Starting recover at 22-AUG-12+
+starting media recovery+
+archived log for thread 1 with sequence 65832 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.7+
+91978259+
+archived log for thread 1 with sequence 65833 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.7+
+91978259+
+archived log for thread 1 with sequence 65834 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.7+
+91978259+
+archived log for thread 1 with sequence 65835 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.7+
+91978259+
+archived log for thread 1 with sequence 65836 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.7+
+91978295+
+archived log file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 thread=1 sequence=65832+
+released channel: c1+
+released channel: c2+
+released channel: c3+
+released channel: c4+
+Oracle Error:+
+ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below+
+ORA-01194: file 1 needs more recovery to be consistent+
+ORA-01110: data file 1: '+DG_DATA/sin/datafile/system.666.791914845'+
*+released channel: a1+*
*+released channel: a2+*
*+RMAN-00571: ===========================================================+*
*+RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============+*
*+RMAN-00571: ===========================================================+*
*+RMAN-03002: failure of Duplicate Db command at 08/22/2012 09:52:27+*
*+RMAN-05501: aborting duplication of target database+*
*+RMAN-03015: error occurred in stored script Memory Script+*
*+RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DG_DATA/sin/archivelog/2012_08_22/thre+*
*+ad_1_seq_65832.513.791978259'+*
*+ORA-00308: cannot open archived log '+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259'+*
+Recovery Manager complete.+
the error is always the same, a previous backup with RMAN was taken on tape on the source database (production).
Please help me to find what is wrong here!!

Hi mseberg
that's exactly i'm doing:
1. Create an Oracle Password File for the Auxiliary Database
a. done, passwd file created*
2. Create the Directory Structure on the remote server
a. done, all the admin structure wa created.*
3. Oracle Net Setup ( you need an entry for the CLONE in your TNSNAMES.ORA on both servers ) ( I use SID_LIST_LISTENER entry for static )
a. done, i have the entries working on my tnsnames.ora (source and target with static listeners)*
4. Create an Initialization Parameter File for the Auxiliary Instance ( I use Parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change locations)
a. done, this is my initialization file:*
*.audit_file_dest='/u01/app/oracle/admin/sin/adump'*
*.audit_trail='db'*
*.compatible='11.2.0.0.0'*
*.db_block_size=8192*
*.db_create_file_dest='DG_DATA'+*
*.db_domain=''*
*.db_files=2048*
*.db_name='sin'*
*.db_recovery_file_dest='DG_DATA'+*
*.db_recovery_file_dest_size=20G*
*.diagnostic_dest='/u01/app/oracle'*
*.dispatchers='(PROTOCOL=TCP) (SERVICE=sinXDB)'*
*.log_archive_format='%t_%s_%r.dbf'*
*.memory_target=7340032000*
*.open_cursors=300*
*.processes=2000*
*.remote_login_passwordfile='EXCLUSIVE'*
*.sessions=2205*
*.undo_tablespace='UNDOTBS1'*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/')+
LOG_FILE_NAME_CONVERT=('/u04/oradata/sin/','DG_DATA/',+*
+'/u05/oradata/sin/','+DG_DATA/',+
+'/u03/oradata/sin/','+DG_DATA/',+
+'/u02/oradata/sin/','+DG_DATA/')+
and this is my command from RMAN:
run*
*+{+*
allocate channel c1 type disk;*
allocate channel c2 type disk;*
allocate channel c3 type disk;*
allocate channel c4 type disk;*
allocate auxiliary channel a1 type disk;*
allocate auxiliary channel a2 type disk;*
set newname for datafile 1 to 'DG_DATA';+*
set newname for datafile 2 to 'DG_DATA';+*
set newname for datafile 3 to 'DG_DATA';+*
set newname for datafile 4 to 'DG_DATA';+*
set newname for datafile 5 to 'DG_DATA';+*
set newname for datafile 6 to 'DG_DATA';+*
set newname for datafile 7 to 'DG_DATA';+*
set newname for datafile 8 to 'DG_DATA';+*
set newname for datafile 9 to 'DG_DATA';+*
set newname for datafile 10 to 'DG_DATA';+*
+...+
set newname for datafile 390 to 'DG_DATA';+*
set newname for datafile 391 to 'DG_DATA';+*
duplicate target database to "sin" from active database nofilenamecheck*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/');+
+}+
do you think the problem may be in the name of the database?, I am using the same name in the auxiliary
and when I get the error, I have the same dbid in both databases (source and destination)
Thanks
MM

RMAN DUPLICATE FOR STANDBY FROM ACTIVE DATABASE fails

Hello
I'm trying to use RMAN DUPLICATE to create a standby database using Oracle 11.2.0.3 with PSU 6 on HP-UX.
Primary is 2 node RAC. Standby is also 2 node RAC.
Standby database instance is started in nomount mode.
I use:
duplicate target database for standby from active database
spfile
<some spfile parameters>
with PFILE I get:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 12:41:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/01/2013 12:41:13
RMAN-11003: failure during parse/execution of SQL statement: alter system set spfile= '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-01565: error in identifying file '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
With SPFILE I get;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 13:06:34
RMAN-05501: aborting duplication of target database
RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause
But I do have RMAN connexion to target database.
Thanks for your help.

Here is the output beginning of the script which clearly shows that I'm always connected to target database:
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 1 13:05:47 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: CU (DBID=1143962925)
connected to auxiliary database: CU (not mounted)
RMAN> set echo on
2> run
3> {
4> configure device type disk parallelism 10;
5>   allocate channel pr1 type disk;
6>   allocate channel pr2 type disk;
7>   allocate channel pr3 type disk;
8>   allocate channel pr4 type disk;
9>   allocate channel pr5 type disk;
10>   allocate channel pr6 type disk;
11>   allocate channel pr7 type disk;
12>   allocate channel pr8 type disk;
13>   allocate channel pr9 type disk;
14>   allocate channel pr10 type disk;
15>   allocate auxiliary channel st1 type disk;
16>   allocate auxiliary channel st2 type disk;
17>   allocate auxiliary channel st3 type disk;
18>   allocate auxiliary channel st4 type disk;
19>   allocate auxiliary channel st5 type disk;
20>   allocate auxiliary channel st6 type disk;
21>   allocate auxiliary channel st7 type disk;
22>   allocate auxiliary channel st8 type disk;
23>   allocate auxiliary channel st9 type disk;
24>   allocate auxiliary channel st10 type disk;
25>   duplicate target database for standby from active database
26>   spfile

How to "roll back" the model if a database update fails

I'd like to know if there's a way to "roll back" the model (the values in the managed beans) if a service call to a database fails during the Invoke Application phase. My understanding of the JSF lifecycle is that the values in the model are updated before a service call to a database would happen. If the database update operation fails, it seems to me that the data in the model and the database would be inconsistent.
For example, say I have a ridiculously simple application that updates a names database. The fields are id, last name, first name. The application has a simple view that allows the user to update a name in the database. The user updates the last name field for a particular record from "Doe" to "Smith" and clicks "submit". The request goes through the lifecycle, the model values are updated from the web form during the Update Model Values phase, then the call to update the database fails during the Invoke Applications phase (the database connection failed). When the Render Response phase completes, the UI would display an error message where I put <h:messages> but the last name value in the UI would show "Smith" instead of "Doe". Is there something I can do to roll the model value back to "Doe" if the database call fails?
I know that I could redirect to a technical error page, but I'd like to avoid it unless it is the best thing to do.
I'd appreciate any advice you can offer.
Thanks.
- Luke

I'd like to know if there's a way to "roll back" the model (the values in the managed beans) if a service call to a database fails during the Invoke Application phase. My understanding of the JSF lifecycle is that the values in the model are updated before a service call to a database would happen. If the database update operation fails, it seems to me that the data in the model and the database would be inconsistent.
For example, say I have a ridiculously simple application that updates a names database. The fields are id, last name, first name. The application has a simple view that allows the user to update a name in the database. The user updates the last name field for a particular record from "Doe" to "Smith" and clicks "submit". The request goes through the lifecycle, the model values are updated from the web form during the Update Model Values phase, then the call to update the database fails during the Invoke Applications phase (the database connection failed). When the Render Response phase completes, the UI would display an error message where I put <h:messages> but the last name value in the UI would show "Smith" instead of "Doe". Is there something I can do to roll the model value back to "Doe" if the database call fails?
I know that I could redirect to a technical error page, but I'd like to avoid it unless it is the best thing to do.
I'd appreciate any advice you can offer.
Thanks.
- Luke

RMAN-06136: ORACLE error from auxiliary database

Dear All,
When i start to recover a tablespace(TSPITR) using RMAN, getting below errors. Could any guide me
RMAN-03002: failure of recover command at 02/07/2013 14:12:30
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01119: error in creating database file '/rman/SHFLCLN/oradata'
ORA-27056: could not delete file
IBM AIX RISC System/6000 Error: 1: Not owner
RMAN-06956: create datafile failed; retry after removing /rman/SHFLCLN/oradata from OS

01119, 00000, "error in creating database file '%s'"
// *Cause: Usually due to not having enough space on the device.
// *Action:

Can we run application services when physical stand by database is in read

can we run application services when physical stand by database is in read only mode
i Want to up the EBS application services and check login when phyiscal standby database is in read only mode.
Is it possible? for checking dataguard database application as well.

but i just want to know that can i start EBS application services and nagivate the application.Without distrubing my primary database and application.You should not do as the moment you open the standby database it becomes invalid.
Thanks,
Hussein

Backup archivelog all and backup archivelog in rman back

Hi,
Whats the difference between backup archivelog all and backup archivelog in rman backup.

Please find below explanation from the online documentation;
+"+
+If you specify BACKUP ARCHIVELOG ALL, then RMAN backs up exactly one copy of each distinct log sequence number. For example, if you archive to multiple destinations, RMAN backs up one copy of each log sequence number—not each copy of each log sequence number. For other commands, such as DELETE ALL does refer to every log, even duplicate log sequences.+
+"+
Hope That Helps.
Ogan
Edited by: Ogan Ozdogan on 27.Tem.2010 00:38
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta007.htm#RCMRF107

Adding Temp tablespace to physical stand by database?

I am getting the below error when i try to load data using SQL loader from physical stand by database to another database after making the physical stand by database in read only mode.
ORA-25153: Temporary Tablespace is Empty.
On primary database when i query
SQL>select ts#,name from v$tablespace;
TS# NAME
2 TEMP
On physical stand by when i query
SQL>select ts#,name from v$tablespace;
TS# NAME
2 TEMP
On primary DB when i query
select name from v$tempfile where ts#=2;
NAME
/dev/vx/rdsk/oradata/tempfile0101
On standby when i query
SQL>select name from v$tempfile where ts#=2;
no rows selected
At this point do i need to add datafile to the TEMP tablespace of stand by database or just need to add TEMP tablespace to stand by database.?
DB version:9.2.0.6
Thank You all...

Can you make sure that /dev/vx/rdsk/oradata/tempfile0101 is copied to standby site during the standby creation. Often it happens that the hot backups are copied to standby ste and generally they dont contain temp files. If the files is present , then i'll suggest you to do a quick bounce of standby instance to make sure that controlfile attempted to access it. You can also try recreating the standby control file on promary and copy it to standby site along with the tempfile and start the instance with new control file.
If you want to add temp files to the standby instance, the only option you have is to add them on primary site. If you have standby_file_management as auto they will get copied over. If not you can copy the files to standby instance and restart the recovery.
Please let us know if any of the hints are applicable to your case.
-Ravi

Stand by database

Hi guys,
OS: Windows Server 2003 (32 bit)
DB Version: 10.2.0.3
Question:
Simple question I guess but still I'm failing to understand the logic. Will the changes applied on the primary database also occur in the stand-by, for instance if I delete a table in the primary database, will that also take effect in the stand-by database?
Regards,
Durbanite

Have you had a log switch to create a new archived redo log in that time?? the change will only be transported across to the standby when it gets writted to an archived redo log that is then sent to the standby and applied (if using physical standby)
If not, in sqlplus, do : alter system switch logfile+; and watch it get sent to the standby and then check the if the table is still there or not.
HTH,
Ric.

Manually Apply Archived log to stand by database

Hi all,
I'm using Oracle 10g. So, we need to apply the archived logs of Primary database to stand by database, but this process must be manually.
A "robot" copy the archived logs to destination. I need to get these archived logs from destination and manually apply to stand by database.
How can I do this?
thank you very much!!!!

How can I do this?First stop current recover process as
alter database recover managed standby database cancel;Then transfer all need archive logs from primary to standby side and apply these manually using below command.
recover standby database until cancel
/*this command will ask full path of archive logs
and give these then finally enter "CANCEL" word*/Finally you can continue normal/automatic state using
alter database recover managed standby database ;

Rman back up on stand by database

Similar Messages

Maybe you are looking for