Control File Auto Backup Alert Log

Hello-
Is there a parameter in the 11g database that needs to be configured to write to the alert log when the controlfile is auto-backed up ?
I have this configured but there are no entries in the alert logs for 11g databases.
I do have them in my 10g alert logs.
Thanks-

No there is no such parameter.
It seems that Oracle 11g does not write anything to alert log when control file is auto backed up but instead writes to a trace file in diagnostic_dest directory tree:
Trace file /u01/app/oracle/diag/rdbms/db112/DB112/trace/DB112_ora_5837.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/EE
System name:    Linux
Node name:      lx01.localdomain
Release:        2.6.18-92.el5
Version:        #1 SMP Fri May 23 22:17:30 EDT 2008
Machine:        i686
Instance name: DB112
Redo thread mounted by this instance: 1
Oracle process number: 29
Unix process pid: 5837, image: [email protected] (TNS V1-V3)
*** 2011-04-18 19:21:39.223
*** SESSION ID:(17.34) 2011-04-18 19:21:39.223
*** CLIENT ID:() 2011-04-18 19:21:39.223
*** SERVICE NAME:(SYS$USERS) 2011-04-18 19:21:39.223
*** MODULE NAME:(backup full datafile) 2011-04-18 19:21:39.223
*** ACTION NAME:(0000023 STARTED111) 2011-04-18 19:21:39.223
Starting control autobackup
*** 2011-04-18 19:21:40.050
Control autobackup written to DISK device
        handle '/tmp/c-732354255-20110418-011'Edited by: P. Forstmann on 18 avr. 2011 19:25

Similar Messages

How to recover datafile.when control file auto backup is off

hi friend
i took hot backup of my database using following command
rman>backup database;
in my case controlfile auto backup is off.
and i have lost my all controlfiles as well as datafiles except spfile.
i have recovered control file using dbms_backup_restore package.
know i am able to mount database using following command
rman> startup mount;
when i wrote following command
rman> restore database;
i got following error
RMAN-06023: no backup or copy of datafile name found to restore
enven i have backup of datbase.
can anybody tell me how to recover datafiles in this case.
thanking you
sohail

hi,
I think you might have a problem here as the error from RMAN is described in the following metalink note
Doc ID: Note:100565.1
You should change you backup script to be something like
rman {
backup database include current controlfile;
do you have any earlier backups of your database?
regards
Alan

What data/control files to backup?

Dear All,
I can't perfom the proper backup - no room at the servers at the moment so I thought of making physical copies of datafiles and maybe control files. Though I'm not sure whether it's save or not and actually what files I have to take. Should I shutdown the database first hand?
If anyone did the same thing before please help)))
Thanks in advance
Marina

Hi,
Before planning the backup, Check for the following things.
1. Archiving mode of database(archive log or nonarchivelog).
2. How critical is the database.
If the database is in noarchivelog mode then you should shutdown the database first and then take the physical backup of All datafiles, control files and Parameter file.
If the database is in archivelog mode then you can simply take a online hot backup of the database. In the documentation you can get the method of taking hot backup.
Hope it helps.

Control File Backups

Hello-
I was looking over some configurations that was setup by another DBA.
There are 3 control files created but they all are on the same disk/directory.
Control file auto backup is on to tape.
If there was a hardware failure and all three control were corrupted/lost then a backup would be used but
full recovery and RESETLOGS would be needed which would lead to redo data loss.
If I configured 1 control file on a seperate disk. I would be able to copy this one and create 3 files again and the database
would be started again without needing recovery if all else was fine.
If the control keeps track of redo logs SCN, Archive logs history and RMAN backups when these change then wouldn't another control file backup/ trace need to be done ?
Control File Trace only alllows to rebuild the database not to copy. How often is the need to taken ? Every change in the database ?
Backup to the Flash Recovery is another backup not an updated copy to copy from but to restore/recovery with.
Do have have these theories correct and my best setup would to send at least one to another disk.
Thanks-

If there was a hardware failure and all three control were corrupted/lost then a backup would be used but
full recovery and RESETLOGS would be needed which would lead to redo data loss. No. If you lose all three controlfiles, you either
a. RESTORE a backup of the controlfile
OR
b. CREATE CONTROLFILE (from a script)
In either case, you do NOT need to do an INCOMPLETE Recovery. You will be doing a COMPLETE Recovery (if you have the Online Redo Logs). However, an OPEN RESETLOGS is still required. The %r in the log_archive_format since 10g allows ArchiveLogs to be retained through ResetLogs.
If the control keeps track of redo logs SCN, Archive logs history and RMAN backups when these change then wouldn't another control file backup/ trace need to be done ? If you RESTORE the controlfile you lose no information. However, you still have to OPEN RESETLOGS.
If you do a CREATE CONTROLFILE, yes, you lose information about ArchiveLogs history and RMAN Backups.
You can issue a CATALOG command to re-catalog available Backups.
Control File Trace only alllows to rebuild the database not to copy.A Control File Trace is to recreate the Controlfile. Not rebuild the database.
Backup to the Flash Recovery is another backup not an updated copy to copy from but to restore/recovery with. I don't understand what your statement or question might be here.
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on Mar 2, 2011 2:44 PM
Edited by: Hemant K Chitale on Mar 2, 2011 2:45 PM

