Standby hot backup

Hi all,
10.2.0
Do i really need a cold backup for creating a standby database.If i take user managed hot backup and copy it to the stadnby server,wouldn't upon redo apply it would be synchronised and become consistent ?

Hashmi wrote:
Hi all,
10.2.0
Do i really need a cold backup for creating a standby database.If i take user managed hot backup and copy it to the stadnby server,wouldn't upon redo apply it would be synchronised and become consistent ?Hi,
Yes you can use hot backup to create standby database?
Let me know the problem you are facing while creating standby database from hot backup.
Regards
Anurag

Similar Messages

Steps to create the standby with Hot Backup........?????

Hi All
I am planning to create the Physical standby with Hot backup ....
Can anyboby give me the link/steps which explains how to do this?
Thanks
Gagan

To copy the file from the primary, you can use RMAN, or manual hot backup copy with begin backup and end backup mode.
You can read the doc about creation of standby database :
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i70835
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1032302
Nicolas.

Using Data Guard and hot backups - 9.2.0.6.0

Hi all,
I have an existing 9.2.0.6.0 database that is setup in a DataGuard environment - one primary database with a physical standby in a separate datacenter. It is all setup and it works beautifully. On our primary database, we currently have 2 different types of backups we are doing - we do an export of the main schema (all of the application data is all in this one schema) 4 times a day, and we do a full database hot backup once a night.
My question is in regards to the hot backup - I don't know that it is even worth doing a hot backup of this database? I am trying to think of a situation where we would actually want to restore a hot backup of the primary database... If we ran into some kind of a data issue, it would probably be quickest and easiest to restore data from one of the exports, and when we did that restore (import), I assume that data change would be replicated through DataGuard to the standby site. But if there was some kind of situation where we wanted to restore a recent hot backup of the primary database, that would essentially break the Data Guard configuration, and I assume that after the hot backup was restored, we would have to somehow re-instantiate Data Guard on the standby site.
Does anyone have any input on this? If you are running with DataGuard, is it even worth it to be doing hot backups? What kind of situation would call for restoring a hot backup, instead of just failing over to the standby?
Thanks!
--Brad

If we ran into some kind of a data issue, it would probably be quickest and easiest to restore data from one of the exportsIt would be quickest to failover to stand by database than restroing from dump file. After all you maintaing stand by db for that reason.
How can you restore database up to the latest changes using export/import ? You may have to restore using rman and apply the logs.
You can backup from stand by database. You do not need to back up primary.

Restoring Logical standby rman backup on production

Hi ,
I have One Production and one logical standby database .
Due to tape problem we are unable to take backups of promary . And due to businness , we cannot take back up on disk in hot period(Bank database ) .
Can anyone tell me , if i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? .
Logical standby is in sync with primary .

user12045405 wrote:
Can anyone tell me , if i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? .
No. http://docs.oracle.com/cd/E11882_01/server.112/e25608/rman.htm#SBYDB4848 says:
>
Note:
Backups of logical standby databases are not usable at the primary database.

Dataguard setup using hot backup files

Hello,
I am planning to setup dataguard using Hot backup (Not RMAN) files from the primary instance. I have a few doubt as, How shall I recover the Standby database using the archive files generated while taking hot backup of primary? Shall I directly execute the "alter database recover managed standby database" command? Will this command take care of the archives generated durring hot backup also?
Appreciate any help on the above.
DB Version:10.2.0.4
Regards.

