RMAN Backup/Recover question

Should I be able to back up a db using RMAN in a 10.1.0.2 installation and recover using RMAN in a 10.1.0.3 installation (using same OS, etc.)?

user13419193 wrote:
Hii..
Thanks for reply and I got yr point.
But Sorry for again questioning, here i want database recovery on same server.
Than what to do?
Do i have to create database thriough dbca on same server??
RegardsWhere are your backup files now? Confirm you still have them and they didn't get dropped as part of your deleting/dropping the database.
If, as you say, you deleted the entire database, there really is no concept of 'same server'. You want to restore/recover the database onto a server which does not currently have any copy/version of that particular database. Whether or not there ever WAS one on that box is pretty much meaningless, except for the fact there may be some bits and pieces we can use. But the basic technique is the same.
You haven't state your OS, which is important. If its Windows, you'll need to use oradim to recreate the service. Once that is done, rman can connect to an 'idle' instance and proceed from there.
Once rman connects to an idle instance, you restore the control file from backup, then mount the database (open the control file) then restore and recover the db. rman will use information in the resotred control file to locate the backupsets and process the rest of the operation. there are details that need to be attended to but that's the overall outline.
Edited by: EdStevens on Oct 7, 2011 8:37 AM

Similar Messages

RMAN backup tag question

I am little confused even after I read the RMAN doc. If I have a full level 0 backup tag "mybk$level_0" database, then my level 1 incremental backup tag has to be the same - "mybk$level_1" or "mybk$level_0".
I just run the incremental backup through the whole weekend and noticed the each run would generated two identical "spfile, controlefile" backup, one before the archivelog backup, one after it. Why?

The tag name can be the same as what you set. Tag names can be of different names and different formats, does not need to be a specific name. You can replace mybk with myarchive if you think that is more meaningful. You can also attach date and time variable with the tags to make them more meaning full.
It doesn't have to be this way,
{ backup incremental level 1 cumulative device type disk tag 'mybk%LEVEL_1' database;
recover copy of database;
backup device type disk tag 'mrarchive' archivelog all not backed up; }
If you are calling the rman backup from shell script you can attach the dates to tags as below.
export TDATE=`date +%a%m%d%y`
tag="Archive_${TDATE}"
or
tag "Archive_${TDATE}"
Below note if from one of the online resources available:
Tags for Backups and Image CopiesYou can assign a user-specified character string called a tag to backup sets and image copies (either copies created by RMAN or copies created by an operating system utility). A tag is a case-insensitive symbolic name for a backup set or file copy such as weekly_backup. You can specify the tag rather than the filename when executing the RESTORE or CHANGE command. The maximum length of a tag is 30 characters.
If you do not specify a tag name, then by default RMAN creates a tag for backups and copies (except for control file autobackups) in the format TAGYYYYMMDDTHHMMSS, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24-hour format), MM is the minutes, and SS is the seconds. For example, a backup of datafile 1 may receive the tag TAG20020208T133437. The date and time refer to when RMAN started the backup. If multiple backup sets are created by one BACKUP command, then each backup piece is assigned the same default tag.
When applied to a backup set, a tag applies to a specific copy of the backup set. If you do not duplex a backup set, that is, make multiple identical copies of it, then a one-to-one correspondence exists between the tag and the backup set. For example, BACKUP COPIES 1 DATAFILE 7 TAG foo creates one backup set with tag foo. However, you can back up this backup set and give this new copy of the backup set the tag bar. So, the backup set has two identical copies: one tagged foo and the other tagged bar.
Tags do not need to be unique, so multiple backup sets or image copies can have the same tag name, for example, weekly_backup. When a tag is not unique, then with respect to a given datafile, the tag refers to the most current suitable file. By default, RMAN selects the most recent backups to restore unless qualified by a tag or a SET UNTIL command. The most current suitable backup containing the specified file may not be the most recent backup, as can occur in point-in-time recovery.
For example, if datafile copies are created each Monday evening and are always tagged mondaypmcopy, then the tag refers to the most recent copy (assuming that no SET UNTIL command is issued before restore or recovery). Thus, if complete recovery is desired, this command switches datafile 3 to the most recent Monday evening copy:
SWITCH DATAFILE 3 TO DATAFILECOPY TAG mondaypmcopy;
Tags can indicate the intended purpose or usage of different classes of backups or file copies. For example, datafile copies that are suitable for use in a SWITCH can be tagged differently from file copies that should be used only for RESTORE.
Note:
If you specify a tag when specifying input files to a RESTORE or SWITCH command, then RMAN considers only backup sets with a matching tag when choosing which backup to use