How to make the control file consistent when I re-mulitplexing them

Oracle 10g R2 on the AIX 5.3L
My current control files (three) from the default set-up are all located in the same directory (/dbbaan/oradata/<SID>/). If I want to change some of the multiplexing of the control file to different directory to avoid the media failure,
1. I copy one or two control files to different directory.
2. create a new init_sid.ora from spfile
2. edit the init_sid.ora file and change the locations of the control file
3. shutdown/restart the DB using the init_sid.ora.
4. create the spfile from the pfile
5 shutdown/restart the DB with new spfile ( "SQL> startup")
My question is: since there is always time lag between copying and recreating the new init_sid.ora, while the control file(s) are constantly updating, how can Db guarrente the consistency of the DB when I restart the DB (the control file specified in the init_sid.ora may be some time old) ? or does it matter?
I did above and my DB restart without problem.

Another problem concerns me. What happen if one of
multiplexed control file location, which I use a NFS
of another server, goes down and is not available
during the operation ( After I restart up the DB)? I
am sure I will see the error of that control file in
the alert log.If one of the control files not accessible during operation, Oracle will crash. So you better make sure all of your control file location are reliable and accessible.

RMAN Auto Control File Backup

Can there be two control file auto file backups one to disk and one to tape ?
Thanks,

Hi
In our RMAN setup SHOW ALL; there is both disk and tape configured. but it does not backup to disk anymore
and I am getting the errors below in my alert.log.
There are about ten old copies on the disk. How do these get purged ?
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\DONT_TOUCH\CONTROL_FILE_BACKUP\%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default Starting control autobackup
Wed Feb 03 00:20:31 2010
Errors in file d:\oracle\product\10.2.0\admin\udump\_ora_3600.trc:
Wed Feb 03 00:20:31 2010
Errors in file d:\oracle\product\10.2.0\admin\udump\_ora_3600.trc:
Wed Feb 03 00:20:31 2010
Errors in file d:\oracle\product\10.2.0\admin\udump\_ora_3600.trc:
Wed Feb 03 00:20:31 2010
Control autobackup written to SBT_TAPE device
     comment 'API Version 2.0,MMS Version 5.0.0.0',
     media '/database/_1265174399_C1_F1'
     handle 'c-1624991920-20100203-01'
Wed Feb 03 08:59:14 2010

Trace file with different name is alert log file.

I am strange today
i found a trace file generated in alert log file with name
/bdump/stlbas_cjq0_1880.trc:
but when i am trying to find out in bdump folder i cannot found
any file with this named. instead i found /bdump/stlbas_cjq0_1853.trc
is there any possibility of being this scenario ?
database version:- 10.2.0.4
Os:- sun solaries spark 64 bits
Regards
Halim

The trace file has been removed/deleted from an OS user. I think you should verify that with OS logs.
Thanks

Multiplexing Online redo logs, archive logs, and control files.

Currently I am only multiplexing my control files and online redo logs, My archive logs are only going to the FRA and then being backed up to tape.
We have to replace disks that hold the FRA data. HP says there is a chance we will have to rebuild the FRA.
As my archive logs are going to the FRA now, can I multiplex them to another disk group? And if all of the control files, online redo logs and archive logs are multiplexed to another disk group, when ASM dismounts the FRA disk group due to insufficient number of disks, will the database remain open and on line.
If so then I will just need to rebuild the ASM volumes, and the FRA disk group and bring it to the mount state, correct?
Thanks!

You can save your online redo logs and archive logs anywhere you want by making use of of init params create_online_log_dest and log_archive_dest_n. You will have to create new redo log groups in the new location and drop the ones in the FRA. The archive logs will simply land wherever you designate with log_archive_dest_n parameters. Moving the control files off FRA is a little trickier because you will need to restore your controlfile to a non-FRA destination and then shutdown your instance, edit the control file param to reflect changes and restart.
I think you will be happier if you move everything off the FRA diskgroup before dismounting it, and not expecting the db to automagically recover from the loss of files on the FRA.

Alert log/trace file

alert log file is generated daily or it will be updated daily?
is trace file part of alert log file or its a seperate file?
how trace file differ's from alert log file.?
thankx....

>>
alert log file is generated daily or it will be updated daily?
>
When oralce starts every first time, oracle does create a alert log file and whenever oracle wants to update the alertlog file, it updates the existing one and in case of missing alert log, it re-create the alert log and updates it.
>>
is trace file part of alert log file or its a seperate file?
>>
No.
>>
how trace file differ's from alert log file.?
>>
alert log contains database activities list carried out in the related database.
trace file can be generated due to number of reasons, like, hardware problems, due to oracle internal errors, user errors, whenever you trace a session and etc.
Jaffar

Unable to open alert log file

