Rman backup taking daytime

Hi
I would like to take the full rman backup of the production database during the business time ( during day)
Is it reduce the performance of the database? if yes please provide the justification or any docs or any link

Hi,
Impact is due to high I/O during backup. It your prod server have enough juice left to take care of increased I/O , then you can take RMAN backup during day time. It is all about your priority. Mostly backup is done during off hours so that Prod users are not impacted due to high disk I/O.
Regards

Similar Messages

RMAN BACKUPS TAKING A LONG TIME IN 11.1.0.6

Its almost 4 days since the RMAN Full Backup is running and it has completed almost 91% and is stuck at this point since last 2 days, so now we killed the RMAN backup Process and started the RMAN Full Backup on Disk. We need to take the RMAN Backups on Tapes.
When we take the RMAN Full Backup to Tape manually with the same script attached, the Backup runs successfully withing Hours. While if the RMAN Full Backup is running through Cronjobs , then it takes days and it gets hung.
Initially it happened with Full backup , now Incremental Backup is also not working.
Log File of Current RMAN Incremental Backup Running and in Hung state
Recovery Manager: Release 11.1.0.6.0 - Production on Mon Nov 5 20:00:02 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ZSBO (DBID=4052190355)
RMAN>
2>
3>
4> run{
5> allocate channel t1 type 'SBT_TAPE'
6> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
7> allocate channel t2 type 'SBT_TAPE'
8> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
9> allocate channel t3 type 'SBT_TAPE'
10> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
11> allocate channel t4 type 'SBT_TAPE'
12> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
13> backup
14> incremental level 2
15> format 'Incremental_zsbo_%U_%t'
16> (database);
17> sql "alter system archive log current";
18> backup
19> format 'arch_zsbo_%d_%s_%p_%t'
20> (archivelog from time 'sysdate-1' all delete input);
21> release channel t1;
22> release channel t2;
23> release channel t3;
24> release channel t4;
25> }
26>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=2086 device type=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: t2
channel t2: SID=2075 device type=SBT_TAPE
channel t2: NMO v4.5.0.0
allocated channel: t3
channel t3: SID=2069 device type=SBT_TAPE
channel t3: NMO v4.5.0.0
allocated channel: t4
channel t4: SID=2061 device type=SBT_TAPE
channel t4: NMO v4.5.0.0
Starting backup at 05-NOV-12
channel t1: starting incremental level 2 datafile backup set
channel t1: specifying datafile(s) in backup set
input datafile file number=00096 name=/data13/oradata/zsbo/A0186LA2591_00_CURR_12.dbf
input datafile file number=00058 name=/data17/oradata/zsbo/A0436IL2022_00_PREV_01.DBF
input datafile file number=00014 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_01.dbf
input datafile file number=00087 name=/data7/oradata/zsbo/A1086IL2502_00_PREV_01.dbf
input datafile file number=00045 name=/data7/oradata/zsbo/A1143BO2515_00_CURR_IDX_01.dbf
input datafile file number=00130 name=/data7/oradata/zsbo/A0171LA2034_01_DEMO_IDX_01.dbf
input datafile file number=00080 name=/data7/oradata/zsbo/A0436IL2022_00_CURR_IDX_02.DBF
input datafile file number=00119 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_05.dbf
input datafile file number=00136 name=/data5/oradata/zsbo/A1225NY2502_00_TEMP_11.dbf
channel t1: starting piece 1 at 05-NOV-12
channel t2: starting incremental level 2 datafile backup set
channel t2: specifying datafile(s) in backup set
input datafile file number=00095 name=/data12/oradata/zsbo/A0186LA2591_00_CURR_11.dbf
input datafile file number=00075 name=/data17/oradata/zsbo/A0186LA2591_00_CURR_IDX_02.dbf
input datafile file number=00094 name=/data6/oradata/zsbo/A0186LA2591_00_CURR_10.dbf
input datafile file number=00151 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_06.dbf
input datafile file number=00148 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_02.dbf
channel t2: starting piece 1 at 05-NOV-12
channel t3: starting incremental level 2 datafile backup set
channel t3: specifying datafile(s) in backup set
input datafile file number=00127 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_01.dbf
input datafile file number=00018 name=/data15/oradata/zsbo/A1225NY2502_00_TEMP_05.dbf
input datafile file number=00062 name=/data15/oradata/zsbo/A0436IL2022_00_TEMP_02.dbf
input datafile file number=00081 name=/data15/oradata/zsbo/A1110CH2505_00_PREV_01.dbf
input datafile file number=00137 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_12.dbf
input datafile file number=00065 name=/data18/oradata/zsbo/A1086IL2003_00_CURR_01.dbf
input datafile file number=00103 name=/data2/oradata/zsbo/A0186LA2591_00_PREV_05.dbf
channel t3: starting piece 1 at 05-NOV-12
channel t4: starting incremental level 2 datafile backup set
channel t4: specifying datafile(s) in backup set
input datafile file number=00059 name=/data6/oradata/zsbo/A0436IL2022_00_PREV_02.DBF
input datafile file number=00068 name=/data5/oradata/zsbo/A0186LA2591_00_CURR_01.dbf
input datafile file number=00071 name=/data9/oradata/zsbo/A0186LA2591_00_CURR_04.dbf
input datafile file number=00078 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_01.dbf
channel t4: starting piece 1 at 05-NOV-12 ----> No Progress since last 10 hours
Any help will be appreciated.
Regards,
Mohit
Edited by: 969777 on Nov 6, 2012 4:29 AM

