RMAN hot backup cloning problem..need a way out

I took hot backup from server A using RMAN
I prepared server A by running preclone on apps and db tier
I copied apps tier and dbTier(tech_st) from server A to server B..Apps and db tier were up and running during the copy.I also copied the RMAN backup sets
now on server B, what should i do..RMAN backup is in backup sets and i need to restore it on server B(Target server)
I am following note 406982.1 for cloning steps..
in advanced clonign options, it doesnt specify to run adcfgclone on apps tier too
please guide
help appreciated

Hi,
The document assumes that you are aware of the RMAN backup, and you know how to duplicate the database.
Oracle Database Documentation
http://www.oracle.com/technology/documentation/database.html
Search this forum for "RMAN Duplicate" there are many documents referenced as this topic was discussed many times before.
Regards,
Hussein

Similar Messages

RMAN & Hot backup cloning taking long time

Dear DBAs,
We are doing both RMAN & Hot backup cloning foe that taking more time to restore data files to TEST instance. scp taking too much time to copy to target server because of its volume of data (1.5 TB) & Mounting the RMAN backups drive on test server and restoring from that drive taking more than 8 hours.
I heard that some companies are using some device to move heavy volume Hot backup copy from source to dest faster for clone the instance easily with in minutes. What is that device name to take hot backup copies from source and restore it in target server.
Test server Specs
Processor 8 cores with 32GB Memory.
Thanks
DBA

Hot backup is not recommanded for the database size more than 1T.
RMAN backup and restore is the only opiton available for a DBA.
Other option is to use EMC Symmentrix/BCV's/Snapshots. EMC uses pair of disks to achive synch the produciton data with test server. read more about EMC symmentrix or ask your storage team.

User hot and Rman hot backup

During user mode hot backup lots of redo gets generated as the entire block is written when any changes are made to a block which is in hot backup mode.But during Rman hot backup less redo are generated why is this so and whatz the logic invloved? and how oracle recovers the file that has been backed up through Rman.
Could you please explain me regarding this in detail it will be really helpful.
kumaresh

From Article Note:76736.1 RMAN FAQ: Recovery Manager -- Frequently Asked
To understand why RMAN does not require extra logging or backup mode,
you must first understand why those features are required for non-RMAN
online backups.
A non-RMAN online backup consists of a non-Oracle tool, such as cp or
dd, backing up a datafile at the same time that DBWR is updating the
file. We can't prevent the tool from reading a particular block at the
exact same time that DBWR is updating that block. When that happens,
the non-Oracle tool might read a block in a half-updated state, so that
the block which is copied to the backup media might only have been
updated in its first half, while the second half contains older data.
This is called a "fractured block". If this backup needs to be restored
later, and that block needs to be recovered, recovery will fail because
that block is not usable.
The 'alter tablespace begin backup' command is our solution for the
fractured block problem. When a tablespace is in backup mode, and a
change is made to a data block, instead of logging just the changed
bytes to the redo log, we also log a copy of the entire block image
before the change, so that we can reconstruct this block if media
recovery finds that this block was fractured. That block image logging
is what causes extra redo to be generated while files are in backup
mode.
The reason that RMAN does not require extra logging is that it
guarantees that it will never back up a fractured block. We can make
that guarantee because we know the format of Oracle data blocks, and we
verify that each block that we read is complete before we copy it to the
backup. If we read a fractured block, we read the block again to obtain
a complete block before backing it up. non-Oracle tools are not able to
do the same thing because they do not know how to verify the contents of
an Oracle data block.
Backup mode has another effect, which is to 'freeze' the checkpoint in
the header of the file until the file is removed from backup mode.
We do this because we cannot guarantee that the third-party backup
tool will copy the file header prior to copying the data blocks.
RMAN does not need to freeze the file header checkpoint because we
know the order in which we will read the blocks, which enables us to
capture a known good checkpoint for the file.

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

Hot Backup cloning vs Cold Backup CLoning

Hi,
when we do cold backu cloning...we get same data as production database..
when we do hot backup cloning..i think we will loose current transactions which are recorded in redo log and not archived ....am i right?????
when we do hot backup cloning....all the database files headers are freezed..means...all latest changes are not copied while we copying datafiles to test machine...but those changes are logged in archived log files...we will get these changes in archived log files...
am i right?????
please correct me if i am wrong.....

