Cold backup registration on rman

5) can we register manual cold backup in rman?

If you take backup using RMAN, it will automatically register with controlfile,
What else you are looking for?
If those are new backup pieces, which are not registered, then you can catalog those backup pieces.
copy all the backup pieces in folder and give
catalog start with 'location'it will register all the pieces.
Thanks

Similar Messages

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

User managed coldbkp vs rman cold backup

Hi,
I confused about rman cold backup in no catalog mode while restore the backup.please anyone clarify it.
1,I am not confused about user manged cold backup.I took the backup (spfile,control file,redo file,datafile,password file.)Is it right one?
2,In rman cold backup in no catalog mod, we used backup sets for backup,control file is autobackup is enabled.
The backup set format is not OS format.The backup stored at flash recovery area.
Just assume,
I lost all files(spfile,control file,redo file,datafile,password file.)How to recover that.
I am not able to identity spfile & control file in backupset in flash recovery area.
How to identity the spfile,control file during the restoration?
3,Rman takes the copy of online redo file in cold backup?
If it's not,How to recover the database & in user managed backup,copy of online redo log file is must?
4,What is the difference between dbid & sid?when it is used?
5,Can i specifty format for spfile when i take the backup? can i use trace file(control file ) for restoration?
I read the oracle documents, but I am not understand the above things clearly.please anyone rectify it.

user3266490 wrote:
Hi,
I confused about rman cold backup in no catalog mode while restore the backup.please anyone clarify it.
1,I am not confused about user manged cold backup.I took the backup (spfile,control file,redo file,datafile,password file.)Is it right one?
Yes,you are right,but first need SHUTDOWN IMMEDIATE;
>
2,In rman cold backup in no catalog mod, we used backup sets for backup,control file is autobackup is enabled.
The backup set format is not OS format.The backup stored at flash recovery area.
If you do not explicitly configured rman then yes it will backup to FRA.
Just assume,
I lost all files(spfile,control file,redo file,datafile,password file.)How to recover that.
First need SET (EXPORT) ORACLE_SID and then
rman target /
startup force nomount;
restore spfile from 'autobackuplocation';
startup force nomount;
restore controlfile from 'autobackuplocation';
catalog start with 'backupandarchiveloglocation';
restore database;
recover database;
alter database open resetlogs;
I am not able to identity spfile & control file in backupset in flash recovery area.
From rman you can execute LIST BACKUP or LIST BACKUP OF CONTROLFILE;
How to identity the spfile,control file during the restoration?
3,Rman takes the copy of online redo file in cold backup?No,RMAN do not backup online logs,due to this do not need.
If it's not,How to recover the database & in user managed backup,copy of online redo log file is must?
If cold backup then you can open database with resetlogs option and online logs will create automatically(if you did not copy this logs)
>
4,What is the difference between dbid & sid?when it is used?
DBID is unique identify database in recovery catalog and using this you can restore controlfile easily.But SID is ORACLE_SID and identify instance.This is environment variable like ORACLE_HOME
5,Can i specifty format for spfile when i take the backup? can i use trace file(control file ) for restoration?
Yes you can identify format manually for spfile. ALTER DATABASE BACKUP CONTROLFILE TO TRACE ... this statement use to getting script for recreating controlfile again.So this is not backup and you can notuse for restoring controlfile.If you do not have a backup of controlfile and all datafilesd available then you can use this statement.
I read the oracle documents, but I am not understand the above things clearly.please anyone rectify it.All these and with all situation clearly explained below doc
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/toc.htm

RMAN Restore from cold backup ?

Hi ,
I am trying to restore the database from production db using the RMAN cold Backup. Both the prod and test(Restore database) are on the same machine. And also I wanted to have the restore db name should be different.
And the restore db name should be different. What are the options I have ?

refer the thread:-
RMAN Restore using RMAN COLD Backup!!
RMAN Restore using RMAN COLD Backup!!

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

Re: does the full cold backup of rman include onlinde redologs?

Hi,
does the full cold backup of rman include onlinde redologs?
So that at the time of recovery when i restore the database the online redologs also restored to that point?
Please kindly add your suggestions. I read in 10g database in mount state while taking RMAN Cold backup as the all the oracle processes are down we cant copy the online redologs.
Am I Correct if not please any one answer me why the online redologs are not copied.
Thanks in Advance
Sai

976630 wrote:
Hi,
does the full cold backup of rman include onlinde redologs?No.
So that at the time of recovery when i restore the database the online redologs also restored to that point?No.
>
Please kindly add your suggestions. I read in 10g database in mount state while taking RMAN Cold backup as the all the oracle processes are down we cant copy the online redologs.
Am I Correct if not please any one answer me why the online redologs are not copied.No. They are not needed because the only valid backup for a cold (or noarchivelog mode database) backup is a consistent backup. Since the backup is already consistent there are no changes to apply.
The online redo logs are (re)created/reset by the "resetlogs" clause when the database is opened.
>
Thanks in Advance
SaiEdited by: Mark Williams on Jan 7, 2013 10:32 PM - Looks like Hemant replied whilst I was typing in my response.

Cold backup using RMAN

Dear All,
db_version :10.2.0.4
os_version:Window 2003 server
Environment:Test
I wish to perform cold backup using RMAN for the same i want to know following :
1. What is the script / command ?
2. How to restore cold backup completely ( ex:- if i lost all my data,redo and archives )
3. Is it mandatory to open the database in RESETLOG mode after recovery ( since i have a cold backup ) ?
Thanks in advance