Hi,
We have upgraded our database from 10.2.0.3 to 11.1.0.6.
The Script runs fine when we take command line backup on disk which we took 6 days backup, but when we schedule the same on cronjob RMAN Full Backup completes till 91% and it hangs forever. Everything was running fine with Incremental backup which we took 2 days before and it ran successfully but the above log is of Incremental Backup which is still in Hang state from the last 10 Hours , but still showing no Errors.
Please let me know if anything you want to confirm.
Thanks for ur prompt response,
Mohit

RMAN backup taking more time than usual suddenly

Hi All,
We are using 11.1.0.7 database, We regularly takes the full level 0 incremental backup which generally tooks 4:30 hours to complete but from last 2-3 days it is taking 6 hours /or more to complete. We did not made any parameter changes or script change in the database.
Below are the details of rman :
RMAN> show all;
RMAN configuration parameters for database with db_unique_name OLAP are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'f:\backup
CONFIGURE DEVICE TYPE DISK PARALLELISM 6 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXOPENFILES 2;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 4 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 5 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 6 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 7 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
CONFIGURE CHANNEL 8 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BZIP2';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'f:\backup\OLAP\SNCFOLAP.ORA';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'F:\BACKUP\OLAP\SNCFOLAP.ORA';
=====================================================
Please help me, as this more time make my schedule task to extend.
Thanks
Sam

sam wrote:
Hi All,
We are using 11.1.0.7 database, We regularly takes the full level 0 incremental backup which generally tooks 4:30 hours to complete but from last 2-3 days it is taking 6 hours /or more to complete. We did not made any parameter changes or script change in the database.could be due to change in server load,
please compare server load(cpu/memory) on above two period.

RMAN backup taking long time

Hi
Oracle 10.1.0.2.0
OS IBM/AIX RISC/6000
I have a db of around 150GB,Normally i take cold backup (using OS commands) it takes around 4 hours. Today i just wanted to use rman to take online backup on disk it took around 8 hours to complete. i used the following.
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
backup database plus archivelog;Do i need to configure more channels?? what else can i do to decrease the time taken by backup.
Thanks

Hi,
To increase the backup speed in RMAN , **Allocate multiple channels and assign files to specific channels.aA
**Allocate Disk buffers like FILESPERSET = number , MAXOPENFILES = number
** Set the backup duration
Eg: BACKUP DURATION 5:00 DATABASE;
BACKUP DURATION 1:00 PARTIAL TABLESPACE <tablespace_name>;
BACKUP DURATION 2:00 PARTIAL MINIMIZE TIME DATABASE;
BACKUP DURATION 2:00 PARTIAL MINIMIZE LOAD DATABASE;
Good luck..
Edited by: sshafiulla on Jan 24, 2010 11:23 AM

Rman backup full then level 0 and level 1 Weekly

