RMAN backup of multiple dbs

Hi,
I have a question regarding RMAN.
I have 2 DBs in 2 different servers and I do a daily backup of the DBs with RMAN (no catalog, just the rman script) The two DBs are connected through an application that writes on both DBs common and connected data for the applicazion it self, so if one db stops and the other keeps working the data i will find on my application will become inconsistens (or at least I will have differences between the dbs).
Is there a way to create a single RMAN script that does a backup of archive logs and db of the two DBs simultaniously so that I am 100% sure that the data is taken exactly at the same moment, and I don't have to worry about having discrepancies between the two dbs in case of a restore procedure? because if one db needs restore I will need to restore BOTH dbs to have the application up and running correctly!
(hope I explaied it well enough)
I have Oracle 10.2.0.4 EE on Windows Server 2003 R2 SP2
Thank you all!

Phelit wrote:
Hi,
I have a question regarding RMAN.
I have 2 DBs in 2 different servers and I do a daily backup of the DBs with RMAN (no catalog, just the rman script) The two DBs are connected through an application that writes on both DBs common and connected data for the applicazion it self, so if one db stops and the other keeps working the data i will find on my application will become inconsistens (or at least I will have differences between the dbs).
Is there a way to create a single RMAN script that does a backup of archive logs and db of the two DBs simultaniously so that I am 100% sure that the data is taken exactly at the same moment, and I don't have to worry about having discrepancies between the two dbs in case of a restore procedure? because if one db needs restore I will need to restore BOTH dbs to have the application up and running correctly!
(hope I explaied it well enough)
I have Oracle 10.2.0.4 EE on Windows Server 2003 R2 SP2
Thank you all!
Hi,
I think you must use data guard configuration.
In data guard configuration databases will be primary and standby database and transport service (SYNC or ASYNC) is send all archived logs to standby
and apply service will apply all received redo logs to standby.
When primary database i failed, then you can convert standby to new primary.
If you will use SYNC transport then you sure you data loss is equal to zero.
Regards
Mahir M. Quluzade

Similar Messages

Can RMAN Backup to multiple destinations on disk?

Hello -
Does RMAN have the ability to backup to multiple destinations?
For example, local filesystem, as well as a remote location?
Thanks in advance!

user11340104 wrote:
Hello -
Does RMAN have the ability to backup to multiple destinations?Yes with duplexed backup sets: http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV89491.
For example, local filesystem, as well as a remote location?
Not on another machine but on tape yes.

RMAN backup into multiple locations

Hi All,
Our database size is 1.4 TB. I am planning to schedule RMAN full backu. But i do not have mount point of size 1.4 TB. We have mount point /rmanbkp1 of size 1200GB and /rmanbkp2 of size 200GB. How can i distribute RMAN backup to these two filesystems.
Can i take tablespace level backups..?
Please suggest.
Thanks
Sandeep Vadlamudi

Hello;
First of all 1200GB, might be enough since you probably are not using all the blocks in the 1.4 TB and will compress you will also lose less.
Can i take tablespace level backups..?
Yes but the value is limited. You cannot for example recover a dropped tablespace.
Test a backup first and get an idea of how much space you really need.
Also once you have a backup how do you free space for the next backup?
You could use the FORMAT command to backup the database to one location and the Archive to the other. 200 GB is not much space.
RMAN backup into more than one location :
http://www.oracle-class.com/?p=2043
Best Regards
mseberg

To take RMAN backup at multiple disk locations

Hi,
Can we configure RMAN to take backup of DB at more than one disk locations with CONFIGURE command.
Thanx.
Ashutosh.

See Re: Setting backup on two different location

Best pratices for RMAN backup management for many databases

Dear all,
We have many 10g databases (>40) hosted on multiple Windows servers which are backup up using RMAN.
A year ago, all backup's were implemented through Windows Scheduled Tasks using some batch files.
We have been busy (re)implementing / migrating such backup in Grid Control.
I personally prefer to maintain the backup management in Grid Control, but a colleague wants now to go back to the batch files.
What i am looking for here, are advices in the management of RMAN backup for multiple databases: do you guys use Grid Control or any third-party backup management tool or even got your home-made solution?
One of the discussion topic is the work involved in case that the central backup location changes.
Well... any real-life advices on best practices / strategies for RMAN backup management for many databases will be appreciated!
Thanks,
Thierry

