RMAN Backup Solution

We are working on a new RMAN backup solution.
Since ours is a 9i OLTP we are planning to go for backup on disk.
Once the backup is on disk then to tape.If we want to restore the database back how we can restore.We dont use recovery catalog.
Thanks in advance
null

One of the best ways to help yourself in oracle forum is to do a search for existing soultions to your problem before you post a new one. That way, you shorten your thread.


I have posted this last week and I believe you could easily find it if you did a search.

 
RMAN Backup and Recovery Script

Similar Messages

Backup solution for E- Business Suite

Hi all,
We have Oracle application and database deployed to a single server, whilst running a server on Oracle Entreprise Linx on 64 bit and running oracle R12.
Therefore basically I see 03 root folders in my server in my Oracle folder namely,
[oracle@test lab01]$ ll
total 12
drwxr-xr-x 4 oracle dba 4096 Jun 24 15:07 apps
drwxr-xr-x 4 oracle dba 4096 Jun 24 15:07 db
drwxr-xr-x 3 oracle dba 4096 Jun 24 15:06 instSo far as my backup solution I am planning to have:
- RMAN backup solution for the database which is represented by the DB folder
- OS tar command" to copy the Oracle application which is represented by the apps* folder --> correct me if I am wrong, I am not sure...
- I am not sure what is the function of the INST folder and what is the best way of backing it up.
Thanks and Regards,

Hi,
- RMAN backup solution for the database which is represented by the DB folder Correct.
- OS tar command" to copy the Oracle application which is represented by the apps* folder --> correct me if I am wrong, I am not sure...Correct.
- I am not sure what is the function of the INST folder and what is the best way of backing it up.Please refer to the "Oracle Applications Concepts" manual for details about the INST folder.
You need to use the OS command to backup this top, just the same way you back up the application tier node files.
Oracle Applications Concepts
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121oacg.pdf
Thanks,
Hussein

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;"

Which backup solution to use?

I didn't see anything here, but only looked a few screens deep, so sorry if this comes up a lot.
I just found out from reading here that I was running BOTH the Windows backup AND the Lenovo R&R backup. Nowhere does the computer warn about this (something that should be fixed, IMO).
I deleted all the R&R backups and recovered almost 60GB of disk space.
Can someone provide a link or an explaination as to which service is "better", or at least a comparison. From reading, it seems it is recommended to only run one of them. I saw one post which said R&R was better at recovering, etc, but I see other posts which says it just fails (for that person)...
I have a 142gb drive (reported size for C Thinkpad T61p purchased in Dec 2007, running Vista Ultimate with SP1
Thanks.

977220 wrote:
Hi ,
We have Oracle 8i DB running on Windows with Backup using CA client.
We are planning to migrate all backups from CA to Netbackup but since Oracle 8i is no longer supported by Netbackup so we need to use either RMAN or User managed backup .
Can somebody guide,which backup solution to use on Oracle 8i (we will migrate DB to MS-SQL) so this will be temporary solution for DB backup.
1) shutdown IMMEDIATE
2) OS file copy all the files
3) STARTUP

Create standby DB with RMAN backup in Oracle 9.2.0.6

