RAC Hot Backup

I have a hot backup script for single-instance.
Any one who want to explain me points to take care in a hot backup for RAC environment?

Hello,
I am sorry to bring this up again since it was last posted on Feb 2007. Does anyone know exactly how to perform user managed backup or at least convince me not to use it in a RAC environment? For example, if my storage array has the snapshot capability and I run Oracle10g RAC on Linux with two nodes cluster using OCFS2 (file systems), can't I just put the database in online backup mode for both instances and just take a snapshot of my Linux volumes? The reason is that I create one shared volume for database datafiles, and one shared volume for online redo logs, and one shared volume for archived logs, in a RAC environment, if one instance fail, then the database is still OK, but if a datafile is missing, then I can just startup one instance, recover the datafile, and then restart the other instance. Is this OK or am I smoking something? Please explain.
Thank you,
TD

Similar Messages

RMAN script for RAC Hot Backup

Anyone who want to share an RMAN script to Hot Backup a 9i RAC Database.

Try to remove the DURATION option in your script.
Here more details about that part.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1010261
Bye, Aron

RAC Cloning using hot backup

Hi,
can somebody help me with the steps for cloning 2 node to 2 node RAC, using hot backup.
Thx.

Actually, the procedure to clone a RAC database do not differ substantially from those of a single-instance database.
You can perform your cloning as if it is a single instance database and once you have your single instance up, you just have to add another instance - and the high level steps would be:
1) Preparing the init.ora file for the second instance.
2) Adding the redo logs for thread 2;
3) Updating the OCR
HTH
Thanks
-Chandra Pabba

Creating RAC database thru RMAN hot backup

Hi Guys,
I am having ERP PROD database on 2 nodes 116 and 117(RAC) server. We have a scheduled RMAN HOT backup of this database
WE also have ASM implemented.
We have another 2 servers named 36 and 37(RAC and ASM) which has ERP Test Database and the thing is that we want to refresh this
test database using ERP PROD RMAN backup.
Can someone please post the proper steps to restore the RMAN backup to ERP Test database as ASM is alos there.
As it is little urgent for us.
help will be appreciated.
Regards,
Milan Rathod

1. take the backup of production database
rman connect target /
backup as compressed backupset database plus archivelog format '/u01/db/backup/%d_%I_%s_%T';
move the backup to test server (same location /u01/db/backup/ bcoz rman checks for backupset in the same location only)
add the below two lines in the test database-- initTEST.ora file
comment cluster_ parameters in initTEST.ora file
eg:-
DB_FILE_NAME_CONVERT = (+EBAOUATDATADG1/prod/,/u01/db/app/admin/test/)
LOG_FILE_NAME_CONVERT = (+EBAOUATDATADG1/prod/,/u01/db/app/admin/test/)
check the connectivity between prod and test database.
from test
$tnsping PROD
from prod machine
$tnsping TEST
in test server
startup nomount
rman target sys@proddb auxiliary /
duplicate target database to test;
after completion of duplicate/clone step convert the single instance test to rac instance by uncomment the cluster_ parameters in initTEST.ora parameter
startup mount the second node in TEST
ALTER DATABASE ENABLE PUBLIC THREAD 2 ;
alter database open;
hope, this will helps you.
Good Luck

Archive logs are missing in hot backup

