RMAN backup multiple database on multiple hosts using recovery catalog

I would like to know if I create one schema called "rman" is enough for repository for backing up multiple database on multiple machines using recovery catalog.
Or is there any better way to handle for reporting peposes.
Quick response is appreciated.
OS Solairs9.
Oracle 9i.
Thanks.
Srini

This worked perfectly fine except for putting sbt in single quotes.
See the reults below.
You are just great Daljith.
Thanks and I do appreciate your help.
Still you did not answe my question.
How come I see backups from June and May even though they are from
diffierent catalog database?
RMAN> allocate channel for maintenance device type 'sbt';
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=9 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: VERITAS NetBackup for Oracle - Release 5.0GA (200)
RMAN> crosscheck backup;
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_22_1_628264333 recid=17 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_21_1_628264333 recid=18 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_23_1_628265249 recid=19 stamp=628265249
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-00 recid=20 stamp=628266151
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_26_1_628266195 recid=21 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_25_1_628266195 recid=22 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-01 recid=23 stamp=628266233
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_29_1_628267004 recid=24 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_28_1_628267004 recid=25 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_30_1_628267919 recid=26 stamp=628267920
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-02 recid=27 stamp=628268832
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_32_1_628268875 recid=28 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_33_1_628268875 recid=29 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-03 recid=30 stamp=628268913
Crosschecked 30 objects
RMAN> delete expired backup;
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
11820 11804 1 1 EXPIRED SBT_TAPE bk_2_1_624018818
11821 11805 1 1 EXPIRED SBT_TAPE bk_1_1_624018817
11822 11806 1 1 EXPIRED SBT_TAPE bk_3_1_624019733
11823 11807 1 1 EXPIRED SBT_TAPE al_5_1_624020641
11824 11808 1 1 EXPIRED SBT_TAPE al_4_1_624020641
11825 11809 1 1 EXPIRED SBT_TAPE al_6_1_624020677
11826 11810 1 1 EXPIRED SBT_TAPE bk_8_1_624115253
11827 11811 1 1 EXPIRED SBT_TAPE bk_7_1_624115252
11828 11812 1 1 EXPIRED SBT_TAPE bk_9_1_624116161
11829 11813 1 1 EXPIRED SBT_TAPE al_11_1_624117067
11830 11814 1 1 EXPIRED SBT_TAPE al_10_1_624117067
11831 11815 1 1 EXPIRED SBT_TAPE bk_13_1_624365687
11832 11816 1 1 EXPIRED SBT_TAPE bk_12_1_624365686
11833 11817 1 1 EXPIRED SBT_TAPE bk_14_1_624366605
11834 11818 1 1 EXPIRED SBT_TAPE al_16_1_624367501
11835 11819 1 1 EXPIRED SBT_TAPE al_15_1_624367501
Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
deleted backup piece
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
deleted backup piece
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
deleted backup piece
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
deleted backup piece
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
deleted backup piece
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
deleted backup piece
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
deleted backup piece
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
deleted backup piece
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
deleted backup piece
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
deleted backup piece
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
deleted backup piece
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
deleted backup piece
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
deleted backup piece
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
deleted backup piece
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
deleted backup piece
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
Deleted 16 EXPIRED objects
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
11895 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11896 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11897 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11916 B F A SBT_TAPE 18-JUL-07 1 1
11926 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11927 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11935 B F A SBT_TAPE 18-JUL-07 1 1
11939 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11940 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11941 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11960 B F A SBT_TAPE 18-JUL-07 1 1
11970 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11971 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11977 B F A SBT_TAPE 18-JUL-07 1 1
RMAN>
Message was edited by:
user539835

Similar Messages

Rman backup to be stored on other machine than catalog and Target database