A "Cold" Backup is called a "Consistent" Backup.
See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref297
Backup :
From the RMAN command line :
SHUTDOWN IMMEDIATE
STARTUP MOUNT
BACKUP DATABASE
BACKUP CURRENT CONTROLFILE -- to get the controlfile in a separate backupsetRestore :
STARTUP MOUNT
RESTORE DATABASE
ALTER DATABASE OPENIf you use an SPFILE, you can have an SPFILE backup included automatically with the controlfile backupset with CONFIGURE CONTROLFILE AUTOBACKUP ON and CONFIGURE CONTROLFILE AUTOBACKUP FORMAT ...
Read the documentation.
Hemant K Chitale

Create new database using rman cold backup

It oracle 10g database version 10.2.0.4
I took the cold backup of the database using rman ( Database name TEST)
1.RMAN> startup mount;
2.RMAN> backup database include current controlfile;
3.RMAN> alter database open;
I aim to create the new database called DEMO using this backup
Please let know the setps for creating new database
Edited by: prajeevan on Jan 19, 2011 9:09 PM

I took the cold backup of the database using rman ( Database name TEST)
1.RMAN> startup mount;
2.RMAN> backup database include current controlfile;
3.RMAN> alter database open;
I aim to create the new database called DEMO using this backup
Please let know the setps for creating new databaseIf it is in archivelog mode you can use duplicate to refresh database DEMO from TEST..
or after cold backup, go to mount ,
create trace file of controlfile becuase you are chaning database name
recreate the controlfile
open database in resetlogs;
check also http://blogs.oracle.com/AlejandroVargas/gems/RMANDUPDBPRACTICE.pdf

Script for cold backup using RMAN

Dear all,
db_version:-10.2.0.4
os_version:- Windows 2003 server
I wish to schedule a script that will take cold backup of my database using RMAN.
Any help is appreciated ..
Edited by: user12000301 on May 18, 2011 5:02 AM

Dear All,
Thanks a lot for your valuable time :
However i have managed to do it as follows :
1. First i have configure the parameter of RMAN ( Since it is my UAT in Noarchive log mode), I have never tried RMAN cold backup on the same.
Following is the out put of SHOW ALL;
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\DB\RMAN_BKP\BACKUPS%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED 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 FORMAT 'D:\DB\RMAN_BKP\BACKUPS\DB_%U.%r';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\DB\RMAN_BKP\BACKUPS\SNCFDB.ORA';
2. I have created a rman_cold_bkp.bat file which has following entry :
cd c:\oracle10g\bin
set oracle_sid=DB
rman target system/*** @D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.rcv log=D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.log
exit
3. Whereas rman_cold_bkp.rcv file contains following contents:
run
allocate channel C1 device type disk;
shutdown immediate;
startup mount;
backup database;
alter database open;
release channel C1;
exit
I did checked it and it;s working fine for me :-)
Regards,
Girish

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.

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

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'

Restore cold backup and RMAN backup

Hi,
I have cold backup as well as RMAN backup. But i don't know how to restore the backup.
Please anybody send, steps or links for restoring both backups.
Regs,
Brijesh

The "script" would depend on how the backup was done.
A cold backup should be a backup of controlfiles and datafiles.
Was it done using RMAN ? Or done using an OS command (e.g. "cp" or "tar" or "cpio") ?
A non-RMAN cold backup can be restored with the same command that was used to create the backup. If the backup did not include the Online Redo Log files, you need to simulate a dummy recovery from the SQL command line (RECOVER DATABASE UNTIL CANCEL ; then CANCEL) and ALTER DATABASE OPEN RESETLOGS.
If the backup was done using RMAN, you need to
1. RESTORE CONTROLFILE FROM '/location_of_backuppiece'
2. ALTER DATABASE MOUNT
3. RESTORE DATABASE
4. ALTER DATABASE OPEN
Hemant K Chitale

About hot & cold backups in rman

Hi all,
I've found out that with rman 9i the following script:
- shutdown immediate;
- startup mount;
- backup database plus archivelog;
- alter database open;
is what I need for a cold backup; somewhere somehow I've caught a glimpse about
this script
- backup database plus archivelog;
which 'should' be able to produce a reliable hot backup, but actually Oracle docs
is not crystal clear on this point: I'd rather ask if:
a/ would "backup database plus archivelog" create an usable full backup on
a 9i archivelogged db?
b/ would the same statement work on a 8.1.7 archivelogged db? (yes, the syntax is different...)
hope somebody may shed some light
thanks for help,
daniele rizzi ([email protected])

backup database plus archivelog; is a 9i RMAN command so it cannot be used in 8i. Here is what it does as stated in the Oracle9i Recovery Manager User's Guide and Reference:
Backing Up Logs Using BACKUP ... PLUS ARCHIVELOG
When backing up objects other than archived logs, you can specify BACKUP ... PLUS ARCHIVELOG to include backups of archived logs. The command performs the following sequential actions:
- Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.
- Runs BACKUP ARCHIVELOG ALL. Note that if backup optimization is enabled (refer to "Backing Up Files Using Backup Optimization"), then RMAN skips logs that it has already backed up to the specified device.
- Backs up files specified in BACKUP command.
- Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.
- Backs up any remaining archived logs generated during the backup.
From what I read it backs up all current archivelogs, backs up the datafiles, and backs up any remaining archivelogs created during the datafile backup. It basically makes it easier to backup the archivelogs by not having to issue a archvielog backup before and after the datafiles to ensure all archivelogs are backed up.

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

Cold backup registration on rman

Similar Messages

Maybe you are looking for