Resume a failed RMAN incremental 0 cold backup to disk

Linux x86-64 10.2.0.4
I'm taking an incremental 0 backup to disk of a database that's mounted. I'm backing up the database to an NFS volume. I lost the NFS mount. Is there any way to resume a backup where it left off at? It complains "ORA-27038: created file already exists" if I restart it. RMAN can easily resume a restore. I don't have the time to redo the whole thing all again. The database is over 10TB. The target isn't up. Is there anything I could do?

Hemant K Chitale wrote:
I lost the NFS mount point, as in it was no longer mounted to the host. If it was any other scenario, I wouldn't be attempting to resume it.and
I still have the previously restored files. I wouldn't be recieving "ORA-27038: created file already exists" otherwise. I am still confused.
I guess that you are talking of a BACKUP not a RESTORE (unlike the sentence that says "previously restored files").I meant backup. I'm also doing a restore for another purpose, so it was on my mind. It was some sort of phsychological slip.
>
"The NFS mount point is no longer mounted.". So what happened to the files that did get written to the NFS mount point ? Did you copy them to tape before the NFS mount point got unmounted ? Or is the NFS server still up and running, with the partial backup intact on it, except that the remote mount is disabled ?
We had a network problem and we lost the NFS mount. Most of the files are there, just not the whole database. I didn't copy them to tape. The whole purpose was to use the backup as a clone by manually recreating the controlfle, and pulling it into another ASM instance on another cluster. We first need to pull it out of the current ASM instance. The NFS volume was remounted, but my concern is being able to resume the backup from where it left off at.
How about running
BACKUP ... NOT BACKED UP SINCE TIME 'date_string'From the documentation : "This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up."I'll have to give that a try. It sounds promising.
>
Hemant K Chitale
http://hemantoracledba.blogspot.com

Similar Messages

Migrate Oracle 11g database from Windows To Linux using RMAN hot / cold backup ?

Hi Friends,
Is it possible to Migrate Oracle 11g database from Windows To Linux using RMAN hot / cold backup ? ( as i would like to perform Point In Time recovery)
(or) The only way is to use RMAN convert as mentioned here - Transporting Data Across Platforms
(or) Is there any other method (except exp/imp and data pump)
Regards,
DB

HI
his post describes the procedure required to migrate a database from Windows to Linux using the RMAN Convert Database command.
Both Windows and Linux platforms have the same endian format, which makes possible to transfer the whole database, making the migration process very straightforward and simple.
To migrate between platforms that have a different endian format, Cross Platform Transportable Tablespaces (XTTS) needs to be used instead.
List of Steps Needed to Complete the Migration
The migration process is simple, but as it has several steps it is convenient to be familiar with them before running it.
1. Check platform compatibility between source and target OS
2. Start the database in read only mode
3. Check database readiness for transport from Windows to Linux using DBMS_TDB.CHECK_DB
4. Check if there are any external objects
5. Execute the Rman Convert database command
6. Copy converted datafiles, generated Transport Script and Parameter File to Linux
7. Edit the init.ora for the new database
8. Edit the Transport Script and Parameter File changing the windows paths to Linux Paths
9. Execute the Transport Script
10.Change the Database ID
11.Check database integrity
Thank you

RMAN and cold backup

I am taking cold backup manually through copy command on every sunday of database every week and archive log backup through RMAN
suppose i want to restore backup on wednesday
how to retreive and apply archive logs
as archive logs are after taking backup are in different format