I am tring to create a standby DB in different host with different directory using RMAN. The commandv with which I tried to create the standby database is the follow:
(in the primary server side)
RUN
ALLOCATE AUXILIARY CHANNEL DUP1 TYPE DISK;
DUPLICATE TARGET DATABASE FOR STANDBY
NOFILENAMECHECK
DORECOVER;
but RMAN give me this error:
Starting restore at 18-FEB-08
channel DUP1: starting datafile backupset restore
channel DUP1: restoring controlfile
output filename=/opferi/oradata/oradata01/data01/cntrl01.dbf
released channel: DUP1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/18/2008 17:57:20
RMAN-03015: error occurred in stored script Memory Script
ORA-19505: failed to identify file "/opferi/oracle/product/9.2.0/dbs/l4j9127p_1_1"
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
The standby database is in a different host with the same directory structure. I started (with nomount option) with the same init file that the primary database.
I read solution like the backupset must be copied manually to the standby host, but for me is not a solution.
The RMAN backup script is the follow (like
RUN {
CROSSCHECK BACKUPSET;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUPSET;
crosscheck archivelog all;
ALLOCATE CHANNEL ch00 TYPE disk;
BACKUP
$BACKUP_TYPE
FORMAT '/rman/opferi2/df_sipd_%d_%u_%s_%p'
DATABASE INCLUDE CURRENT CONTROLFILE FOR STANDBY;
sql 'alter system archive log current';
backup format '/rman/opferi2/archive_log_%d_t%t_s%s_p%p' (archivelog all);
RELEASE CHANNEL ch00;
when $BACKUP_TYPE=0
Can anyone help my with this problem?? Thaks
Cristian.
PS. Sorry my bad english because I am from Latin America

Requirements are:
1 the backup should be accessible to both target and auxiliary database in the same location.
2 On Unix this can be arranged through NFS, provided you set the read and write buffer to 32k.
Obviously the backup can not be located in $ORACLE_HOME/dbs, as you can not mount a NFS directory over $ORACLE_HOME/dbs without loosing functionality.
Hth
Sybrand Bakker
Senior Oracle DBA

Create a database from 32bit rman backup with NEW name on a 64bit system

Hello,
i'm more programmer than database admin but i need to set up a 10gR2 apex development server based on our productive instance in a short time.
For that i want to use a rman backup of the productive machine (SLES 10 32bit, DB10GR2+ASM, APEX 3.1).
Because of the less time i got, i want to use an existing machine (SLES 11 64bit, DB10GR2+ASM) as destination.
On this machine i want to create a new instance from the backup i took. I Already read note 881395.1 but i'm quite unsure about 2 things
a) It's VERY IMPORTANT that the development instance has another name than the productive instance.
When i follow 881395.1 and set the enviromental variable ORACLE_SID to another new name. Will this be all? Or will there be problems using another SID because of references in the controlfile or sth. like that?
b) It's VERY IMPORTANT that the datafiles aren't stored in the same path and with the same names as the productive instance. It is another server but there is already a copy of the database (our dba tried to set up a standby solution on this machine) and i don't want to bother this!
How can i rename the datafiles before restoring the backup from scatch?
I found this: set newname for datafile 1 to '<filesystem based filename>';
Will this help? Do i need to rename every single file? Or is it possible to set a path in which all datafiles will be restored?
c) What about the 32bit to 64 bit thing? Will this work? Or do i need to convert the database? How? RMAN Convert?
Or could RMAN convert anyhow used to realize the whole thing?
Thank you very much for your support!
Regards
Daniel

Hello,
i'm more programmer than database admin but i need to set up a 10gR2 apex development server based on our productive instance in a short time.
For that i want to use a rman backup of the productive machine (SLES 10 32bit, DB10GR2+ASM, APEX 3.1).
Because of the less time i got, i want to use an existing machine (SLES 11 64bit, DB10GR2+ASM) as destination.
On this machine i want to create a new instance from the backup i took. I Already read note 881395.1 but i'm quite unsure about 2 things
a) It's VERY IMPORTANT that the development instance has another name than the productive instance.
When i follow 881395.1 and set the enviromental variable ORACLE_SID to another new name. Will this be all? Or will there be problems using another SID because of references in the controlfile or sth. like that?
b) It's VERY IMPORTANT that the datafiles aren't stored in the same path and with the same names as the productive instance. It is another server but there is already a copy of the database (our dba tried to set up a standby solution on this machine) and i don't want to bother this!
How can i rename the datafiles before restoring the backup from scatch?
I found this: set newname for datafile 1 to '<filesystem based filename>';
Will this help? Do i need to rename every single file? Or is it possible to set a path in which all datafiles will be restored?
c) What about the 32bit to 64 bit thing? Will this work? Or do i need to convert the database? How? RMAN Convert?
Or could RMAN convert anyhow used to realize the whole thing?
Thank you very much for your support!
Regards
Daniel

Rman backup with standby database

Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance

726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance
"I scanned thru MOS but could find solutions for rman with active DG."
Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

RMAN backup in RAC failing with error ORA-19566