Hi Thierry,
Thierry H. wrote:
Thanks for your reaction.
So, i understand that Grid Control is for you not used to manage the backups, and as a consequence, you also have no 'direct' overview of the job schedules.
One of my concern is also to avoid that too many backups are started at the same time to avoid network / storage overload. Such overview is availble in Grid Control's Jobs screen.
And, based on your strategy, do you recreate a 'one-time' Oracle scheduled job for every backup, or do your scripts create an Oracle job with multiple schedule?
You're very welcome!
Well, Grid Control is not an option for us, since each customer is in a separate infrastructure, and with their own licensing. I have no real way (in difference to your situation) to have a centralized point of control, but that on the other hand mean that I don't have to consider network/storage congestion, like you have to.
The script is run from a "permanent" job within the dba-scheduler, created like this:
dbms_scheduler.create_job(
        job_name        => 'BACKUP',
        job_type        => 'EXECUTABLE',
        job_action      => '/home/oracle/scripts/rman_backup.sh',
        start_date      => trunc(sysdate)+1+7/48,
        repeat_interval => 'trunc(sysdate)+1+7/48',
        enabled         => true,
        auto_drop       => false,
        comments        => 'execute backup script at 03:30');and then the "master-script", determines which level to use, based on weekday from the OS. The actual job schedule (start date, run interval etc) is set together with the customer IT/IS dept, to avoid congestion on the backup resources.
I have no overview of the backup status, run times etc, but have made monitoring scripts that will alert me if/when a backup either fails, or runs for too long. This, in addition with scheduled disaster/recovery tests makes me sleep rather well at night.. ;-)
I realize that there (might be) better ways of doing backup scheduling in your environment, since my requirements are so completely different than yours, but I guess that we all face the same challenges in unifying the environments as much as possible, to minimize the amount of actual work we have to do. :-)
Good luck!
//Johan

RMAN BACKUP PERFORMANCE.

Hello Sir,
Oracle Version : 9.2.0.1 /10.2.0.1
Operating System : ANY
This is just for knowledge :
What will be the performance issue if I have more than 1db (for example 10 Dbs.) and I start RMAN backups of all Dbs simultaneously and only the default channel to disk is being used ?
If there is any performance issue i.e. slowdown, what will be the best remedy for that and how ?
Please guide
Thanks & Regards Neeraj

