Regarding RMAN backup and recovery using archivelogs during cloning process

Hi there,
We are running 9i database (RAC) in archivelog mode.We are in the process of cloning DEVELOPMENT database using our PRODUCTION database.
For this we planned to take RMAN backup by keeping the production database in MOUNT stage.
In this regard, will it be possible to make use of archivelogs generated during and after this backup (in mount stage), after some days during recovery time, if it asks for recovery after cloning process.
Thanks,
Balu.

Hi Alok,
why there is a need for standby here? you mean to say standby db?
what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

Similar Messages

BACKUP AND RECOVERY USING RMAN

제품 : ORACLE SERVER
작성날짜 : 2003-08-04
BACKUP AND RECOVERY USING RMAN
==============================
1. Backup Method
1.1 backing up in noarchivelog mode
SVRMGR> shutdown;
SVRMGR> startup mount
rman을 가동시킨 후 다음을 수행
run {
# backup the database to disk
allocate channel dev1 type disk;
backup (database format '/oracle/backups/bp_%s_%p'); }
1.2 Backing up databases and tablespaces in archivelog mode >
- database 단위 backup script
run {
allocate channel dev1 type 'sbt_tape';
backup skip offline (database format '/oracle/backups/%d_%u');
release channel dev1;
- tablespace 단위 backup script
run {
allocate channel dev1 type disk;
backup
(tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
format '/oracle/backups/bp_%s_%p');
- datafile 단위 backup script
run {
allocate channel dev1 type disk;
backup
(datafile '?/dbs/t_dbs1.f'
format '/oracle/backups/%d_%u');
- control file backup script
control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
같은 방법으로도 백업받을 수 있다.
run {
allocate channel dev1 type 'sbt_tape';
backup
(tablespace tbs_5 include current controlfile
format '%d_%u');
- archived logs backup script
NLS_LANG=american
NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
run {
allocate channel dev1 type 'sbt_tape';
backup
(archivelog from time 'Nov 13 1996 20:57:13'
until time 'Nov 13 1996 21:06:05'
all
format '%d_%u');
run {
allocate channel dev1 type 'sbt_tape';
backup
(archivelog low logseq 288 high logseq 301 thread 1
all delete input
format '%d_%u');
- copying datafiles
run {
allocate channel dev1 type disk;
copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
- incremental backups
새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
반드시 수행한다.
run {
allocate channel dev1 type 'sbt_tape';
backup incremental level 0
(database
format '%d_%u');
run {
allocate channel dev1 type 'sbt_tape';
backup incremental level 1
(database
format '&d_%u');
2. Recovery Method
- tablespace recovery
run {
allocate channel dev1 type disk;
allocate channel dev2 type 'sbt_tape';
sql "alter tablespace tbs_1 offline immediate" ;
set newname for datafile 'disk7/oracle/tbs11.f'
to 'disk9/oracle/tbs11.f' ;
restore (tablespace tbs_1) ;
switch datafile all ;
recover tablespace tbs_1 ;
sql "alter tablespace tbs_1 online" ;
release channel dev1;
release channel dev2;
- point-in-time recovery
TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
data는 없는 temporary segemnt만 가지고 있음.
NLS_LANG=american
NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
SVRMGR> shutdown abort;
SVRMGR> startup nomount;
run {
# recover database until 3pm after restoring tbs_1 to a new location
allocate channel dev1 type disk;
allocate channel dev2 type 'sbt_tape';
set until time 'Nov 15 1996 15:00:00'
set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
to '?/dbs/temp1.f' ;
set newname for datafile '?/dbs/tbs_12.f'
to '?/dbs/temp2.f' ;
restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
replicate controlfile from '/vobs/oracle/dbs/cf1.f';
sql "alter database mount" ;
restore database skip tablespace temp1;
switch datafile all;
recover database skip tablespace temp1;
sql "alter database open resetlogs";
sql "drop tablespace temp1";
sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
release channel dev1;
release channel dev2;
- 전체 데이타베이스를 복구하려 할때
current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
수 있다.
replace script restore_recover_db_cf {
execute script restore_cf;
sql 'alter database mount';
execute script restore_db;
execute script recover_db;
sql 'alter database open resetlogs';
replace script alloc_1_disk {
allocate channel d1 type disk;
setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
replace script rel_1_disk {
release channel d1;
replace script restore_cf {
execute script alloc_1_disk;
restore
controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
replicate
controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
execute script rel_1_disk;
replace script restore_db {
execute script alloc_1_disk;
restore
(database);
execute script rel_1_disk;
replace script recover_db {
execute script alloc_1_disk;
recover
database;
execute script rel_1_disk;
Reference Documents
<Note:104796.1>

Hi Alok,
why there is a need for standby here? you mean to say standby db?
what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

Logical backup and recovery using export/import

Hi,
Anyone provide me the clear steps and command to take logical backup and recovery using the import and export method...??.
im using oracle 9i database and redhat linux server version 4.0.........???.
thanks,
vasanth.......

user12864080 wrote:
Hi,
Anyone provide me the clear steps and command to take logical backup and recovery using the import and export method...??.
im using oracle 9i database and redhat linux server version 4.0.........???.
thanks,
vasanth.......Vasant,
Though you have got links already for using the exp/imp , I would strongly suggest that when you mention backup/recovery, RMAN is the tool that you should be using. Exp/imp is/was never considered as a backup tool. You should read this paper to get the answer of "why rman" ?
http://www.evdbt.com/TD_Rman.pdf
Aman....

Rman backup and recovery architecture question.

Hi
Oracle : 11.2.0.2.0
OS : Redhat Linux.
We currently have RMAN implemented with scirpts taking backups for each database.These run through cron jobs on nightly schedule.
I am tasked with the automation of the recovery process , that will happen maybe every quarterly to check if we can recover effetively from the backups.( don't ask why).
My questions are
1) Should I be using OEM to do RMAN recovery instead of my scripts. What are the cons of doing it this way.
2) I have around 20 databases. My thought is to seetup Grid Control, and effectively setup the backups there provided answer to question 1 is yes.
3) Is there a way to automate the recovery using Grid control.
4) Should I be doing it differently and if so what? What is the standard practice?
Thanks in advance for your help.

Hi,
My suggestion is scripting.
You can find some recovery methods.
http://taliphakanozturken.wordpress.com/2011/05/26/rman-data-recovery-methods/
Talip Hakan Ozturk
http://taliphakanozturken.wordpress.com/

How to make an encrypted compressed RMAN backup and recovery

Hallo!I am trying to make an RMAN backup that is compressed (definitely use compressed backup set in OEM).
But my emphasis is to make the backup encrypted with a key (hoping to use Public Key Infrastructure )such that the database data can be sent via the network and the recepient can use a decryption key to decrypt the data.
The recepient must also use a password to access the encrypted file for decryption.
Is it possible to do this?If so please give the steps.
Thanks.

You can encrypt the backupset with RMAN Encrypted Backups, however Oracle Advanced Security Option (additional cost) is required.

Rman backup and recovery

Hi Expert,
If I backup using rman for Oracle RAC database without backup archivelog . Can i perform recovery as the archivelog still on share disk . Tks
Regard
Liang

user13290160 wrote:
Hi Expert,
If I backup using rman for Oracle RAC database without backup archivelog . Can i perform recovery as the archivelog still on share disk . Tks
The answer would be yes but you must backup archivelogs as well. Think about the situation when your shared storage itself is completely gone taking down the archivelogs as well. Even you would have the backup of the database, it would be of no use since you won't have the archivelogs with you to recover it.
Aman....

RMAN backup and restore for Disaster Recovery

Hi Guys,
I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
Starting restore at 21-SEP-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
ystem01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
ysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
ndotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
sers01.dbf
channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
Finished restore at 21-SEP-11
Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/
whereas my latest backups are stored at a different location.
I am executing following steps at the RMAN prompt on hosta and hostb:
hosta (production site)
backup as compressed backupset database plus archivelog
backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
backup spfile
hostb (Disaster site)
set dbid=13732232063
startup force nomount
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
shutdown immediate
/* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
/* restart rman here */
quit
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
/* call the next two commands on run */
restore database;
recover database;
alter database open resetlogs
quit
Any help will be greatly appreciated.
Thanks,
Rajesh

Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
I take backup on Host A using:
rman target /
backup as compressed backupset database plus archivelog;
backup spfile;
quit;
I restore the backup on Host B using:
set dbid=13732232063;
startup force nomount;
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
shutdown immediate;
startup force nomount;
restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
quit;
/* restart rman here */
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset' noprompt;
restore database;
recover database;
alter database open resetlogs;
quit;
I take another backup on Host A using (notice no spfile backup this time):
backup as compressed backupset database plus archivelog;
quit;
I restore the database on Host B using:
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
recover database;
alter database open;
quit;
Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
RMAN> list backup of database;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
8T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
97 Full 259.16M DISK 00:00:00 28-SEP-11
BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
7
Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
TAG20110928T183527787lv0nb_.bkp
List of Datafiles in backup set 97
File LV Type Ckp SCN Ckp Time Name
1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
Output of list backup (done after restoring the control file)
RMAN> list backup;
BS Key Size Device Type Elapsed Time Completion Time
87 89.20M DISK 00:00:26 28-SEP-11
BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
List of Archived Logs in backup set 87
Thrd Seq Low SCN Low Time Next SCN Next Time
1 34 1302253 20-SEP-11 1306439 20-SEP-11
1 35 1306439 20-SEP-11 1307647 20-SEP-11
1 36 1307647 20-SEP-11 1307701 20-SEP-11
1 37 1307701 20-SEP-11 1311393 20-SEP-11
1 38 1311393 20-SEP-11 1311511 20-SEP-11
1 39 1311511 20-SEP-11 1332479 20-SEP-11
1 40 1332479 20-SEP-11 1344418 20-SEP-11
1 41 1344418 20-SEP-11 1350409 20-SEP-11
1 42 1350409 20-SEP-11 1350449 20-SEP-11
1 43 1350449 20-SEP-11 1350854 21-SEP-11
1 44 1350854 21-SEP-11 1350895 21-SEP-11
1 45 1350895 21-SEP-11 1353114 21-SEP-11
1 46 1353114 21-SEP-11 1353254 21-SEP-11
1 47 1353254 21-SEP-11 1353865 21-SEP-11
1 48 1353865 21-SEP-11 1353988 21-SEP-11
1 49 1353988 21-SEP-11 1375403 21-SEP-11
1 50 1375403 21-SEP-11 1376149 21-SEP-11
1 51 1376149 21-SEP-11 1376206 21-SEP-11
1 52 1376206 21-SEP-11 1376246 21-SEP-11
1 53 1376246 21-SEP-11 1379990 21-SEP-11
1 54 1379990 21-SEP-11 1380229 21-SEP-11
1 55 1380229 21-SEP-11 1380266 21-SEP-11
1 56 1380266 21-SEP-11 1380528 21-SEP-11
1 57 1380528 21-SEP-11 1380724 21-SEP-11
1 58 1380724 21-SEP-11 1380861 21-SEP-11
1 59 1380861 21-SEP-11 1381033 21-SEP-11
1 60 1381033 21-SEP-11 1381077 21-SEP-11
1 61 1381077 21-SEP-11 1402243 22-SEP-11
1 62 1402243 22-SEP-11 1423341 22-SEP-11
1 63 1423341 22-SEP-11 1435456 22-SEP-11
1 64 1435456 22-SEP-11 1454415 23-SEP-11
1 65 1454415 23-SEP-11 1490903 23-SEP-11
1 66 1490903 23-SEP-11 1491266 23-SEP-11
1 67 1491266 23-SEP-11 1491347 23-SEP-11
1 68 1491347 23-SEP-11 1492761 23-SEP-11
1 69 1492761 23-SEP-11 1492891 23-SEP-11
1 70 1492891 23-SEP-11 1493678 23-SEP-11
1 71 1493678 23-SEP-11 1493704 23-SEP-11
1 72 1493704 23-SEP-11 1494741 23-SEP-11
1 73 1494741 23-SEP-11 1494790 23-SEP-11
1 74 1494790 23-SEP-11 1510154 23-SEP-11
1 75 1510154 23-SEP-11 1514286 23-SEP-11
1 76 1514286 23-SEP-11 1531967 24-SEP-11
1 77 1531967 24-SEP-11 1543266 24-SEP-11
1 78 1543266 24-SEP-11 1558427 24-SEP-11
1 79 1558427 24-SEP-11 1566924 24-SEP-11
1 80 1566924 24-SEP-11 1578292 24-SEP-11
1 81 1578292 24-SEP-11 1596894 25-SEP-11
BS Key Size Device Type Elapsed Time Completion Time
88 84.03M DISK 00:00:30 28-SEP-11
BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
List of Archived Logs in backup set 88
Thrd Seq Low SCN Low Time Next SCN Next Time
1 82 1596894 25-SEP-11 1609028 25-SEP-11
1 83 1609028 25-SEP-11 1622303 25-SEP-11
1 84 1622303 25-SEP-11 1626430 25-SEP-11
1 85 1626430 25-SEP-11 1634486 25-SEP-11
1 86 1634486 25-SEP-11 1648398 25-SEP-11
1 87 1648398 25-SEP-11 1669259 26-SEP-11
1 88 1669259 26-SEP-11 1686820 26-SEP-11
1 89 1686820 26-SEP-11 1686959 26-SEP-11
1 90 1686959 26-SEP-11 1689168 26-SEP-11
1 91 1689168 26-SEP-11 1704759 26-SEP-11
1 92 1704759 26-SEP-11 1719597 27-SEP-11
1 93 1719597 27-SEP-11 1740407 27-SEP-11
1 94 1740407 27-SEP-11 1750125 27-SEP-11
1 95 1750125 27-SEP-11 1765592 27-SEP-11
1 96 1765592 27-SEP-11 1781498 28-SEP-11
1 97 1781498 28-SEP-11 1802311 28-SEP-11
1 98 1802311 28-SEP-11 1811009 28-SEP-11
1 99 1811009 28-SEP-11 1813811 28-SEP-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

Backup and recovery questions

Hi,
I am a newbie in Oracle database 11g Release 11.2.0.1.0 and Oracle Linux and I have questions regarding backup and recovery.
I used the “Schedule Oracle-Suggested Backup” and have it run nightly to back up to local disk. In the Backup Setting, on the Retention Policy, I selected “Retain backup that are necessary for a recovery to any time within the specified number of days (point-in-time recovery) day = 7”
With the setting above, I checked the “Manage Current Backups” and I have many back sets for SPfiles, controlfiles, datafiles, and archivelogs for the last several days. However, for image copies, I have only one set and it get over write nightly. With the configuration above, is that true that I can only recover to any point in last 24 hours?
My goal is to be able to recover any “point-in-time” in the past 5 days, should I change my Retention Policy to “Retain at least the specified number of full backups for each datafile” to 5 backups (each full daily backup)? Please provide some advices. Thanks

By looking the following, it looks like by default its 24 hours but it depends upon the recovery window you choose.
Enterprise Manager makes it easy to set up an Oracle-suggested backup strategy for backups to disk that protects your data and provides efficient recoverability to any point in the a recovery window of your choosing. (In the simplest case, examined in this section, this window is 24 hours.) The Oracle-suggested strategy leverages Oracle's incremental backup and incrementally-updated backup features to provide faster backups than whole database backups, and faster recoverability than is possible through applying database changes from the archived log to your datafiles.
The Oracle-suggested backup strategy is based on creating an image copy of your database. This copy is rolled forward by means of incrementally updated backups. Oracle Enterprise Manager schedules RMAN backups jobs for you to run during the overnight hours.
For each datafile, the strategy calls for backups as follows:
At the beginning of day 1 of the strategy (the time the first scheduled job actually runs), an incremental level 0 datafile copy backup. It contains the datafile's contents at the beginning of day 1. In a restore-and-recovery scenario, the redo logs from day 1 can be used to recover to any point during day 1.
At the beginning of day 2, an incremental level 1 backup is created, containing the blocks changed during day 1. In a restore-and-recovery scenario, this incremental level 1 can be applied to quickly roll forward the level 0 backup to the beginning of day 2, and redo logs can be used to recover to any point during day 2.
At the beginning of each day n for days 3 and onwards, the level 1 backup from the beginning of day n-1 is applied to the level 0 backup. This brings the datafile copy to its state at the beginning of day n-1. Then, a new level 1 is created, containing the blocks changed during day n-1. In a restore-and-recovery scenario, this incremental level 1 can be applied to the datafile rolled forward on day n-1 to the beginning of day n, and redo logs can be used to recover the database to any point during day n.
The datafile copies used in the Oracle-suggested backup strategy are tagged with the tag ORA$OEM_LEVEL_0. The level 1 incremental backups for use in this strategy are created for use with datafile copies that are so labelled. You can safely implement other backup strategies without concern for interference from the backups for the Oracle suggested strategy.
There are also Oracle-suggested strategies that use tape backups along with disk backups, but those are beyond the scope of this chapter.

Need clarification for cold backup and recovery

Hello Everyone ..
I have much confusion on cold backup and recovery topic.
Already i posted a scanario regarding this and i want to know some clarity points to understand.
1. I had cold backup two days before
2. I am creating an object *(EMP)* and inserting some records then issue log switch continiously.
3. Manually i removed all physical files (datafiles , control files , log files , redolog files ...)
4. then i issued STARTUP FORCE MOUNT;
5. here i am getting error identifying control file.
6. cold backup two days before all files restored
6. then i issue recover database using backup controlfile until cancel;
7. i am trying to issue select * from emp; i am getting error
select * from emp
*ERROR at line 1:
ORA-00942: table or view does not existMy QUESTION IS
After cold backup finished , i created emp table ..
when restoring old back " There is no emp table"
*- then , can i recover emp table ? - If so , please explain about this ..*
Note : REF - LINK https://forums.oracle.com/forums/message.jspa?messageID=11056341#11056341
- Above link says what i did ? . In this thread i am asking concept & logic ..
please do NOT consider as "*DUPLICATE*"

When you recover the database using backup controlfile until cancel, you have to apply archived logs. Did you apply all of them?
If the create command was in the online redo, not yet archived, and you lost the online redo, then you won't have it. This is why you want to have redo multiplexed, it is a critical piece.
In some recovery scenarios, if you haven't lost the online redo, you need to specify those files as if they were archives.
It is normally easier to just be sure you have the latest controlfiles and let Oracle figure it out automatically (which is why you want to use online RMAN backups rather than cold backups). But yes, it is important to understand what is going on for different scenarios. I used to have manual standbys, and one of the disaster instruction sets explained to try to get online redo over to the standby to lose as few transactions as possible. That could still be useful for some snapshot hardware type scenarios, assuming the business is too cheap to do proper failovers.

Which one is the Best Backup and Recovery Method in your point of view?

Friends,
Currently we are taking hot backup with archive mode.
we have backup script to copy the datafile and we will copy the archive files in a separate folder.
alter tablespace system begin backup;
host cp /u01/app/oracle/oradata/livedb/system.dbf /u02/online_backup
alter tablespace system end backup;
like the above script we will copy all the other data files.
then in the test environment. we will copy the datafile and archive file.
we will be recovering by using the below statement.
sql>recover database until cancel using backup controlfile.
currently no problem in backup and recovery.
What i want is......
is there any other sophisticated and safe way to take a backup and restore it to another server?
if yes, can anybody point out the steps or link.
I have heard about......
DataGuard
RMAN
EXP/IMP
but i never used the above.
Thanks
sathyguy

DataGuard
RMAN
EXP/IMP ...
The only real backup/recovery method here is RMAN, Oracle's integrated backup/recovery tool, which I prefer. As an example for a fully functional RMAN command see 'backup database plus archivelog delete all input'. This statement provides a complete hot database backup including archivelogs and deletes at the successful end all archivelogs in all destinations . Compare this statement with all the steps necessary to do the same job manually. Don't worry you have many ways to finetune your backup.
For more informations there's a quick start guide:
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14193/toc.htm
Dataguard is a high availibility tool, which provides a kind of backup in terms of having a logical or physical standby database. When primary side fails you can switch to this standby database. Such a constellation does not mean, database backups are no longer necessary.
Export/Import is a logical backup, still often used to recover from human errors (you accidentally dropped a table for example). Don't use it as a replacement for physical backups, especially hot backups,in case of media failures you always will have loss of data, because changes made afterwards the export are not captured.
Once again I recommend you seriously should consider RMAN.
Werner

RMAN backup and restore in network

Hi,
I have already did cold backup of database using RMAN in the same disk on a linux OS. It was successful.
Now i want to do the same backup in a different disk on a another system. Both the systems are in same network.
Please help me

You can name the NFS mount point anything meaningful.
In your RMAN Backup script, you would use the FORMAT clause to specify the location where the backups are to go to.
For example, if the filesystem from linux2 is NFS-mounted on linux as as /NFS_backup your RMAN command would be
BACKUP DATABASE FORMAT '/NFS_backup/%U';
BACKUP ARCHIVELOG ALL FORMAT '/NFS_backup%U' DELETE INPUT ;Look up the syntax of the formatSpec in the Backup and Recovery Reference for formats other than %U. %U generates a Unique File Name.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Error in Oracle Database Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-13

on page 88 of the "Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-13", the example 5-1 SHOW ALL Command is the same of the "Backup and Recovery User's Guide 11g Release 2 (11.2) E10642-06" on page 82 and that output is related to a Oracle Database 11g version (the 10g doesn't print the first line "RMAN configuration parameters for database with db_unique_name PROD1 are:").

My test cases here:
Database administrator workshop: Differences in default RMAN configuration settings between 12c and 11g
{code}[oracle@vsi08devpom ~]$ export ORACLE_SID=CDB001
[oracle@vsi08devpom admin]$ sqlplus system/oracle@CDB001
SQL*Plus: Release 12.1.0.1.0 Production on Thu Sep 26 09:10:50 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Last Successful login time: Tue Jul 16 2013 13:43:48 +02:00
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> show con_name
CON_NAME
CDB$ROOT
[oracle@vsi08devpom ~]$ rman target /
Recovery Manager: Release 12.1.0.1.0 - Production on Thu Sep 26 09:12:42 2013
Copyright (c) 1982, 2013, Oracle and/or its affiliates. All rights reserved.
connected to target database: CDB001 (DBID=4134963396)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name CDB001 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/app/oracle/product/12.1.0/db_1/dbs/snapcf_CDB001.f'; # default{code}
{code}
[oracle@localhost orcl]$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Sep 25 08:12:17 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1229390655)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/oracle/app/oracle/product/11.2.0/dbhome_2/dbs/snapcf_orcl.f'; # default
{code}

Need help on Oracle manual Backup and Recovery?

Dear Gurus,
I want to study Oracle manual Backup and Recovery(without RMAN) in detail.
Is there any book or site, which describes more scenarios and explanation on manual backup and Recovery(without RMAN)
Regards
Sanjeev

user12868781 wrote:
Dear Gurus,
I want to study Oracle manual Backup and Recovery(without RMAN) in detail.Why?
My car has a flat tire. The manufacturer packed a spare tire, jack, and lug wrench in the trunk of the car at no additional cost, and described the process in the owners manual. I want to replace the flat tire without using any method other than the one involving the use of the tools designed for and provided for the job.
Is there any book or site, which describes more scenarios and explanation on manual backup and Recovery(without RMAN)
Regards
Sanjeev

Backup and Recovery from Archive Log

Dear all,
I implemented hot backup with oracle9i and
Can anybody suggest me how to backup and recovery archive log ?
Thanks for advance.
Chara

assuming you are using RMAN for backup -
backup ( archivelog all );
backup ( archivelog all delete input ); - to delete from file system.
If you are not using RMAN but backup using a script which puts the tablespaces in hot backup mode then you just need to backup archive log directory.
The archive logs are required when you need to do a database recovery. You don't recover archive log files.
rgds

Backup and Recovery Plan

I know very little backup and recovery plan in oracle using RMAN or any agent.
Is this right way to summarize the backup and recovery plan for 24 X 7 system required to have 99.99% up time.
The backup and recovery strategy recommended below is based on the premise that database is set ‘ARCHIVE LOG’ mode.
The database files must be backed up using an RMAN backup (or tape agent i.e. Oracle Agent for Veritas) to allow for recovery of corrupted files or files on failed volumes. These archive logs and RMAN backups should be written to a directory on a separate volume from any other database files. It is not recommended to store RMAN backups in the Oracle Control files. The RMAN backups and archive logs and document images are then written to tape in accordance with the GFS backup strategy.
Any suggestions and inputs would be helpful
Thanks

It was a generic note for the productions databases, i.e. have db in archivelog mode, take backups through RMAN to TAPE or on disk which will be used in case of disaster or media recovery.
You need to decide what kind backup and recovery policy you need to have and where you are going to copy/place the backup.
Just keeping in mind the following:
1. How quickly the database can be recovered in case of disaster/media recovery.
2.Make sure no transaction are lot, in another way, recovery until point of time.
3. What kind of policy you need, incremental, cummulative or full backup.
Jaffar

Regarding RMAN backup and recovery using archivelogs during cloning process

Similar Messages

Maybe you are looking for