Guys by using below procedure you can rebuild your data gurad by using manual hot backup.
1) On the primary database, defer the archival of redo data .
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER;
2)
put primary database in backup mode
copy all the datafiles from primary database to Standby database (you can copy to other location in primary server and tar&zip it and send it to stand by and unzip and untar there)
Once you copy the datafiles to another location on primary server,you can use below command for tar and zip
go to the copied datafiles location and issue below command
tar cvf - .|gzip -c > /dump/backup/drdb_backup.tar.gz
put primary database in end backup.
3) create stabdby controlfile by using below command and send it to standby server
alter database create standby controlfile as '/dump/drbackup/2standby.ctl'
4) copy all generated archive logs (from the time of database begin abckup) from primary database server to standby database log_archive_dest location.
5) on standby database once we placed all datafiles and controlfiles in place use below commands
export ORACLE_SID=standbydb
SQL> starup nomount;
SQL> alter database mount standby database;
SQL> recover standby database;
--AUTO
SQL> alter database open read only;
SQL> shut immediate
SQL> startup nomount;
SQL> alter database mount standby database;
SQL> alter database open read only;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
6) On the primary database, issue the following statement to reenable archiving to the physical standby database:
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
Thanks & Regards,
Satish Kumar Sadhu.
Edited by: Satish Kumar Sadhu on Apr 10, 2013 11:05 PM

Oracle Hot Backup Script Windows Server 2003

Hello,
Does anyone here have a working Oracle 10I database hot backup script for Windows Server 2003? If so can you please post it here.
Thanks.