When all is said and done there is really no difference in the clone database made from a cold backup or a hot backup as both are point in time recoveries.
In the case of the cold backup the source database was made unavailable to users while the backup was taken. If you have that luxary then that is fine, but many sites would need or want to keep the source available while the backup runs.
The backup type should not be an issue unless you really need to capture the source database with the data in a specific known state where no changes were taking place.
IMHO -- Mark D Powell --

Automating refreshing one system with the rman hot backup copy from another

Hi Apps DBAs,
Right now we have two systems: production (OPEBSN) and production support (FINSUP).
I implemented a cronjob, which can refresh FINSUP every night from the cold backup of production. We shutdown the production system at night.
But our istore on production will go live soon and our production system will run 24*7.
The production is already hot backed up from RMAN.
Is it possible to do the following?
Automating refreshing FINSUP from the RMAN hot backup of OPEBSN?
If it is possible, would you please outline the general idea or give me a reference documentation?
If it is not possible, is there any other way to realize our purpose?
Thank you in advance!
Lily

There is some discussion about this topic in the belwo askTom thread.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:21934468026100
Sam
http://appstech-sam.blogspot.com

RMAN Hot backup Restore in new Server

Hi,
Our Current Environment:
Source: Current Production
Database: 11.1.0.7
OS: Windows server 2003 R2
Target Environemnt:
Database 11.2.0.1
OS:windows server 2008 R2
Here my scenario is need to take RMAN Hot backup in Prod Instance and need to restore in New Server with smae SID which is going to use as Prod instance.
Please suggest the detailed steps in order to achive the goal.
Waiting for your thoughts.
Thanks
Shaik

RMAN can make it easy to restore a database to a new host.
Notice that: Using RMAN RESTORE and RECOVER commands to move a database permanently to another host, will keep the original database identifier (DBID) and will therefore cause a conflict in the RMAN repository, because the restored database with the same DBID will be considered the current target database.
Below you may find the steps:
Preparing the New Host
Record the DBID of the source database.
Copy the initialization parameter file from the source database to the new host.
Make sure that all source database backups are available to the new host. Do not connect to the recovery catalog.
Restoring and Recovering on the New Host
Configure environment variables on the new host.
Connect to the new target database with NOCATALOG.
Set the DBID.
Start the instance with NOMOUNT.
Restore the SPFILE from backup.
Shut down the new instance.
Edit the PFILE.
Start the instance with NOMOUNT (again).
Create an RMAN RUN block to restore the control file.
Create an RMAN RUN block to restore and recover the database.
Open the database with RESETLOGS.
Regards,

Unique Error while doing hot backup Cloning!

Dear All,
I am using EBS 11.5.10.2 with DB 9.2.0.6.
I am doing hot backup cloning by referring *[Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g) Using Hot Backup on Open Database|https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=760772.1]*
I am facing a unique issue, when I run adcfgclone.pl dbconfig <my_context_file>, application of my Production Server start misbehaving and it gives me an error:
Node Id does not exist for the current application server id.When I check the FND_NODE table I found that there server id was empty in it.
I have to run than run the following steps as the resolution:
1. Shutdown all the services.
2. EXEC FND_CONC_CLONE.SETUP_CLEAN;
3. COMMIT;
4. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers,to repopulate the required system tables.
5.start all the services and verify the issue.
Than application behaves normally.
Is there any additional step to be followed while Hot Backup Cloning other than mentioned in the above mentioned ML Doc?
Please suggest,
Anchorage :)

I am facing a unique issue, when I run adcfgclone.pl dbconfig <my_context_file>, application of my Production Server start misbehaving and it gives me an error:
Node Id does not exist for the current application server id.Where did you get this error?
This is very strange, how come this happens in Production, when you are doing cloning in TEST/DEV instance.
Is there any additional step to be followed while Hot Backup Cloning other than mentioned in the above mentioned ML Doc?I feel there are no other additional steps, as I Recently did successfully hotbackup cloning using the same document.

Hot backup cloning in ebs r12