Hi all, i have 2 node RAC and i am trying to take rman backup of the database which is in ASM filesystem.
There is a corruption in SYSAUX file and rman is failing to take backup of the sysaux datafile and error thrown at the end like
piece handle=/home/oracle/orabackup/BLOOM_LVL0_20120627_1qnejueh_s58_p1 tag=TAG20120627T185538 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/27/2012 18:56:17
*ORA-19566: exceeded limit of 0 corrupt blocks for file +DATA/bloom/datafile/sysaux.257.775475317*
Then i tried to validate the backup in rman of the datafile sysaux nad fired the following query
SQL> SELECT * FROM v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
3 32011 1 0 ALL ZERO
3 32049 40 0 ALL ZERO
3 32034 1 0 ALL ZERO
3 28964 1 1399837 LOGICAL
3 32015 2 0 ALL ZERO
and found all the blocks in the table WRH$_SQL_PLAN.
Then dropped the table, and tried to take backup of the database and it is failing again with the same error..
ANY SOLUTION TO TAKE BACKUP OF THE DATABASE.
anyhow we can SET MAXCORRUPT FOR DATAFILE 3 to value, but does this works all time...
Thanks in advance,
TEJAS

Both are good suggestions, but
Osama-mustafa wrote:
RMAN> blockrecover datafile 5 block 2684; -- Fix Eror That ship has already sailed:
TEJAS_DBA wrote:
And Yes this is the first time i am taking backup on the database.And:
Osama-mustafa wrote:
Or Skip Option
Like
RMAN> RUN{
2> SET MAXCORRUPT FOR DATAFILE 1,3 to 1;
3> BACKUP DATABASE;
4> }The OP was aware of this option and hopefully was able to get at least some sort of a backup eventually. But as for the dropped WRH$_SQL_PLAN, TEJAS is, I will use the word "braver" than most. And as often is the case, Dan Morgan offered the only bit of sensible advise.
Open an SR.
Good luck.

Rman backup error

Hi,
I am taking the rman backup i got below error please give me the solution.
Starting backup at 13-DEC-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=33 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=50 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/u01/oracle/oradata/dev/system01.dbf
input datafile fno=00002 name=/u01/oracle/oradata/dev/undotbs01.dbf
channel ORA_DISK_1: starting piece 1 at 13-DEC-12
channel ORA_DISK_2: starting full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00003 name=/u01/oracle/oradata/dev/sysaux01.dbf
channel ORA_DISK_2: starting piece 1 at 13-DEC-12
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/13/2012 12:05:14
ORA-19504: failed to create file "/u03/rmbackp/1gnsomrp_1_1"
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
channel ORA_DISK_1 disabled, job failed on it will be run on another channel
my mount point has 777 oracle:dba /u03/rmbackup . Below is the my rman configuration parameters.
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/rmbackup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 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 1 DEVICE TYPE DISK FORMAT'/u03/rmbackp/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO'/u03/rmbackup/snapcf_dev.f';
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/rmbackup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 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 1 DEVICE TYPE DISK FORMAT'/u03/rmbackp/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO'/u03/rmbackup/snapcf_dev.f';

Did you see error :
ORA-19504: failed to create file "/u03/rmbackp/1gnsomrp_1_1"
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directoryThere haven't directory : /u03/rmbackp and Channel 1 device type disk format is showed : /u03/rmbackp/%U
Error there.
Mahir

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

Steps to restore RMAN backups from tape to disk

Hi All,
using Netbackup Veritas Volume
DB:10.2.0.3.0
OS:AIX 64 bit
Could nayone please share the steps to - restore RMAN backups from tape to disk.
An early reply would be appreciated!!
Thanks for your time!
Regards,

Hi,
I went through as per your action plan it is giving below error I found a solution on meta doc id 559190.1 but i am not able to understant how to start observiced as it is mentioned in the doc id.
allocated channel: t1
channel t1: sid=2386 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.4.1.0
Starting restore at 09-MAY-10
channel t1: looking for autobackup on day: 20100509
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/09/2010 11:57:01
ORA-27191: sbtinfo2 returned error
Additional information: 2
RMAN>
Thanks,