connect target sys/aa@oas
connect catalog rman/rman@catdb
connect auxiliary /
run {
set newname for datafile 1 to '/ORADATA/dupdb/system01.dbf';
set newname for datafile 2 to '/ORADATA/dupdb/undotbs01.dbf';
set newname for datafile 3 to '/ORADATA/dupdb/users01.dbf';
set newname for datafile 4 to '/ORADATA/dupdb/indx01.dbf';
set newname for datafile 5 to '/ORADATA/dupdb/example01.dbf';
allocate auxiliary channel dupdb1 type disk;
set until sequence 2 thread 1;
duplicate target database to dupdb
logfile
GROUP 1 ('/ORADATA/u02/redo01.log') SIZE 200k REUSE,
GROUP 2 ('/ORADATA/u03/redo02.log') SIZE 200k REUSE;
I THINK THIS OPTION WILL WORK

RAC to RAC CLONE FROM RMAN Cold Backup

Hi All,
I need your kind assistance in Cloning my Oracle RAC 11.2.0.2 Environment to remote host. Following is Disk layout
DGVOT (ASM Disk group holding OCR and Voting Disk)
DGDATA (ASM Disk Group Holding Data FIles)
DGFRA (ASM Disk Group Holding Fast Recovery FIles)
Remote Host is on different location so cannot use RMAN duplicate with auxiliary channel.
Have luxury of downtime so I want to take RMAN Consistent( Cold Backup)
SAME Disk layout is available to remote hosts.
11.2.0.2 CLusterware (GI) Plus the oracle binaries are already installed.
Can any body tell me the steps to
1) How to take cold backup to disk so that I can tar and copy to remote host
2) clone the database on remote host
3) How i will add the database listener and other resources of this databasee to clusterware.
actually this is my first RAC clone so i am not much aware of detail steps.
I have gone though many metalink notes but no one is matching with my requirements. your expert advice will help me a lot
Regards,

Hi
1) How to take cold backup to disk so that I can tar and copy to remote host.
Use Rman for cold backupIn mount stage execute
RMAN>backup database plus archivelog format '<disk_path>/dbp%U';
RMAN> backup current controlfile format '<disk_path>/ctl%U';
Copy thse backup sets to remote host
2) clone the database on remote host
Create Similar ASM Disk groups as on source
create pfile/spifile, startup instance in nomount mode
catalog backup set
RMAN> catalog start with '<backup_set location>';
Restore controlfile
RMAN>restore controlfile;
RMAN> restore database;
RMAN> recover database;
On successfull recovery
RMAN>sql 'alter database open';
3) How i will add the database listener and other resources of this databasee to clusterware.
User srvctl to add resources
Usage: srvctl <command> <object> [<options>]
commands: enable|disable|start|stop|relocate|status|add|remove|modify|getenv|setenv|unsetenv|config|convert|upgrade
objects: database|instance|service|nodeapps|vip|network|asm|diskgroup|listener|srvpool|server|scan|scan_listener|oc4j|home|filesystem|gns|cvu
For detailed help on each command and object and its options use:
srvctl <command> -h or
srvctl <command> <object> -h
Thanks,
Ajay More

Failed RMAN Duplicate from NON-RAC to RAC-ASM

Hi All!
Is it possible to resume a failed RMAN Duplicate? Database is 10gR2.
Please advice...
Regards,
cmadiam

Once you fix the disk group name you can run the duplicatie, it should work fine.
Please refer the link
http://www.oracleracexpert.com/2009/10/migrate-database-to-asm-using-rman.html
Hope this helps,
Regards
http://www.oracleracexpert.com
Duplicate RAC DB using RMAN
http://www.oracleracexpert.com/2009/12/duplicate-rac-database-using-rman.html

Script for cold backup on windows

looking for a script that can be scheduled nightly to perform
a cold backup to disk of a 8.1.7 database on windows.
while i've seen many, i'm looking for one that will keep 3 days worth
of backups... then write over the oldest etc...
thanks
dg

set term off
set head off
set feedback off
set verify off
spool c:\coldbackup.bat
select 'copy '||name||' c:\DBBACKUP' from v$datafile;
select 'copy '||name||' c:\DBBACKUP' from v$controlfile;
select 'copy '||name||' c:\DBBACKUP' from v$tempfile;
select 'copy '||member||' c:\DBBACKUP' from v$logfile;
spool off
shutdown IMMEDIATE
host c:\coldbackup.bat
startup
host del c:\coldbackup.bat
set term on
set head on
set feedback on
set verify on

Incrementally Updated Backups -- do you Backup to TAPE ?

Incrementally Updated Backups on disk provide
a. only a single image of the database
b. as of only a particular point in time (the last incremental update)
c. no protection against disk/storage failure as the backups are on the same server as the database
Your Incrementally Updated Backups should go to Tape or to another Disk Area on another server or Virtual Tape Library frequently.
You may find the need to "restore and recover the database as of 3 days ago OR as of the last critical processing date" which cannot be done if you incrementally update your backup every day.
A backup on disk doesn't protect you from disk failure.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Look in the FAQ for SuperDuper at: <http://www.shirt-pocket.com/forums/showthread.php?t=3942&highlight=time+capsul e>
where you'll find a discussion of what you can do.

