Starting a RMAN backup strategy

Hi,
I took an incremental level 0 backup using RMAN while the database was in mount mode.
Are the archive logs from before the update still necessary in order to perform a recovery?
If not, how do I delete them using RMAN so that my next backup using 'backup database plus archivelog...' won't backup them?
Thanks.

Hi,
Are the archive logs from before the update still necessary in order to perform a recovery?Only if you need to roll forward to a point in time from a previous backup.
Can you post the output of:
show retention policy;If you know the exact start time of the level 0 backup you could delete the old archivelogs with.
delete copy of archivelog all completed before "to_date('define_time_here','YYYY-MM-DD:HH24:MI:SS')";Regards,
Tycho

Similar Messages

RMAN Backup Strategy Comment Needed

Hi,
Currently I'm trying to implement a backup strategy with RMAN.
Scenario: My side we're 5 days operational (Monday to Friday). I'm planning my backup as follow:
Mon – Incremental level 1 differential
Tue – Incremental level 1 differential
Wed – Incremental level 1 cumulative
Thurs – Incremental level 1 differential
Fri – Incremental level 0 (aka full database backup)
I planned Mon,Tues and Thurs as an incremental differential, while Wed as an incremental cumulative. With Wed as a cumulative backup, my thinking is that if my db is to fail on Thurs/Fri, my recovery will need to apply fewer backups but at the expense of storage.
Any comment or view about the strategy will be greatly appreciated.
Thanks and Regards
Eugene (ET)

hi,
there is Oracle suggested backup strategy
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm
other
http://books.google.cz/books?id=3aEIIqRHkY8C&pg=RA1-PA326&lpg=RA1-PA326&dq=oracle+rman+backup+stratery&source=bl&ots=DrnVZ3tZPs&sig=QajKM0SXbpoa3eWZgl5kmwmSUPI&hl=cs&ei=o6xcSvSaCpKwsAbmu8yVDA&sa=X&oi=book_result&ct=result&resnum=4
Regards,
Tom

Rman backup strategy

hi,
just wanted to hear some thoughts from some pros..
platform: oracle 9i on windows
i switch from user-managed backups to rman recently. My full nightly backups are abt 20GB in size on completion.
we backup to tape, but i want to keep some disk backups for faster recovery.
i do not have disk space to keep more than 3 backups at any time. Cleanup will be regular and tedious. If i use a utility like gzip after, i can get it down to abt 4-5 GB and thus keep alot of backups on disk.
Does it make sense to compress all backups "older than the latest", and reduce the size so i can keep abt a week on disk?

Backup & Recovery Check List
Alejandro Vargas
Oracle Support Israel.
Rman Recovery Scenarios And Configuration
1. Complete Closed Database Recovery. System tablespace is missing
2. Complete Open Database Recovery. Non system tablespace is missing
3. Complete Open Database Recovery (when the database is initially closed). Non
system tablespace is missing
4. Recovery of a Datafile that has no backups.
5. Restore and Recovery of a Datafile to a different location.
6. Control File Recovery
7. Incomplete Recovery, Until Time/Sequence/Cancel
download the pdf format of full document in the below link:
google it oracle backup and recovery scenarios
[PDF]
Backup & Recovery Check List
File Format: PDF/Adobe Acrobat - Quick View
Oracle Support Israel. User Managed Recovery Scenarios And Configuration .... 4. recover automatic database using backup controlfile; ...
static7.userland.com/oracle/gems/.../BackupAndRecoveryChecklist.pdf
It will be very useful and helps you.
regards,
Rajeysh

Synchronous multimaster replication Backup strategy using RMAN

Hi all,
I am using synchronous multimaster replication. my question is backup strategy has to perofirm in all the master site or only in any of 1 mastersite? what all problems will encounter in RMAn backup in my scenario please help me out with your suggestion
nagaraj.K
[email protected]

You ask: "I want to configure backup strategy using RMAN. any one can help me that"
And the answer is clearly no we can not.
An RMAN backup strategy depends on your SLA (Service Level Agreement) with your customers that you didn't post. What is your down-time window? What is your skill set?
You ask: "How to configure for RMAN Incremental backup?"
Read the docs at http://tahiti.oracle.com for your version (which you didn't mention).
You ask: "What will be backup space and there size ?"
We have no idea. Are you going to create an image copy or a backup set? Read the docs and learn the difference. Are you going to turn on compression? Are you going to back up only changed blocks? We don't know.
You ask: "how to manage growing online archiving files?"
Again we can't help you without knowing your SLA. How many MG/GB are they? What period of time do you need to retain them to meet your SLA? When you figure this out back up to tape those you don't need to keep on the server.
You ask: "how to manage growing data and there disk space?"
This is one we can answer: BUY MORE DISK! That was easy.
You ask: "How we can give good performance our CPU and memory?"
Do you really expect that we can with zero knowledge of your environment, your version, your application, etc. distill into a few short paragraphs the collective wisdom of Cary Millsap, Jonathan Lewis, and the rest of the Oak Table Network membership?
Of course we can not. So what you need to do is buy Cary's book, Jonathan's book, and take their classes.
You ask: "we need keep all archive log in backup files or we need to remove old archive files?"
Remove the old ones after being absolutely sure you have a good backup.
You ask: "where we can take backup tape drive,SAN,disk removable hard disk? which one is better?"
No one solution is better than the other. They are all adequate.