Please share your thoughts of backups.
Friday -> Take a full rman backup
Saturday -> Take a level 0 rman backup -> If recovery needed restore full and apply level 0 ?
Sunday -> Take a level 1 rman backup -> If recovery needed restore full and apply incremental 1 ?
Monday -> Take a level 2 rman backup -> If recover needed restore full and apply incremental 1 ?
Tuesday -> Take a level 1 rman backup -> If recover needed restore full and apply incremental 2 ?
Wednesday -> Take a level 2 rman backup -> If recovery needed restore full and apply incremental 1 ?
Thursday -> Take a level 1 rman backup -> If recovery need restore full and apply incremental 2 ?
Thanks

Please note that Full and level 0 backs are same...
Sunday -> Take a level 0 rman backup
Monday -> Take a level 1 rman backup
Tuesday -> Take a level 1 rman backup
Wednesday -> Take a level 2 rman backup
Thursday -> Take a level 1 rman backup
Friday-> Take a level 1 rman backup
Saturday -> Take a level 1 rman backup
Taking level 2 in the middle of the week, so that in case of any recovery you need ao apply changes since the last level 0, 1 or 2

I am getting below error while taking RMAN backup.

Friends,
I am getting below error while taking RMAN backup.
The issue is related with a lock while trying to backup the controlfile.
The lock is more likely caused by the autobackup controlfile process started just before RMAN process was also trying the backup controlfile as shown in the following alert.log excerpt.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Is there anyway to solve this issue?Thanks in advance.

Hi,
SQL> SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
FROM v$session s, v$enqueue_lock l
WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2; 2 3
no rows selected
Oracle version : 10.2.0.3
I am getting this error once in a month not everyday.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Please suggest me based on this..Thanks in advance..

Taking daily rman backup of archivelogs

Hi,
Technical info:
OS: Windows 2003 EE
DB: Oracle 10g EE v. 10.2.0.3
DB size: 30 GB
I need help to create a rman script or suggestions for creating a Job in Grid Control.
I want to take a daily (monday to friday) rman backup of archivelogs in the time interval 9 AM to 5 PM. The script should be run every 2 hours. I want the script to remove the archivelogs that are older than 4 days. The retention policy is 9 days.
Any suggestions will be very much appreciated.

Hi,
Yes, I have realized that I can create different jobs in Grid Control one for each day and each time: for example: at 9 AM, 11 AM, etc until 5 PM.
Each job performs a backup archivelog and removes those backups that are older than 4 days.
But I have to create 25 jobs (5 jobs for each day).
Is there a simpler way to achieve the same result?

Taking rman backup from a different server

HI Al,
Is it possible for us run the rman backup from a different server other than the server on which database exist .
For Ex :
Our database is on server X
But , I want to schedulde the archive backup from the server Y .
How can we do this and is it possible ...
Regds
Rahul Gupta

Yes, as long the RMAN executable is compatible to the target database, on metalink:
RMAN Compatibility Matrix
Doc ID: 73431.1
rman sys/<password>@<connect_string>
Werner

Taking RMAN backup of primary and standby databases.

Hi,
I am going to setup a Standby for Primary two node RAC to single node standby.
My doubt is, in standby both primary and standby will have the same db_name. So how can i take the RMAN backup of both primary and standby by using a single catalog.
That is, we can register the primary DB with catalog using it's db_name. But how can we register the standby with catalog using same db_name as it is already registered.
Thanks,
Mahi

Are you using a physical or logical standby?
If its a physical standby why do you need to back up both databases? backup the standby and you are done, the backup from the standby can be recovered to either the live serever or the standby if needed, andt hen the archivelogs used to bring it up to date.
If its a logical standby then change the database name for the standby and you can back both up to the same catalog, or alternativly cretae a new catalog for the standby, either as a new database or a new schema in your existing catalog.

Problem in recovery from RMAN backup in case of disk failure

Hi
I have Oracle 9.2.0.1.0 on Windows. Full Hot RMAN backup of database is scheduled on daily basis. I am taking backup on disks. And then i do manually copy them on tapes. If any disk failure occurs than can i recover database completely in this scenario. If tried restoing that backup on different machine as given below
set ORACLE_SID=<name>
rman target sys/<pwd>@ORACLE_SID nocatalog
startup nomount
restore spfile
create pfile from spfile
startup nomount pfile
alter database mount
restore database
Everything worked fine till above steps. Now i will execute last step.
recover database
Here it gives error:-RMAN-06054: media recovery requesting unknown log: thread 1 scn 264750
Still i typed
alter database open resetlogs
Now i can open my database, But is it recovered completely? Or there is loss of some data? Why it is giving this error?
Thanks in advance. Waiting for reply.