Hi,
Please take a look on this links:
- http://blogs.sun.com/glennf/entry/parallelizing_oracle_backup_with_rman
- [Advise On How To Improve Rman Performance - Note:579158.1|https://metalink.oracle.com/metalink/plsql/f?p=130:14:725432850963062762::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,579158.1,1,1,1,helvetica]
- [RMAN Performance Tuning Diagnostics - Note:311068.1|https://metalink.oracle.com/metalink/plsql/f?p=130:14:725432850963062762::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,311068.1,1,1,1,helvetica]
- [Known RMAN Performance Problems - Note:247611.1|https://metalink.oracle.com/metalink/plsql/f?p=130:14:725432850963062762::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,247611.1,1,1,1,helvetica]
Do you have access to Metalink?
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com
Edited by: F. Munoz Alvarez on Sep 17, 2008 9:43 PM

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>

Why does my archivelog RMAN backups end up in ORACLE_HOME/dbs ?

DB version: 11.2
Platform: Solaris 10
I have noticed that , rman backup pieces containing archivelogs end up in $ORACLE_HOME/dbs directory despite using format parameter. This happened for both Level 0 AND Level 1 backups.
I know that backup files end up in $ORACLE_HOME/dbs when you forget to specify FORMAT. But FORMAT is included in my Level0 and Level 1 Scripts as shown below. Is there anything else wrong with my L0 and L1 scripts ?
Following are my Level0 and Level 1 backup scripts
-- Level0
run
allocate channel LEVEL0_TBLQA device type disk;
crosscheck backup;
delete noprompt obsolete;
backup as backupset incremental level 0 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_full_%U_%T.bkp' plus archivelog delete input;
release channel LEVEL0_TBLQA;
}--- Level 1
run {
backup as compressed backupset incremental level 1 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_L1_%U_%T.bkp' plus archivelog delete all input;
}This DB is using control file as catalog.

backup as backupset incremental level 0 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_full_%U_%T.bkp' plus archivelog delete input;
backup as compressed backupset incremental level 1 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_L1_%U_%T.bkp' plus archivelog delete all input;This is because, the format you have specified stands good only till the backup of database (backup as compressed backupset incremental level 1 database format ".....") and not for the archive log in your script. Hence, the archivelog backups get stored in the $ORACLE_HOME/dbs location and the database backup gets stored in the format location you have mentioned in your RMAN script.
Instead you can use as below:
run
allocate channel LEVEL0_TBLQA device type disk format '/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_full_%U_%T.bkp';
crosscheck backup;
delete noprompt obsolete;
backup as backupset incremental level 0 database plus archivelog delete input;
release channel LEVEL0_TBLQA;

Duplicate RMAN backup output to multiple destinations

Hi
We run Oracle 10.2, we have a requirment to duplicate the rman backup to three destinations at the same time, given that FRA is defined, following is the backup script:
rman
connect target /
backup as compressed backupset database plus archivelog delete imput;
Of course this will backup to FRA only.
The requirment is to duplicate the rman backup output to FRA , /orabackup1 and /orabackup2 in the same one command, i.e, without running the backupo three times.
What change would be needed in the script syntax?

See Re: RMAN backup to two locations

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

Create a new Database in an other server using a copie of RMAN backup

Hi all,
I want to create an other instance for our production database. We have disk and tape in rman backup. My question is can i create a new database using our disk backup in an other server?
If some procedure or steps is there, email it to my adresse [email protected]
Hamid.
Thanks

By means of the use of Recovery Manager it is possible to duplicate a database out from a previously taken rman backup. The method will be outlined in the next few lines.
Let's assume a source database named SRCDB and the target database, named GEMINI. A unix like environment is assumed, but it can be implemented on windows as well, just beware of the particular Oracle implementation on a windows platform (orapwd file name, service creation, path format)
1. Create a password file for the Cloned (GEMINI) instance:
orapwd file=/u01/app/oracle/product/9.2.0.1.0/dbs/orapwGEMINI password=password entries=10
2. Configure tnsnames.ora and listner.ora
Properly identify the database at the tnsnames.ora and have the instance manually registered against the listener.ora files, both files located at the $ORACLE_HOME/network/admin directory.
2.a Manually register the database against the listener (listener.ora)
(SID_DESC =
(ORACLE_HOME = /u01/app/oracle/product/9.2.0.1.0)
(SID_NAME = GEMINI)
2.b Added the target GEMINI to the tnsnames.ora
GEMINI =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1521))
(CONNECT_DATA =
(ORACLE_SID = GEMINI)
2.c Reload the listener
lsnrctl reload
3. Create a new init.ora for the cloned database.
Next create an init.ora file for the cloned database. In case the same paths cannot be used on the target host, either because it is the same source host or because those paths are not reproducible on the target, then DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT may be required to be defined
DB_NAME=GEMINI
CONTROL_FILES=(/u02/oradata/GEMINI/control01.ctl,
/u02/oradata/GEMINI/control02.ctl,
/u02/oradata/GEMINI/control03.ctl)
# Convert file names to allow for different directory structure.
DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/GEMINI/)
LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/GEMINI/)
# block_size and compatible parameters must match those of the source database
DB_BLOCK_SIZE=8192
COMPATIBLE=9.2.0.0.0
4. Connect to the cloned instance
ORACLE_SID=GEMINI; export ORACLE_SID
sqlplus /nolog
conn / as sysdba
5. Create an SPFILE based on the init.ora
CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/GEMINI/pfile/init.ora';
6. Start the database in NOMOUNT mode:
STARTUP FORCE NOMOUNT;
7. Connect to the TARGET, CATALOG and AUXILIARY databases.
By means of the rman three connections are open, one for the Source Database (SOURCEDB), another for the Catalog database (RCAT), and one more for the cloned database (GEMINI)
ORACLE_SID=GEMINI; export ORACLE_SID
rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
8. Complete or Incomplete clone (recover)
From the rman the database using one of the following commands:
8.a Clone the database by means of a complete recover.
DUPLICATE TARGET DATABASE TO GEMINI;
8.b Clone the database up to a defined point in time in the past by means of an incomplete recover
DUPLICATE TARGET DATABASE TO GEMINI UNTIL TIME 'SYSDATE-2';
9. Process finished.
Once the process is finished, the newly created GEMINI database is ready to be used as an independent new cloned database.
Ref. RMAN Clone a Database
~ Madrid

Restore spfile from rman backup ---- error.