Hi Guys
I am using oracle 10.2.0.4.0 on windows 2003 64 . I am unable to open my alert log file. My alert log file opens in a notepad. I get the following error:
'C:\oracle\admin\efint\bdump\alert_efint.log file is too large for notepad. Use another editor to edit the file.'
I tried opening it with wordpad. It gives back 'Failed to open document error.'
My database is working but it wont let me open my alert file. I was able to open it yesterday but not today.
Any help is appreciated
Thanks in advance....
regards

Hi,
I recommend that you download tail for windows:
http://www.x64bitdownload.com/downloads/t-64-bit-tail4win-download-ljrvpdfr.html
This is the description:
Tail4Win is a real-time log monitor and viewer, is a windows port of the UNIX 'tail -f' command, it can be used to view the end of a growing file. By using Tail4Win system administrator can monitor log files of server applications in real-time, e.g. Apache's error.log and access.log, or IIS, Tomcat, Resin log files. And programmer can monitor application traces easy and quickly. Tail4win can display the last part of a large file quickly without loading the entire file. And it is a file viewer only, it makes no changes to log files. Main fetures: Monitor changes to files and display the changed lines in realtime. Monitor files of any size quickly, no need to load the entire file. Highlighting and filtering let you focus on important informations. Watch multiple files at same time. Real command line support, just like using Unix/Linux "tail" command. Capture and display OutputDebugString (Windows debugging API) output.
Regards,
Mario Alcaide
http://marioalcaide.wordpress.com

Who writes alert log file?

Hi guys ,
I have been searching for answer to this question,.............
Which process(backgroud process) writes to alert log file?

Trace files for user processes are normally in the user_dump. They are created only when tracing is requested OR when Oracle encounters an error.
The alert.log is a file that is used to continously display the status of the database as it changes with important events (e.g. archival of log, alter system commands, ora-1555 errors, indexes unusable, datafile space allocation etc). Most of these are issues which affect the entire instance/database. However, where a sever error is encountered in a user process, Oracle writes a trace file in user_dump_dest for that error and a message indicating the error and the name of the trace file to the alert.log.
Similarly, the background processes may also be writing to their own trace files to indcate status /tracing.
The level of detail being logged can vary by version and by setting specific database events (if specified by Oracle Support) in the instance.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm#sthref729
Hemant K Chitale

Upgraded to 10.2.0.2.0, but problem with 'identifying control file'

I just applied the metalink patch to upgrade from 10.2.0.1.0 to 10.2.0.2.0 in order to install the SOA Suite. It was a clean install for 10.2.0.1.0, followed by applying the patch. I am now trying to run the new database, but I get an error:
ORA-00205: error in identifying controle file, check alert log for more info.
I edited by init.ora file, and the two control files are there as (ora_control1, ora_control2).
Any help would be greatly appreciated.
Kind regards,
Anthony

We had a similar issue and had to fix it by copying all the data files and control files to backup then ...
1) run database creation assistant to delete the database
2) using database creation assistant, create a new database with the same name
3) shut down the new database
4) leaving the new spfile in place, copy all the backups back over including controlfiles.
5) startup the database.
Don't know if it will help in your situation or not, but worth a try if someone else has the same type of problem.

Alert log error Warning

Hi,
am getting this warning in my alert log file;
db_create_file_dest is same as db_recovery_file_dest
This database is running in NoArchivelog mode;
What does this error mean?
TIA
Phani krishna.

Hi,
This means that in this database has been configured goth parameters to use same directory. And this is not realy advisable since
. db_create_file_dest difnes where DATAFILES (and if db_create_online_log_dest is not defines REDO LOGs and CONTROLFILEs) created via OMF are created
. db_recovery_file_dest difnes where Oracle should create Redo log files, Control files, RMAN backups (datafile copies, control file copies, backup pieces, control file autobackups), Archived logs, Flashback logs
So you should define these parameters to different directories. I don't know if it's critical, but I would change it ASAP or open a SR to get further info. Though it's just a warning, I don't think it's safe to ignore.
Regards,
Yoann.

Control File issue