I have target database on machine A, catalog on machine B. I am executing RMAN from machine B but want to store RMAN backup on machine C. is it possible.

Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: NEFT (DBID=3608824086)
connected to recovery catalog database
RMAN> run{
2> allocate channel c1 device type disk format '\\bobfs\f\RMAN\data\neft\Rman_NEFT_%U';
3> backup full database;
4> backup current controlfile;
5> }
6>
allocated channel: c1
channel c1: sid=16 devtype=DISK
Starting backup at 15-OCT-08
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00011 name=F:\DATABASE\NEFT\DATABASENEFT_DATA1.DBF
input datafile fno=00015 name=F:\DATABASE\NEFT\UNDOTBS.DBF
input datafile fno=00013 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_DATA1.DBF
input datafile fno=00002 name=F:\DATABASE\NEFT\UNDOTBS01.DBF
input datafile fno=00001 name=F:\DATABASE\NEFT\SYSTEM01.DBF
input datafile fno=00014 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_NDX1.DBF
input datafile fno=00005 name=F:\DATABASE\NEFT\EXAMPLE01.DBF
input datafile fno=00012 name=F:\DATABASE\NEFT\DATABASENEFT_NDX1.DBF
input datafile fno=00010 name=F:\DATABASE\NEFT\XDB01.DBF
input datafile fno=00006 name=F:\DATABASE\NEFT\INDX01.DBF
input datafile fno=00009 name=F:\DATABASE\NEFT\USERS01.DBF
input datafile fno=00003 name=F:\DATABASE\NEFT\CWMLITE01.DBF
input datafile fno=00004 name=F:\DATABASE\NEFT\DRSYS01.DBF
input datafile fno=00007 name=F:\DATABASE\NEFT\ODM01.DBF
input datafile fno=00008 name=F:\DATABASE\NEFT\TOOLS01.DBF
channel c1: starting piece 1 at 15-OCT-08
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 10/15/2008 10:45:38
ORA-19504: failed to create file "\\bobfs\f\RMAN\data\neft\Rman_NEFT_7qjt6tat_1_1"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
Recovery Manager complete.
I am executing rman from catalog machine,
WHen i give path \\bobfs\f\RMAN\data\neft\ in start-> run it is accessible from there.
I cant understand why rman is not abl to create file there.
full rights are given to user. and user on rman catalog and network machine is same having same password

Issue Creating Duplicate Database on Different host using RMAN Backup

HI friends..
I m trying to create a duplicate db on different host ....... 27
i have live production db on ............. 15
its up 24*7.
i know how to create dup db using cold backup..but dont know how to create it using RMAN Backup..
I have googled..but getting issues..
Steps Taken till now
Note- I dont have catalog created on live db..
I already have set the tnsnames.ora on both servers
1) Took full backup plus archivelog plus control file on 15
2) moved it to another host..ie 27
3) now on live db..
I conected to rman target /
so i m now connected to prod db
than i try to conect to rman auxiliary sys/sys@dubpd..
But it gives me insufficient privilages error..
Can you tell me what to do next..Coz unless i get into mount phase on sever 27( new server)..i cannot use the control file from backup).my dupdb is up in nomount phase..but what enxt i can do..to restore the control file and than restore the backup after cataloging them to right path..
Thanks in advance frieds...

sai121 wrote:
Nope ..on live db..
@comand prompt when i type sqlplus sys/sys@dupdb..
its says 0ra-12518...Listener cannot hand off client connection..
My tns name for live server is..*primary* on live server .. whose ip is 15..(lIVE SERVER).
i also have another entery with tns names- standby .on live server .. whose ip is 27..(other server for duplicated db).
now @command prompt..@live server.. i did sqlplus sys/sys@standby
It gives me ORA-12518
Am i missing something..1- It could be a network problem. You may enable tracing on listener (and examine the logs).
2- Add "DIRECT_HANDOFF_TTC_LISTENER=OFF" to listener.ora, then reload the listener
3- You may want to increase "large_pool_size"

Backup multiple computers using Time machine to a single external drive

Is it possible to backup multiple computers to a single external drive connected to an Xserve using Time machine? We have a Six TB external drive that we are connecting to an Xserve that has three drives. We want to backup the entire