Hi,
I am trying to execute recovery on new machine ...
I have done the following steps..
I have one database as ora10g2 as peroduction database on one machine as hosta
I have created a catalog on another machine cora10g2 (hostb)
I have taken a full backup from hosta as per following ...
the following command execute from hosta machine.
$ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
Backup completed ...
Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
I have done the following setting ...on host b
set oracle_sid=DUP
and execute following command ...
rman target / catalog rman/rman@cora10g2
RMAN> set dbid 2760732370
executing command: SET DBID
database name is "BAAN10G2" and DBID is 2760732370
RMAN>
RMAN>
RMAN> startup force nomount ;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
starting Oracle instance without parameter file for retrival of spfile
Oracle instance started
Total System Global Area 159383552 bytes
Fixed Size 1977112 bytes
Variable Size 67114216 bytes
Database Buffers 83886080 bytes
Redo Buffers 6406144 bytes
RMAN>
RMAN>
RMAN>
RMAN> show all ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 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 '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
RMAN>
RMAN>
RMAN> list backup of spfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
2420 Full 7.33M DISK 00:00:01 14-JUN-07
BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
SPFILE Included: Modification time: 14-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2509 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2694 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2760 Full 80.00K DISK 00:00:01 15-JUN-07
BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
Piece Name: /rman/spfile/spfile.ora
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2769 Full 7.33M DISK 00:00:02 15-JUN-07
BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
SPFILE Included: Modification time: 15-JUN-07
RMAN>
RMAN>
RMAN> restore spfile from autobackup ;
Starting restore at 19-JUN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=36 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=35 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=34 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=33 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20070619
channel ORA_DISK_1: looking for autobackup on day: 20070618
channel ORA_DISK_1: looking for autobackup on day: 20070617
channel ORA_DISK_1: looking for autobackup on day: 20070616
channel ORA_DISK_1: looking for autobackup on day: 20070615
channel ORA_DISK_1: looking for autobackup on day: 20070614
channel ORA_DISK_1: looking for autobackup on day: 20070613
channel ORA_DISK_1: no autobackup in 7 days found
channel ORA_DISK_2: looking for autobackup on day: 20070619
channel ORA_DISK_2: looking for autobackup on day: 20070618
channel ORA_DISK_2: looking for autobackup on day: 20070617
channel ORA_DISK_2: looking for autobackup on day: 20070616
channel ORA_DISK_2: looking for autobackup on day: 20070615
channel ORA_DISK_2: looking for autobackup on day: 20070614
channel ORA_DISK_2: looking for autobackup on day: 20070613
channel ORA_DISK_2: no autobackup in 7 days found
channel ORA_DISK_3: looking for autobackup on day: 20070619
channel ORA_DISK_3: looking for autobackup on day: 20070618
channel ORA_DISK_3: looking for autobackup on day: 20070617
channel ORA_DISK_3: looking for autobackup on day: 20070616
channel ORA_DISK_3: looking for autobackup on day: 20070615
channel ORA_DISK_3: looking for autobackup on day: 20070614
channel ORA_DISK_3: looking for autobackup on day: 20070613
channel ORA_DISK_3: no autobackup in 7 days found
channel ORA_DISK_4: looking for autobackup on day: 20070619
channel ORA_DISK_4: looking for autobackup on day: 20070618
channel ORA_DISK_4: looking for autobackup on day: 20070617
channel ORA_DISK_4: looking for autobackup on day: 20070616
channel ORA_DISK_4: looking for autobackup on day: 20070615
channel ORA_DISK_4: looking for autobackup on day: 20070614
channel ORA_DISK_4: looking for autobackup on day: 20070613
channel ORA_DISK_4: no autobackup in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/19/2007 18:00:13
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN>
I am not able to restore spfile from rman backup ;;;

Hi,
I would like to know few things
1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

RMAN backup and restore for Disaster Recovery