Hi All,
11.2.0.1 on AIX 7.1 and Level 0 happens on every SATURDAY and L1 backup run every day.
We are using following script for level0 RMAN backup:
RUN {
SHOW ALL;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
ALLOCATE CHANNEL ch1 TYPE DISK;
ALLOCATE CHANNEL ch2 TYPE DISK;
ALLOCATE CHANNEL ch3 TYPE DISK;
ALLOCATE CHANNEL ch4 TYPE DISK;
BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L0_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL0';
BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L0_%d_%D%M%Y_%u_%s_%p'   ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL0';
BACKUP FORMAT '/oraclebackup/HFM11PROD/CF_L0_%d_%D%M%Y_%u_%s_%p' CURRENT CONTROLFILE TAG='LEVEL0';
BACKUP FORMAT '/oraclebackup/HFM11PROD/SP_L0_%d_%D%M%Y_%u_%s_%p' SPFILE TAG='LEVEL0';
CROSSCHECK ARCHIVELOG ALL;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL ch1;
RELEASE CHANNEL ch2;
RELEASE CHANNEL ch3;
RELEASE CHANNEL ch4;
}Now backup logs shows that we have backup of control file in two backup pieces : One implicitly in a backup piece DF_L0_HFM11PRD_10112012_l8npv5b6_13992_1
and other one is explicitly in CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 .
RMAN> RUN {
2> SHOW ALL;
3> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
4> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
5> ALLOCATE CHANNEL ch1 TYPE DISK;
6> ALLOCATE CHANNEL ch2 TYPE DISK;
7> ALLOCATE CHANNEL ch3 TYPE DISK;
8> ALLOCATE CHANNEL ch4 TYPE DISK;
9> BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L0_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL0';
10> BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L0_%d_%D%M%Y_%u_%s_%p'   ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL0';
11> BACKUP FORMAT '/oraclebackup/HFM11PROD/CF_L0_%d_%D%M%Y_%u_%s_%p' CURRENT CONTROLFILE TAG='LEVEL0';
12> BACKUP FORMAT '/oraclebackup/HFM11PROD/SP_L0_%d_%D%M%Y_%u_%s_%p' SPFILE TAG='LEVEL0';
13> CROSSCHECK ARCHIVELOG ALL;
14> DELETE NOPROMPT OBSOLETE;
15> RELEASE CHANNEL ch1;
16> RELEASE CHANNEL ch2;
17> RELEASE CHANNEL ch3;
18> RELEASE CHANNEL ch4;
19> }
RMAN configuration parameters for database with db_unique_name HFM11PRD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
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 DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/orahyp_p/product/11.2/dbs/snapcf_HFM11PRD.f'; # default
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
allocated channel: ch1
channel ch1: SID=1210 device type=DISK
allocated channel: ch2
channel ch2: SID=1477 device type=DISK
allocated channel: ch3
channel ch3: SID=66 device type=DISK
allocated channel: ch4
channel ch4: SID=1156 device type=DISK
Starting backup at 10-NOV-12
channel ch1: starting compressed incremental level 0 datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u04/oradata/HFM11PRD/system01.dbf
input datafile file number=00008 name=/u04/oradata/HFM11PRD/EPM_HFM4.DBF
input datafile file number=00012 name=/u04/oradata/HFM11PRD/EPM_HFM8.DBF
input datafile file number=00017 name=/u04/oradata/HFM11PRD/EPM_HFM12.DBF
input datafile file number=00004 name=/u04/oradata/HFM11PRD/EPM_HSS1.DBF
input datafile file number=00020 name=/u04/oradata/HFM11PRD/EPM_HFM3.DBF
channel ch1: starting piece 1 at 10-NOV-12
channel ch2: starting compressed incremental level 0 datafile backup set
channel ch2: specifying datafile(s) in backup set
input datafile file number=00003 name=/u04/oradata/HFM11PRD/undots01.dbf
input datafile file number=00009 name=/u04/oradata/HFM11PRD/EPM_HFM5.DBF
input datafile file number=00013 name=/u04/oradata/HFM11PRD/EPM_HFM9.DBF
input datafile file number=00018 name=/u04/oradata/HFM11PRD/EPM_HFM13.DBF
input datafile file number=00005 name=/u04/oradata/HFM11PRD/EPM_BI1.DBF
input datafile file number=00021 name=/u04/oradata/HFM11PRD/EPM_HFM15.DBF
channel ch2: starting piece 1 at 10-NOV-12
channel ch3: starting compressed incremental level 0 datafile backup set
channel ch3: specifying datafile(s) in backup set
input datafile file number=00007 name=/u04/oradata/HFM11PRD/EPM_HFM2.DBF
input datafile file number=00011 name=/u04/oradata/HFM11PRD/EPM_HFM7.DBF
input datafile file number=00016 name=/u04/oradata/HFM11PRD/EPM_HFM11.DBF
input datafile file number=00002 name=/u04/oradata/HFM11PRD/sysaux01.dbf
input datafile file number=00022 name=/u04/oradata/HFM11PRD/EPM_HSS_new1.DBF
channel ch3: starting piece 1 at 10-NOV-12
channel ch4: starting compressed incremental level 0 datafile backup set
channel ch4: specifying datafile(s) in backup set
input datafile file number=00006 name=/u04/oradata/HFM11PRD/EPM_HFM1.DBF
input datafile file number=00010 name=/u04/oradata/HFM11PRD/EPM_HFM6.DBF
input datafile file number=00015 name=/u04/oradata/HFM11PRD/EPM_HFM10.DBF
input datafile file number=00019 name=/u04/oradata/HFM11PRD/EPM_HFM14.DBF
input datafile file number=00014 name=/u04/oradata/HFM11PRD/userdata01.dbf
channel ch4: starting piece 1 at 10-NOV-12
channel ch2: finished piece 1 at 10-NOV-12
_*piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_l8npv5b6_13992_1 tag=LEVEL0 comment=NONE*_
channel ch2: backup set complete, elapsed time: 00:10:46
channel ch2: starting compressed incremental level 0 datafile backup set
channel ch2: specifying datafile(s) in backup set
_*including current control file in backup set*channel ch2: starting piece 1 at 10-NOV-12_
channel ch2: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_lbnpv5vc_13995_1 tag=LEVEL0 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:01
channel ch2: starting compressed incremental level 0 datafile backup set
channel ch2: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch2: starting piece 1 at 10-NOV-12
channel ch2: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_lcnpv5ve_13996_1 tag=LEVEL0 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:01
channel ch1: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_l7npv5b6_13991_1 tag=LEVEL0 comment=NONE
channel ch1: backup set complete, elapsed time: 00:11:03
channel ch4: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_lanpv5b7_13994_1 tag=LEVEL0 comment=NONE
channel ch4: backup set complete, elapsed time: 00:11:32
channel ch3: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_l9npv5b6_13993_1 tag=LEVEL0 comment=NONE
channel ch3: backup set complete, elapsed time: 00:11:52
Finished backup at 10-NOV-12
Starting backup at 10-NOV-12
current log archived
channel ch1: starting compressed archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=40007 RECID=40001 STAMP=798971664
input archived log thread=1 sequence=40008 RECID=40002 STAMP=798972711
input archived log thread=1 sequence=40009 RECID=40003 STAMP=798973470
input archived log thread=1 sequence=40010 RECID=40004 STAMP=798974835
input archived log thread=1 sequence=40011 RECID=40005 STAMP=798975943
channel ch1: starting piece 1 at 10-NOV-12
channel ch2: starting compressed archived log backup set
channel ch2: specifying archived log(s) in backup set
input archived log thread=1 sequence=40012 RECID=40006 STAMP=798976804
input archived log thread=1 sequence=40013 RECID=40007 STAMP=798977866
input archived log thread=1 sequence=40014 RECID=40008 STAMP=798978754
input archived log thread=1 sequence=40015 RECID=40009 STAMP=798980083
input archived log thread=1 sequence=40016 RECID=40010 STAMP=798981194
channel ch2: starting piece 1 at 10-NOV-12
channel ch3: starting compressed archived log backup set
channel ch3: specifying archived log(s) in backup set
input archived log thread=1 sequence=40017 RECID=40011 STAMP=798982283
input archived log thread=1 sequence=40018 RECID=40012 STAMP=798983171
input archived log thread=1 sequence=40019 RECID=40013 STAMP=798984077
input archived log thread=1 sequence=40020 RECID=40014 STAMP=798985146
input archived log thread=1 sequence=40021 RECID=40015 STAMP=798985212
channel ch3: starting piece 1 at 10-NOV-12
channel ch4: starting compressed archived log backup set
channel ch4: specifying archived log(s) in backup set
input archived log thread=1 sequence=40022 RECID=40016 STAMP=798985214
input archived log thread=1 sequence=40023 RECID=40017 STAMP=798985992
input archived log thread=1 sequence=40024 RECID=40018 STAMP=798987561
input archived log thread=1 sequence=40025 RECID=40019 STAMP=798988338
channel ch4: starting piece 1 at 10-NOV-12
channel ch4: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_lgnpv61k_14000_1 tag=LEVEL0 comment=NONE
channel ch4: backup set complete, elapsed time: 00:00:15
channel ch1: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_ldnpv61j_13997_1 tag=LEVEL0 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:26
channel ch2: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_lenpv61j_13998_1 tag=LEVEL0 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:26
channel ch3: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_lfnpv61j_13999_1 tag=LEVEL0 comment=NONE
channel ch3: backup set complete, elapsed time: 00:00:25
Finished backup at 10-NOV-12
Starting backup at 10-NOV-12
channel ch1: starting compressed full datafile backup set
channel ch1: specifying datafile(s) in backup set
_*including current control file in backup set*_
channel ch1: starting piece 1 at 10-NOV-12
channel ch1: finished piece 1 at 10-NOV-12
_*piece handle=/oraclebackup/HFM11PROD/CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 tag=LEVEL0 comment=NONE*_channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-NOV-12
Starting backup at 10-NOV-12
channel ch1: starting compressed full datafile backup set
channel ch1: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch1: starting piece 1 at 10-NOV-12
channel ch1: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/SP_L0_HFM11PRD_10112012_linpv62i_14002_1 tag=LEVEL0 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-NOV-12Following is the script of Leve 1 RMAN backup.
RUN {
SHOW ALL;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
ALLOCATE CHANNEL ch1 TYPE DISK;
ALLOCATE CHANNEL ch2 TYPE DISK;
ALLOCATE CHANNEL ch3 TYPE DISK;
ALLOCATE CHANNEL ch4 TYPE DISK;
BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L1_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL1';
BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L1_%d_%D%M%Y_%u_%s_%p'   ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL1';
CROSSCHECK ARCHIVELOG ALL;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL ch1;
RELEASE CHANNEL ch2;
RELEASE CHANNEL ch3;
RELEASE CHANNEL ch4;
}Following is the log from Level 1 backup which shows that it has marked the backup of control file in backup piece CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 as obsolete and deleted.
RMAN> RUN {
2> SHOW ALL;
3> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
4> ALLOCATE CHANNEL ch1 TYPE DISK;
5> ALLOCATE CHANNEL ch2 TYPE DISK;
6> ALLOCATE CHANNEL ch3 TYPE DISK;
7> ALLOCATE CHANNEL ch4 TYPE DISK;
8> BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L1_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL1';
9> BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L1_%d_%D%M%Y_%u_%s_%p'   ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL1';
10> CROSSCHECK ARCHIVELOG ALL;
11> DELETE NOPROMPT OBSOLETE;
12> RELEASE CHANNEL ch1;
13> RELEASE CHANNEL ch2;
14> RELEASE CHANNEL ch3;
15> RELEASE CHANNEL ch4;
16> }
RMAN configuration parameters for database with db_unique_name HFM11PRD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
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 DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
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 ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/orahyp_p/product/11.2/dbs/snapcf_HFM11PRD.f'; # default
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
allocated channel: ch1
channel ch1: SID=1718 device type=DISK
allocated channel: ch2
channel ch2: SID=1499 device type=DISK
allocated channel: ch3
channel ch3: SID=119 device type=DISK
allocated channel: ch4
channel ch4: SID=1166 device type=DISK
Starting backup at 12-NOV-12
channel ch1: starting compressed incremental level 1 datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u04/oradata/HFM11PRD/system01.dbf
input datafile file number=00008 name=/u04/oradata/HFM11PRD/EPM_HFM4.DBF
input datafile file number=00012 name=/u04/oradata/HFM11PRD/EPM_HFM8.DBF
input datafile file number=00017 name=/u04/oradata/HFM11PRD/EPM_HFM12.DBF
input datafile file number=00004 name=/u04/oradata/HFM11PRD/EPM_HSS1.DBF
input datafile file number=00020 name=/u04/oradata/HFM11PRD/EPM_HFM3.DBF
channel ch1: starting piece 1 at 12-NOV-12
channel ch2: starting compressed incremental level 1 datafile backup set
channel ch2: specifying datafile(s) in backup set
input datafile file number=00003 name=/u04/oradata/HFM11PRD/undots01.dbf
input datafile file number=00009 name=/u04/oradata/HFM11PRD/EPM_HFM5.DBF
input datafile file number=00013 name=/u04/oradata/HFM11PRD/EPM_HFM9.DBF
input datafile file number=00018 name=/u04/oradata/HFM11PRD/EPM_HFM13.DBF
input datafile file number=00005 name=/u04/oradata/HFM11PRD/EPM_BI1.DBF
input datafile file number=00021 name=/u04/oradata/HFM11PRD/EPM_HFM15.DBF
channel ch2: starting piece 1 at 12-NOV-12
channel ch3: starting compressed incremental level 1 datafile backup set
channel ch3: specifying datafile(s) in backup set
input datafile file number=00007 name=/u04/oradata/HFM11PRD/EPM_HFM2.DBF
input datafile file number=00011 name=/u04/oradata/HFM11PRD/EPM_HFM7.DBF
input datafile file number=00016 name=/u04/oradata/HFM11PRD/EPM_HFM11.DBF
input datafile file number=00002 name=/u04/oradata/HFM11PRD/sysaux01.dbf
input datafile file number=00022 name=/u04/oradata/HFM11PRD/EPM_HSS_new1.DBF
channel ch3: starting piece 1 at 12-NOV-12
channel ch4: starting compressed incremental level 1 datafile backup set
channel ch4: specifying datafile(s) in backup set
input datafile file number=00006 name=/u04/oradata/HFM11PRD/EPM_HFM1.DBF
input datafile file number=00010 name=/u04/oradata/HFM11PRD/EPM_HFM6.DBF
input datafile file number=00015 name=/u04/oradata/HFM11PRD/EPM_HFM10.DBF
input datafile file number=00019 name=/u04/oradata/HFM11PRD/EPM_HFM14.DBF
input datafile file number=00014 name=/u04/oradata/HFM11PRD/userdata01.dbf
channel ch4: starting piece 1 at 12-NOV-12
channel ch1: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_lvnq4e3a_14015_1 tag=LEVEL1 comment=NONE
channel ch1: backup set complete, elapsed time: 00:01:36
channel ch1: starting compressed incremental level 1 datafile backup set
channel ch1: specifying datafile(s) in backup set
channel ch4: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m2nq4e3a_14018_1 tag=LEVEL1 comment=NONE
channel ch4: backup set complete, elapsed time: 00:01:35
channel ch4: starting compressed incremental level 1 datafile backup set
channel ch4: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch4: starting piece 1 at 12-NOV-12
including current control file in backup set
channel ch1: starting piece 1 at 12-NOV-12
channel ch1: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m3nq4e6a_14019_1 tag=LEVEL1 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
channel ch4: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m4nq4e6a_14020_1 tag=LEVEL1 comment=NONE
channel ch4: backup set complete, elapsed time: 00:00:01
channel ch3: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m1nq4e3a_14017_1 tag=LEVEL1 comment=NONE
channel ch3: backup set complete, elapsed time: 00:01:39
channel ch2: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m0nq4e3a_14016_1 tag=LEVEL1 comment=NONE
channel ch2: backup set complete, elapsed time: 00:02:41
Finished backup at 12-NOV-12
Starting backup at 12-NOV-12
current log archived
channel ch1: starting compressed archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=40201 RECID=40195 STAMP=799144567
input archived log thread=1 sequence=40202 RECID=40196 STAMP=799145383
input archived log thread=1 sequence=40203 RECID=40197 STAMP=799146296
input archived log thread=1 sequence=40204 RECID=40198 STAMP=799147040
input archived log thread=1 sequence=40205 RECID=40199 STAMP=799147640
input archived log thread=1 sequence=40206 RECID=40200 STAMP=799148271
channel ch1: starting piece 1 at 12-NOV-12
channel ch2: starting compressed archived log backup set
channel ch2: specifying archived log(s) in backup set
input archived log thread=1 sequence=40207 RECID=40201 STAMP=799149018
input archived log thread=1 sequence=40208 RECID=40202 STAMP=799150009
input archived log thread=1 sequence=40209 RECID=40203 STAMP=799150549
input archived log thread=1 sequence=40210 RECID=40204 STAMP=799151041
input archived log thread=1 sequence=40211 RECID=40205 STAMP=799151860
input archived log thread=1 sequence=40212 RECID=40206 STAMP=799152535
channel ch2: starting piece 1 at 12-NOV-12
channel ch3: starting compressed archived log backup set
channel ch3: specifying archived log(s) in backup set
input archived log thread=1 sequence=40213 RECID=40207 STAMP=799153553
input archived log thread=1 sequence=40214 RECID=40208 STAMP=799153980
input archived log thread=1 sequence=40215 RECID=40209 STAMP=799154283
input archived log thread=1 sequence=40216 RECID=40210 STAMP=799155243
input archived log thread=1 sequence=40217 RECID=40211 STAMP=799155964
input archived log thread=1 sequence=40218 RECID=40212 STAMP=799156899
channel ch3: starting piece 1 at 12-NOV-12
channel ch4: starting compressed archived log backup set
channel ch4: specifying archived log(s) in backup set
input archived log thread=1 sequence=40219 RECID=40213 STAMP=799157722
input archived log thread=1 sequence=40220 RECID=40214 STAMP=799158015
input archived log thread=1 sequence=40221 RECID=40215 STAMP=799158018
input archived log thread=1 sequence=40222 RECID=40216 STAMP=799158847
input archived log thread=1 sequence=40223 RECID=40217 STAMP=799159640
input archived log thread=1 sequence=40224 RECID=40218 STAMP=799160590
channel ch4: starting piece 1 at 12-NOV-12
channel ch4: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m8nq4e8h_14024_1 tag=LEVEL1 comment=NONE
channel ch4: backup set complete, elapsed time: 00:00:25
channel ch1: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m5nq4e8g_14021_1 tag=LEVEL1 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:36
channel ch2: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m6nq4e8g_14022_1 tag=LEVEL1 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:36
channel ch3: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m7nq4e8g_14023_1 tag=LEVEL1 comment=NONE
channel ch3: backup set complete, elapsed time: 00:00:35
Finished backup at 12-NOV-12
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402011737949656.ARC RECID=40195 STAMP=799144567
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402021737949656.ARC RECID=40196 STAMP=799145383
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402031737949656.ARC RECID=40197 STAMP=799146296
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402041737949656.ARC RECID=40198 STAMP=799147040
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402051737949656.ARC RECID=40199 STAMP=799147640
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402061737949656.ARC RECID=40200 STAMP=799148271
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402071737949656.ARC RECID=40201 STAMP=799149018
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402081737949656.ARC RECID=40202 STAMP=799150009
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402091737949656.ARC RECID=40203 STAMP=799150549
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402101737949656.ARC RECID=40204 STAMP=799151041
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402111737949656.ARC RECID=40205 STAMP=799151860
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402121737949656.ARC RECID=40206 STAMP=799152535
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402131737949656.ARC RECID=40207 STAMP=799153553
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402141737949656.ARC RECID=40208 STAMP=799153980
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402151737949656.ARC RECID=40209 STAMP=799154283
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402161737949656.ARC RECID=40210 STAMP=799155243
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402171737949656.ARC RECID=40211 STAMP=799155964
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402181737949656.ARC RECID=40212 STAMP=799156899
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402191737949656.ARC RECID=40213 STAMP=799157722
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402201737949656.ARC RECID=40214 STAMP=799158015
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402211737949656.ARC RECID=40215 STAMP=799158018
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402221737949656.ARC RECID=40216 STAMP=799158847
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402231737949656.ARC RECID=40217 STAMP=799159640
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402241737949656.ARC RECID=40218 STAMP=799160590
Crosschecked 24 objects
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           18521832 10-NOV-12
Backup Piece       18521838 10-NOV-12          /oraclebackup/HFM11PROD/CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1
Backup Set           18521846 10-NOV-12
Backup Piece       18521848 10-NOV-12          /oraclebackup/HFM11PROD/SP_L0_HFM11PRD_10112012_linpv62i_14002_1
deleted backup piece
backup piece handle=/oraclebackup/HFM11PROD/CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 RECID=14000 STAMP=798988367
deleted backup piece
backup piece handle=/oraclebackup/HFM11PROD/SP_L0_HFM11PRD_10112012_linpv62i_14002_1 RECID=14001 STAMP=798988370
Deleted 2 objects
released channel: ch1
released channel: ch2
released channel: ch3
released channel: ch4
RMAN> exit;Now, on Friday when i am trying to do a restore for this database on another server i am getting error as below. Restore script is as below.
run
allocate AUXILIARY channel c1 device type disk;
allocate AUXILIARY channel c2 device type disk;
allocate AUXILIARY channel c3 device type disk;
allocate AUXILIARY channel c4 device type disk;
set until scn 699575816;
duplicate target database to HFM11TMP;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
}Error is as:
   sql clone "alter system set db_unique_name =
