Rman controlfile autobackup

when we configure rman controlfiel autobackup on
then whenever any structural change is there , control file's backup is taken automatically...
but can you please tell me that after how much time this file is backed up and what are the parameters to change the time of backup...

920273 wrote:
when we configure rman controlfiel autobackup on
then whenever any structural change is there , control file's backup is taken automatically...
but can you please tell me that after how much time this file is backed up and what are the parameters to change the time of backup... I got to know from that from 11gR2 creation of automatic controlfile backup is deferred as compared to previous releases. This is to increase performance.
So from 11gR2 onwards whenever there are multiple structure changes only then (after few minutes) controlfie autoback will take place. Unless like in previous release you had every controlfile backup created after every DDL command. But in 11gR2 its not. MUltiple DDL are batched and only 1 confile backup is created after few minutes.
This is also possible then no information is written to alert.log for autoback file, but you have to check SID__m000_<OS_PID>.trc file after you made several structre changes to 11gR2 to make sure backup of confile took place
Further ->RMAN CONTROLFILE AUTOBACKUP NOT CREATED DURING DB STRUCTURE CHANGE [ID 1068182.1]

Similar Messages

RMAN controlfile autobackup to tape

Hi,
How can i configure controlfile autobackup to tape ,
we have tivoli DP for oracle.
I have configured as below, but still disk is getting allocated.
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
Thanks,
Kumar.

Hi,
Try with this
CONFIGURE DEFAULT DEVICE TYPE TO SBT;

RMAN-06497: controlfile is not current, controlfile autobackup skipped

Hi,
I am doing backup of the standby database. However I encountered error "RMAN-06497: WARNING: controlfile is not current, controlfile autobackup skipped"
Why is the control file not current and backup skipped? Please guide me.
Regards,
Eye GEe

Hi,
It is backed up.
>
SQL> select controlfile_type from v$database;
CONTROL
STANDBY
SQL> disc
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> exit
bash-3.00$ rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Aug 20 12:27:19 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: YHASHMI (DBID=1454390871, not open)
RMAN> backup datafile 1 tag "standby_dat1";
Starting backup at 20-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=152 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/u/oracle/oradata/dyhashmi/system01.dbf
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=/u1/flash_recovery_area/DYHASHMI/backupset/2010_08_20/o1_mf_nnndf_STANDBY_DAT1_66w9vbc5_.bkp tag=STANDBY_DAT1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
Finished backup at 20-AUG-10
Starting Control File and SPFILE Autobackup at 20-AUG-10
piece handle=/u1/flash_recovery_area/DYHASHMI/autobackup/2010_08_20/o1_mf_s_727448768_66w9w3qr_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 20-AUG-10
Did you check the standby alert log?

Meaning of 'controlfile autobackup on' in rman ?

Hello,
i wanted to ask whats the use of "controlfile autobackup on" when using rman. The reason why i'm asking is, because even i leave the default setting "off", during executing "backup database" rman writes on the screen that it's including the controlfile in the backup.
so whats the advantage of using the "autobackup on" setting ?
kind regards

One more cogent point for auto backup on will always get automized backup whenever you made any physical structural change in yours database ,whenver you make any physical structural changes in yours database it goes to be highlight in control file,auto backup on will take this new highlighted control file backup at the spot,needn't to take control file backup after any structural changes It will be backed up itself in yours FRA (Flash recovery area).
Khurram

What's the difference between "controlfile autobackup" and "snapshot contro

Hi All,
What's the difference between "controlfile autobackup" and "snapshot controlfile" in RMAN configure ? Both are controlfile backups, what the difference between the controlfiles they backup ? Why there are two of these options ?
thanks

RMAN creates a control file snapshot to perform catalog resync operations. Control file autobackup will automatically create a backup of the control file whenever there are database structure changes.

No controlfile autobackups in 10gR2. Bug?

I'm using 10.2.0.4 enterprise edition and have no flash recovery area set up. In rman I have controlfile autobackup = on but I am not getting any controlfile backups when I make structural changes to the database.
Here's a snipped version of my RMAN config.
<tt>
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
</tt>
Now I go to sqlplus to show that there is no FRA, and create a tablespace.
<tt>
SQL> show parameter recov
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
SQL> create tablespace dummy datafile '/export/home/oracle/dummy01.dbf' size 2m;
Tablespace created.
</tt>
Now I check the dbs directory for backup controlfiles. None are created
<tt>
$ pwd
/oracle2/app/oracle/product/10.2.0.4/dbs
$ ls -l c-*
c-*: No such file or directory
So what am I doing wrong? This works fine in 10.1 and 9.2. Did something change in 10.2? Do I have to create a flash recovery area for controlfile autobackups to work in 10.2?