If RMAN incremental level-1 backup fails...

Hi there,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Best regards

Hi,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Check the V$BACKUP_SET dictionary to confirm whether the last backup has been touched by data dictionary. If the failed incremental backup is picked up then the previous incremental backup will be required in case of the next DIFFERENTIAL INCREMENTAL LEVEL 1 backup.
But to be on safe side , it is recommended you take a LEVEL 01 CUMILATIVE INCREMENTAL backup from Level 0 till date. So that the recovery process can go through even if the previous backup is not valid.
Thanks &
Best Regards

ORA-00313: open failed for members during restore from COLD backup

Hi all,
I took a cold backup of an 11.1 database using RMAN (database in mount state).
I used the following command to restore it:
restored the controlfile and then
RESTORE DATABASE FROM TAG 'TAGxxxxxxxxxx';
Now I'm restoring it and it's taking too much time. When checking alert log it says:
ORA-51106: check failed to complete due to an error. See error below
ORA-48318: ADR Relation [HM_FINDING] of version=3 cannot be supported
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_02.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
RMAN is still in progress, why does it complain about redo?
I'm not doing recovery since it was a cold backup.
Thanks in advance.

Hi Michael,
Yes, it's the correct one because it says "full restore complete":
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_01.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Tue Apr 30 14:38:14 2013
Full restore complete of datafile 32 /oracle1/oradata/******/apr_sesm_index_01.dbf. Elapsed time: 1:25:42
checkpoint is 12652187135448
last deallocation scn is 12651877642745
Tue Apr 30 15:38:04 2013
Full restore complete of datafile 34 /oracle1/oradata/******/apr_stage_data_01.dbf. Elapsed time: 6:42:52
checkpoint is 12652187135448
last deallocation scn is 12651877637877
thanks,

RMAN: Increment backup very slow

Hi All,
We have Datawarehouse database having size around 7TB. Increment backup performance is extremely poor it is taking approx 14hrs to complete the process. We have also enabled block change tracking but failed to meet target.
Below mentioned DB info & RMAN configuration parameters:
DB: 11.1.0.6
OS: Linux 2.6.18-128.el5 x86_64
System has 16 processor when more than two process per CPU i.e. 32
CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01copy/control_bkp/autobackup_control_file%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 13 BACKUP TYPE TO COMPRESSED BACKUPSET;
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 COMPRESSION ALGORITHM 'BZIP2';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbs/snapcf_PRODDB.f'; # default
Thanks in advance.

Thnaks for reply.
Have you configured Compressed backups?
--> Yes. with below command.
RMAN> backup as compressed backupset incremental level 1 tag=$v_tag database;
Have you allocated channels ?
--> Yes.
allocate channel backup_disk1 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk2 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk3 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk4 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk5 type disk format '$v_bdest/%U' maxpiecesize 10G;
What is the Large pool size configured? try to increase.
--> large_pool_size=1073741824
Is backup to DISK or TAPE? mentioned in script?
--> Backup goes to DISK only.
How is DISK performance?
--> How can we calculate DISK performance on LINUX?
Regards,

Cold backup downtime using RMAN

Over the weekend I performed a cold RMAN backup on a 3.6 TB
database. Because a lot of the database was backed up with
transportable tablespaces, the net amount being backed up was
approximately 365 Gb. I took down the database at 11:00 and the
script finished at 4am, but in reviewing the logs, the database
actually appears to have been opened at 2am.
I assumed that the database would be down the entirety of the
backup. Can anyone help me understand why the database was
opened so long before the RMAN command completed? Was the
backup adversely affected in any way by a user obtaining access
prior to the RMAN process completing.
Any information greatly appreciated.