Set the drive as a network share in the File Sharing section of System Preferences on the Xserve it is connected to and see if Time Capsule on the other machines can see it. If so, it should work. If you don't want the whole drive as a network share create a folder for backups on it and set that folder as a network share.

What actually RMAN "backup validate database" does?

OS: AIX 5.3L; DB: Oracle 10g R2
According to the RMAN doc, the validate actually run an integrity check on all datafiles and the archive logs if includes the "archivelog all" without creating any backupset. But I want to know what exact process Oracle engine is doing behind ? Because when I used it the first time, it took VARY long time to finish the validate process, the whole backup ( I followed the backup report as it was going). Then when I repeated it in my second backup process, the total backup time is back to normal as without it. Example: with my 31G DB, 6 and 1/2 hours first time, then 23 minutes for repeat.

I read that doc too. I think maybe I did not ask question more clearly. But I want to understand what Oracle really does when this process checks all the blocks of the datafiles physically? Did it log its process, so the next run will know what it did before for the same block. Remember I observed that my repeat of the validate run vary fast comparing to that of the first time. I also checked with the paging activity and the iostat of the AIX, I did not see too much changes. Since I am going to apply this backup scheme to my prod box (same AIX 5.3 platform), I need to locate a suitable time period to run the first level 0 backup.

Backup controlfile recovery catalog

Hello
If I am using recovery catalog do I still need to backup controlfile with rman ?
or, can I restore controlfile using recovery catalog so that I dont need to backup controlfile explicitly?

How much effort, scripting, time and disk space does it cost to take controlfile backups ? In any case a Full Backup and/or SYSTEM Tablespace backup and/or ControlfileAutoBackupOn would cause controlfile backups.
What if catalog database is unavailable or corrupted ?
Hemant K Chitale

Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

I will explain my scenario below:
We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
Please suggest me the best way forward...
Many Thanks
Nukesh

Hi Asif,
I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
RMAN> list incarnation;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
RMAN> exit
TEST1DB-> rman target sys@MYTEST1
Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: MYTEST (DBID=2433328848, not open)
RMAN> reset database to incarnation 2;
using target database control file instead of recovery catalog
database reset to incarnation 2
RMAN> run {
2> restore database until scn 10000;
3> recover database until scn 10000;
4> alter database open resetlogs;
5> };
Starting restore at 07-NOV-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/07/2010 11:45:18
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
RMAN-01007: at line 0 column 2 file: standard input
RMAN>
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
RMAN> exit
SQL> select name from v$database;
NAME
MYTEST
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>

How to backup Oracle Database Single Instance using RMAN