I can understand the confusion with this whole concept.
What I meant by all archivelogs is all the archivelogs that were backed up with the backup itself. Again, it is essential to ensure that you archive the current redo log AFTER the backup is performed and then back those archivelogs too. Good thing is, RMAN will take care of this for you if you backup the archivelogs with the BACKUP DATABASE command and/or backup the archivelogs AFTER you run the BACKUP DATABASE command.
Once you've mounted the controlfile and CATALOG the archivelogs, you can go into SQL*Plus and issue the following query:
select SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE# from v$archived_log
order by FIRST_TIME;This will tell you what archivelog is the latest. Logs generated during the backup may also provide the necessary information. Performing Disaster Recovery should help to understand the full process.
The ONLINELOG directory in FRA is only populated if you've configured your redo logs to be stored there. However, you are on 9i...right? If so 9i doesn't utilize a FRA.
HTH
Edited by: ebrian on Oct 3, 2008 1:08 PM

Rman backup

Hi,
I want to take one time RMAN backup with indefinite retention policy. what is the best way. I want to recover the database whenever I want may be after year time.
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
or
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 500 days;
or
CONFIGURE RETENTION POLICY TO NONE;
Regards,
DBA

user573035 wrote:
Hi ,
Thanks for your reply. I decided to go as below.
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '${BACKUP_DIR}/${THEDBNAME}/cf_%d_%F';
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 6;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE = 20G;
This way I will have 2 backup and I will stop to take backup from RMAN. If it requires in future I can restore any of them.
Regards,
DBAI am confused about what you are trying to achieve here, and without knowing that, we really can't give any good advice.
What do you mean by "I will stop to take backup from RMAN" ?
It's sounding like you are planning on only taking one or two backups and never backing up again ..... ?
Are you running in archive log mode? Are you taking regular full and/or incremental backups? What are you trying to achieve by holding one backup for such a long period of time? How do you think this is better than the usual practice of taking a full backup once every week or so and incremental backups daily, with a retention period specified in terms of recovery window (time) instead of redundancy (number of backups)?
You may have some very good reasons, or simply haven't described your intent very well, but right now it sounds like you are about to head down the road to database recovery hell.

Rman backup in noarchivelog mode

hi all,
My database(ORCL) is in noarchivelog mode
I am taking RMAN backup using recovery catalog(backupdb)
target database(ORCL) is in mount mode
I am getting following errors:
RMAN> backup database;
Starting backup at 01-AUG-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel defaul
t
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 a
nd serial=:2
RMAN-10002: ORACLE error: ORA-12571: TNS:packet writer failure
RMAN-03002: failure of backup command at 08/01/2008 15:52:03
ORA-03114: not connected to ORACLE
I again tried and then i got these errors:
C:\Documents and Settings\Administrator>set oracle_sid=backupdb
C:\Documents and Settings\Administrator>rman catalog rman1/rman
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
RMAN> connect target sys/sys@orcl
connected to target database (not started)
RMAN> backup database;
Starting backup at 01-AUG-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/01/2008 16:12:40
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
RMAN>
please explain
Message was edited by:
ArchanaTewatia

Hi,
Try to study the errors Correctly ..
RMAN> connect target sys/aqtechmvardi@orcl
connected to target database (not started)
RMAN> backup database;
Starting backup at 01-AUG-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/01/2008 16:12:40
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Try to mount the Target DataBase it will work.
Thanks
Pavan Kumar N

Whats the difference ( RMAN BACKUP)

Please let me know the diffrence between
1.Alter database begin backup
2. backup database
After my own research all i can find is that Alter database begin backup freeeze the SCN and then we can copy the files from OS level
Where backup database directly create backup set ( backup piece) ..
I would like to know the functional differnce between the two if there is any...
Plus ...doing alter database begin backup ...am i not taking care of logical corruption..
Does alter database being backup does not validate or find out the logical corruption before...
I also came know from a OCA that it just puts in backup mode and dont really pay attention to checking or validating the files...before backin up.
Is that true?
Thanks in advance
Max
Edited by: Sunny-ORACLE on Aug 18, 2009 4:59 AM