Hi Guys,
I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
Starting restore at 21-SEP-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
ystem01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
ysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
ndotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
sers01.dbf
channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
Finished restore at 21-SEP-11
Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/
whereas my latest backups are stored at a different location.
I am executing following steps at the RMAN prompt on hosta and hostb:
hosta (production site)
backup as compressed backupset database plus archivelog
backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
backup spfile
hostb (Disaster site)
set dbid=13732232063
startup force nomount
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
shutdown immediate
/* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
/* restart rman here */
quit
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
/* call the next two commands on run */
restore database;
recover database;
alter database open resetlogs
quit
Any help will be greatly appreciated.
Thanks,
Rajesh

Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
I take backup on Host A using:
rman target /
backup as compressed backupset database plus archivelog;
backup spfile;
quit;
I restore the backup on Host B using:
set dbid=13732232063;
startup force nomount;
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
shutdown immediate;
startup force nomount;
restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
quit;
/* restart rman here */
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset' noprompt;
restore database;
recover database;
alter database open resetlogs;
quit;
I take another backup on Host A using (notice no spfile backup this time):
backup as compressed backupset database plus archivelog;
quit;
I restore the database on Host B using:
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
recover database;
alter database open;
quit;
Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
RMAN> list backup of database;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
8T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
97 Full 259.16M DISK 00:00:00 28-SEP-11
BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
7
Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
TAG20110928T183527787lv0nb_.bkp
List of Datafiles in backup set 97
File LV Type Ckp SCN Ckp Time Name
1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
Output of list backup (done after restoring the control file)
RMAN> list backup;
BS Key Size Device Type Elapsed Time Completion Time
87 89.20M DISK 00:00:26 28-SEP-11
BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
List of Archived Logs in backup set 87
Thrd Seq Low SCN Low Time Next SCN Next Time
1 34 1302253 20-SEP-11 1306439 20-SEP-11
1 35 1306439 20-SEP-11 1307647 20-SEP-11
1 36 1307647 20-SEP-11 1307701 20-SEP-11
1 37 1307701 20-SEP-11 1311393 20-SEP-11
1 38 1311393 20-SEP-11 1311511 20-SEP-11
1 39 1311511 20-SEP-11 1332479 20-SEP-11
1 40 1332479 20-SEP-11 1344418 20-SEP-11
1 41 1344418 20-SEP-11 1350409 20-SEP-11
1 42 1350409 20-SEP-11 1350449 20-SEP-11
1 43 1350449 20-SEP-11 1350854 21-SEP-11
1 44 1350854 21-SEP-11 1350895 21-SEP-11
1 45 1350895 21-SEP-11 1353114 21-SEP-11
1 46 1353114 21-SEP-11 1353254 21-SEP-11
1 47 1353254 21-SEP-11 1353865 21-SEP-11
1 48 1353865 21-SEP-11 1353988 21-SEP-11
1 49 1353988 21-SEP-11 1375403 21-SEP-11
1 50 1375403 21-SEP-11 1376149 21-SEP-11
1 51 1376149 21-SEP-11 1376206 21-SEP-11
1 52 1376206 21-SEP-11 1376246 21-SEP-11
1 53 1376246 21-SEP-11 1379990 21-SEP-11
1 54 1379990 21-SEP-11 1380229 21-SEP-11
1 55 1380229 21-SEP-11 1380266 21-SEP-11
1 56 1380266 21-SEP-11 1380528 21-SEP-11
1 57 1380528 21-SEP-11 1380724 21-SEP-11
1 58 1380724 21-SEP-11 1380861 21-SEP-11
1 59 1380861 21-SEP-11 1381033 21-SEP-11
1 60 1381033 21-SEP-11 1381077 21-SEP-11
1 61 1381077 21-SEP-11 1402243 22-SEP-11
1 62 1402243 22-SEP-11 1423341 22-SEP-11
1 63 1423341 22-SEP-11 1435456 22-SEP-11
1 64 1435456 22-SEP-11 1454415 23-SEP-11
1 65 1454415 23-SEP-11 1490903 23-SEP-11
1 66 1490903 23-SEP-11 1491266 23-SEP-11
1 67 1491266 23-SEP-11 1491347 23-SEP-11
1 68 1491347 23-SEP-11 1492761 23-SEP-11
1 69 1492761 23-SEP-11 1492891 23-SEP-11
1 70 1492891 23-SEP-11 1493678 23-SEP-11
1 71 1493678 23-SEP-11 1493704 23-SEP-11
1 72 1493704 23-SEP-11 1494741 23-SEP-11
1 73 1494741 23-SEP-11 1494790 23-SEP-11
1 74 1494790 23-SEP-11 1510154 23-SEP-11
1 75 1510154 23-SEP-11 1514286 23-SEP-11
1 76 1514286 23-SEP-11 1531967 24-SEP-11
1 77 1531967 24-SEP-11 1543266 24-SEP-11
1 78 1543266 24-SEP-11 1558427 24-SEP-11
1 79 1558427 24-SEP-11 1566924 24-SEP-11
1 80 1566924 24-SEP-11 1578292 24-SEP-11
1 81 1578292 24-SEP-11 1596894 25-SEP-11
BS Key Size Device Type Elapsed Time Completion Time
88 84.03M DISK 00:00:30 28-SEP-11
BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
List of Archived Logs in backup set 88
Thrd Seq Low SCN Low Time Next SCN Next Time
1 82 1596894 25-SEP-11 1609028 25-SEP-11
1 83 1609028 25-SEP-11 1622303 25-SEP-11
1 84 1622303 25-SEP-11 1626430 25-SEP-11
1 85 1626430 25-SEP-11 1634486 25-SEP-11
1 86 1634486 25-SEP-11 1648398 25-SEP-11
1 87 1648398 25-SEP-11 1669259 26-SEP-11
1 88 1669259 26-SEP-11 1686820 26-SEP-11
1 89 1686820 26-SEP-11 1686959 26-SEP-11
1 90 1686959 26-SEP-11 1689168 26-SEP-11
1 91 1689168 26-SEP-11 1704759 26-SEP-11
1 92 1704759 26-SEP-11 1719597 27-SEP-11
1 93 1719597 27-SEP-11 1740407 27-SEP-11
1 94 1740407 27-SEP-11 1750125 27-SEP-11
1 95 1750125 27-SEP-11 1765592 27-SEP-11
1 96 1765592 27-SEP-11 1781498 28-SEP-11
1 97 1781498 28-SEP-11 1802311 28-SEP-11
1 98 1802311 28-SEP-11 1811009 28-SEP-11
1 99 1811009 28-SEP-11 1813811 28-SEP-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