Rman backup optimization question

Hi,
I have come across a RAM related question and would like to understand the answer:
The RMAN configuration has backup optimization set to ON. Which of the following commands will this setting affect?
a) Backup Archivelog with ALL or LIKE options, b) Backup Backupset ALL, c) Backup Tablespace, d) Backup Database
I believe all of the above are affected by backup optimization, however, only a, b and d seems correct, not c. I wonder why tablespace is not affected - it does not say read only, etc.?
Any ideas? Thanks.

Thanks for the quick response!
Meanwhile I did a few tests below, and yes, tablespace does obviously not use backup optimization. But why? Doesn't the same like backup database apply? Isn't using the same retention policy?
RMAN> backup database;
skipping datafile 5; already backed up 2 time(s)
RMAN> backup archivelog ALL;
skipping archived log file /u02/fra/ORCL/ar...; already backed up 1 time(s)
RMAN> backup tablespace example;
input datafile file number=00005
piece handle=/u02/fra/ORCL/backupset....
RMAN> backup tablespace example;
input datafile file number=00005
piece handle=/u02/fra/ORCL/backupset....

Rman backup Compress question

Oracle ver 10.2.0.1 -- 24/7
250G database. I ran the script
run {
allocate channel c1 type disk format '/hotbackup/%d/db_%d_t%t_s%s_p%p%c';
set limit channel c1 kbytes 2024800;
sql "alter system archive log current";
backup as compressed backupset
incremental level 0
filesperset=20 (database include current controlfile);
release channel c1;
# Backup all archive log files
allocate channel t1 type disk format '/hotbackup/%d/al_%d_%s_%p%c';
backup as compressed backupset filesperset=20 (archivelog all delete input);
release channel t1;
delete noprompt backup completed before 'sysdate-1';
And the backup file is still around 220G. Is there another way to compress? Anybody have an idea how to make the backup smaller?
Thank You

How many CPU's does your server have?
And why don't you let RMAN choose the default's regarding the files per set, the backup set piece size, etc. Whenever you run a compressed backup, RMAN would normally use at approx.12% of CPU per channel. A 45hr backup time is clearly unacceptable that too when it is a 24/7 database but as your are using a single channel, which might be the culprit. I would suggest to use about 4 channels (depending on your CPU load) and do not put any restrictions on the files per set and backup set piece size.
We do a compressed backup to disk of a 230G database on a 8 proc server with 4 channels allocated and the backup normally completes in about 1.45 hours and the FULL backup size produced is around 30G ( level 0 is a FULL backup).

RMAN Backup Plan Question

Hello -
If I'm backing up specific datafiles (say 3 datafiles in one RMAN script) and I have 4 of these scripts - so a total of 12 files being backup up, should I have a separate script that just backs up all of the archived log files? Or should I include a Backup Archivelog all command in each specific script?

backup each datafile once according to your backup shedule there is no advantage of backup each data file foure times it conversly decrade or slow down your backup working. there is no need to include archive logs in your scripts. I think you should create seprate sript for archived logs.

RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,

Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg

Can not recover table from rman backup

For testing I want to recover deleted table from rman backup.
I have make vm of oracle 11g. the following step i have applied but could not recover the table.
rman> backup database ;
On sqlplus create login as scott/tiger
create table scott.emp1(col1 varchar2(10));
insert into emp1(col1) value('Yasir ') ;
commit ;
select * from emp1 ;
it shows me one row successfully.
Now i have login the sys as sysdba
sqlplus> alter system switch logfile ;
after this i have drop the table .
Now to recover the table i have restored database on same vm.
rman>restore database ;
rman> recover database ;
rman> alter database open ;
on sqlplus i have issued
sqlplus> select * from scott.emp1 ;
table or view does not exist.
any help how to recover the deleted table from rman backup

Hi,
Check this test case
SQL> create table TEST2 as select * from emp;
Table created.
SQL> select count(*) from TEST2;
COUNT(*)
15
SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
TO_CHAR(SYSDATE,'DD-
10-SEP-2013 10:57:05
SQL> alter system switch logfile;
System altered.
SQL> drop table TEST2 purge;
Table dropped.
SQL> shu immediate
[oracle@vnode MYSHELL]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DDTEST (DBID=1667776968, not open)
RMAN> run{
set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6>
media recovery complete, elapsed time: 00:00:02
Finished recover at 10-SEP-13
database opened
RMAN> exit
SQL> set lin 200 pages 100
SQL> select count(*) from test2;
COUNT(*)
15
HTH

Unable to restore and recover my Database from RMAN Backup

Dear All,
Iam practicing RMAN in Windows environment.
My configurations are
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%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 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
then i tried to startup the DB but it is saying
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
So i tried to restore the Database with my rman backup
RMAN> restore database;
But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
So, i am unable to recover my DB
Please tell me whether i am doing any mistake, what is the solution for my problem.
Thanks in advance
Mahi

All you restored was your datafiles.
Now issue recover database and that will apply the archive logs.
This is in the oracle documentation.
"You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
In this case after issuing restore database in RMAN, then issue this.
"Recover database"
It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

Completeness of Prerequisites for Recovering Tables for PDBs from RMAN Backups

Could you verify the completeness of following prerequisities on pag. 441 of the "Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-14"
Prerequisites for Recovering Tables and Table Partitions from RMAN Backups
■ The target database must be in read-write mode.
■ The target database must be in ARCHIVELOG mode.
■ You must have RMAN backups of the tables or table partitions as they existed at the point in time to which you want recover these objects.
■ To recover single table partitions, the COMPATIBLE initialization parameter for target database must be set to 11.1.0 or higher.
According to my test Database administrator workshop: How to recover a table in a pluggable database from a backup
those prerequisities are valid for CDBs or non-CBDs, but if you want to recover tables or table partitions in PDBs a different prerequisite is needed.
Indeed if you have a backup of only the pluggable database including the missing table (the third prerequisite above), but you don't have any backup of the container database the command...
recover table ... of pluggable database ... until scn ... auxiliary destination ...
will fail with the following errors:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/12/2014 12:22:18
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
So to recover table in PDBs you must have also the RMAN backups of the CDB or in the opposite way it's not sufficient to have only the backups of the pluggable database, because during the creation of the auxiliary database the SYS, SYSAUX and the UNDO tablespace are required.
Regards,
MarcoV

Hi,
Before dropping a DB we had taken an RMAN backup.I hope you were in mount mode.
Will RMAN automatically recognize the FORMAT of the backup piece and restore ?No it won't.
First you have to restore a controlfile in nomount mode with:
restore controlfile from '/u04/backup/rmanbkp /02mo9fnc_1_1';
and do alter database mount.
Than you have to run "catalog start with '/u04/backup/rmanbkp'; " so the instance now knows where to find the pieces.
Now you can run a restore database command.
Than open the database with resetlogs.
Regards,
Tycho

RMAN-06067: RECOVER DATABASE required with a backup or created control file

Hi,
Oracle version :10.2.04
I recovered control files
RMAN> restore controlfile to '/oracle/ora10gr4/dbs/nis.ctl';
Starting restore at 21-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: restoring control file
output filename=/oracle/ora10gr4/dbs/nis.ctl
channel ORA_DISK_1: reading from backup piece /data_idx1/ORAMIG/OMIGTEST/cfc-260103938-20120821-03
channel ORA_DISK_1: restored backup piece 1
piece handle=/data_idx1/ORAMIG/OMIGTEST/cfc-260103938-20120821-03 tag=TAG20120821T152259
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 21-AUG-12after this i got the below error when i tried to open DB.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf'So i tried the following.
RMAN> restore datafile '/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf';
Starting restore at 21-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf
channel ORA_DISK_1: reading from backup piece /data_idx1/ORAMIG/OMIGTEST29_1_791910787
channel ORA_DISK_1: restored backup piece 1
piece handle=/data_idx1/ORAMIG/OMIGTEST29_1_791910787 tag=TAG20120821T151306
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 21-AUG-12
RMAN> recover datafile '/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf';
Starting recover at 21-AUG-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/21/2012 16:21:45
RMAN-06067: RECOVER DATABASE required with a backup or created control fileCan anyone pls help me with this error?
Thanks

Hi,
Try this command after restore control file.
RMAN> restore database;
RMAN> recover database;
RMAN> alter database open resetlogs;Paste here result, if you are get error.
Regards
Mahir M. Quluzade
www.mahir-quluzade.com

Rman and Flash Recover questions.

I am trying to understand some of the new features of Oracle 10g as they relate to backup and recovery.
1) Flashback Query? I have looked thru many technical bulletins in the Oracle Technology Network and Metalink and am still confused as from where Flashback Query retrieves the data. Documentation seems to point to the Undo Tablespace. Is this is true I assume the Undo Tablespace would have to be quite large if you wanted to retrieve a record that might be > 1 week old on an active database. The undo_retention parm would have to be set quite large and the Undo Tablespace would have to be created with the "Retention Guarantee" clause. Correct?
2) Backing Up the Flash Recovery Area to Tape?
For all databases we backup with Rman this is the standard backup configuration we use for Oracle 9i.
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 100 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/crs01/app/oracle/product/9.2/dbs/snapcf_CRSP.f'; # default
The standard Rman backup script we use is seen below.
run {
# Full database backup including the control file and spfile
backup database format '%d_%U' ;
# Switch logs before backing up the archive logs
sql 'alter system archive log current';
# Backup all the archive logs for the past 5 days
backup archivelog from time 'sysdate-5' format '%d_archives_%U';
# Mark unavailable backups as expired
crosscheck backup;
# Delete backups older than 100 days
delete noprompt obsolete;
delete expired backup;
# Delete archive logs older than 7 days
delete noprompt archivelog until time 'SYSDATE-7';
# Backup control file again
backup current controlfile;
resync catalog;
If we use Flash Recovery area and have enough disk space for two days of Rman backups to be stored there we must move anything over two days old to tape. The command "Backup Recovery Area" backs up the Rman backups in the Flash area to tape, correct? Will any of the
configuration or backup commands listed above have to change? Upon execution of the Restore command in Rman will Rman know to retrieve from tape a backup > 2 days old?
Thanks

Hi David
1.yes u need large undo tablespace that hold information for long time.
and set undo retension parameter according to need of flashback query.
But Don't set "Retention Guarantee" because when u set this parameter it will fail DML transaction on database.
because it will give importance to retail data in undo.
In simple Scenerio(No Guarantee Mode)
if DML required undo space in undo tablespace then it will overwrite expired undo and select query may be fail with "snapshot too old error"
But when u set it to undo retension then
oracle will not able overwrite on expired undo and u r DML query fail..........
so in normal prod database we will give more importance on DML query rather then Select query
so Don't use undo retension to gurantee mode.
But u can use in dataware house where query take long time to fetch result even in days.
2.u need to config MML for taking backup of rman to tape directly.
Thanks and regards
Kuljeet Pal Singh

RMAN backup and TSM question

We have rman backup file name contains the datetime so it is unique and easy to tell. But TSM keeps every file 4 versions, so the backup file (always 1 version because of unique name) will stay on tape forever. I have no idea about TSM, according to your experience, what is the normal solution here?

Dedicated forum for {forum:id=74}.
But quickly, in general, "DBA" and "TSM/Storage manager" need to agree on media manager use and setup the system accordingly.
Edited by: orafad on May 19, 2011 3:00 PM

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

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

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>

RMAN Backup/Recover question

Similar Messages

Maybe you are looking for