Folks,
Hello. I am using Oracle Database Server 11gR1 with Operating System Oracle Linux 5.10.
I understand how to backup database instance in SQL Server with Windows. But don't really understand how to backup database instance in Oracle with Linux.
I have done Cold backup and Hot backup for the database instance HRCS90 but both get the same error message.
Cold backup is below:
SQL> startup
ORACLE instance started.
Total System Global Area 538677248 bytes
Fixed Size                  2146024 bytes
Variable Size             528482584 bytes
Database Buffers            4194304 bytes
Redo Buffers                3854336 bytes
Database mounted.
Database opened.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
RMAN> backup database;
Starting backup at 25-NOV-13
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/25/2013 14:26:52
RMAN-06171: not connected to target database
RMAN> backup HRCS90
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, as, backup, backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, database, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, force, file, incremental, keep, (, maxsetsize, nochecksum, noexclude, nokeep, not, proxy, pool, reuse, recovery, section, skip, spfile, skip readonly, setsize, tablespace, tag, to, validate"
RMAN-01008: the bad identifier was: HRCS90
RMAN-01007: at line 1 column 8 file: standard input
RMAN> backup database HRCS90
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, backup, backupset, channel, copy, controlfilecopy, current, database, datafile, datafilecopy, delete, diskratio, db_recovery_file_dest, filesperset, format, from, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, plus, reuse, recovery, section, ;, skip, spfile, skip readonly, setsize, tablespace, tag, to"
RMAN-01008: the bad identifier was: HRCS90
RMAN-01007: at line 1 column 17 file: standard input
While the database instance HRCS90 is startup, I do hot backup using the same commands and get the same error message with above cold backup.
My question is:
Can any folk tell me the specific steps (command by command) to backup a single database instance in Oracle using RMAN ?
Thanks.

Folks,
Hello. Thanks a lot for replying. My database instance named HRCS90 is going to be backed up. My backup directory is /backup_Database_Instance_HRCS90.
If database in open state, we must back up in archive log. If database in mount state but not open, we can back up in noarchive log.
I have tried to back up HRCS90 in archive and noarchive log when database in mount state but not open as below:
SQL>startup mount;
SQL>exit
[user@linux bin]$./rman
RMAN>connect target;
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup as backupset database plus archivelog;
Starting backup at 01-DEC-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=44 device type=DISK
specification does not match any archived log in the recovery catalog
backup cancelled because all files were skipped
Finished backup at 01-DEC-13
Starting backup at 01-DEC-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
channel ORA_DISK_1: starting piece 1 at 01-DEC-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/01/2013 17:52:45
ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 13: Permission denied
RMAN>
RMAN>
RMAN>
RMAN>
RMAN> backup as backupset database;
Starting backup at 01-DEC-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
channel ORA_DISK_1: starting piece 1 at 01-DEC-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/01/2013 17:56:51
ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 13: Permission denied
As we see the above last 2 commands, either archive or noarchive, I get the same error:
Archive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
Noarchive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
My question is:
What is the file "full_0boqei2c_11_1" or "full_0coqeia5_12_1" ? How to solve the above error ?
Thanks.

How to restore a single instance database to RAC (10g) using RMAN ?

Hi all,
I have a single instance database configured using file system in a unique server, so now I need to restore this database using RMAN to a new RAC environment with two nodes and ASM also.
Does anyone can help with this documentation or a link about any information about this restore using rman ?
I tryied found on metalink but threres isn´t this specific case. Only how to convert single instance to 10g RAC, but without how to use with rman information.
System: Windows 2003
Oracle 10g R2
Thanks.
Wander(Brazil)

Wander(Brazil) wrote:
Hi all,
I have a single instance database configured using file system in a unique server, so now I need to restore this database using RMAN to a new RAC environment with two nodes and ASM also.
In essense you are really doing nothing more than restoring a backup on a new host. If you want a blow by blow detail of how to accomplish it take at http://www.oracledistilled.com/oracle-database/restore-database-to-another-host-using-rman
In order to write the files to the ASM Disk groups you will use the SET NEWNAME FOR DATAFILE in your restore script. You will also need to create the ORACLE_BASE/admin/<DBSID> structure on all of node. Once you get the database completely restore you will need to edit the SPFILE to include the proper value for the CLUSTER* parameters and each the node specific parameters. Sorry that it is kind of higher level than what you are probably looking for but the link above and what I put here should get you were want to go.

RMAN backup on the physical standby database.

Hello,
11.2.0.3 EE database. Is it a requirement to open the database in read only mode in order to take a hot backup?
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER DATABASE OPEN READ ONLY;
I've initiated a rman backup without opening the db in read only and the following output is so far:
RMAN> backup format '/dbstor2/LTS/LTS_rman/%d_set%s_piece%p_%T_%U' check logical database plus archivelog;
Starting backup at 15-OCT-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=603 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
I plan on taking this backup and using it to refresh our Dev and QA dbs. Do you see any issues with taking a backup without opening the db in ready only mode?
-SteveV

No we are not using Active Dataguard. An issue I am investigating is why can't I perform an archivelog backup from the standby?
RMAN> backup archivelog all format '/dbstor2/LTS/LTS_rman/arc.rman.bak';
Starting backup at 15-OCT-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=603 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 15-OCT-12

Rman backup on physical standby database without cancelling MRP

Hi all,
Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
regarrds,

Hi,
On Standby Side:
SQL> alter database mount;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
*input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
*input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> exit
Recovery Manager complete.
[oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
And will not delete this archived log, because it is needed for standby or upstream capture process.
Updated
When MRP stoped
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=24 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> Apply process is stopped and new redo received from primary.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        407
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        405
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> I think, codes is understandable.
Regard
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

RMAN backup uses more space than actual DB size

Hi All,
Yesterday, we have configured the RMAN backup for an RAC db in HP-UX. The total DB size is 82GB
but the RMAN took around 250G space for backup and the backup failed. The oracle db is 10.2.0.1.
$ ls -artl
total 520626852
drwxr-xr-x 23 root root 8192 Feb 10 15:49 ..
drwxr-xr-x 2 root root 96 Feb 10 16:09 lost+found
-rw-rw-rw- 1 oracle dba 290 Feb 10 20:35 backup.log
-rw-rw---- 1 oracle dba 22768640000 Feb 10 21:30 bk_4_1_678488912
-rw-rw---- 1 oracle dba 37469036544 Feb 10 21:40 bk_3_1_678488912
-rw-rw---- 1 oracle dba 28807331840 Feb 10 21:52 bk_5_1_678490229
-rw-rw---- 1 oracle dba 22659448832 Feb 10 22:01 bk_6_1_678490845
-rw-rw---- 1 oracle dba 22775595008 Feb 10 22:14 bk_7_1_678491581
-rw-rw---- 1 oracle dba 19507593216 Feb 10 22:15 bk_8_1_678492076
-rw-rw---- 1 oracle dba 18644811776 Feb 10 22:29 bk_9_1_678492883
-rw-rw---- 1 oracle dba 19040927744 Feb 10 22:31 bk_10_1_678492958
-rw-rw---- 1 oracle dba 18791776256 Feb 10 22:44 bk_11_1_678493794
-rw-rw---- 1 oracle dba 15491096576 Feb 10 22:45 bk_12_1_678493889
-rw-rw---- 1 oracle dba 19860652032 Feb 10 23:00 bk_13_1_678494656
-rw-rw---- 1 oracle dba 20742381568 Feb 10 23:01 bk_14_1_678494701
drwxrwxrwx 3 oracle dba 1024 Feb 10 23:01 .
Why this is happening ? Any bug or i am missing out anything. Please help.
Regards,
Anand.

We are using the belwo scripts,
rman target sys/system nocatalog msglog /backup/backup.log
RUN {
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
INCREMENTAL LEVEL=0
SKIP INACCESSIBLE
TAG hot_db_bk_level0
FILESPERSET 5
FORMAT '/backup/bk_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
filesperset 20
FORMAT '/backup/al_%s_%p_%t'
ARCHIVELOG from time 'sysdate - 1' ;]
#For backing up the archive of the second server.
ALLOCATE CHANNEL ch02 TYPE DISK connect 'sys/system@qicdbr2';
BACKUP
filesperset 20
FORMAT 'al2_%s_%p_%t'
ARCHIVELOG from time sysdate - 1 ;
RELEASE CHANNEL ch02;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
BACKUP
FORMAT '/backup/cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
RMAN> LIST BACKUPSET SUMMARY;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
2 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
3 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
4 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
5 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
6 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
7 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
8 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
9 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
10 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
11 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
12 B 0 A DISK 10-FEB-09 1 1 NO HOT_DB_BK_LEVEL0
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/orahome/OraRAC/dbs/snapcf_QICDB1
.f'; # default

Manually register rman backup with oracle database 10g

Dear All.
I want to restore full backup of database.
I have not configure flash_recovery_area.
how i can manually register full rman backup of database with oracle database 10g.?
Please help me.
Thanks & Regards
Ravi Kumar

This is the 10gR2 documentation on the CATALOG command :
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
You must be specific when stating the version you are running. Commands may be limited or unavailable in older versions versus more recent versions of Oracle.
Hemant K Chitale

PRODUCTION DATABASE RMAN BACKUPS FAILING CONTINUOSLY DATABASE NOT AVAILABL

Database is up and running but am facing the problem in RMAN below are the details
[oracle@Oracle01 log]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Mar 30 02:35:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: LAGOPROD (DBID=3989619179)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 03/30/2012 02:35:39
ORA-03114: not connected to ORACLE
could you please help on it why its throughing on error
FYI
==
STATUS OPEN_MODE LOG_MODE LOGINS
OPEN READ WRITE ARCHIVELOG ALLOWED
Edited by: 924453 on Mar 30, 2012 1:43 AM

924453 wrote:
Database is up and running but am facing the problem in RMAN below are the details
[oracle@Oracle01 log]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Mar 30 02:35:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: LAGOPROD (DBID=3989619179)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 03/30/2012 02:35:39
ORA-03114: not connected to ORACLE
could you please help on it why its throughing on error
FYI
==
STATUS OPEN_MODE LOG_MODE LOGINS
OPEN READ WRITE ARCHIVELOG ALLOWED
Edited by: 924453 on Mar 30, 2012 1:43 AMYou are not connected to oracle. show us the result of
export ORACLE_SID= sid
export ORACLE_HOME = your oracle home
export PATH=$PATH:$ORACLE_HOME/bin
sqlplus / as sysdba

Archivelog files and Rman backup

Hi all,
Please somebody guide me regarding the following concept.
We have the oracle server version 10.2.0.1.0, working with Windows OS,
I had set the parameter log_archive_dest_1 for locating archivelog files, then I had changed the archivelog files to the flash recovery area(located in another disk) by using the parameters db_recovery_file_dest_size and db_recovery_file_dest.
Now the archivelog files are being located at two different location. At this point, If I take backup for archivelog files with the aid of RMAN, then ,
How will the RMAN take backup from those two different locations?
Thanks&Regards,
Jai.

PROBLEM :
I have archivelogs duplexed - when running RMAN - rman backups up the archivelogs from both duplexed destinations - from the user manual - this should not be the case, any ideas?
Details:
I have archivelogs duplexed
I have the following set in rman :
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/rman/WPPMD/control_%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 10 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/rman/WPPMD/backup_%d_%T_%U' MAXPIECESIZE 10 G;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'LOW' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_WPPMD.f'; # default
When I run backups via a script :
backup incremental level=$RMAN_LEVEL database plus archivelog;
($RMAN_LEVEL changes between 0 and 1 depending on the day of the week)
It backs both duplex copies of the same archivelog
From the document :
Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
It says :
Even if your redo logs are being archived to multiple destinations and you use RMAN to back up archived redo logs,
RMAN selects only one copy of the archived redo log file to include in the backup set. (Since logs with the same log sequence number are identical, there is no need to include more than one copy.)
But this is not the case ie
RMAN> list archivelog sequence 2445;
using target database control file instead of recovery catalog
List of Archived Log Copies for database with db_unique_name WPPMD
=====================================================================
Key Thrd Seq S Low Time
4640 1 2445 A 17-DEC-10
Name: /log/recovery_area/WPPMD/archivelog2/1_2445_735315419.dbf
4639 1 2445 A 17-DEC-10
Name: /log/recovery_area/WPPMD/archivelog/2010_12_17/o1_mf_1_2445_6jpx9n7c_.arc
So it still backing up both copies of the archive log.
Any ideas? is this a bug?
Thanks
Luca
Edited by: user4599449 on 17-Dec-2010 07:05
Edited by: user4599449 on 17-Dec-2010 07:06

RMAN backup multiple database on multiple hosts using recovery catalog

Similar Messages

Maybe you are looking for