Sunny-ORACLE wrote:
Please let me know the diffrence between
1.Alter database begin backup
2. backup database
After my own research all i can find is that Alter database begin backup freeeze the SCN and then we can copy the files from OS level
Where backup database directly create backup set ( backup piece) ..
I would the functional differnce between the two if there is any...The backup database doesn't need to freeze any headers as RMAN knows how to read the datafiles of oracle. Its knows them very well. So there is nothing we need in the case of rman to check that when the backup was done.
Plus ...doing alter database begin backup ...am i not taking care of logical corruption..
Does alter database being backup does not validate or find out the logical corruption before...
I came know from a OCA that it just puts in backup mode and dont really pay attention to checking or validating the files...before backin up.
Yes its correct, the commands, alter database begin backup pr backup database doesn't check for any sort of corruptions. Fordoing that, you either need to fire up oS util. DBV for checking the physical corruptions or use RMANs Backup Validate or Backup Validate Check Logical to check for physical/logical corruptions.
HTH
Aman....

Rman backup errors..

hi guru's
please tell me the answeres..for this
what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?

user13014926 wrote:
hi guru's
please tell me the answeres..for this
what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
You can continue backup from which files not backed up and this is call restartable backup.Please refer below link
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008543
>
i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?If you manually delete archivelogs then you will get an error so before executing this backup command you have to execute CROSSCHECK ARCHIVELOG ALL and DELETE EXPIRED ARCHIVELOG ALL then your problem will solve.

10.1.0.2.0 RMAN backup- What would cause RMAN to hang?

Oracle gurus- Fellow in trouble, need your guidance.
I have a serious issue that has no direct error to examine or fix.
I have a replicated offline server that has a scripted RMAN backup to run nightly, but the backup times flux from what should be only 1 hour 30 minutes. Every other day it takes up to 10 hours to complete a backup that normally takes 1 hr 30 minutes. There is no difference in data loads- the server is offline and the data has not changed to any effect. I use database control instead of grid control, and I turn off emctl every night before the rman backup- I thought maybe emctl was hogging resources. There is nothing else running on the server except replication inserting a couple of rows of data on three tables every other minute.
Where would I look to see where the problem exists when no errors are generated?
Does RMAN wait to backup files if they are being accessed?
Here is my backup script (the OS is Linux AS3) I run an AT job nightly.
at -f /path/path/rman_backup 0600 tomorrow
rman target/
run {
backup database plus archivelog;
delete noprompt obsolete;
sql 'alter system archive log current';
exit;
The Administrators are running a Legato Jukebox backup? a tape backup that backs up my DB files nightly. They run the Legato backup 3 hours after my RMAN backup- the problem is that my RMAN backup may be running during the Legato backup- so I assume that contention occurs and both backups fight for the DB files. This is not an issue when RMAN plays nice and finishes in the normal 1 hour 30 minutes, but when it exceeds 3 hours- we have serious issues, both RMAN and Legato backups take 10 hours.
Please help, I am really puzzled. This is causing me major headaches, how can I assure that RMAN has a consistent backup time to completion. Is there anyway to script it to use more resources to ensure it finishes quickly?

Have you monitored CPU and I/O during this process? Are there any other processes running during this time? You mentioned the server is offline, but you also mentioned replication is taking place ?
You could query V$BACKUP_ASYNC_IO and look at EFFECTIVE_BYTES_PER_SECOND, WAITS and IO_COUNT.
During the backup, you can run the following query to monitor RMAN:
SELECT sid, serial#, context, sofar, totalwork,
     round(sofar/totalwork*100,2) "% Complete"
     FROM v$session_longops
     WHERE opname LIKE 'RMAN%'
     AND opname NOT LIKE '%aggregate%'
     AND totalwork != 0
     AND sofar <> totalwork;If the % Complete doesn't seem to be increasing, you should run the following select to determine what waits exist:
SELECT sid, seconds_in_wait AS sec_wait, event FROM v$session_wait
     WHERE wait_time = 0
     ORDER BY sid;

Rman backup taking daytime

Similar Messages

Maybe you are looking for