unfortunately i think you misunderstood the original question. i took the database down to do the cold backup. in order to use rman, you have to startup nomount the instance.
the script run was:
#!/usr/bin/ksh
rman msglog '/data2/oracle2/local/log/rman_lvl0.log' <<EOF
@connect.rman
run {
backup incremental level 0 tag full_bkup0 database diskratio=0;
alter database open;
exit;
EOF
exit
the "alter database open" tells RMAN to open the database once the backup is completed. i had a process running that checked each 10 seconds to see if the PID for the RMAN process was still running. The process itself appears to have run for an additional 2 hours after the database was opened.
there is nothing on the system to suggest that the database was opened by anything other than RMAN. was the database opened prematurely? was the additional time spent in the RMAN script doing the sync in the database? did the usage by the user prior to RMAN completing invalidate the backup? (so far the cloning is still running without error).

RMAN not opening database after cold backup

OS: RHES4
10g R2
I am having a problem using RMAN to run a cold backup. The error from the log tell me that the database is already open. However when I check the database, the status is that it is in MOUNT. I can then open it but am not sure why RMAN cannot. The log is below:
Output Log
SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 11 02:00:13 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> Connected.
SQL> Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 11 02:00:32 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORACLE instance started.
Total System Global Area 687865856 bytes
Fixed Size          780700 bytes
Variable Size          149165668 bytes
Database Buffers     536870912 bytes
Redo Buffers          1048576 bytes
Database mounted.
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Recovery Manager: Release 10.1.0.3.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN>
connected to target database: TEST10G (DBID=3717786770)
using target database controlfile instead of recovery catalog
RMAN> 2> 3> 4> 5>
allocated channel: oem_disk_backup
channel oem_disk_backup: sid=160 devtype=DISK
Starting recover at 11-MAY-06
no copy of datafile 1 found to recover
no copy of datafile 2 found to recover
no copy of datafile 3 found to recover
no copy of datafile 4 found to recover
no copy of datafile 5 found to recover
no copy of datafile 6 found to recover
no copy of datafile 7 found to recover
no copy of datafile 8 found to recover
no copy of datafile 9 found to recover
no copy of datafile 10 found to recover
no copy of datafile 11 found to recover
no copy of datafile 12 found to recover
no copy of datafile 13 found to recover
no copy of datafile 14 found to recover
no copy of datafile 15 found to recover
no copy of datafile 16 found to recover
no copy of datafile 17 found to recover
no copy of datafile 18 found to recover
Finished recover at 11-MAY-06
Starting backup at 11-MAY-06
no parent backup or copy of datafile 18 found
no parent backup or copy of datafile 1 found
no parent backup or copy of datafile 8 found
no parent backup or copy of datafile 9 found
no parent backup or copy of datafile 10 found
no parent backup or copy of datafile 11 found
no parent backup or copy of datafile 13 found
no parent backup or copy of datafile 14 found
no parent backup or copy of datafile 15 found
no parent backup or copy of datafile 17 found
no parent backup or copy of datafile 4 found
channel oem_disk_backup: starting compressed incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
input datafile fno=00003 name=/home/oracle/oradata/dev10g/sysaux01.dbf
input datafile fno=00002 name=/home/oracle/oradata/dev10g/undotbs01.dbf
input datafile fno=00005 name=/home/oracle/oradata/dev10g/example01.dbf
input datafile fno=00012 name=/home/oracle/oradata/dev10g/FLOW_7.dbf
input datafile fno=00016 name=/home/oracle/oradata/dev10g/FLOW_11.dbf
input datafile fno=00006 name=/home/oracle/oradata/dev10g/FLOW_1.dbf
input datafile fno=00007 name=/home/oracle/oradata/dev10g/FLOW_2.dbf
channel oem_disk_backup: starting piece 1 at 11-MAY-06
channel oem_disk_backup: finished piece 1 at 11-MAY-06
piece handle=/home/oracle/flash_recovery_area/DEV10G/backupset/2006_05_11/o1_mf_nnnd1_TAG20060511T020039_265nr8h8_.bkp comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:01:15
channel oem_disk_backup: starting datafile copy
input datafile fno=00018 name=/home/oracle/oradata/dev10g/designer1.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_designer_265ntmow_.dbf tag=ORA$OEM_LEVEL_0 recid=9 stamp=590119379
channel oem_disk_backup: datafile copy complete, elapsed time: 00:01:05
channel oem_disk_backup: starting datafile copy
input datafile fno=00001 name=/home/oracle/oradata/dev10g/system01.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_system_265nwnw0_.dbf tag=ORA$OEM_LEVEL_0 recid=10 stamp=590119436
channel oem_disk_backup: datafile copy complete, elapsed time: 00:01:05
channel oem_disk_backup: starting datafile copy
input datafile fno=00008 name=/home/oracle/oradata/dev10g/FLOW_3.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_3_265nyp5w_.dbf tag=ORA$OEM_LEVEL_0 recid=11 stamp=590119448
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
channel oem_disk_backup: starting datafile copy
input datafile fno=00009 name=/home/oracle/oradata/dev10g/FLOW_4.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_4_265nysc5_.dbf tag=ORA$OEM_LEVEL_0 recid=12 stamp=590119452
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
channel oem_disk_backup: starting datafile copy
input datafile fno=00010 name=/home/oracle/oradata/dev10g/FLOW_5.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_5_265nz0jc_.dbf tag=ORA$OEM_LEVEL_0 recid=13 stamp=590119458
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
channel oem_disk_backup: starting datafile copy
input datafile fno=00011 name=/home/oracle/oradata/dev10g/FLOW_6.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_6_265nz3oo_.dbf tag=ORA$OEM_LEVEL_0 recid=14 stamp=590119463
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
channel oem_disk_backup: starting datafile copy
input datafile fno=00013 name=/home/oracle/oradata/dev10g/FLOW_8.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_8_265nzbvj_.dbf tag=ORA$OEM_LEVEL_0 recid=15 stamp=590119469
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
channel oem_disk_backup: starting datafile copy
input datafile fno=00014 name=/home/oracle/oradata/dev10g/FLOW_9.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_9_265nzg1k_.dbf tag=ORA$OEM_LEVEL_0 recid=16 stamp=590119473
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
channel oem_disk_backup: starting datafile copy
input datafile fno=00015 name=/home/oracle/oradata/dev10g/FLOW_10.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_10_265nzo6x_.dbf tag=ORA$OEM_LEVEL_0 recid=17 stamp=590119480
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:07
channel oem_disk_backup: starting datafile copy
input datafile fno=00017 name=/home/oracle/oradata/dev10g/FLOW_12.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_flow_12_265nzwdb_.dbf tag=ORA$OEM_LEVEL_0 recid=18 stamp=590119487
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
channel oem_disk_backup: starting datafile copy
input datafile fno=00004 name=/home/oracle/oradata/dev10g/users01.dbf
output filename=/home/oracle/flash_recovery_area/DEV10G/datafile/o1_mf_users_265nzzo0_.dbf tag=ORA$OEM_LEVEL_0 recid=19 stamp=590119489
channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:03
channel oem_disk_backup: starting compressed incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel oem_disk_backup: starting piece 1 at 11-MAY-06
channel oem_disk_backup: finished piece 1 at 11-MAY-06
piece handle=/home/oracle/flash_recovery_area/DEV10G/backupset/2006_05_11/o1_mf_ncsn1_TAG20060511T020039_265o04n1_.bkp comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:00:03
Finished backup at 11-MAY-06
released channel: oem_disk_backup
RMAN>
Recovery Manager complete.
SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 11 08:03:38 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> Connected.
SQL> alter database open
ERROR at line 1:
ORA-01531: a database already open by the instance
Unable to open the database.

Do you have an OMS configured for OEM? You'll need to connect to an OMS to perform backups thru OEM. The process is explained here Managing Backup and Recovery.
Here is a SAMPLE configuration script:
configure device type disk parallelism 1;
configure channel device type disk format 'd:\oracle_backup\%d_%U.%p';
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to 'd:\oracle_backup\cf_auto_%F.bkp';
configure retention policy to recovery window of 2 days;
configure backup optimization on;and a SAMPLE backup script:
rem
rem rman_backup.cmd
rem
rem Full database backup plus archivelogs.
for /f "tokens=2-4" %%i in ('echo %date:/= %') do set vdate=%%i_%%j_%%k
echo backup database plus archivelog;
echo sql "alter database backup controlfile to trace as ''d:\oracle_backup\controlORCL9%vdate%.txt''";
echo sql "create pfile=''d:\oracle_backup\initORCL9%vdate%.ora'' from spfile";
echo crosscheck backup;
echo crosscheck archivelog all;
echo delete noprompt obsolete recovery window of 2 days;
echo delete noprompt archivelog all completed before 'sysdate-7';
) | rman target / log=backup.logYou could scheduled the rman_backup.cmd script to run every night at 10pm thru the Windows task scheduler.