''HFM11TMP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
   shutdown clone immediate;
   startup clone force nomount
   restore clone primary controlfile;
   alter clone database mount;
executing Memory Script
executing command: SET until clause
sql statement: alter system set db_name = ''HFM11PRD'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''HFM11TMP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size               2298480896 bytes
Database Buffers            1962934272 bytes
Redo Buffers                  12152832 bytes
allocated channel: c1
channel c1: SID=112 device type=DISK
Starting restore at 06-NOV-12
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/06/2012 15:13:32
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restoreRMAN is searching for backup of controlfile in backup piece CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1. But this has been already obsolete.
Now, if it not possible to get above backup piece back, then how to proceed with restore with backup piece DF_L0_HFM11PRD_10112012_l8npv5b6_13992_1 as it also has control file backup and available on disk, not obsolete. I can understand the reason for marking CF* file as obsolete because of redundency 1. But how to proceed with restore with available backup ?

Hello;
I would change my configure for one :
RMAN>CONFIGURE CONTROLFILE AUTOBACKUP ON;Would use this to check :
list backup of controlfile completed before <date>And would catalog everything again just to be sure before starting the restore.
You may have to catalog use the control file piece to avoid the error.
RMAN> catalog backuppiece ...Another idea is to test the restore using something like this :
RMAN> run {
        set until time "to_date('2012 NOV 17 07:00','YYYY MON DD HH24:MI')";
        restore controlfile preview;
      }Best Regards