HI i was doing the hot backup cloning in ebsr12.
i have backed up the control files and datafiles and the trace file also.
i have done the steps till copying the db and apps tier.
next is
2) Create the target database control file manually
Open the backed up control file
a. remove all lines before the startup nomount statement
b. Modify the REUSE to SET
c. Modify Source DB SID to Target SID (Here PROD to TEST)
d. Modify NORESETLOGS TO RESETLOGS
e. delete all lines after the CHARACTER SET statement
i am not sure about editing the control file ....
I am a started in db's
can anyone help me in this?

HI i was doing the hot backup cloning in ebsr12.
i have backed up the control files and datafiles and the trace file also.
i have done the steps till copying the db and apps tier.Looks like you are doing cold backup and not hot backup! Was the database cleanly shutdown before copying the database files?
a. remove all lines before the startup nomount statementCorrect -- Or you could leave those lines if they are commented.
b. Modify the REUSE to SETCorrect.
c. Modify Source DB SID to Target SID (Here PROD to TEST)Correct.
d. Modify NORESETLOGS TO RESETLOGSCorrect.
You will also have to change ARCHIVELOG to NOARCHIVELOG -- If your source instance is in ARCHIVELOG mode.
e. delete all lines after the CHARACTER SET statementKeep the lines/command that open the database and create the temporary tablespace.
Thanks,
Hussein

Hot Backup Cloning

Hi Hussein and Fadi,
Do you have any experience on doin Hot Backup Cloning of Oracle Apps 11.5.10.2.
Can you please share your experience

the issue here is in the database part
i use the following steps
-run preclone
-Copy the Application tier file system (same as normal cloning)
-Copy the Database tier file system
here i put all the tablspace in backup mode
alter tablespace tablesacpe_name begin backup;
-Copy the data files
When finish the copy we have to execute the following sql statement on the source database:
-Put the database back in normal mode.
Alter tablespace tablesacpe_name end backup;
ALTER SYSTEM ARCHIVE LOG CURRENT;
-Copy Archive logs
after that you can start working in the target env. for the database you have to
-fix init.ora to reflect new paths and new sid
-start the database nomount.
-create control file manual.
-alter database mount.
-recover the database.
hope that helped
fadi

How to restore RMAN hot backup to another database on another server?

I want to know how to restore RMAN hot backup from production server to another database on a testing server.
The hot backup is from a database named PROD on the production server
The database to be restored with the hot backup is TEST on the testing server. There is already a PROD database on the testing server and this PROD database must be kept.
I have read some threads about changing initTEST.ora to PROD to restore such backup but (I think) will not work in my case since I already have a PROD database on the testing server.
The version is 11gR2 on Linux but the compatible parameter is set to 10.2.0.1.0.
Thanks for any help.

Hi,
Since you are on 11g, hope this helps you http://shivanandarao.wordpress.com/2012/04/28/duplicating-database-without-connecting-to-target-database-or-catalog-database-in-oracle-11g/
881656
Handle:     881656
Status Level:     Newbie
Registered:     Aug 25, 2011
Total Posts:     53
Total Questions:      31 (31 unresolved)
Looks like forum is of no help to you. To get better responses, consider closing your threads by providing appropriate points if you feel that they have been answered. Keep the forum clean !!

Creating RAC database thru RMAN hot backup

Hi Guys,
I am having ERP PROD database on 2 nodes 116 and 117(RAC) server. We have a scheduled RMAN HOT backup of this database
WE also have ASM implemented.
We have another 2 servers named 36 and 37(RAC and ASM) which has ERP Test Database and the thing is that we want to refresh this
test database using ERP PROD RMAN backup.
Can someone please post the proper steps to restore the RMAN backup to ERP Test database as ASM is alos there.
As it is little urgent for us.
help will be appreciated.
Regards,
Milan Rathod

