Rman causing control file contention

Hi,
may i ask for your opinions and advice regarding control file contention issues.
last week when rman was running it caused a locking issue with another session in another node and based on ash/awr reports there was a control file contention issue..
in need of your advice and opinions
thanks.

Hi,
I have too little experience with RAC, so you better wait for some answers from experts on that matter.
Nevertheless, my thoughts are as follows:
* You have enqueue contention, and this should be taken care of by the GES part of your CRS layer: maybe a place to check if you can trace back any problems.
* I thought that the version management should be like : CRS version >= ASM version >= DB version .... and this is no longer your situation since your CRS version seems to be 10g when your database run 11g.
Maybe you could also mention if you use ASM, and where your control files are located.
Again, wait for experienced answers...
HTH,
Thierry

Similar Messages

RMAN Restore Control File Fails - File Header Validation Fails

hi everyone,
This is 9i on Windows 2000.
I'm trying to restore a control file from a backup made by RMAN on another server.
I expected Oracle/RMAN to choke because it knows the backup file was not made from this servers database.
RMAN>restore control file from '......' gives ORA-19563 Control File header validation failed
Is there a way to force RMAN to restore a file, in a situation like this?
Thanks,
John

>>I expected Oracle/RMAN to choke because it knows the backup file was not made from this servers database.
What do you mean by this statement ? Do you mean that the servers are on different platforms ? If so first you need to do RMAN platform conversion to able to recognize the controlfile.
If not, Can you make sure of the following
1) source and target servers are same operating system
2) source and target database homes have same versions.

Checkpointing - control file contents question

Some clarification is needed if possible...
When you commit a transaction:
- commit scn is recorded in the itl of the data block and undo segment header
- lgwr records the committed scn (for all data blocks involved) to the redo log
Checkpoint Event
- (3 seconds or possibly less passes by) CKPT wakes up and signals DBWn to write dirty (modified and committed)
blocks to disk
- CKPT records the scn of those blocks in the control file (data file and redo thread sections) and the data file
header (task of checkpoint when a log switch occurs)
- Checkpoint position in the Redo Log is forwarded
Control file contents question:
When LGWR writes the commit scn to the redo log, who writes the scn to the control file? LGWR or CKPT?
Also, when is the redo thread scn written?
Matt

Matt,
This is my understanding of the stuff. Feel free to correct me.
Checkpoint SCN , as I mentioned in my last reply is the marker of the point till which the data is "chekpointed" to the datafiles. This marker tells the controlfile that in the case of the crash, where to start recovery of the datafile and have to go which extent in the redo stream? This is only available in the datafile header and in the controlfile. This doesn't get recorded in the redo log file/stream.
I mentioned checkpoint queue in my reply too. Though I couldn't find any reference directly mentioned between this and in the checkpoint SCN but I believe my theory , if not totall, partially is correct. The incremental checkpoint is the stuff which makes the decision that how many redo blocks needs to be applied to the datafile if its closed without a proper checkpoint. So this part is maintained in the Datafile header itself in the form of the checkpoint SCN. When not matched with the conrolfile checkpoint SCN, which is always higher than this, a recovery is reported.
I hope its somewhat correct. Do let me know your views too.
Cheers
Aman....

RMAN causing "log file sync"

Hi,
Maybe someone can help me on this.
We have a RAC database in production that (for some) applications need a response of 0,5 seconds. In general that is working.
Outside of production hours we make a weekly full backup and daily incremental backup so that is not bothering us. However as soon as we make an archive backup or a backup of the control file during production hours we have a problem as the application have to wait for more then 0,5 seconds for a respons caused by the event "log file sync" with wait class "Commit".
I already adjusted the script for RMAN so that we use only have 1 files per set and also use one channel. However that didn't work.
Increasing the logbuffer was also not a success.
Increasing Large pool is in our case not an option.
We have 8 redolog groups with each 2 members ( each 250 Mb) and an average during the day of 12 logswitches per hour which is not very alarming. Even during the backup the I/O doesn't show very high activity. The increase of I/O at that moment is minor but (maybe) apperantly enough to cause the "log file sync".
Oracle has no documentation that gives me more possible causes.
Strange thing is that before the first of October we didn't have this problem and there were no changes made.
Has anyone an idea where to look further or did anyone experience a thing like this and was able to solve it?
Kind regards