Cannot make rman backup - ORA-19501

Hello,
database and grid infrastuture 11.2.0.1 in Solaris X86
I am trying to make an rman backup of 2 databases located in ASM but when I try it I have the following error:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 09/08/2011 15:38:04
ORA-19501: read error on file "+DG/prd.dbf", block number 28544 (block size=8192)
ORA-15081: failed to submit an I/O operation to a disk
ORA-15081: failed to submit an I/O operation to a disk
The alertlog of the database, when I run the rman has the following errors:
ORA-27063: number of bytes read/written is incorrect
WARNING: IO Failed. group:2 disk(number.incarnation):0.0xf0f2117f disk_path:/dev/rdsk/c5t60060480000290104585533031374538d0s6
AU:7063 disk_offset(bytes):7406092288 io_size:1048576 operation:Read type:asynchronous
result:I/O error process_id:14808
WARNING: failed to read mirror side 1 of virtual extent 139 logical extent 0 of file 273 in group [2.4251116087] from disk DG001 allocation unit 7063 reason error; if possible,will try another mirror side
ORA-15080: synchronous I/O operation to a disk failed
WARNING: failed to write mirror side 1 of virtual extent 139 logical extent 0 of file 273 in group 2 on disk 0 allocation unit 7063
My suspicious was problems with ASM but I have no errors in ASM. All disks are OK and the databases are working fine.
I runned dbverify against the database datafiles and no problems at all.
The problems seems like the Bug 9068033: RMAN BACKUP FAILED INTERMITTENT ORA-19501 ORA-2706, or bug 8510426 but I can't see any solution in metalink and this bug probably aplies to 10g and not 11g.
Can you please help me out?
Thank you.

The errors look like problems in the I/O system, I don't think there's block corruption from Oracle's point of view. Nevertheless you may check which object owns block 28544 in datafile +DG/prd.dbf.
select file_id from dba_data_files
where file_name = '+DG/prd.dbf';
SELECT SEGMENT_NAME, SEGMENT_TYPE
FROM DBA_EXTENTS
WHERE FILE_ID = <file_id from above>
AND 28544 BETWEEN block_id AND block_id + blocks;
It may be the block belongs to nothing, but there's still a physical defect. I remember a problem where RMAN complained about a bad block, but no issues in the database business. The reason no object owned this block, so the database did never access it.
Werner

RMAN Backup implementation

Hi All,
We are planning to implement the rman backup for the 10.2.0.4,10.2.0.5,11.1.0.7 and 11.2.0.2 databases (around 500 databases).For that i need all your advice for the below queries
1) Which database version is best for the recovery catalog database ?
2) How many databases we can register in the recovery catalog database ? Is there any limitation ?
3) We are planning to implement incremental backup for some databases . For that what is the best solution for this ? we are concerning
about the retention period ..?
4) what is the best backup method for huge size databases OLTP( 1TB , 2TB ) and OLAP databases ?
Please advice me . Thanks a lot
Regards
Kamal

Hello , :
I am able to connect the target database thro RMAN, when
my target database open and running.
How can I startup the target database through RMAN.
I am not able to connect to target database through RMAN.
when target database is down.
RMAN> connect catalog rman/rman
RMAN> connect target sys/oracle@ringtest
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12505: TNS:listener could not resolve SID given in connect descriptor

Rman Backup time error

Today i saw this error in our production backup time .
Please let me know how to leave out from this.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/27/2011 01:13:47
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 05/27/2011 01:10:52
ORA-19566: exceeded limit of 0 corrupt blocks for file
N:\USERS01.DBF
Regs,
Brij

Also, be aware that rman: backup validate (check logical) command could not show the corrupted blocks if that block are newer used(or used before, but freed later for example). In this case, rman validate does not populate V$database_block_corruption but it also does not allows you to continue with your backup.
So the solution will be, as previous posters said, either set the limit for the sustained number of corrupted blocks or format/repair the corrupted block.
For checking the corrupted blocks you could also use db verify utility(dbv). This will definitely show you the details about corrupted blocks, even they are not used ever.

RMAN Backup Solution

Similar Messages

Maybe you are looking for