RMAN backup in ORACLE RAC database

Hi there,
We are using RMAN backup strategy for taking backups from one node(eg.node1).Database is RAC database, version 9.2.3. and OS is Solaris 5.10.
this is the configuration which we use, as follows:
Connecting to Prod.Database using catalog database.
rman catalog=rman/rman@CATDB target=sys/oracle@PRODDB(node 2).
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanback/_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
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 '/rmanback/CMWPROD_%s.bak';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oracle@PRODDB(node2)';
CONFIGURE MAXSETSIZE TO 7 G;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/9.2.3/dbs/snapcf_CMWPROD1.f';
As the above config shows RMAN is connecting to PROD DB (node 2). But we need to take backups (datafiles and as well as archive logs) from two nodes (i.e from node 1 and as well as node 2).
Is there any possibility for taking backups from two nodes?
Thanks,
Balu.

Duplicate thread
RMAN configuration in ORACLE RAC database
Khurram

Hello RMAN backup problem.....

Hi there,
We are haveing a setup of Windows Server 2003 with Oracle 10g Rel2 and Veritas NetBackup Ver 5 MP 5 is being used to trigger the backup. On 1st of July 2007, backup failed for the first time. Error was RMAN-06059:expected archived log not found, lost of archived log compromises recoverability. No one paid attention then, I am looking into the same last couple of days.
I have certain questions.... as I am not big on RMAN.
1) Is it possible to have an RMAN backup without RMAN repository.
2) I have taken RMAN backup with having a separate repository and having a catalog to the database to be backed up.
3) I do not find any rman repository over here, so this point one comes into picture.
4) If it is possible how to synchronize the archived logs.
5) start the rman backup again.
Please help.

Hi Alanm,
I was away for few days. Thanks for the update, that it is possible. In this senario please tell me the exact steps how to do. So that I can implementing the same as a backup procedure.
When I said that it should have been supported with the current setup, which is using VERITAS backup procedure and has a policy for bakup. As we do not have a RMAN repository I wanted to figure out how to resync archive logs that are missing from its location to the VERITAS.
I want to take a full RMAN backup with current archived logs as starting point. Also I will like to give backup set name as I want to. Which I think is possible.
So lets ignore the sync part. Please write to me as to how should should I start RMAN without its repository.
Please do reply.
Thanks
Shiva

WHAT IS BEST STRATEGY FOR RMAN BACKUP CONFIGURATION

Hi all,
my database size is 50GB I want TAKe WEEKLY FULL BACKUP AND INCREMENTAL BACKUP
WITHOUT RECOVERY CATALOG.by follwing commands
weekly full database backup
run
backup as compressed backupset
incremental level=0
device type disk
tag "weekly_database"
format '/sw/weekly_database_%d_t%t_c%c_s%s_p%p'
database;
I want do CONFIGURE RMAN BY FOLLWING stragtegy
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
'\SW\AUTOCFILE_'%F';
and other is by default
sql>alter system set control_file_record_keep_time=15 days;
os--aix6 and for two database 10g2 and 11g2
what is best configuration strategy for rman backup.AND BACKUP WITH RECOVERY CATALOG OR WITHOUT RECOVERY CATALOG
PLEASE TELL ME
Edited by: afzal on Feb 26, 2011 1:45 AM

For simply two databases, there really wouldn't be a need for a recovery catalog. You can still restore/recover without a controlfile and without a recovery catalog.
From this:
afzal wrote:
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.I am assuming you want to keep two weeks worth of backups, therefore these:
alter system set control_file_record_keep_time=15 days;
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 daysShould be:
RMAN> sql 'alter system set control_file_record_keep_time=22';
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14;22 would give you that extra layer of protection for instances when a problem occurs with a backup and you want to ensure that data doesn't get aged out.

RMAN backup slow