Here is a basic batch script I have used for a hot backup of Oracle databases using RMAN
Will just need to update some locations based on you environment just check all the comments and change what you need to but this can be scheduled to run regularly through the windows scheduler for database backups.
This will take a hot backup and backup the archive logs.
Let me know if you have any quesitons.
REM #####################################################################
REM # Name: rman_hot_backup_dsk.bat
REM #
REM # Description:
REM #
REM # Generic Hot backup script that accepts the SID
REM #
REM # Parameters: Instance Name, backup level
REM #
REM #####################################################################
REM #
REM # Check if SID was Passed
if (%1)==() goto USAGE
if (%2)==() goto USAGE
REM # assign ORACLE_SID to passed SID
set ORACLE_SID=%1
REM # Set the hot backup level 0-full 1-incremental
set LEVEL=%2
REM # export the page list
set [email protected]
REM # assign a date we can use as part of the logfile
set DTE=%date:~-4%%date:~4,2%%date:~7,2%_%time:~0,2%%time:~3,2%%time:~6,2%
REM # Take the spaces out of the date string so we can use in our file name
set DTE=%DTE: =%
REM # set the script location
REM # Set location of where you will put script
set SCRIPTLOC=C:\app\oracle\scripts
cd %SCRIPTLOC%
REM # Set the Temporary command file that we will write our rman script to
set CMDFILE=%SCRIPTLOC%\%ORACLE_SID%_rman_hot_backup_dsk.cmd
REM # Remove the temporary file if it exists
del /q %CMDFILE%
REM # Set the logfile directory
REM # Change based on where you want the backup logs to go
set LOGPATH=W:\ORACLE_BACKUP\logs
set LOGFILE=%ORACLE_SID%_rman_hot_backup_dsk_%DTE%.log
set LOG=%LOGPATH%\%LOGFILE%
REM # Set the path of the backup location
REM # Change based on disk pach for you disk based backups
set BACKLOC=\\VirtualBox\ORA_ITS03P\ORACLE_BACKUP\%ORACLE_SID%
REM # Lets set the ORACLE_HOME for the host
REM # Set to your actual ORACLE_HOME location
set ORACLE_HOME=C:\app\oracle\product\10.2.0\db_1
# Set the rest of the Oracle Environment
# based on our ORACLE_HOME
set LIBPATH=%ORACLE_HOME%/lib
set LD_LIBRARY_PATH=%ORACLE_HOME%/lib
set TNS_ADMIN=%ORACLE_HOME%/network/admin
REM #set ORA_NLS10=%ORACLE_HOME%/nls/data
REM Set our PATH with the ORACLE_HOME so that we have a good
REM clean environment to work with
set PATH=%ORACLE_HOME%/bin;%ORACLE_HOME%/OPatch;%PATH%
REM # Write Temporary command file for RMAN backup
echo # configure retention policy >> %CMDFILE%
echo CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # lets start clean for our hot backup by doing full crosschecks >> %CMDFILE%
echo change archivelog all crosscheck ; >> %CMDFILE%
echo crosscheck backup of database; >> %CMDFILE%
echo crosscheck backup of controlfile; >> %CMDFILE%
echo # >> %CMDFILE%
echo # delete all expired and obsolete backups >> %CMDFILE%
echo allocate channel for maintenance type disk ; >> %CMDFILE%
echo delete noprompt expired archivelog all ; >> %CMDFILE%
echo delete noprompt expired backup ; >> %CMDFILE%
echo delete noprompt obsolete ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Configure control file for auto backup >> %CMDFILE%
echo configure controlfile autobackup on ; >> %CMDFILE%
echo CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%BACKLOC%\%ORACLE_SID%_controlfile_%%F' ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Configure default device type here we use disk and set parallelism to 2 >> %CMDFILE%
echo configure default device type to disk ; >> %CMDFILE%
echo configure device type disk parallelism 2 ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Must format the default channel for the device type disk >> %CMDFILE%
echo # other wise tmp area in creating pieces will be done in >> %CMDFILE%
echo # the $ORACLE_HOME/dbs directory >> %CMDFILE%
echo CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT = '%BACKLOC%\%ORACLE_SID%_hot_%%U' ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Configure our retention policy for this database >> %CMDFILE%
echo configure retention policy to recovery window of 14 days ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Let configure our channels for our backup >> %CMDFILE%
echo # Channel 1 disk and we indicate where it goes not taking the default >> %CMDFILE%
echo configure channel 1 device type disk MAXPIECESIZE = 4G format '%BACKLOC%\%ORACLE_SID%_hot_%%U' ; >> %CMDFILE%
echo # Channel 2 disk and we indicate where it goes not taking the default >> %CMDFILE%
echo configure channel 2 device type disk MAXPIECESIZE = 4G format '%BACKLOC%\%ORACLE_SID%_hot_%%U' ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Backup our database with compression on >> %CMDFILE%
echo backup as compressed backupset incremental level %LEVEL% tag hot_%LEVEL%_%DTE% DATABASE ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Backup our archive log files that have not been backed up >> %CMDFILE%
echo backup as compressed backupset format '%BACKLOC%\%ORACLE_SID%_Archive_%%d_%%s_%%p_%%t' archivelog all not backed up 1 times ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # Backup Control file for standby in case needed >> %CMDFILE%
echo backup current controlfile for standby ; >> %CMDFILE%
echo # >> %CMDFILE%
echo # let put a controlfile to trace >> %CMDFILE%
echo sql 'ALTER DATABASE BACKUP CONTROLFILE TO TRACE' ; >> %CMDFILE%
REM # Run the RMAN backup without using the recovery catalog
%ORACLE_HOME%\bin\rman target=/ nocatalog cmdfile=%CMDFILE% msglog=%LOG%
REM # Remove our temporary command file
del /q %CMDFILE%
REM # Mail Archive backup log
REM # This relies on the free bmail utility
bmail -date -m %LOG% -f [email protected] -s <smtpserver> -t %PAGE_LIST% -a "HOT Backup results"
REM # Goto end of script as we are done
goto END
:USAGE
echo "Must Pass ORACLE_SID and hot backup level as parameters."
goto END
:END

Frequency of Hot backups using RMAN

Hello.
After years of running various inhouse utilities to backup our Oracle databases we are now going to implement RMAN in our shop. We are running Oracle 10.2.0.4 EE databases on Solaris servers in Archivelog mode, so we'd like to perform "hot" backups. A caveat to this is that we also have "standby" databases that we manually manage via a series of scripts that works rather well and helps our CIO sleep at night.
So what we're trying to do is tackle one obstacle at a time. We'd like to implement RMAN hot backups (including archivelogs) without having RMAN remove the archivelog backups that are out there. We simply want RMAN to backup the archivelog files, we'll manage their movement and removal ourselves for the time being.
The script I have put together simply issues: Backup database plus archivelog format='/dumps/rman/F_Database_%d_set%s_%T_%U';
The configuration settngs (we want at least a 2 day recovery period) are:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/dumps/rman/controlfiles/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/dumps/rman/W_Database_%d_set%s_%T_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/xora01/app/oracle/product/10g/dbs/snapcf_glprd.f'; # default
We are using an RMAN catalog.
So my question is, if I perform the backup of the database (using the above command) once or twice a week and back-up only the archivelogs on a daily basis, would I be covered and save space at the same time? I think this might cover me as far as the archivelogs are concerned as well until my management is more comfortable with RMAN and allows us to install/use Data Guard.
Thanks for you opinions/suggestions...

