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

Similar Messages

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?

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]

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;

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!!!!!

Creating a new controlfile with datafiles in RMAN backup

Hi,
i am using oracle 10g (10.2.0.1) in RHEL5 server. i am trying to restore a RMAN backup from one server to another new server with new db name. i have taken out the spfile from RMAN autobackup and created pfile from it and edited the pfile with new dbname and directory structure and started the db in nomount with the new pfile. Now i have restored the controfile from the RMAN autobackup tried to put the database in mount state. But it failed due to the below error
RMAN-03002: failure of alter db command at 11/05/2012 21:44:56
ORA-01103: database name 'ORADB' in control file is not 'DEVDB'
Hence i shutdown the database and started the db in nomount with new pfile and tried to create the controlfile with the new db name,but it failed as it is looking for the datafiles.
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file
'/u01/app/oracle/oradata/DEVDB/datafile/o1_mf_system_80jq0kfw_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
All my datafiles reside in my RMAN backup. How to get the datafiles from RMAN backup in the above scenario??
Regards,
007

Hello;
The location and filename and DBIS will be different, but you need something like this :
$ORACLE_HOME/bin/rman << EOF
CONNECT TARGET /
STARTUP NOMOUNT;
SET DBID 3754763357; #DBID of PROD database
RUN
   ALLOCATE CHANNEL c1 DEVICE TYPE disk format '/u01/oradata/backups';
   RESTORE CONTROLFILE FROM '/u01/oradata/backups/sb_t790762003_s85_p1';
   ALTER DATABASE MOUNT;
   SET NEWNAME FOR DATAFILE 1 TO '/u01/app/oracle/oradata/CLONE/system01.dbf';
    SET NEWNAME FOR TEMPFILE 1 TO '/u01/app/oracle/oradata/CLONE/temp01.dbf';
   RESTORE DATABASE;
   SWITCH DATAFILE ALL;
   RECOVER DATABASE;
   release channel c1;
ALTER DATABASE OPEN RESETLOGS; So you need "SET NEWNAME" for all your files
Full Example
http://www.visi.com/~mseberg/rman/restore_database_without_catalog.html
Best Regards
mseberg

Error while taking backup through RMAN in 10g XE

While taking backup through RMAN in XE instance , an error comes out.
The contents of oxe_backup_current file is as below :
XE Backup Log
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jul 6 15:49:51 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: XE (DBID=2635631092)
RMAN>
echo set on
RMAN> shutdown immediate;
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
RMAN> startup mount;
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area     805306368 bytes
Fixed Size                     1261444 bytes
Variable Size                209715324 bytes
Database Buffers             591396864 bytes
Redo Buffers                   2932736 bytes
RMAN> configure retention policy to redundancy 2;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
new RMAN configuration parameters are successfully stored
RMAN> configure controlfile autobackup format for device type disk clear;
RMAN configuration parameters are successfully reset to default value
RMAN> configure controlfile autobackup on;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
RMAN> sql "create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile";
*sql statement: create pfile=''/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora'' from spfile*
*RMAN-00571: ===========================================================*
*RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
*RMAN-00571: ===========================================================*
*RMAN-03009: failure of sql command on default channel at 07/06/2011 15:50:57*
*RMAN-11003: failure during parse/execution of SQL statement: create pfile='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfile2init.ora' from spfile*
*ORA-27086: unable to lock file - already in use*
*Linux Error: 11: Resource temporarily unavailable*
Additional information: 8
Additional information: 16476
RMAN> backup as backupset device type disk database;
Starting backup at 06-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=102 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/usr/lib/oracle/xe/oradata/XE/sysaux.dbf
input datafile fno=00005 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_log01.dbf
input datafile fno=00006 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_lrg01.dbf
input datafile fno=00001 name=/usr/lib/oracle/xe/oradata/XE/system.dbf
input datafile fno=00009 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_log01.dbf
input datafile fno=00010 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_lrg01.dbf
input datafile fno=00002 name=/usr/lib/oracle/xe/oradata/XE/undo.dbf
input datafile fno=00004 name=/usr/lib/oracle/xe/oradata/XE/users.dbf
input datafile fno=00008 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_sml01.dbf
input datafile fno=00012 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_sml01.dbf
input datafile fno=00011 name=/usr/lib/oracle/xe/oradata/XE/ftress_indx_mdm01.dbf
input datafile fno=00007 name=/usr/lib/oracle/xe/oradata/XE/ftress_data_mdm01.dbf
channel ORA_DISK_1: starting piece 1 at 06-JUL-11
channel ORA_DISK_1: finished piece 1 at 06-JUL-11
piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T155057_718dw649_.bkp tag=TAG20110706T155057 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
Finished backup at 06-JUL-11
Starting Control File and SPFILE Autobackup at 06-JUL-11
piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755797849_718dwofy_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 06-JUL-11
RMAN> configure controlfile autobackup off;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters are successfully stored
RMAN> alter database open;
database opened
RMAN> delete noprompt obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           3      06-JUL-11
Backup Piece       3      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp
Backup Set           4      06-JUL-11
Backup Piece       4      06-JUL-11          /usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp
deleted backup piece
backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/2011_07_06/o1_mf_nnndf_TAG20110706T133443_7184wr4d_.bkp recid=3 stamp=755789684
deleted backup piece
backup piece handle=/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/autobackup/2011_07_06/o1_mf_s_755789675_7184x7fp_.bkp recid=4 stamp=755789699
Deleted 2 objects
RMAN>
Recovery Manager complete.
RMAN error: See log for details.

I think it is trying to overwrite exiting file. Either give a different name or cleanup the files in preferred location.

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

Meaning of 'controlfile autobackup on' in rman ?

Similar Messages

Maybe you are looking for