Clonning using RMAN Cold Backup?

Hi,
I have a COLD RMAN backup in prod server and now i want to clone test db using this backup through RMAN. I have 2 question regarding this
1) Where do i need to place the prod RMAN COLD backup files in test server?
2) If i ran below command how RMAN will know where did i placed the backup in test server?
In Test Server
RMAN> duplicate target database to test;DB Version is : 10.2.0.4
Thanks in advance

thanks. Now it is unable to restore the datafiles from rman backup.Below steps i tried.
[oracle@Test test1]$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Feb 21 08:58:46 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initprod2.ora';
Oracle instance started
Total System Global Area     603979776 bytes
Fixed Size                     1268896 bytes
Variable Size                163578720 bytes
Database Buffers             436207616 bytes
Redo Buffers                   2924544 bytes
RMAN> restore controlfile from '/u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak';
Starting restore at 21-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control01.ctl
output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control02.ctl
output filename=/u01/app/oracle/product/10.2.0/oradata/test1/control03.ctl
Finished restore at 21-FEB-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> catalog start with '/u01/app/oracle/product/10.2.0/backup/test1';
Starting implicit crosscheck backup at 21-FEB-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 21-FEB-12
Starting implicit crosscheck copy at 21-FEB-12
using channel ORA_DISK_1
Finished implicit crosscheck copy at 21-FEB-12
searching for all files in the recovery area
cataloging files...
no files cataloged
searching for all files that match the pattern /u01/app/oracle/product/10.2.0/backup/test1
List of Files Unknown to the Database
=====================================
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
File Name: /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_08n3s02u_1_1.bak
RMAN>
RMAN> restore database;
Starting restore at 21-FEB-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/app/oracle/oradata/prod2/system.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/prod2/usr04.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/prod2/undo.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/prod2/sysaux.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/prod2/p1_01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/prod2/p2_01.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
ORA-19870: error reading backup piece /u01/app/oracle/product/10.2.0/backup/test1/21_RMAN_BACKUP_07n3rvvq_1_1.bak
ORA-19504: failed to create file "/u01/app/oracle/oradata/prod2/system.dbf"
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
failover to previous backup
creating datafile fno=1 name=/u01/app/oracle/oradata/prod2/system.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/21/2012 09:01:09
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/u01/app/oracle/oradata/prod2/system.dbf'