Did you try to test it ?
[oracle@lx01 ~]$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Fri Mar 25 21:46:47 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: DB102 (DBID=831971560)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/tmp/%F';
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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/EE/dbs/snapcf_DB102.f'; # default
RMAN> exit
Recovery Manager complete.
[oracle@lx01 ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Mar 25 21:39:15 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> host ls -al /tmp
total 36
drwxrwxrwt 6 root   root     4096 Mar 25 21:41 .
drwxr-xr-x 30 root   root     4096 Mar 25 21:14 ..
drwxrwxrwt 2 root   root     4096 Mar 25 21:16 .font-unix
drwxrwxrwt 2 root   root     4096 Mar 25 21:14 .ICE-unix
drwx------ 2 root   root     4096 May 24 2010 keyring-RqLT3M
drwx------ 2 root   root     4096 Jan 20 2010 keyring-uxZ8jN
srwxr-xr-x 1 root   root        0 May 24 2010 mapping-root
-rw-r--r-- 1 oracle oinstall    0 Mar 7 10:10 tes
-rwsr-s--x 1 oracle oinstall    0 Mar 7 10:14 test
SQL> create tablespace test datafile '/tmp/test.dbf' size 10m;
Tablespace created.
SQL> host ls -al /tmp
total 17256
drwxrwxrwt 6 root   root         4096 Mar 25 21:45 .
drwxr-xr-x 30 root   root         4096 Mar 25 21:14 ..
-rw-r----- 1 oracle oinstall 7110656 Mar 25 21:45 c-831971560-20110325-02
drwxrwxrwt 2 root   root         4096 Mar 25 21:16 .font-unix
drwxrwxrwt 2 root   root         4096 Mar 25 21:14 .ICE-unix
drwx------ 2 root   root         4096 May 24 2010 keyring-RqLT3M
drwx------ 2 root   root         4096 Jan 20 2010 keyring-uxZ8jN
srwxr-xr-x 1 root   root            0 May 24 2010 mapping-root
-rw-r--r-- 1 oracle oinstall        0 Mar 7 10:10 tes
-rwsr-s--x 1 oracle oinstall        0 Mar 7 10:14 test
-rw-r----- 1 oracle oinstall 10493952 Mar 25 21:45 test.dbf
SQL>and in instance alert log you have:
[oracle@lx01 ~]$ tail -f /u01/app/oracle/admin/DB102/bdump/alert_DB102.log
Starting background process QMNC
Completed: alter database open
QMNC started with pid=18, OS id=6198
Fri Mar 25 21:45:29 2011
create tablespace test datafile '/tmp/test.dbf' size 10m
Fri Mar 25 21:45:30 2011
Starting control autobackup
Control autobackup written to DISK device
        handle '/tmp/c-831971560-20110325-02'
Completed: create tablespace test datafile '/tmp/test.dbf' size 10mEdited by: P. Forstmann on 25 mars 2011 21:49

Default device type configuration of controlfile autobackup ?

1. configure controlfile autobackup format for device type disk to 'E:\oracle\oradata\oid\bk\%F';
2. backup current controlfile;
rman first use default device type ORA_DISK_1 and backup the file at "E:\ORACLE\ORA92\DATABASE\0AEU5OQL_1_1" (windows 2000)
then backup file at "E:\ORACLE\ORADATA\OID\BK\C-804947643-20030807-00"
when i backup database , rman can backup the controlfile at "E:\ORACLE\ORADATA\OID\BK\"
when i backup controlfile manully , why rman first backup it at the default device ??
thanks:)

One more cogent point for auto backup on will always get automized backup whenever you made any physical structural change in yours database ,whenver you make any physical structural changes in yours database it goes to be highlight in control file,auto backup on will take this new highlighted control file backup at the spot,needn't to take control file backup after any structural changes It will be backed up itself in yours FRA (Flash recovery area).
Khurram

Turn CONTROLFILE AUTOBACKUP ON;

Hi everyone,
I turned cotrolfile autobackup on... but I cannot find any controlfile backup format like '%F.bck' in "/backup/db/backup/RMAN"?
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/db/backup/RMAN/%F.bck';
Please advice,
Amy

Have you run a BACKUP DATABASE since after setting the controlfile autobackup on ?
The autobackup is created when a database backup is executed or a change to the database physical structure is executed (eg additional of a tablespace and/or datafile).