1. take the backup of production database
rman connect target /
backup as compressed backupset database plus archivelog format '/u01/db/backup/%d_%I_%s_%T';
move the backup to test server (same location /u01/db/backup/ bcoz rman checks for backupset in the same location only)
add the below two lines in the test database-- initTEST.ora file
comment cluster_ parameters in initTEST.ora file
eg:-
DB_FILE_NAME_CONVERT = (+EBAOUATDATADG1/prod/,/u01/db/app/admin/test/)
LOG_FILE_NAME_CONVERT = (+EBAOUATDATADG1/prod/,/u01/db/app/admin/test/)
check the connectivity between prod and test database.
from test
$tnsping PROD
from prod machine
$tnsping TEST
in test server
startup nomount
rman target sys@proddb auxiliary /
duplicate target database to test;
after completion of duplicate/clone step convert the single instance test to rac instance by uncomment the cluster_ parameters in initTEST.ora parameter
startup mount the second node in TEST
ALTER DATABASE ENABLE PUBLIC THREAD 2 ;
alter database open;
hope, this will helps you.
Good Luck

RMAN Hot Backup Errors.

Hello Everyone
I would appreciate if someone can assist me in resolving a problem. Starting from December of last year, we were able to take daily hot backups of our ORACLE 10g database server successfully with no issues. Presently we have been experiencing a number of errors in the logs, even though the script has not been changed. The main errors are as follows:
RMAN-03009: failure of backup command on t1 channel at 05/08/2007 00:01:19
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
In investigating the errors, it seemed to be associated to the tablespace not being put offline or backup mode cleanly, I assumed this was due to persons working later, so I scheduled the backup for a later time but I still got the same error in the log the following day. Can you assist me in resolving this problem please?

Is the db running in ARCH mode?
Error:     ORA 19602
Text:     cannot backup or copy active file in NOARCHIVELOG mode
Cause:     You tried to copy or backup a file that was not closed cleanly, and
     the database was in NOARCHIVELOG mode. This is not allowed because when
     restored, the file will require redo application before it is usable,
     and redo is not currently being saved beyond the contents of the online
     redo logs.
Action:     Take the tablespace offline clean or close the database and retry the
     copy or backup. Take the tablespace offline clean or close the database
     and retry

RMAN hot backup on RAC instances

10gR2 RHEL 4 AS 64 bit
Node1 - FPRCPROD1
Node2 - FPRCPROD2
Database Name - FPRCPROD
Hi All,
I am trying to do an RMAN hot back up of my 2 node RAC database. The backup script is all ready to go but I am having a problem. I have a 2 part question:
When I run my script it is getting the ORACLE_SID from the /etc/oratab file. And in that file, for both my nodes, the entry is as follows:
FPRCPROD:/opt/app/oracle/product/10.2.0/db_1:N
Isn't is suppose to have the instance name (FPRCPROD1)? and FPRCPROD2 on the second node?
Which ORACLE_SID am I suppose to have to make the script run successfully? FPRCPROD or FPRCPROD1?
Thank you.

This is from documentation (9i, but also valid for 10g):
Verify the contents of the oratab file
Check the existence and contents of the oratab file on all nodes. The default location is /var/opt/oracle/oratab (or /etc/oratab on some operating systems). The contents should be:
V920:/u01/app/oracle/product/9.2.0:N
Notice that the entry should contain the database name (V920) and NOT the instance name (ORACLE_SID). This file should be the same on all nodes.
As you can see, use database name, NOT instance name.
Werner

RMAN hot backup requires archivelog all the time?

Hi all,
consider the case: a dml operation is running in oracle 11g database. after sometime it got completed and issued a commit statement. Now i took a full database hot backup using rman. but dint take archivelog backup(its must i know, but i want to know whether we can do incomplete recovery using only the full database backup and open database using RESETLOGS option?
Kindly let me know whether we can do incomplete recovery using only full database backup or we must need archivelog to open the database?
Regards,

Say your BACKUP DATABASE begins at 01:00am and finishes at 01:50am. At the minimum, you need to backup the Archivelogs from 01:00am to the first archivelolg after 01:50am. Technically you don't need the archivelogs of before 01:00am. However, if you want the ability to do a point in time recovery (which is a MUST for any production database), you would also backup the "earlier" archivelogs which can be used with the previous database backup.
Your commit does NOT guarantee that the database files are immediately updated -- DBWR "lazily" defers writing to the database files. Your commit is preserved in the online redo log. This has to be archived as an Archivelog and backed up.
Hemant K Chitale

RMAN hot backup cloning problem..need a way out

Similar Messages

Maybe you are looking for