Hi,
I have a Production Database (10204) running on HP Unix (B.11.11).
Daily morning 6AM, a full RMAN backup runs. The db size is only around 225GB. But it takes 4.5 hours to complete.
The syntax which I use is given below.
RMAN> run {
     allocate channel ch1 type "sbt_tape";
     allocate channel ch2 type "sbt_tape";
     allocate channel ch3 type "sbt_tape";
send
'NB_ORA_CLIENT=jjcprd04-back.backup.ncsus.jnj.com,NB_ORA_POLICY=JJCPRD04-RMAN';
     backup
     format 'bk_%s_%p_%t'
     (database include current controlfile);
     sql 'alter system archive log current';
     backup
     format 'arch_%d_%s_%p_%t'
     (archivelog all delete input );
Is there a way to increase the speed of this backup? Currently the backup is way too slow as it takes 4.5 hours to copy 225GB of data!
Thanks!

I'll start by stating that backups directly to tape are generally quite slow.
I'd still recommend moving to disk backups though... and just archiving it to a tape...Hi Jony,
You can of course backup to disk. Thats a common solution. But you have to deal with space more than everything. In addition to that backing up to disk does not free you from moving/copying your data - depending on your backup strategy - to a long-term storage.
So you have two different and not conjunct backup operations: the rman backup itself and the job which backups the rman area to another media.
In recovery cases you might end up with RMAN requesting older backupsets which are not on disk anymore. This will most probably lead to recovery failures and manual intervention which is not desirable in recovery scenarios.
Another point is the control of the data flow. Backing up via a MML (i.e. "to tape") does not necessarily mean "to tape". Instead it means "to the backup software" which is responsible for managing the backup data. Common scenarios involve backing up the full backups via SAN directly to tape and backing up the archivelogs or incremental backups over LAN which will be stored by the backup software on a hard disk and later copied and/or moved on to tape. The data flow (to SAN / to disk / whereever) is solely controlled by the backup software.
The advantage here is one continuous backup and restore job. The backup software deals with "where is my saveset located" and requests automatically the needed tapes or disks in recovery scenarios. This makes recoveries far more flexible and comfortable.
Regarding the throughput i have set up a rather large OLTP database ( 12 TB currently) which is backed up with EMC Networker. Full backups are written via SAN directly to tape. The average speed with four LTO-3 drives is approx. 550 MB/s (the tape drives compress the data in hardware; the database itself is text-only and seems rather good compressable). I guess thats not too bad.
you can also compress the BACKUPSETS (this generates a little more CPU but less network IO)He said he is on HP-UX. These kind of CPUs tend to be not that fast. Using compression is an option worth testing but there is another point to test when doing compressed backups: The RESTORE TIME.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Best pratices for RMAN backup management for many databases

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

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

RMAN backup destination

Hi
Is there any way to mention the RMAN backup destination for datafiles and archivelog files with their exact name?
e.g
backup as backupset
format 'c:\backup\'
filesperset 1
database plus archivelog all;
Backup will be stored in c:\backup with the actual name of the files.
Destination has to be other than the FRA.
Regards

Does this mean if I use non FRA then 'delete force
noprompt obsolete;' will not delete the obsole
backups from non FRA destinations?
-- but I have checked it is deleting even from the
non FRA location also.
no i didnt mean to say that i mean to say if you dont use FRA for backup strategy then you are also not using OMF (Oracle managed files) cause one of the parameter db_recovery_file_dest_size define location of RMAN backups which enable also the OMF and its advantegous to use OMF cause it reduce wasted disk space consumed by obsolete files by deleting itself when FRA pressure goes to 85%.
You can mock up this situtaion by enabling FRA which in turn enable OMF and start taking backup iteratively when oracle see the space goes to 85% then OMF will remove the earliest obsolete files,you can check it in yours oracle alert log files where you will find
Deleted oracle managed files '<filename>'
I hope yours confusion is cleared now.
Khurram

Min space rman backup

dear all,
i have 11g oracle database and my database size is 120gb .how much hard disk space i must keep to take backup of my database using rman .my backup strategy is on sunday i take level 0 incremental backup and on mon,tue.wed,thurs,fri and sat i m taking incremental level 1 differential backup.so how much minimum space i must keep on my hard disk for 1 week rman backup? your help appreciated.
thanks and regards,

941949 wrote:
dear all,
i have 11g oracle database and my database size is 120gb .how much hard disk space i must keep to take backup of my database using rman .my backup strategy is on sunday i take level 0 incremental backup and on mon,tue.wed,thurs,fri and sat i m taking incremental level 1 differential backup.so how much minimum space i must keep on my hard disk for 1 week rman backup? your help appreciated.
thanks and regards,
This is a question I'm having to answer as well. There are a lot of variables that determine how much space will be needed in any particular circumstance and the guidelines are only just that, guidelines. I read the links presented by Abufazal and while they are as good a starting point as any, you really have to read them with a critical eye and a firm understanding of your own backup and recovery requirements. Ultimately the only way to know how much space is going to be needed is to run the backups and see.

Valid One-Time Backup Strategy?

I wanted to get some feedback on a one-time backup strategy. We currently run RMAN incremental level 0 backups once a week, then run incremental level 1 backups nightly. These seem sufficient for our needs.
In the near future, though, we are planning an upgrade of 9i to 10g. In case we need to undo the upgrade, I want to make sure I have all bases covered when performing this upgrade. My strategy is:
- Run a level 1 incremental right before starting the upgrade.
- Shut down the instance
- Backup the entire ORACLE_HOME(without the data files) using OS commands(tar)
- Backup the entire oraInventory directory.
If I needed to restore the 9i database to its pre-upgrade condition, I would simply untar the ORACLE_HOME, the oraInventory and then run an rman restore and recover.
Is there any flaw in this strategy?
Thanks, Nick

RMAN Compatibility Matrix and Guide (Note:73431.1)
https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=73431.1&blackframe=1
Bye, Aron

How can i do a RMAN backup of my database from the network ?

i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.

Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus

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

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..

Starting a RMAN backup strategy

Similar Messages

Maybe you are looking for