Hi All,
We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
=======================
rman target / nocatalog <<EOF
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
run {
allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
#--Switch archive logs for all threads
sql 'alter system archive log current';
backup as COMPRESSED BACKUPSET database include current controlfile;
#--Switch archive logs for all threads
sql 'alter system archive log current';
#--Backup Archive logs and delete what we've backedup
backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
exit
EOF
=======================
Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
=======================
Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
=======================
Regards,
Kunal.

All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/13/2012 04:22:56
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
ORA-00310: archived log contains sequence 28772; sequence 28773 required
ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
Let me try the susggestions provided above.

RAC RMAN BACKUP Recovery FOR Oracle APPS Application

Hi,
We have an Application which is similar to Oracle APPs application and We have a RAC Database at Backend.
As I am a Oracle RAC DBA and never worked as an Oracle apps DBA.
Each Week or month We have to deploy a patch on Our Database which are kind of sql changes to Database and before we applying we need to backup our Database.
I am very comfortable while applying patches on Single instance Database:-
I Usually shutdown my database and backing up My Database(Conistent\cold Backup) before applying patch.
and I have a Flash back on both option I am having for my Database.
Problem:-
But in Production I have RAC Database, on which I already configured Hot Backup.
FlashBackup Feature is there with me, but Not reliable.
I want cold backup along with my existing hot backup, and want to restore same if something goes wrong.
Since ASM is configured so we have only option RMAN backup.
IF possible kindly Share your knowledge and Experience of your to handle Such Problem.

Sir,
RMAN is already configured for backing up database online.
My only intention is to have cold or consistent backup before applying application patch, So that at the time of crisis I will resotre my Cold/Conistent backup.
Because I am using 11gr2 RAC with ASM, so only option is there for me to use rman as backup tool.
But I never tried to Have Cold backup in RAC environment in my previous jobs, and I am new to this Oracle APPS DBA technology. So Here I am looking for a Strategy that Normally oracle apps dba use while applying patch to Oracle Database and kind of backup strategy they use.
Regards
Gaurav

FULL HOT Backup failing with a 6 on media management layer....

Hi all,
My thanks in advance for reading and any posts. Appologies for the long post, but wanted to make sure I got all information required into the post
*******************The background*************************
We are currently doing full hot backups of all production databases to tape. The database we use is RAC install (9.2.0.6.0) on Linux Redhat Enterprise 4 (database on OCFS). We use a seperate Solaris 8 box with 2 HP Ultium tape drives over a standard Cat5 line (100mb), we use Veritas Netbackup 5.1 as our media manager and we use an RMAN repositry on another box. Currently the backup is taking on average 17 hours to complete (something that I have been through with Oracle).
We use the below rman script to do the full database backup.
DATE=`date +%m%d%Y-%H%M%S`; export DATE
USER=`id | cut -f2 -d"(" | cut -f1 -d")"`
ORACLE_SID=ausl5; export ORACLE_SID
ORACLE_USER=oracle; export ORACLE_USER
ORACLE_HOME=/u01/oracle/product/9.2.0 export ORACLE_HOME
#delete log files older than 35 days
find /var/adm/netbackup -name "auslive*" -mtime +35 -type f -exec rm {} \;
#if [ "${USER}" = "root" ]
#then
# su - ${ORACLE_USER} "cd /rac/DBA/scripts/BACKUP/" #-c "${CMD_STRING}"
# SUCCESS=$?
#else
# eval "/rac/DBA/scripts/BACKUP"
# SUCCESS=$?
#fi
<<EOF su - oracle
<<EOF1 /u01/oracle/product/9.2.0/bin/rman msglog /var/adm/netbackup/AUSLIVE_b
ackup.${DATE} append
connect target sys/fowler@rman_ausl5
connect catalog rman/rman@rman
#change archivelog all validate;
run {
allocate channel ch1 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch2 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch3 type sbt_tape;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl5';
#CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl3';
#CONFIGURE CHANNEL 3 DEVICE TYPE 'SBT_TAPE' CONNECT = 'SYS/fowle
r@rman_ausl4';
change archivelog all validate;
###=============== Veritas Calls =========================
send "NB_ORA_CLASS=ORAhot_AUSLIVE";
#send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_SCHED=full";
###=====================main backup sections =============
backup
incremental level=0
filesperset 15
format "bk_%s_%p_%t"
tag "hot_${ORACLE_SID}_${DATE}"
database;
sql "alter system archive log current";
change archivelog all validate;
backup
filesperset 10
format "ct_%s_%p_%t"
current controlfile;
sql "alter system archive log current";
backup
filesperset 150
format "al_%s_%p_%t"
archivelog all not backed up 2 times;
change archivelog all validate;
backup
filesperset 50
format "al_%s_%p_%t"
archivelog until time 'SYSDATE-4' delete input;
change archivelog all validate;
release channel ch1;
#release channel ch2;
#release channel ch3;
exit
EOF1
EOF
Now due to the backup taking so long, we often have archive log backups that kick off. We generally get Restore Validates of this backup once a week.
*********************************Problem*******************************
Getting to the problem, the media manager generally completes the job with a 6, which in Veritas means that the backup failed to back up the requested files. I guess that this could be something to do with the media manager layer. But myself and my colleagues are of the opinion that this is something to do with the archive log backups running inbetween (hence the change archivelog all validate; appearing so many times in the script).
Has anyone got any ideas?
Thanks again for any posts / ideas,
Mark.

No I mean, it really tries to backup everything; control file, archive logs etc...
Yeah I will admit its a bit strange, didn't code it myself. The idea was to do a bit a of house keeping at the same time with the archived redo logs (hence the file system stuff with the archived redo logs).
You see we thought that this might be causing the issue.
any ideas are welcomed,
thanks again,
Mark.

How to take a Hot backup of Oracle database

1: put the db in archive log mode
2: set the db_sid to correct one
3: login to sqlplus
4: verify the name of the db that you are connected to
select name from v$database;
5: check if the db is in archive log made
select log_mode from v$database;
if not in archive log mode
another command to check
archive log list;
6: find where on disk oracle writes archive log when it is in archive log mode
sql> show parameter log_archive_dest_1;
if the value is found to be 0, that means no values will be recorded, so we need to change it
sql> alter system set log_archive_dest_1='LOCATION=c:\database\oradata\finance\archived_logs\'
scope=spfile;
7: shutdown immediate; < this is done just to prepare the db for hot backups >
8: startup the db in mount mode
startup mount;
( 3 startup types : nomount - just starts the instance, mount - locates the control files and open up according to the values, open - finds the datafiles from the control files and opens up the db )
9: put the db in archive log mode
alter database archivelog;
10: open the database
alter database open;
11: check the status of the db
select log_mode from v$database;
SQL> archive log list;
12: create a directory for archived log
check if its empty, if empty we need to switch
sql> alter system archive log current;
run it 5 times < need to put / and enter > , then check the archive log dir , we will find files
13: make a table in the database and insert data in it
create table employees (fname varchar(2));
check the table
desc employees;
insert values
insert into employees values ('Mica');
14: tablespace must be in hot backup mode
check the status
select * from v$backup;
if found not active, then we need to change
we cannot put the db in hot backup mode, unless it is archive log mode
change to hot backup mode
alter database begin backup;
check the status
select * from v$backup;
15: now we can only COPY DBF FILES
copy *dbf <distination location>
16: need to take the db out to hot backup mode
alter database end backup;
17: need to make another archive log switch
alter system archive log current;
18: need to copy control files now, need to do a binary bckup
alter database backup controlfile to '<location>\controlbackup';
19: insert more values to the table
insert into employess values ('NASH')
COMMIT;
make another archive log switch : alter system archive log current;
do the same process for more values
20 : backup all the archive logs to a new location
21: shutdown the db and simulate a hw error, delete all the files from the database folder
22: try to start the sqlplus and db ::: error
23: copy all the backups to the db dir
need to copy the control files, rename the binary backup of the control file and make the copies as needed
24: try to mount the db, error < must use reset logs or noreset logs >
25: need to do a recovering of the database
shutdown
restore the archive logs
startup mount;
recover database until cancel using backup controlfile;
it will ask for a log file :
yes for recovery
cancel for cancelling recovery
26: check status: open the database in readonly
alter database open read only;
check the tables to see the data
shutdown immediate
shartup mount;
recover again : recover database until cancel using backup controlfile;
if oracle is asking for a log that do nto exist , all we have to do is type cancel
27: open the database
alter database open;
need to do reset logs
alter database open resetlogs;
28: check the db that you are connected, check the tables
thanks and regards
VKN
site admin
http://www.nitrofuture.com

A very long list ... let me make it shorter.
SQL> archive log list;If I see this:
Database log mode No Archive ModeI put the database into archivelog mode and leave it there forever.
If it is in archivelog mode:
RMAN> TARGET SYS/<password>@<service_name> NOCATALOG
RMAN> BACKUP DATABASE PLUS ARCHIVELOG;Though there are a lot of things one could do better such as incrementals with block change tracking, creating an RMAN catalog, etc.

Unique Error while doing hot backup Cloning!

Dear All,
I am using EBS 11.5.10.2 with DB 9.2.0.6.
I am doing hot backup cloning by referring *[Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g) Using Hot Backup on Open Database|https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=760772.1]*
I am facing a unique issue, when I run adcfgclone.pl dbconfig <my_context_file>, application of my Production Server start misbehaving and it gives me an error:
Node Id does not exist for the current application server id.When I check the FND_NODE table I found that there server id was empty in it.
I have to run than run the following steps as the resolution:
1. Shutdown all the services.
2. EXEC FND_CONC_CLONE.SETUP_CLEAN;
3. COMMIT;
4. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers,to repopulate the required system tables.
5.start all the services and verify the issue.
Than application behaves normally.
Is there any additional step to be followed while Hot Backup Cloning other than mentioned in the above mentioned ML Doc?
Please suggest,
Anchorage :)