mseberg
Edited by: mseberg on Nov 16, 2012 10:12 AM
Edited by: mseberg on Nov 16, 2012 11:13 AM

Snapshot control file

Hi,
I am interested in time of snapshot control file creation.
I have read that snapshot control file is created before the backup take the place. I have tried to take the simple rman>backup database command, but I have seen that snapshot control file is created after all backup process (I have seen the time of creating the snapshot control file).
Can anybody tell me about this? When the snapshot control file is created (before backup, maybe in the memory, because I can't see it on the file system).
Regards,
Dragan

Hi,
I have read this sentence from Oracle Database 10g RMAN Backup & Recovery:
RMAN needs to get a consistent view of the control file when it sets out to make backup of every datafile. It only needs to know the most recent checkpoint information and file schematic information at the time backup begins. After the backup starts, RMAN needs this information to stay consistent for duration of the backup operation; in other words, it needs a read consistent view of the control file. With the constant updates from the database, this is nearly impossible - unless RMAN were to lock the control file for the duration of the backup. But that would mean the database could not advance checkpoint or switch logs or produce new archive logs. Impossible.
To get around this, RMAN uses the snapshot control file, an exact copy of your control file that is only used by RMAN during backup and resync operations. At the beginning of these operations, RMAN refreshes the snapshot control file from the actual control file, thus putting a momentary lock on the control file. Then, RMAN switches to the snapshot and uses it for the duration of the backup; in this way, it has read consistency without holding up database activity.
I must ask you if I am using control file only (not recovery catalog) what is happening when I am executing simple RMAN command> backup database;
You have said that I don't create snapshot of control file at that moment, only at the end of the backup process (I have also try it in my environment and snapshot is created at the end of the backup process).
How RMAN knows what to backup (which files), he takes this information from original control file (not from snapshot) I suppose.
What is happening when he finished backup of some backup set, he writes that information again in original control file I suppose.
And at the end of all process why he takes snapshot of control file (to backup control file from it, not from original control file, because control file is always changing, need to lock it). In that snapshot control file (and in the its backup) we will have the pointers on files that are made after the backup process started (is this true).
Thanks,
Regards
Dragan

Control File Auto Backup Alert Log

Similar Messages

Maybe you are looking for