The only possible contention I can see is between the log writer and the archiver. 'Backup archivelog' in RMAN means implicitly 'ALTER SYSTEM ARCHIVE LOG CURRENT' (log switch and archiving the online log).
You should alternate redo logs on different disks to minimize the effect of the archiver on the log writer.
Werner

NEED TO RECOVER A DATABASE USING RMAN with CONTROL FILE AND NO RMAN CATALOG, DISK FAILURE..

Hello All,
The disk failure caused our production data on the disk to be resotred with the backup data available and recovered through RMAN with cotrolfile , and no catalog DB is configured.
I had the restored the spfile and control file then recovered the database,
startup nomount;
RESTORE SPFILE FROM ' path ' ;
Shutdown immediate;
startup nomount
Restore controfile from autobackup;
restore database;
[AT POINT , A MESSAGE PROMPTED LIKE " failur of restored command - some targets not found" (thinking may be few archives are not found, i proceeded to incomeplete recovery of DB) ]
recover database;
Finished reocvery .
Now in the Grid control i see that 60 blocks of a particular datafile are corrupted and needs recovery. Do i need to get the data file resotred again and recover it or any simple way to recover this data file
When i perform the block recovery , it says recovery failed and when i run the data file recovery it succeeds. Please provide you inputs to recover the database as it is production BI database and pretty critical to our client.
Thanks for your valuable time in advance.
Regards,
Ran G.