I am facing a unique issue, when I run adcfgclone.pl dbconfig <my_context_file>, application of my Production Server start misbehaving and it gives me an error:
Node Id does not exist for the current application server id.Where did you get this error?
This is very strange, how come this happens in Production, when you are doing cloning in TEST/DEV instance.
Is there any additional step to be followed while Hot Backup Cloning other than mentioned in the above mentioned ML Doc?I feel there are no other additional steps, as I Recently did successfully hotbackup cloning using the same document.

How to find out which archived logs needed to recover a hot backup?

I'm using Oracle 11gR2 (11.2.0.1.0).
I have backed up a database when it is online using the following backup script through RMAN
connect target /
run {
allocate channel d1 type disk;
backup
incremental level=0 cumulative
filesperset 4
format '/san/u01/app/backup/DB_%d_%T_%u_%c.rman'
database
}The backup set contains the backup of datafiles and control file. I have copied all the backup pieces to another server where I will restore/recover the database but I don't know which archived logs are needed in order to restore/recover the database to a consistent state.
I have not deleted any archived log.
How can I find out which archived logs are needed to recover the hot backup to a consistent state? Can this be done by querying V$BACKUP_DATAFILE and V$ARCHIVED_LOG? If yes, which columns should I query?
Thanks for any help.

A few ways :
1a. Get the timestamps when the BACKUP ... DATABASE began and ended.
1b. Review the alert.log of the database that was backed up.
1c. From the alert.log identify the first Archivelog that was generated after the begin of the BACKUP ... DATABASE and the first Archivelog that was generated after the end of the BACKUP .. DATABASE.
1d. These (from 1c) are the minimal Archivelogs that you need to RECOVER with. You can choose to apply additional Archivelogs that were generated at the source database to contininue to "roll-forward"
2a. Do a RESTORE DATABASE alone.
2b. Query V$DATAFILE on the restored database for the lowest CHECKPOINT_CHANGE# and CHECKPOINT_TIME. Also query for the highest CHECKPOINT_CHANGE# and CHECKPOINT_TIME.
2c. Go back to the source database and query V$ARCHIVED_LOG (FIRST_CHANGE#) to identify the first Archivelog that has a higher SCN (FIRST_CHANGE#) than the lowest CHECKPOINT_CHANGE# from 2b above. Also query for the first Archivelog that has a higher SCN (FIRST_CHANGE#) than the highest CHECKPOINT_CHANGE# from 2b above.
2d. These (from 2c) are the minimal Archivelogs that you need to RECOVER with.
(why do you need to query V$ARCHIVED_LOG at the source ? If RESTORE a controlfile backup that was generated after the first Archivelog switch after the end of the BACKUP ... DATABASE, you would be able to query V$ARCHIVED_LOG at the restored database as well. That is why it is important to force an archivelog (log switch) after a BACKUP ... DATABASE and then backup the controlfile after this -- i.e. last. That way, the controlfile that you have restored to the new server has all the information needed).
3. RESTORE DATABASE PREVIEW in RMAN if you have the archivelogs and subsequent controlfile in the backup itself !
Hemant K Chitale

Question on recovery from Hot backup

Whenever I tried to recover from my hot backup using recover database untill cancel (or any other until option)..
I get messages similar to the following :
SQL> recover database using backup controlfile until cancel ;
ORA-00279: change 212733060 generated at 11/18/2008 23:50:58 needed for thread
1
ORA-00289: suggestion : /d01/oradata/devl/arc/1_282_667362770.dbf
ORA-00280: change 212733060 for thread 1 is in sequence #282
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/1_282_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/2_257_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/3_258_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 4
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
I have all my archive files in the archive dest location.
Is there any way to prevent this warning messages and let oracle find all the archive files?
As you can see from the messages, Oracle is finding the correct file, then why there is an error message and why we have to provide the file names one-by one.
Please help !!!

Oracle will look for needed archive logfile from your log archive destination.
If you are sure all these files are under /d01/oradata/devl/arc/, you can input AUTO, Oracle will work down the list until done.

Complete Recovery from HOT BACKUP

One of our server had media failuer. We are rebuilding new server and reinstalling oracle on it. I have hot backup of instance which I would like to recover.
Can I have steps please. I will appreciate your help...!

Hi,
What is the OS and version of Oracle?
Do you have all the archivelogs after the hot backup? Is the backup a valid backup? Is it a RMAN backup or normal file system backup of the datafiles?
Regards,
Badri.

Recovery from hot backup

I have a problem with recovery hot backup from production database to test database and open it to use.
I have 'hot backup' without temporary tablespace and roll tablespace, I cant shut down production database (24x7), please give me a regulations how to recover database from hot backup, without online redo logs, temp tablespace, roll tablespace only with archive logs, and.....after this ..rename database sid.
Every time when I recovered database, it's still want to recover...and recover from archive logs and I cant open it, it's still inconsistent.Please send me an answer for [email protected]
thanks!

Hi,
What is the OS and version of Oracle?
Do you have all the archivelogs after the hot backup? Is the backup a valid backup? Is it a RMAN backup or normal file system backup of the datafiles?
Regards,
Badri.

Consistent hot backup possible

Is a consistent hot backup possible?
I would like to perform hot backups while the database is in basically a read only state. I am currently using Oracle recommended backups via OEM, for example.
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
release channel oem_disk_backup;
allocate channel oem_sbt_backup1 type 'SBT_TAPE' format '%U';
backup recovery area;
Would executing the sql command "alter database begin backup;" before running the above RMAN script accomplish this task? Then off course when completed execute sql "alter database end backup;".
My basic concern is this type of RMAN hot backup usable in a disaster situation, i.e recreated on another server from tape backup.
I am open to any other ideas.
Thanks for your help in advance.
Ed - Wasilla, Alaska
Edited by: evankrevelen on Sep 11, 2008 10:18 PM

Thanks everyone who replied to this thread.
Just to clarify my complete backup strategy, there are two RMAN scripts run on daily and weekly basis. The daily does pickup the archivelogs. I had shown the weekly when first opening this thread. Here is the daily.
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
release channel oem_disk_backup;
allocate channel oem_sbt_backup1 type 'SBT_TAPE' format '%U';
backup archivelog all not backed up;
backup backupset all not backed up since time 'SYSDATE-1';
My question now is what RMAN does in the increments. It appears to be updating the original level 0 copies of datafiles with changed blocks only. Is the new copy of the datafile now a level 0 type file?
Here is a transcript from one of the daily backups.
Starting recover at 11-SEP-08
channel oem_disk_backup: starting incremental datafile backupset restore
channel oem_disk_backup: specifying datafile copies to recover
recovering datafile copy fno=00001 name=+DEVRVYG1/landesk/datafile/system.2576.616107783
recovering datafile copy fno=00002 name=+DEVRVYG1/landesk/datafile/undotbs1.2574.616107865
recovering datafile copy fno=00003 name=+DEVRVYG1/landesk/datafile/sysaux.2575.616107829
recovering datafile copy fno=00004 name=+DEVRVYG1/landesk/datafile/users.2572.616107871
recovering datafile copy fno=00005 name=+DEVRVYG1/landesk/datafile/landesk.2914.616107643
channel oem_disk_backup: reading from backup piece +DEVRVYG1/landesk/backupset/2008_09_10/nnndn1_tag20080910t220150_0.12330.665100189
channel oem_disk_backup: restored backup piece 1
piece handle=+DEVRVYG1/landesk/backupset/2008_09_10/nnndn1_tag20080910t220150_0.12330.665100189 tag=TAG20080910T220150
channel oem_disk_backup: restore complete, elapsed time: 00:05:16
Finished recover at 11-SEP-08
Starting backup at 11-SEP-08
channel oem_disk_backup: starting incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
input datafile fno=00005 name=+DEVG1/landesk/datafile/landesk.374.614072207
input datafile fno=00003 name=+DEVG1/landesk/datafile/sysaux.384.614002027
input datafile fno=00001 name=+DEVG1/landesk/datafile/system.383.614002025
input datafile fno=00002 name=+DEVG1/landesk/datafile/undotbs1.385.614002027
input datafile fno=00004 name=+DEVG1/landesk/datafile/users.386.614002027
channel oem_disk_backup: starting piece 1 at 11-SEP-08
channel oem_disk_backup: finished piece 1 at 11-SEP-08
piece handle=+DEVRVYG1/landesk/backupset/2008_09_11/nnndn1_tag20080911t220708_0.12999.665186835 tag=TAG20080911T220708 comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:02:26
channel oem_disk_backup: starting incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel oem_disk_backup: starting piece 1 at 11-SEP-08
channel oem_disk_backup: finished piece 1 at 11-SEP-08
piece handle=+DEVRVYG1/landesk/backupset/2008_09_11/ncsnn1_tag20080911t220708_0.2301.665186983 tag=TAG20080911T220708 comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:00:21
Finished backup at 11-SEP-08
It appears to be updating the previous copy with updated blocks thus rolling forward the datafile copy to a new level 0 copy.
Then to restore from the backup RMAN would first use this new copy of the datafile and then apply any archivelogs to them to bring the database to the point in time the incremental backup was taken.
Are these assumptions true?
Thanks for your help,
ED

When to use REUSE/SET, NO-ARCHIVELOGS in create controlfile in HOT BACKUP?

I am a trainee Oracle DBA and have the following queries. Kindly reply with detailed explanation as I want to get my concepts cleared!
Q1>> While doing a user managed hot backup, when we are creating a control file(CREATE CONTROLFILE) from trace for recovery when do we use the create control file with the following options:
*1. REUSE / SET*
*2. ARCHIVELOGS / NOARCHIVELOGS*
Q2>> In what scenarios do we re-create the control file while recovering datafiles from a hot backup??
Thanks a tonne!
Regards,
Bhavi

Hemant K Chitale wrote:
1.1 It is not "REUSE/SET". These are two very different clauses.
REUSE is when you want the CREATE to overwrite the existing controlfile(s). If the controlfile(s) {as named in the instance parameter file, initSID.ora or spfileSID.ora} is/are already present, the CREATE fails unless REUSE is specified.
SET is when you want to change the database name. Oracle then creates the controlfile(s) with the specified database name and updates the headers of all the datafiles. If you run a CREATE with a database name that is different from that in the datafile headers, the CREATE fails unless you include a SET to specify that the name must be changed. Note that this also means that the name in the instance parameter file must already have been updated.
1.2 ARCHIVELOG/NOARCHIVELOG is to set the database state. The same is achieved by issuing an "ALTER DATABASE ARCHIVELOG/NOARCHIVELOG" when the database is MOUNTed but not OPEN.
2. You'd run the CREATE CONTROLFILE if you do not have a binary backup of the controlfile.
Optionally, you can also use CREATE CONTROLFILE to rename all the datafiles by specifying the new locations of the datafiles -- the datafiles must already be present in the new locations, else the CREATE fails if it doesn't find a datafile that is included in the list of datafiles included in the CREATE statement.
RMAN is the correct way to run Backups. User Managed Backup scripts are used in cases like Storage-based Snapshots / SnapClones / BCV.
Hemant K ChitaleThanks that was really helpful..One last question when to use the resetlogs/noresetlogs clause in the create controlfile statement. I have noticed that at times it accepts resetlog while at times it accepts noresetlogs

RAC Hot Backup

Similar Messages

Maybe you are looking for