RMAN cold backup taking more time than usual

Hi everybody.. please help me resolving below issue..
I have configured the RMAN in one of the production database with separate catalogue database six months earlier. I have sceduled weekly cold backup through RMAN on sunday 6pm. Normally it used to take one hour to complete the cold backup and database goes down soon as the job starts.
But since from then every week the time taken to just initiate the database shutdown continuosly increasing and recently when i checked it is taking 1 hour to initiate the database shutdown. Once the initiation starts it hardly take 1 to 3 min to shutdown.
Database is up and running during that one Hour. I was in the assumption that RMAN takes some time to execute its internal packages.
Please help
Regards,
Arun Kumar

Hi John and Tychos,
Thank you very much for your valuable inputs.
Yesterday there was cold backup and i have monitored the CPU usage. But there was no load on the CPU at that time and CPU usage was 0%
I have tried connecting to RMAN manually and it connects within a second. And also noticed in prstat -a that rman connects as soon as the job starts.
So i think that its taking time at the deleting obsolete backups.
But I have observerd following observation.
Before executing the delete obsolete command as mentioned before
RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 83409 25-JUL-09
Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
Backup Set 83410 25-JUL-09
Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
Backup Set 83411 25-JUL-09
Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
After executing the delete obsolete command
RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 83409 25-JUL-09
Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
Backup Set 83410 25-JUL-09
Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
Backup Set 83411 25-JUL-09
Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
Please advice me on the following.
1. Why its not deleting the obsolete BACKUP SETS?
2. Is it normal that RMAN takes this much deleting obsolete backup sets? How can i minimize the time taking for deleting obsolete files.
Thanks and Regards,
Arun Kumar

Rman incremental backup

Hi,
we are using oracle10g(10.2.0.3).
is it possible to apply rman incremental backup on top of manual full backup?
Note:There is no level 0 backup available
Thanks
With Regards
Umair

Yes, you can.
Register your manual backup in recovery catalog as level 0 backup. Then take a fresh incremental backup. I have demonstrated the same in my article. You may download the same from here .
Go through the section "Rolling forward a backup".
Regards,
S.K.

Resume a failed RMAN incremental 0 cold backup to disk

Similar Messages

Maybe you are looking for