Hi,
So my question is, if I perform the backup of the database (using the above command) once or twice a week and back-up only the archivelogs on a daily basis, would I be covered and save space at the same time? I think this might cover me as far as the archivelogs are concerned as well until my management is more comfortable with RMAN and allows us to install/use Data Guard.Your idea also not bad to save disk space. it is also depends on database size and space availability on your server.
or else you can go for weekly once fulll backup, remaining days incremental backups & archivelog backups.
rman incremental backups take only chanegd blocks so it wont occupy much space
1) sunday - full backup - level 0
2) monday - inc1 & arch
3) tuesday - inc2 & arch
4) wednesday - inc1 & arch
5) thursday - inc2 & arch
6) friday - inc1 & arch
7) saturday - inc2 & arch... & so on...
Thanks

How to take a Hot backup of Oracle database

1: put the db in archive log mode
2: set the db_sid to correct one
3: login to sqlplus
4: verify the name of the db that you are connected to
select name from v$database;
5: check if the db is in archive log made
select log_mode from v$database;
if not in archive log mode
another command to check
archive log list;
6: find where on disk oracle writes archive log when it is in archive log mode
sql> show parameter log_archive_dest_1;
if the value is found to be 0, that means no values will be recorded, so we need to change it
sql> alter system set log_archive_dest_1='LOCATION=c:\database\oradata\finance\archived_logs\'
scope=spfile;
7: shutdown immediate; < this is done just to prepare the db for hot backups >
8: startup the db in mount mode
startup mount;
( 3 startup types : nomount - just starts the instance, mount - locates the control files and open up according to the values, open - finds the datafiles from the control files and opens up the db )
9: put the db in archive log mode
alter database archivelog;
10: open the database
alter database open;
11: check the status of the db
select log_mode from v$database;
SQL> archive log list;
12: create a directory for archived log
check if its empty, if empty we need to switch
sql> alter system archive log current;
run it 5 times < need to put / and enter > , then check the archive log dir , we will find files
13: make a table in the database and insert data in it
create table employees (fname varchar(2));
check the table
desc employees;
insert values
insert into employees values ('Mica');
14: tablespace must be in hot backup mode
check the status
select * from v$backup;
if found not active, then we need to change
we cannot put the db in hot backup mode, unless it is archive log mode
change to hot backup mode
alter database begin backup;
check the status
select * from v$backup;
15: now we can only COPY DBF FILES
copy *dbf <distination location>
16: need to take the db out to hot backup mode
alter database end backup;
17: need to make another archive log switch
alter system archive log current;
18: need to copy control files now, need to do a binary bckup
alter database backup controlfile to '<location>\controlbackup';
19: insert more values to the table
insert into employess values ('NASH')
COMMIT;
make another archive log switch : alter system archive log current;
do the same process for more values
20 : backup all the archive logs to a new location
21: shutdown the db and simulate a hw error, delete all the files from the database folder
22: try to start the sqlplus and db ::: error
23: copy all the backups to the db dir
need to copy the control files, rename the binary backup of the control file and make the copies as needed
24: try to mount the db, error < must use reset logs or noreset logs >
25: need to do a recovering of the database
shutdown
restore the archive logs
startup mount;
recover database until cancel using backup controlfile;
it will ask for a log file :
yes for recovery
cancel for cancelling recovery
26: check status: open the database in readonly
alter database open read only;
check the tables to see the data
shutdown immediate
shartup mount;
recover again : recover database until cancel using backup controlfile;
if oracle is asking for a log that do nto exist , all we have to do is type cancel
27: open the database
alter database open;
need to do reset logs
alter database open resetlogs;
28: check the db that you are connected, check the tables
thanks and regards
VKN
site admin
http://www.nitrofuture.com