Regarding Controlfile Autobackups

Hi Expert !!
From Oracle Documentation (Oracle Database Backup and Recovery Advanced Users's Guide 10g Release 2):
Page: 2-29
"By default, control file autobackups are turned off, and no control file autobackups are performed. If CONFIGURE CONTROLFILE AUTOBACKUP is ON, then RMAN
automatically backs up the control file and the current server parameter file (if used to start up the database) in one of two circumstances: when a successful backup must be recorded in the RMAN repository, and when a structural change to the database affects the contents of the control file which therefore must be backed up."
Page 2-30
"The control file is also automatically backed up after database structural changes such as adding a new tablespace, altering the state of a tablespace or datafile (for example, bringing it online), adding a new online redo log, renaming a file, adding a new redo thread, and so on. Losing this information would compromise your ability to recover the database. This backup is performed by the server process itself, rather than one of the RMAN channels. This type of autobackup, unlike autobackups that occur after a successful backup, is always created on disk."
I have configured my RMAN enviroment as below (truncated the output to only non-default values for clarity):
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u10/test%F';According to the documentation, when I create or drop a tablespace, server process should backup controlfile to "/u10" location but its not happening in my case. Neither a backup piece is created in $ORACLE_HOME/dbs location.
Could anybody tell me where am I making a mistake?
Thanks once again

Thanks for the reply.
This kind of autobackup is done successfully?No, I am not doing any RMAN backup. I am simply creating a new tablespace (from SQL*Plus), so the server process should automatically backup my controlfile.
Am I not correct?

Configure controlfile autobackup

Hi.
Trying to sort an RMAN issue for a local company and found that someone has set configure controlfile autobackup format for device type disk to 'D:\stupid_path\CF_%F' no kidding; no wonder these guys are having issues. How do I get it back to it's default value, or find out what the default value was.
Rob.
Edited by: Rob,B on Oct 14, 2011 2:21 PM
Edited by: Rob,B on Oct 14, 2011 2:29 PM

Sorted it
configure controlfile autobackup format for device type disk clear;
Now to have a quiet word in someone's ear before I chop his fingers off!
Rob.

Duplicating controlfile autobackup

hello
i can use following command in RMAN for duplicating backup set
BACKUP DEVICE TYPE DISK COPIES 2 DATAFILE 7 FORMAT '/tmp/%U','/oradata/%U'
but how i can duplicate controlfile autobackup?
thanks

Autobackup of controlfiles are never multiplexed.

CONTROLFILE AUTOBACKUP

Dear All,
Please comment the scenario below.
I have the following configuration:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'd:\oracke\backup\%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
Then I perform:
BACKUP DATABASE;
The automatic backup of the controlfile is created after creating the database backup. It's Ok!
BUT!!!
If I run command
REPORT OBSOLETE;
It shows me that recent autobackuo of the control file is obsolete!!! And corespondenly
DELETE OBSOLETE;
delets this controlfile autobackup. It seems wrong for me or I am missing something!
Since if configure autobackup controlfile is on, BACKUP DATABASE as default does not perform controlfile backup, then if I run DELETE OBSOLETE after perfoming fresh backup to purge unnecessary backups and to manage disk space and immeadiatly after this real controlfile crashes, I won't be able to recover.
Thank you in advance for any explanation why recent controlfile autobackup is reported is obsolete.
Regards

Dear Artem,
Well there surely seems to be a problem with Oracle 9i R2 and the Rention Policy based on Recovery WIndow. As far as 9i R1 was concerned I have never had this problem.
But now in 9i R2 just delete obsolete and COFIGURE the parameter again for Retention policy, it works fine as it should and does not mark the backup as obsolete!!!!!

RMAN: Controlfile not aware of last backupset.

Hello,
I have a question about RMAN 9i (9.2.0.7)
My rman script is the following:
run {
sql 'alter system switch logfile';
allocate channel local_xxx type disk format 'd:\oracle\orabackup\backup\xxx\b_%u_%s_p';
backup (database include current controlfile);
backup (archivelog all delete input);
I want to clone this backup on another system:
I start a non-mounted instance.
There i restore my control file:
restore controlfile to 'c:\oracle\oradata\xxx\control01.ctl' from 'D:\oracle\orabackup\backup\xxx\B_MUL03FR1_1758_P';
Then i mount my database and type 'list backupset'
The last backupset that is known is the previous backupset... (1757)
Why is the last backupset not known in this controlfile ? Is my syntax false?
Do i need to backup the controlfile explicitly after the backup database command ?

I'm afraid i need the catalog backuppiece command, which is only available in 10g.
The catalog command in 9i can only catalog controlfile, datafile and archivelog...
The 9i manual states
You cannot use CATALOG to perform the following operations:
Recatalog backup pieces or backup sets. If you run CHANGE ... UNCATALOG against an RMAN backup, then it is permanently unusable by RMAN.
For now i'm gonna change my script that my controlfile is backed up as the last item in a seperate backupset.
Edited by: michiel.stubbe on Dec 8, 2009 10:19 AM

RMAN 에서 controlfile 백업 받기

SQL 프롬프트가 아니 RMAN 프롬프트에서 특정 패스로
컨트롤 파일을 백업하려 합니다.
RMAN>sql 'alter database backup controlfile to '/oracle/ora.bak' reuse';
위와 같이 패스를 지정하면 에러가 납니다.
따옴표 때문인것 같은데.. 해결 방법 있을까요??
아니면 RMan 커맨드중에서
RMAN>backup current controlfile to '/oracle/ora.bak'
처럼.. 특정 패스로 컨트롤파일을 직접 떨구는 방법 없을까요?
PL/SQL 에러가 발생하는데... ' ' 따옴표 때문인 것 같기도 하고..
해결 방법 좀 일러주세요..
감사합니다.

SQL 프롬프트가 아니 RMAN 프롬프트에서 특정 패스로
컨트롤 파일을 백업하려 합니다.
RMAN>sql 'alter database backup controlfile to '/oracle/ora.bak' reuse';
위와 같이 패스를 지정하면 에러가 납니다.
따옴표 때문인것 같은데.. 해결 방법 있을까요??
아니면 RMan 커맨드중에서
RMAN>backup current controlfile to '/oracle/ora.bak'
처럼.. 특정 패스로 컨트롤파일을 직접 떨구는 방법 없을까요?
PL/SQL 에러가 발생하는데... ' ' 따옴표 때문인 것 같기도 하고..
해결 방법 좀 일러주세요..
감사합니다.

PERFORMING FULL RECOVERY WHEN THE RECOVERY CATALOG AND CONTROLFILE ARE LOST

제품 : RMAN
작성날짜 : 2002-05-30
PERFORMING FULL RECOVERY WHEN THE RECOVERY CATALOG AND CONTROLFILE ARE LOST
===========================================================================
PURPOSE
Recovery Catalog와 Controlfile이 손상되었을 때 Oracle9i의 new feature인
Controlfile Autobackup을 이용하여 full recovery를 수행하는 방법을 알아본다
EXPLANATION
Catalog와 Controlfile이 모두 손상되었을 경우 full recovery를 수행할 수 있도록
하기 위해 oracle9i부터 Controlfile Autobackup이라는 New feature를 제공한다.
이 Feature가 활성화되면 RMAN은 자동으로 특정 형식(specific format)으로
controlfile을 backup한다 나중에 RMAN은 Recovery catalog를 access하지 않고도
이 backup을 인식할 수 있다. 이 형식은 "%F"라는 variable을 포함하는데
이 variable은 중요한 정보인 DATABASE ID를 포함하고 있다.
이것은 다음과 같은 CONFIGURE 명령을 사용하여 Turn-on 될 수 있다.
RMAN> configure controlfile autobackup on;
활성화시킨 후에 controlfile autobackup의 format을 변경할 수 있다. 그러나
이것은 반드시 variable "%F"를 포함해야만 한다. 그렇지 않으면 다음과 같은 Error
를 만나게 된다.
RMAN> configure controlfile autobackup format for
2> device type disk to 'c:\backups\%U';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 01/31/2002 11:57:21
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06492: controlfile autobackup format "c:\backups\%U" must specify a "%F"
format specifier
%F 는 RMAN이 recovery catalog 없이 backup piece를 인식하도록 Key이다.
이 Feature가 활성화 된 후에 RMAN은 BACKUP 명령을 수행할 때마다 controlfile에
대해서 별도의 backup을 수행한다. 이전에는, controlfile 은 오직 system
tablespace가 backup되는 경우에만 자동으로 backup되었다.
Database Backup은 아래와 같은 log를 출력한다.
RMAN> backup database;
Starting backup at 31-JAN-02
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\ORADATA\PROD\SYSTEM01.DBF
input datafile fno=00002 name=C:\ORACLE\ORADATA\PROD\UNDOTBS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\PROD\EXAMPLE01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\PROD\INDX01.DBF
input datafile fno=00008 name=C:\ORACLE\ORADATA\PROD\USERS01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\PROD\CWMLITE01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\PROD\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\PROD\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 31-JAN-02
channel ORA_DISK_1: finished piece 1 at 31-JAN-02
piece handle=C:\BACKUPS\01DFKAIH_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:56
Finished backup at 31-JAN-02
Starting Control File Autobackup at 31-JAN-02
piece handle=C:\BACKUPS\C-4159396170-20020131-00 comment=NONE
Finished Control File Autobackup at 31-JAN-02
Note:
Controlfile backup은 backup의 끝에서 수행된다.
그리고 이 backup piece name의 두번째 string은 dbid이다(4159396170)
Current controlfile이 database와 함께 손실되고 Recovery catalog도 손상되어
사용할 수 없게 되었을 때 controlfile autobackup이 controlfile을 restore하기
위해 사용될 수 있다. restore된 controlfile은 db를 mount하고 datafile들을
restore하기 위해 사용될 수 있다.
Controlfile autobackup을 이용하여 full recovery를 수행하기 위해서는 아래와
같은 과정을 수행하면 된다.
1. Target instance를 위한 new init.ora를 생성한다. backup이 있다면 이것을
사용할 수 있다.
2. Startup nomount your new instance.
3. RMAN은 시작하나 어떤 connect statement도 수행하지 않는다.
4. RMAN prompt상에서 DBID를 설정한다. 만약 DBID를 모르면 controlfile autobackup
의 이름으로부터 이것을 알 수 있다.
RMAN> set dbid=4159396170;
5. Dbid를 설정한 후에 nomount로 startup한 target instance에 connect한다.
RMAN> connect target /
6. 만약에 backup이 disk상에 있고 controlfile autobackup을 non-default location
으로 지정하였다면 파일을 다음과 같은 위치로 옮겨 놓는다
ON UNIX : ORACLE_HOME/dbs
ON WINDOWS: ORACLE_HOME/database
RMAN은 controlfile autobackup을 찾기 위해 위 directory를 검색한다.
만약 controlfile autobackup location을 바꾸지 않으면 위 directory안에
backup이 생성되게 된다.
만약에 backup이 tape에 있다면 restore시 channel과 device를 기술하기 위해서
run block을 사용해야 한다. database가 mount되어 있지 않기 때문에
default device와 channel을 설정할 수 없다.
RMAN> run { allocate channel c_1 type 'sbt_tape'
parms "ENV=(NB_ORA_SERV=rm-wgt)";
restore controlfile from autobackup;}
7. Restore the controlfile:
RMAN> restore controlfile from autobackup;
8. Mount the database from the restored controlfile:
RMAN> alter database mount;
9. Restore datafiles:
RMAN> restore database;
10. file들을 restore한 후에 recovery를 수행할 수 있다.
이때 current online redo log가 없고 또한 backup controlfile을 사용하기
때문에 incomplete recovery를 수행해야 한다. 이를 수행하기 위해서는
"UNTIL TIME"을 설정해야 하고 open시에는 resetlogs를 사용해야 한다.
RMAN> set until time=<time stamp>;
RMAN> recover database;
RMAN> alter database open resetlogs;
REFERENCE DOCUMENT
NOTE:174623.1

BACKUP Command Behavior
ON
If the backup includes datafile 1, then RMAN does not automatically include the current control file in the datafile backup set. Instead, RMAN writes the control file and server parameter file to a separate autobackup piece.
Note: The autobackup occurs regardless of whether the BACKUP or COPY command explicitly includes the current control file, for example, BACKUP DATABASE INCLUDE CURRENT CONTROLFILE.
OFF
If the backup includes datafile 1, then RMAN automatically includes the current control file and server parameter file in the datafile backup set. RMAN does not create a separate autobackup piece containing the control file and server parameter file.
BUT Dear Mohammed,
It is not working accordingly. what I did is :-
1. I switched off the AUTOBACKUP
2. Then I took whole database backup, that means it included File # 1
3. But according to above it is going to include autobackup of controlfile and spfile in the same backupset .
4. But when I asked it to restore controlfile from autobackup it said NO AUTOBACKUP FOUND.
COULD YOU PLEASE HELP ME ONCE AGAIN DEAR.
If it works accroding to above then it should have my Autobackup.
Regards
Harpreet Singh

Rman controlfile autobackup

Similar Messages

Maybe you are looking for