These is a common problem if the object are created due to NOLOGGIN option. If you check most of the object which are facing block corruption is indexes .
Use the below query to check the objects :
It will map each block from v$database_block_corruption to either a segment or if the block is free.
$ sqlplus / as sysdba
set pagesize 2000
set linesize 250
SELECT e.owner, e.segment_type, e.segment_name, e.partition_name, c.file#
, greatest(e.block_id, c.block#) corr_start_block#
, least(e.block_id+e.blocks-1, c.block#+c.blocks-1) corr_end_block#
, least(e.block_id+e.blocks-1, c.block#+c.blocks-1)
- greatest(e.block_id, c.block#) + 1 blocks_corrupted
, null description
FROM dba_extents e, v$database_block_corruption c
WHERE e.file_id = c.file#
AND e.block_id <= c.block# + c.blocks - 1
AND e.block_id + e.blocks - 1 >= c.block#
UNION
SELECT s.owner, s.segment_type, s.segment_name, s.partition_name, c.file#
, header_block corr_start_block#
, header_block corr_end_block#
, 1 blocks_corrupted
, 'Segment Header' description
FROM dba_segments s, v$database_block_corruption c
WHERE s.header_file = c.file#
AND s.header_block between c.block# and c.block# + c.blocks - 1
UNION
SELECT null owner, null segment_type, null segment_name, null partition_name, c.file#
, greatest(f.block_id, c.block#) corr_start_block#
, least(f.block_id+f.blocks-1, c.block#+c.blocks-1) corr_end_block#
, least(f.block_id+f.blocks-1, c.block#+c.blocks-1)
- greatest(f.block_id, c.block#) + 1 blocks_corrupted
, 'Free Block' description
FROM dba_free_space f, v$database_block_corruption c
WHERE f.file_id = c.file#
AND f.block_id <= c.block# + c.blocks - 1
AND f.block_id + f.blocks - 1 >= c.block#
order by file#, corr_start_block#;
Below oracle support note will help you :
ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING - Error explanation and solution (Doc ID 794505.1)
The Gains and Pains of Nologging Operations (Doc ID 290161.1)
SQL> select d.NAME as DBF_NAME, t.NAME as TS_NAME, d.UNRECOVERABLE_CHANGE# as NOLOG_CHNG#, to_char(d.UNRECOVERABLE_TIME, 'Dy DD-Mon-YYYY HH24:MI:SS') as NOLOG_TIME from V$DATAFILE d join V$TABLESPACE t on d.TS# = t.TS# order by t.NAME;
Thanks,
gssdba.wordpress.com

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

Rman backup control file

hii i am working on oracle 10g 10.2.0.4.0 on solaris 10 have asm and rac setup(2 node rac).
i have only one control file--+DATA_DG1/ftssdb/controlfile/current.270.664476369
i am backing up these control file with rman
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/rman_node1/%F';
c-31850833-20100909-00 is a backed up piece of control file.
now suddenly one system admin deleted that control file...how can i recover my database using rman backup??

You can found these entries like :
CREATE CONTROLFILE REUSE DATABASE "DBNAME" NORESETLOGS NOARCHIVELOG ==depends what is your db log mode
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 8
MAXLOGHISTORY 800
LOGFILE
GROUP 1 '/u01/oracle/7.1.6/dbs/log1p716.dbf' SIZE 500K,
GROUP 2 '/u01/oracle/7.1.6/dbs/log2p716.dbf' SIZE 500K,
GROUP 3 '/u01/oracle/7.1.6/dbs/log3p716.dbf' SIZE 500K
DATAFILE
'/u01/oracle/7.1.6/dbs/systp716.dbf' SIZE 40M,
'/u01/oracle/7.1.6/dbs/tempp716.dbf' SIZE 550K,
'/u01/oracle/7.1.6/dbs/toolp716.dbf' SIZE 15M
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;
Edited by: user00726 on Sep 9, 2010 4:42 AM

Rman repository:control file

Hi all,
we know that rman uses target database controlfile instead of a recovery catalog.
And it stores circular reuse and non circular reuse records.
circular reuse records contains non critical information.
non circular reuse records contains critical records like datafiles and redlogs.
my quest is what the non critical information means....
am a newbie here and i didnt get exact answer in google.
thanks...
Edited by: 944850 on Sep 5, 2012 9:22 PM

hi,
got the answer.
controlfile contains two parts of memory.
One is used to store the meta data of the target database and another one is to store information about the datafiles and redolog files .
so the memory which stores the metadata will be reusable.
the meta data will be retained in this reusable memory for 7 days by default.
If we want to change the retention time, use "control_file_keep_record_time"
so we came to know that during the database open process,from mount to open the informations about the datafile and redlog file will be collected from the controlfile of the target database which is non reusable.
Thanks
Edited by: 944850 on Sep 10, 2012 9:21 PM
Edited by: 944850 on Sep 10, 2012 9:22 PM

Strange Corrupt Block Error in Control File not in CONTROL_FILES

When in RMAN connected to the TARGET and CATALOG I issue a RESYNC CATALOG I get this error:
RMAN> RESYNC CATALOG;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync command on default channel at 08/17/2009 10:36:59
ORA-00227: corrupt block detected in control file: (block 15, # blocks 1)
ORA-00202: control file: 'E:\ORACLE\PRODUCT\10.2.0\DATABASE\SNCFEBIZ01PD.ORA'
RMAN>
This control file is in the Oracle Windows default dir but I am not using it and did not create it.
My control files listed in the init.ora are:
SQL> show parameter control
NAME TYPE VALUE
control_file_record_keep_time integer 7
control_files string E:\ORACLE\ORADATA\EBIZ01PD\CNT
RL01.DBF, D:\ORACLE\ORADATA\EB
IZ01PD\CNTRL02.DBF, E:\ORACLE\
ORADATA\EBIZ01PD\CNTRL03.DBF
Any idea why this is happening?

That is a SNAPSHOT CONTROLFILE, created by RMAN as a copy of the current controlfile.
Wonder how and why the copy is corrupted ? Check the timestamp of the file to see when it was created. A RESYNC will always create a fresh Snapshot Controlfile.
See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmarchi.htm#sthref65

ORA-00245: control file backup failed; target is likely on a local file sys

Hello,
our RAC (Linux, 11.2.0.3.0) is rather new and we are still on gaining experiences with that system...
When starting the backup with RMAN we are getting the following error:
Starting Control File and SPFILE Autobackup at 04-JUL-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 07/04/2012 16:41:48
ORA-00245: control file backup failed; target is likely on a local file system
The reason for the error is clear ORA-00245 - in a RAC environment the location of the Snapshot Controlfile must be on a shared location.
When executing the RMAN command "show all" on each node, we are getting
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD021.f'; # default
for node #1
and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD022.f'; # default
for node #2
When using a shared location for the Snapshot Controlfile do we still need to setup 2 different names for that file?
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD021.f'; # default
for node #1 and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD022.f'; # default
for node #2
Or should we configure just one Snapshot Controlfile?
The RMAN setup for "CONFIGURE SNAPSHOT CONTROLFILE NAME TO..." must be changed on both nodes - correct?
Hopefully my question is clear enough - any help will be appreciated.
Rgds
JH
Edited by: VivaLaVida on 05.07.2012 11:41

No, it must be configured on a shared storage:Not really required, i've RAC setup and snapshot is configured on local storage.
Configuring the RMAN Snapshot Control File Location
The snapshot control file is a copy of a database control file created in an operating system-specific location by Recovery Manager. RMAN creates the snapshot control file so that it has a consistent version of a control file to use when either resynchronizing the recovery catalog or backing up the control file. In Oracle RAC, the snapshot control file is only needed on the nodes on which RMAN performs backups; the snapshot control file does not need to be globally available to all instances in an Oracle RAC environment.
See below from doc.
http://docs.oracle.com/cd/B28359_01/rac.111/b28254/rman.htm#i455026

Control file failed error while duplicating database using RMAN

I am using oracle database 10g R2 and trying to make a clone of the source database orcl on the same machine but with different directory structure with the name of test.
When i run the duplicate command to create test database, then following error is generted:
D:\>rman target sys@orcl nocatalog auxiliary /
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Nov 11 12:13:26 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: ORCL (DBID=1264668332)
using target database control file instead of recovery catalog
connected to auxiliary database: TEST (not mounted)
RMAN> @script.txt
RMAN> Run {
2> Allocate channel C1 type disk;
3> allocate auxiliary channel 'adisk_0' type DISK;
4> duplicate target database to "test";
5> #BACKUP INCREMENTAL LEVEL 1 DATABASE;
6> #BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE;
7> #BACKUP INCREMENTAL LEVEL 0 DATABASE;
8> #delete obsolete;
9> }
allocated channel: C1
channel C1: sid=140 devtype=DISK
allocated channel: adisk_0
channel adisk_0: sid=157 devtype=DISK
Starting Duplicate Db at 11-NOV-11
contents of Memory Script:
   set until scn 12926250;
   set newname for datafile 1 to
"D:\TEST\ORADATA\SYSTEM01.DBF";
   set newname for datafile 2 to
"D:\TEST\ORADATA\UNDOTBS01.DBF";
   set newname for datafile 3 to
"D:\TEST\ORADATA\SYSAUX01.DBF";
   set newname for datafile 4 to
"D:\TEST\ORADATA\USERS01.DBF";
   set newname for datafile 5 to
"D:\TEST\ORADATA\EXAMPLE01.DBF";
   set newname for datafile 6 to
"D:\TEST\ORADATA\GL.DBF";
   restore
   check readonly
   clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 11-NOV-11
channel adisk_0: starting datafile backupset restore
channel adisk_0: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\TEST\ORADATA\SYSTEM01.DBF
restoring datafile 00002 to D:\TEST\ORADATA\UNDOTBS01.DBF
restoring datafile 00003 to D:\TEST\ORADATA\SYSAUX01.DBF
restoring datafile 00004 to D:\TEST\ORADATA\USERS01.DBF
restoring datafile 00005 to D:\TEST\ORADATA\EXAMPLE01.DBF
restoring datafile 00006 to D:\TEST\ORADATA\GL.DBF
channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_07\O1_MF_NNND0_TAG20111107T220822_7CJ
P
channel adisk_0: restored backup piece 1
piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_07\O1_MF_NNND0_TAG20111107T220822_7CJ44MH4_.BKP tag=TAG20111107T220
channel adisk_0: restore complete, elapsed time: 00:01:46
Finished restore at 11-NOV-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
MAXLOGFILES     16
MAXLOGMEMBERS      3
MAXDATAFILES      100
MAXINSTANCES     8
MAXLOGHISTORY      292
LOGFILE
GROUP 1 ( 'D:\TEST\ORADATA\REDO01.LOG' ) SIZE 50 M REUSE,
GROUP 2 ( 'D:\TEST\ORADATA\REDO02.LOG' ) SIZE 50 M REUSE,
GROUP 3 ( 'D:\TEST\ORADATA\REDO03.LOG' ) SIZE 50 M REUSE
DATAFILE
'D:\TEST\ORADATA\SYSTEM01.DBF'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
   switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=766930525 filename=D:\TEST\ORADATA\UNDOTBS01.DBF
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=766930525 filename=D:\TEST\ORADATA\SYSAUX01.DBF
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=766930526 filename=D:\TEST\ORADATA\USERS01.DBF
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=766930526 filename=D:\TEST\ORADATA\EXAMPLE01.DBF
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=766930526 filename=D:\TEST\ORADATA\GL.DBF
contents of Memory Script:
   set until scn 12926250;
   recover
   clone database
    delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 11-NOV-11
channel adisk_0: starting incremental datafile backupset restore
channel adisk_0: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: D:\TEST\ORADATA\SYSTEM01.DBF
destination for restore of datafile 00002: D:\TEST\ORADATA\UNDOTBS01.DBF
destination for restore of datafile 00003: D:\TEST\ORADATA\SYSAUX01.DBF
destination for restore of datafile 00004: D:\TEST\ORADATA\USERS01.DBF
destination for restore of datafile 00005: D:\TEST\ORADATA\EXAMPLE01.DBF
destination for restore of datafile 00006: D:\TEST\ORADATA\GL.DBF
channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_09\O1_MF_NNND1_TAG20111109T223628_7CO
P
channel adisk_0: restored backup piece 1
piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_09\O1_MF_NNND1_TAG20111109T223628_7COGJZVT_.BKP tag=TAG20111109T223
channel adisk_0: restore complete, elapsed time: 00:00:07
channel adisk_0: starting incremental datafile backupset restore
channel adisk_0: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: D:\TEST\ORADATA\SYSTEM01.DBF
destination for restore of datafile 00002: D:\TEST\ORADATA\UNDOTBS01.DBF
destination for restore of datafile 00003: D:\TEST\ORADATA\SYSAUX01.DBF
destination for restore of datafile 00004: D:\TEST\ORADATA\USERS01.DBF
destination for restore of datafile 00005: D:\TEST\ORADATA\EXAMPLE01.DBF
destination for restore of datafile 00006: D:\TEST\ORADATA\GL.DBF
channel adisk_0: reading from backup piece D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_10\O1_MF_NNND1_TAG20111110T221428_7CR
P
channel adisk_0: restored backup piece 1
piece handle=D:\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2011_11_10\O1_MF_NNND1_TAG20111110T221428_7CR1MQFO_.BKP tag=TAG20111110T221
channel adisk_0: restore complete, elapsed time: 00:00:16
starting media recovery
archive log thread 1 sequence 524 is already on disk as file D:\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_11_11\O1_MF_1_524_7CS
C
archive log filename=D:\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2011_11_11\O1_MF_1_524_7CSG2HVT_.ARC thread=1 sequence=524
media recovery complete, elapsed time: 00:00:14
Finished recover at 11-NOV-11
contents of Memory Script:
   shutdown clone;
   startup clone nomount ;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area     230686720 bytes
Fixed Size                     1248236 bytes
Variable Size                 67109908 bytes
Database Buffers             155189248 bytes
Redo Buffers                   7139328 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "TEST" RESETLOGS ARCHIVELOG
MAXLOGFILES     16
MAXLOGMEMBERS      3
MAXDATAFILES      100
MAXINSTANCES     8
MAXLOGHISTORY      292
LOGFILE
GROUP 1 ( 'D:\TEST\ORADATA\REDO01.LOG' ) SIZE 50 M REUSE,
GROUP 2 ( 'D:\TEST\ORADATA\REDO02.LOG' ) SIZE 50 M REUSE,
GROUP 3 ( 'D:\TEST\ORADATA\REDO03.LOG' ) SIZE 50 M REUSE
DATAFILE
'D:\TEST\ORADATA\SYSTEM01.DBF'
CHARACTER SET WE8MSWIN1252
released channel: C1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/11/2011 12:16:21
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'TEST' does not match parameter db_name 'orcl'
RMAN> **end-of-file**
Script.txt
Run {
Allocate channel C1 type disk;
allocate auxiliary channel 'adisk_0' type DISK;
duplicate target database to "test";
}Kindly help?

Moazzam wrote:
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'TEST' does not match parameter db_name 'orcl'
Kindly help?>Please check what is the value of parameter db_name in the standby database? It should be match with TEST name
Cheers

Control File error while duplicating Database through Rman

Hi,
Oracle Ver: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
Os:Win Xp
I am trying to create a Standby through Rman....
I am using this Run Block to take backup of Primary Database.......
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
setlimit channel d1 kbytes 2097150;
setlimit channel d2 kbytes 2097150;
backup incremental level 0 format 'e:\Oracle\standby\rman\df_%U' database
include current controlfile for standby;
sql "alter system archive log current";
backup
archivelog all format 'e:\Oracle\standby\rman\al_%U' delete input;
}After taking the Backup when I am trying to create the standby with Duplicate command it s giving me Error...
The Run Block I am using is ......
RMAN> run {
2> allocate auxiliary channel dup1 type disk;
3> allocate auxiliary channel dup2 type disk;
4> set newname for datafile 1 to 'E:\Oracle\standby\system01.dbf';
5> set newname for datafile 2 to 'E:\Oracle\standby\UNDOTBS01.DBF';
6> set newname for datafile 3 to 'E:\Oracle\standby\SYSAUX01.DBF';
7> set newname for datafile 4 to 'E:\Oracle\standby\USERS01.DBF';
8> duplicate target database for standby
9> dorecover;
10> }
allocated channel: dup1
channel dup1: sid=37 devtype=DISK
allocated channel: dup2
channel dup2: sid=36 devtype=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 02-OCT-08
contents of Memory Script:
   set until scn 1105194;
   restore clone standby controlfile;
   sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 02-OCT-08
channel dup1: starting datafile backupset restore
channel dup1: restoring control file
channel dup1: reading from backup piece E:\ORACLE\STANDBY\RMAN\DF_0VJS4RS7_1_1
channel dup1: restored backup piece 1
piece handle=E:\ORACLE\STANDBY\RMAN\DF_0VJS4RS7_1_1 tag=TAG20081002T124502
channel dup1: restore complete, elapsed time: 00:00:01
output filename=D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\CTL1STANDBY.ORA
Finished restore at 02-OCT-08
sql statement: alter database mount standby database
released channel: dup1
released channel: dup2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/02/2008 13:01:43
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/02/2008 13:01:43
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
*ORA-00201: control file version 10.2.0.1.0 incompatible with ORACLE version 10.2.0.0.0*
ORA-00202: control file: 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\CTL1STANDBY.ORA'Why i am getting this Incomaptable Control File error inspite of Backing up the control File.....
Regards,
Prosenjit Mukherjee

Check the value for the parameter "COMPATIBLE" in the source and standby database instance parameter files.
"COMPATIBLE" should be the same.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i70517
"... ensure the COMPATIBLE initialization parameter is set to the same value on both the primary and standby databases"
Edited by: Hemant K Chitale on Oct 2, 2008 4:09 PM
Added link and quote from 10g doc

Restore from OSB. RMAN-06024: no backup or copy of the control file found

I backed up controlfile for standby on production server to OSB media:
-bash-3.00$ rman target / catalog rman/rman@emgc
Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:15:33 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: EMGC (DBID=1838014073)
connected to recovery catalog database
RMAN>
RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
BACKUP CURRENT CONTROLFILE FOR STANDBY tag 'stb_ctl';
RELEASE CHANNEL ch1;
CONFIGURE DEVICE TYPE 'SBT_TAPE' CLEAR;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> 2> 3> 4> 5> 6>
allocated channel: ch1
channel ch1: sid=1085 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
Starting backup at 25-JAN-11
channel ch1: starting compressed full datafile backupset
channel ch1: specifying datafile(s) in backupset
including standby control file in backupset
channel ch1: starting piece 1 at 25-JAN-11
channel ch1: finished piece 1 at 25-JAN-11
piece handle=1em30ngu_1_1 tag=STB_CTL comment=API Version 2.0,MMS Version 10.3.0.2
channel ch1: backup set complete, elapsed time: 00:00:27
Finished backup at 25-JAN-11
released channel: ch1
RMAN> list backup of controlfile;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
RMAN configuration parameters are successfully reset to default value
starting full resync of recovery catalog
full resync complete
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
Handle: 1em30ngu_1_1 Media: mf_rman-000003
Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
RMAN>
On standby server I try to restore this control file but there is some trouble with restore... By the way I can delete that backup piece...
-bash-3.00$ rman target / catalog rman/rman@emgc
Recovery Manager: Release 10.2.0.5.0 - Production on Tue Jan 25 15:34:32 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: emgc (not mounted)
connected to recovery catalog database
RMAN> set DBID=1838014073;
executing command: SET DBID
database name is "EMGC" and DBID is 1838014073
RMAN> RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
crosscheck backup of controlfile;
2> 3> 4> 5>
allocated channel: ch1
channel ch1: sid=1093 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
Crosschecked 1 objects
released channel: ch1
RMAN> list backup of controlfile;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1479 Full 512.00K SBT_TAPE 00:00:18 25-JAN-11
BP Key: 1480 Status: AVAILABLE Compressed: YES Tag: STB_CTL
Handle: 1em30ngu_1_1 Media: mf_rman-000003
Standby Control File Included: Ckp SCN: 33567224 Ckp time: 25-JAN-11
RMAN> RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
RESTORE CONTROLFILE FROM TAG 'STB_CTL';
2> 3> 4> 5>
allocated channel: ch1
channel ch1: sid=1093 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
Starting restore at 25-JAN-11
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/25/2011 15:35:20
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN> RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE 'SBT_TAPE';
delete noprompt backup of controlfile;
2> 3> 4> 5>
allocated channel: ch1
channel ch1: sid=1093 devtype=SBT_TAPE
channel ch1: Oracle Secure Backup
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
1480 1479 1 1 AVAILABLE SBT_TAPE 1em30ngu_1_1
deleted backup piece
backup piece handle=1em30ngu_1_1 recid=40 stamp=741367328
Deleted 1 objects
released channel: ch1
RMAN>

You cannot specify a tag for a standby control file.
read here
http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmstand.htm#1002594
Edited by: Adigozalov Gurban on Jan 25, 2011 2:14 PM

Control file and Rman

Hello,
I have 2 disctinct servers.
oracle 10gr2 in each one with the same linux red hat 4 version.
the second server is just to TEST if the backup create with the first one, works fine.
So the install in each server is exactlly the same...
same files, same path etc.
Scenario:
1 from srv one I execute a full backup with RMAN
2 I copy the file in server 2
3 I move a datafile in order to create an error
4 I test : restore database in server 2...
I get the followin error:
RMAN-03002: failure of restore command at 02/24/2008 21:15:37
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 8 found to restore
and this command return no result:
RMAN> list backupset;
RMAN>
the file created with server 1 have been copied in the declared path into server 2...
I have execute a crosscheck backup too
RMAN> crosscheck backup;
using channel ORA_DISK_1
RMAN>
Must I copy the controle file too? in this case will I have an inconsistent error?
Thanks to help
Cheers

You must have
controlfile autobackup on
(If you don't change the format it will be in $ORACLE_HOME/dbs, and the format will be c-<database id>-<yyyymmdd>_<piece>.ctl).
You must copy that file, as it has information about your most recent backup, the backup you just made.
Hth
Sybrand Bakker
Senior Oracle DBA

RMAN-06024: no backup or copy of the control file found to restore

I am cloning a new database using a full backup from previous nightly rman backup using a standby database utilizing catalog. When I run the duplicate command, I get
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/27/2011 15:04:05
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 restore
But the backup of controlfile does exists in the right place. What am I missing?

958210 wrote:
i was trying to clone a database to a remote machine, but it is giving me the following error
'RMAN-06024: no backup or copy of the control file found to restore
ORA-19505: failed to identify file "/u01/app/oracle/product/11.2.0/dbs/c-1617115651-20120912-02"
even though i can list the backup of the control file in the source machine.
thank you
'How do I ask a question on the forums?
SQL and PL/SQL FAQ
Since we don't know what you did, so we can't know what you did wrong

Rman causing control file contention

Similar Messages

Maybe you are looking for