A very long list ... let me make it shorter.
SQL> archive log list;If I see this:
Database log mode No Archive ModeI put the database into archivelog mode and leave it there forever.
If it is in archivelog mode:
RMAN> TARGET SYS/<password>@<service_name> NOCATALOG
RMAN> BACKUP DATABASE PLUS ARCHIVELOG;Though there are a lot of things one could do better such as incrementals with block change tracking, creating an RMAN catalog, etc.

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.

How to find out which archived logs needed to recover a hot backup?

I'm using Oracle 11gR2 (11.2.0.1.0).
I have backed up a database when it is online using the following backup script through RMAN
connect target /
run {
allocate channel d1 type disk;
backup
incremental level=0 cumulative
filesperset 4
format '/san/u01/app/backup/DB_%d_%T_%u_%c.rman'
database
}The backup set contains the backup of datafiles and control file. I have copied all the backup pieces to another server where I will restore/recover the database but I don't know which archived logs are needed in order to restore/recover the database to a consistent state.
I have not deleted any archived log.
How can I find out which archived logs are needed to recover the hot backup to a consistent state? Can this be done by querying V$BACKUP_DATAFILE and V$ARCHIVED_LOG? If yes, which columns should I query?
Thanks for any help.

A few ways :
1a. Get the timestamps when the BACKUP ... DATABASE began and ended.
1b. Review the alert.log of the database that was backed up.
1c. From the alert.log identify the first Archivelog that was generated after the begin of the BACKUP ... DATABASE and the first Archivelog that was generated after the end of the BACKUP .. DATABASE.
1d. These (from 1c) are the minimal Archivelogs that you need to RECOVER with. You can choose to apply additional Archivelogs that were generated at the source database to contininue to "roll-forward"
2a. Do a RESTORE DATABASE alone.
2b. Query V$DATAFILE on the restored database for the lowest CHECKPOINT_CHANGE# and CHECKPOINT_TIME. Also query for the highest CHECKPOINT_CHANGE# and CHECKPOINT_TIME.
2c. Go back to the source database and query V$ARCHIVED_LOG (FIRST_CHANGE#) to identify the first Archivelog that has a higher SCN (FIRST_CHANGE#) than the lowest CHECKPOINT_CHANGE# from 2b above. Also query for the first Archivelog that has a higher SCN (FIRST_CHANGE#) than the highest CHECKPOINT_CHANGE# from 2b above.
2d. These (from 2c) are the minimal Archivelogs that you need to RECOVER with.
(why do you need to query V$ARCHIVED_LOG at the source ? If RESTORE a controlfile backup that was generated after the first Archivelog switch after the end of the BACKUP ... DATABASE, you would be able to query V$ARCHIVED_LOG at the restored database as well. That is why it is important to force an archivelog (log switch) after a BACKUP ... DATABASE and then backup the controlfile after this -- i.e. last. That way, the controlfile that you have restored to the new server has all the information needed).
3. RESTORE DATABASE PREVIEW in RMAN if you have the archivelogs and subsequent controlfile in the backup itself !
Hemant K Chitale

Question on recovery from Hot backup

Whenever I tried to recover from my hot backup using recover database untill cancel (or any other until option)..
I get messages similar to the following :
SQL> recover database using backup controlfile until cancel ;
ORA-00279: change 212733060 generated at 11/18/2008 23:50:58 needed for thread
1
ORA-00289: suggestion : /d01/oradata/devl/arc/1_282_667362770.dbf
ORA-00280: change 212733060 for thread 1 is in sequence #282
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/1_282_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/2_257_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/d01/oradata/devl/arc/3_258_667362770.dbf
ORA-00279: change 212733060 generated at needed for thread 4
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
I have all my archive files in the archive dest location.
Is there any way to prevent this warning messages and let oracle find all the archive files?
As you can see from the messages, Oracle is finding the correct file, then why there is an error message and why we have to provide the file names one-by one.
Please help !!!

Oracle will look for needed archive logfile from your log archive destination.
If you are sure all these files are under /d01/oradata/devl/arc/, you can input AUTO, Oracle will work down the list until done.

Complete Recovery from HOT BACKUP

One of our server had media failuer. We are rebuilding new server and reinstalling oracle on it. I have hot backup of instance which I would like to recover.
Can I have steps please. I will appreciate your help...!

Hi,
What is the OS and version of Oracle?
Do you have all the archivelogs after the hot backup? Is the backup a valid backup? Is it a RMAN backup or normal file system backup of the datafiles?
Regards,
Badri.

Recovery from hot backup

I have a problem with recovery hot backup from production database to test database and open it to use.
I have 'hot backup' without temporary tablespace and roll tablespace, I cant shut down production database (24x7), please give me a regulations how to recover database from hot backup, without online redo logs, temp tablespace, roll tablespace only with archive logs, and.....after this ..rename database sid.
Every time when I recovered database, it's still want to recover...and recover from archive logs and I cant open it, it's still inconsistent.Please send me an answer for [email protected]
thanks!

Hi,
What is the OS and version of Oracle?
Do you have all the archivelogs after the hot backup? Is the backup a valid backup? Is it a RMAN backup or normal file system backup of the datafiles?
Regards,
Badri.

Consistent hot backup possible

Is a consistent hot backup possible?
I would like to perform hot backups while the database is in basically a read only state. I am currently using Oracle recommended backups via OEM, for example.
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
release channel oem_disk_backup;
allocate channel oem_sbt_backup1 type 'SBT_TAPE' format '%U';
backup recovery area;
Would executing the sql command "alter database begin backup;" before running the above RMAN script accomplish this task? Then off course when completed execute sql "alter database end backup;".
My basic concern is this type of RMAN hot backup usable in a disaster situation, i.e recreated on another server from tape backup.
I am open to any other ideas.
Thanks for your help in advance.
Ed - Wasilla, Alaska
Edited by: evankrevelen on Sep 11, 2008 10:18 PM

Thanks everyone who replied to this thread.
Just to clarify my complete backup strategy, there are two RMAN scripts run on daily and weekly basis. The daily does pickup the archivelogs. I had shown the weekly when first opening this thread. Here is the daily.
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
release channel oem_disk_backup;
allocate channel oem_sbt_backup1 type 'SBT_TAPE' format '%U';
backup archivelog all not backed up;
backup backupset all not backed up since time 'SYSDATE-1';
My question now is what RMAN does in the increments. It appears to be updating the original level 0 copies of datafiles with changed blocks only. Is the new copy of the datafile now a level 0 type file?
Here is a transcript from one of the daily backups.
Starting recover at 11-SEP-08
channel oem_disk_backup: starting incremental datafile backupset restore
channel oem_disk_backup: specifying datafile copies to recover
recovering datafile copy fno=00001 name=+DEVRVYG1/landesk/datafile/system.2576.616107783
recovering datafile copy fno=00002 name=+DEVRVYG1/landesk/datafile/undotbs1.2574.616107865
recovering datafile copy fno=00003 name=+DEVRVYG1/landesk/datafile/sysaux.2575.616107829
recovering datafile copy fno=00004 name=+DEVRVYG1/landesk/datafile/users.2572.616107871
recovering datafile copy fno=00005 name=+DEVRVYG1/landesk/datafile/landesk.2914.616107643
channel oem_disk_backup: reading from backup piece +DEVRVYG1/landesk/backupset/2008_09_10/nnndn1_tag20080910t220150_0.12330.665100189
channel oem_disk_backup: restored backup piece 1
piece handle=+DEVRVYG1/landesk/backupset/2008_09_10/nnndn1_tag20080910t220150_0.12330.665100189 tag=TAG20080910T220150
channel oem_disk_backup: restore complete, elapsed time: 00:05:16
Finished recover at 11-SEP-08
Starting backup at 11-SEP-08
channel oem_disk_backup: starting incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
input datafile fno=00005 name=+DEVG1/landesk/datafile/landesk.374.614072207
input datafile fno=00003 name=+DEVG1/landesk/datafile/sysaux.384.614002027
input datafile fno=00001 name=+DEVG1/landesk/datafile/system.383.614002025
input datafile fno=00002 name=+DEVG1/landesk/datafile/undotbs1.385.614002027
input datafile fno=00004 name=+DEVG1/landesk/datafile/users.386.614002027
channel oem_disk_backup: starting piece 1 at 11-SEP-08
channel oem_disk_backup: finished piece 1 at 11-SEP-08
piece handle=+DEVRVYG1/landesk/backupset/2008_09_11/nnndn1_tag20080911t220708_0.12999.665186835 tag=TAG20080911T220708 comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:02:26
channel oem_disk_backup: starting incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel oem_disk_backup: starting piece 1 at 11-SEP-08
channel oem_disk_backup: finished piece 1 at 11-SEP-08
piece handle=+DEVRVYG1/landesk/backupset/2008_09_11/ncsnn1_tag20080911t220708_0.2301.665186983 tag=TAG20080911T220708 comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:00:21
Finished backup at 11-SEP-08
It appears to be updating the previous copy with updated blocks thus rolling forward the datafile copy to a new level 0 copy.
Then to restore from the backup RMAN would first use this new copy of the datafile and then apply any archivelogs to them to bring the database to the point in time the incremental backup was taken.
Are these assumptions true?
Thanks for your help,
ED

When to use REUSE/SET, NO-ARCHIVELOGS in create controlfile in HOT BACKUP?

I am a trainee Oracle DBA and have the following queries. Kindly reply with detailed explanation as I want to get my concepts cleared!
Q1>> While doing a user managed hot backup, when we are creating a control file(CREATE CONTROLFILE) from trace for recovery when do we use the create control file with the following options:
*1. REUSE / SET*
*2. ARCHIVELOGS / NOARCHIVELOGS*
Q2>> In what scenarios do we re-create the control file while recovering datafiles from a hot backup??
Thanks a tonne!
Regards,
Bhavi

Hemant K Chitale wrote:
1.1 It is not "REUSE/SET". These are two very different clauses.
REUSE is when you want the CREATE to overwrite the existing controlfile(s). If the controlfile(s) {as named in the instance parameter file, initSID.ora or spfileSID.ora} is/are already present, the CREATE fails unless REUSE is specified.
SET is when you want to change the database name. Oracle then creates the controlfile(s) with the specified database name and updates the headers of all the datafiles. If you run a CREATE with a database name that is different from that in the datafile headers, the CREATE fails unless you include a SET to specify that the name must be changed. Note that this also means that the name in the instance parameter file must already have been updated.
1.2 ARCHIVELOG/NOARCHIVELOG is to set the database state. The same is achieved by issuing an "ALTER DATABASE ARCHIVELOG/NOARCHIVELOG" when the database is MOUNTed but not OPEN.
2. You'd run the CREATE CONTROLFILE if you do not have a binary backup of the controlfile.
Optionally, you can also use CREATE CONTROLFILE to rename all the datafiles by specifying the new locations of the datafiles -- the datafiles must already be present in the new locations, else the CREATE fails if it doesn't find a datafile that is included in the list of datafiles included in the CREATE statement.
RMAN is the correct way to run Backups. User Managed Backup scripts are used in cases like Storage-based Snapshots / SnapClones / BCV.
Hemant K ChitaleThanks that was really helpful..One last question when to use the resetlogs/noresetlogs clause in the create controlfile statement. I have noticed that at times it accepts resetlog while at times it accepts noresetlogs

Standby hot backup

Similar Messages

Maybe you are looking for