Restoring Rman backup on New Host with different directory structure

Hi,
I have a following scenario to clone the database.
1. clone the database on new server
2. source is non - ASM and target is ASM
3. On source incremental level 0 backup taken on disk connecting to catalog, the backup is moved to target host to different directory structure
4. source is running on 32-bit Linux two node Rac and Target is running on 64-bit Linux two node Rac
I did the following steps and getting below error:
1. I copied incremental Level 0 backup to target server(where we need to build new db) to different directory structure
2. On target i created pfile and build the instance, as dbf file are in multiple locations in source i put following tow parameters in init.ora of target database
*.db_file_name_convert =(/u02/oradata/app1p/,+QADATA2/udev/datafile),(/u03/oradata/app1p/,+QADATA1/udev/datafile),(/u12/oradata/app1p/,+QADATA1/udev/datafile,),(/u99/oradata/app1p/,+QADATA1/udev/datafile),(/u09/oradata/app1p/,+QADATA1/udev/datafile),(/u14/oradata/app1p/,+QADATA1/udev/datafile),(/u07/oradata/app1p/,+QADATA1/udev/datafile),(/u06/oradata/prod/,+QADATA1/udev/datafile'),(/u05/oradata/app1p/,+QADATA1/udev/datafile)
*.log_file_name_convert =("/u99/oradata/app1p/","+QADATA2/udev/onlinelog/")
3. connected to rman -->> started db in nomount -->> restored the controlfile --> cataloged the backup piece and then i am trying to restore
All the above steps i did using the Doc id *How To Restore Rman Backups On A Different Node When The Directory Structures Are Different [ID 419137.1]*
script i am using is :
RMAN> run {
2> set until time "to_date('DEC/20/2010 05:30:00','Mon/DD/YYYY HH24:MI:SS')";
3> allocate channel c1 device type disk;
4> allocate channel c2 device type disk;
5> allocate channel c3 device type disk;
6> allocate channel c4 device type disk;
7> set newname for datafile 1 to '+QADATA1/UDEV/DATAFILE';
8> set newname for datafile 2 to '+QADATA1/UDEV/DATAFILE';
9> set newname for datafile 3 to '+QADATA1/UDEV/DATAFILE';
10> set newname for datafile 4 to '+QADATA1/UDEV/DATAFILE';
11> set newname for datafile 5 to '+QADATA1/UDEV/DATAFILE';
12> set newname for datafile 6 to '+QADATA1/UDEV/DATAFILE';
13> set newname for datafile 54 to '+QADATA1/UDEV/DATAFILE';
set newname for datafile 63 to '+QADATA1/UDEV/DATAFILE';
14> 15> set newname for datafile 67 to '+QADATA1/UDEV/DATAFILE';
16> set newname for datafile 68 to '+QADATA1/UDEV/DATAFILE';
17> set newname for datafile 50 to '+QADATA1/UDEV/DATAFILE';
18> set newname for datafile 39 to '+QADATA1/UDEV/DATAFILE';
19> set newname for datafile 38 to '+QADATA1/UDEV/DATAFILE';
20> set newname for datafile 7 to '+QADATA1/UDEV/DATAFILE';
21> set newname for datafile 9 to '+QADATA1/UDEV/DATAFILE';
22> set newname for datafile 8 to '+QADATA1/UDEV/DATAFILE';
23> set newname for datafile 11 to '+QADATA1/UDEV/DATAFILE';
24> set newname for datafile 10 to '+QADATA1/UDEV/DATAFILE';
25> set newname for datafile 66 to '+QADATA1/UDEV/DATAFILE';
26> set newname for datafile 48 to '+QADATA1/UDEV/DATAFILE';
27> set newname for datafile 47 to '+QADATA1/UDEV/DATAFILE';
28> set newname for datafile 12 to '+QADATA1/UDEV/DATAFILE';
29> set newname for datafile 13 to '+QADATA1/UDEV/DATAFILE';
30> set newname for datafile 14 to '+QADATA1/UDEV/DATAFILE';
31> set newname for datafile 15 to '+QADATA1/UDEV/DATAFILE';
32> set newname for datafile 16 to '+QADATA1/UDEV/DATAFILE';
33> set newname for datafile 18 to '+QADATA1/UDEV/DATAFILE';
34> set newname for datafile 17 to '+QADATA1/UDEV/DATAFILE';
35> set newname for datafile 19 to '+QADATA1/UDEV/DATAFILE';
36> set newname for datafile 69 to '+QADATA1/UDEV/DATAFILE';
37> set newname for datafile 60 to '+QADATA1/UDEV/DATAFILE';
38> set newname for datafile 59 to '+QADATA1/UDEV/DATAFILE';
39> set newname for datafile 55 to '+QADATA1/UDEV/DATAFILE';
40> set newname for datafile 53 to '+QADATA1/UDEV/DATAFILE';
41> set newname for datafile 44 to '+QADATA1/UDEV/DATAFILE';
set newname for datafile 22 to '+QADATA2/UDEV/DATAFILE';
42> 43> set newname for datafile 21 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 20 to '+QADATA2/UDEV/DATAFILE';
44> 45> set newname for datafile 72 to '+QADATA2/UDEV/DATAFILE';
46> set newname for datafile 70 to '+QADATA2/UDEV/DATAFILE';
47> set newname for datafile 65 to '+QADATA2/UDEV/DATAFILE';
48> set newname for datafile 64 to '+QADATA2/UDEV/DATAFILE';
49> set newname for datafile 57 to '+QADATA2/UDEV/DATAFILE';
50> set newname for datafile 56 to '+QADATA2/UDEV/DATAFILE';
51> set newname for datafile 49 to '+QADATA2/UDEV/DATAFILE';
52> set newname for datafile 45 to '+QADATA2/UDEV/DATAFILE';
53> set newname for datafile 26 to '+QADATA2/UDEV/DATAFILE';
54> set newname for datafile 25 to '+QADATA2/UDEV/DATAFILE';
55> set newname for datafile 24 to '+QADATA2/UDEV/DATAFILE';
56> set newname for datafile 23 to '+QADATA2/UDEV/DATAFILE';
57> set newname for datafile 27 to '+QADATA2/UDEV/DATAFILE';
58> set newname for datafile 28 to '+QADATA2/UDEV/DATAFILE';
59> set newname for datafile 29 to '+QADATA2/UDEV/DATAFILE';
60> set newname for datafile 30 to '+QADATA2/UDEV/DATAFILE';
61> set newname for datafile 73 to '+QADATA2/UDEV/DATAFILE';
62> set newname for datafile 32 to '+QADATA2/UDEV/DATAFILE';
63> set newname for datafile 31 to '+QADATA2/UDEV/DATAFILE';
64> set newname for datafile 34 to '+QADATA2/UDEV/DATAFILE';
65> set newname for datafile 33 to '+QADATA2/UDEV/DATAFILE';
66> set newname for datafile 35 to '+QADATA2/UDEV/DATAFILE';
67> set newname for datafile 36 to '+QADATA2/UDEV/DATAFILE';
68> set newname for datafile 37 to '+QADATA2/UDEV/DATAFILE';
69> set newname for datafile 51 to '+QADATA2/UDEV/DATAFILE';
70> set newname for datafile 43 to '+QADATA2/UDEV/DATAFILE';
71> set newname for datafile 40 to '+QADATA2/UDEV/DATAFILE';
72> set newname for datafile 41 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 71 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 58 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 52 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 46 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 42 to '+QADATA2/UDEV/DATAFILE';
73> 74> 75> 76> 77> 78> set newname for datafile 62 to '+QADATA2/UDEV/DATAFILE';
79> set newname for datafile 61 to '+QADATA2/UDEV/DATAFILE';
80> set newname for datafile 74 to '+QADATA2/UDEV/DATAFILE';
81> restore database;
82> switch datafile all;
83> recover database;
84> alter database open resetlogs;
85>
86> release channel c1;
87> release channel c2;
88> release channel c3;
89> release channel c4;
90> }
Getting the following error, copied lines from the error i am getting.
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 27-DEC-10
released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 12/27/2010 08:09:08
RMAN-06026: some targets not found - aborting restore
RMAN-06100: no channel to restore a backup or copy of datafile 74
RMAN-06100: no channel to restore a backup or copy of datafile 73
Please advice...
Thanks,
Tanveer Mohammed

If you would like, please refer the link:-
http://gavinsoorma.com/2010/04/creating-an-asm-duplicate-database-from-a-non-asm-database/

Oracle 9i RMAN backup filling up all disk and failing at the very end

Hello to all and thank you in advance for any input from any of you.
I am new in oracle and the only one in my company with a little bit of oracle knowledge, which is not a whole lot.
I inherited a few servers (Linux and Windows based). We mostly run all our production environment on a Linux box hosting oracle 10g release 10.2.0.1 but we had a legacy application server that still runs on 9i release 9.2.0.1.0. This server is a windows 2003 box, the previous DBA or someone else with admin rights to this machine compressed the whole drive where oracle resides, when I started summarying the oracle assets, I saw this server with no backups scheduled and a compressed disk with very limited space after this compression, only 13 GB left, the database if uncompressed would definitively filled up all the disk. The machine is in used and cannot be taken down for more than a couple of hours. We tried adding another disk but the machine only accept it as a hot spare. The database is in archive mode, when I tried to run a RMAN backup, it start filling up the database drive until it's empty and it crashes the whole machine, it seems like the buffer is growing and growing until it fills up the whole drive. The only way to get the server up and running again is to reboot the machine since the server is more than 6 years old we are not please with this action because we are afraid the machine would go south in one of those reboots.
Has anyone heard of similar issues when running RMAN on a compressed drive? Can the compressed disk have any involvement in this kind of odd behaviour? I tried running the backup in debug mode and creating a log in a different disk (the one where the backup is going to) and still the same issue. Again any help is much appreciate,
Sincerely,
Alex

Sybrand,
Thank you for your fast response, I am going to use your previous post to answer one by one your question,
1 The Oracle binaries --- on a compressed drive > Yes
2 The Oracle database control files redo log files and datafiles on that same compressed drive? > Yes
3 The archived redo log ditto? > Yes
I know for a fact (as I have been using that in 9i) you can create a RMAN backup on a compressed drive, and you can have your archived redo go to a compressed drive. No problemo! > Excellent good news!!!
But I would never touch the data files. Please note backup sets are multiplexed files consisting of multiple datafiles, so RMAN would need to do some calculations to decompress several blocks at the same time and to calculate a new block and compress it.
Do you have enough space to:
a) (preferred) to make datafile copies instead of a backup >
Not in the drive that hosts the oracle instance but yes on an external usb drive (1TB) I attached to use as a backup repository, maybe this is why I am having these issues. I only have 13 GB left on that drive where the oracle instance resides (actually as I explained in a previous reply to Mark, the server only has 3 slots for disks, two of them as configured as RAID 1 and the other is a hot spare because the RAID configuration manager cannot can only added as hot-spare. The raided disk are partitioned in two, one small partition is for the OS and the other is for the oracle instance). When you said make a copy of the datafiles, I assumed you are talking about doing manual backups, and copying the database after using using "alter tablespace tablespace_name begin backup; then copy the file; alter tablespace tablespace_name end backup;
b) use filesperset=1 on the backup command line, so the multiplexing (and associated calculations) stop. I have not tried the option of fileperset yet but I can tryi it and see if that helps.
Can you post the last few lines of the RMAN log where RMAN bombs out? Note: the last few lines. Not all of it, or you must send some paracetamol in conjunction! >
When I ran the debug option, I stopped the backup at less than 20% because I didn't want to reboot the system in the middle of the production time, the backup consumed at least 3 GB during the time was running. The times I ran the RMAN backup I didn't used the debug option so I don't have a log long enough to send unless you want the last few lines of what I have.
Thanks again for your input,
Sincerely,
Alex

RMAN backup of multiple dbs

Similar Messages

Maybe you are looking for