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
Similar Messages
-
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Hi,
on 10g R2, on Win 2003
my rman backup failed (just at the end) with :
release channel 000
ORA-00230: operation disallowed: snapshot control file enqueue unavailable1-should I rerun the back up task ?
2-how to verify if this backup is correct/good ?
PS : I use nocatalog (controlfile for repository)
Thank you.1-should I rerun the back up task ?appear its failed during controlfile backup if database backup log fine than just take controlfile backup.
2-how to verify if this backup is correct/good ?in 10g ,we can see status in v$rman_status view,it also show any other running job as well.
select * from (select SID ,recid ,STATUS,operation,MBYTES_PROCESSED/1024 "GB",START_TIME,END_TIME from v$rman_status order by start_time desc) where rownum <11 -
Restoring Control file from snapshot
Hi,
As in RMAN the following configuration will create snapshot of control file.
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'product/10.2.0/dbs/snapcf_PROD.f'; # default
My question is how to restore control file from this snapshot to another location.
Regards
KrishnaCopy RMAN backup files including archive log backup files to the target server
Copy the SNAPSHOT CONTROL FILE or backed up control file from source server to target server.
Source Server:
RMAN> connect target /;
connected to target database: HRDMO (DBID=209403493034)
RMAN> show SNAPSHOT CONTROLFILE NAME;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/10g/dbs/snapcf_HRDMO.f'; # default
Target Server:
Export ORACLE_SID=HRDMO
RMAN
RMAN>startup nomount;
RMAN> set DBID=209403493034;
executing command: SET DBID
RMAN> restore controlfile from '/opt/oracle/standby/dbs/snapcf_crmprod.f'; # The location where you have it in target srvr.
RMAN>alter database mount;
RMAN> run
2> {
3> sql 'alter session set NLS_DATE_FORMAT="YYYY-MM-DD HH24:MI:SS"';
4> set until time '2008-01-31 01:00:00';
5> restore database;
6> recover database;
7> }
RMAN>alter database open resetlogs;
You have the copy of instance in the target server.
Edited by: rajeysh on Jun 23, 2010 3:34 PM -
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:41No, 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 -
RMAN> register database;
database registered in recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00206: error in writing (block 29824, # blocks 64) of control file
ORA-00202: control file: '/u01/app/oracle/product/11.2.0.2/db_1/dbs/snapcf_bibp1.f'
ORA-27072: File I/O error
Additional information: 4
Additional information: 29824
Additional information: 200704
I have created catalog server and want to configure on both node.its RAC env. bibp1 and bibp2
when am trying to register the database when give me above error.In 11.2.0.2, the Snapshot Control file must be on a Clustered File System or ASM. It cannot be on a local filesystem.
See Oracle Support Notes
RMAN Snapshot Controlfile Must Reside on Shared Device for RAC database in 11G [ID 1263621.1]
In RAC environment from 11.2 onwards Backup Or Snapshot controlfile needs to be in shared location [ID 1472171.1]
You need to :
CONFIGURE SNAPSHOT CONTROLFILE NAME TO <shared_location_file>;Hemant K Chitale -
Need of configure snapshot ctl file ???
why i need to Configure snapshot controlfile ??
this is a temporary file used by rman for read consistenacy.
<As Per oracle DOC>
RMAN needs to resynchronize from a read-consistent version of the control file, it creates a temporary snapshot control file.
Thanks
Kuljeet Pal Singh -
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 -
Job output is no longer available in the database control file
Im running my rman backup with Oracle Enterprise manager grid control 10.2.0.1.
In nocatalog mode.
When I look for the job output in the "View Backup Report" section, it says
Job output is no longer available in the database control file.
Here is my rman setup:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 7;
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 '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;
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 '/opt/oracle/app/oracle/product/10.2.0/db_1/dbs/snapcf_mus_prod.f'; # default
anyone knows why i cannot see my rman job output?show parameter control_file_record_keep_time;
NAME TYPE VALUE
control_file_record_keep_time integer 7
The backup is usually the last one. And it's the day before.
If i go to the JOB tab in oem, then click on the job detail, i can see the detail of my rman backup. But i cannot see the backup detail in the View Backup Report section off the database. It says the error message : Job output is no longer available in the database control file -
Control File and SPFILE Autobackup command struck
O.S Version:
Linux Version "Red Hat Enterprise Linux Server release 6.2 (Santiago)
Linux version 2.6.32-220.13.1.el6.x86_64 ([email protected]) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Thu Mar 29 11:46:40 EDT 2012
2.6.18-308.16.1.el5 x86_64
Tape Archiver : HP Data Protector
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Problem :
In one of our environment, OEM grid 11g scheduled Level 0 backup struck at the Control File and SPFILE Autobackup.
RMAN Script:
run {
2> backup format '<%d_%s:%t:%p:%f>.df' incremental level 0 cumulative database;
3> sql 'alter system archive log current';
4> backup format '<%d_%s:%t:%p>.al' archivelog all not backed up;
5> }
RMAN Configuration
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TestDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 45 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'TestDB_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'TestDB_%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TestDB,OB2BARLIST=Siv_ORA_TESTSrvr1_TestDB_DB,OB2BARHOSTNAME=TESTSrvr1)';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DG_TestDB_UAT_DATA_01/TestDB/TEMPFILE/snapcf_TestDB.f';
RMAN Log:
1. Backup started at 07-SEP-2013 07:09:46
Finished backup at 07-SEP-2013 07:16:38
Wherein the Control file backup started at 07-SEP-2013 07:16:38 failed at 09/07/2013 12:44:38. It kept struck for 5 Hours.
Starting backup at 07-SEP-2013 07:09:46
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=250 instance=TestDB device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protector A.06.20/370
allocated channel: ORA_SBT_TAPE_2
Finished backup at 07-SEP-2013 07:16:38
Starting Control File and SPFILE Autobackup at 07-SEP-2013 07:16:38
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_SBT_TAPE_1 channel at 09/07/2013 12:44:38
ORA-19506: failed to create sequential file, name="TestDB_c-2078060264-20130907-ff", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: Cannot find requested element ERR(-2)
ORACLE error from recovery catalog database: ORA-03113: end-of-file on communication channel
Process ID: 2045
Session ID: 89 Serial number: 36509
RMAN> delete noprompt archivelog all backed up 1 times to sbt;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 09/07/2013 13:00:07
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE
RMAN> **end-of-file**
Why does the RMAN Backup struck at Controlfile , SPFile autobackup?Hello;
I believe the issue is caused by your media management software. You should contact your media management vendor.
Try the same operation to disk and I bet it works.
Best Regards
mseberg -
Control File Sequential Read in 11.2
Hi to all,
i'm in 11.2 database and i'm looking an awr report.
Time:
Begin Snap: 9642 31-Gen-12 16:00:26 51 2.5
End Snap: 9643 31-Gen-12 16:40:27 52 2.6 This is my load profile:
Load Profile Per Second Per Transaction Per Exec Per Call
~~~~~~~~~~~~ --------------- --------------- ---------- ----------
DB Time(s): 0.2 0.3 0.01 0.02
DB CPU(s): 0.1 0.1 0.00 0.01
Redo size: 2,989.8 4,490.0
Logical reads: 1,823.2 2,738.1and this is the wait:
Top 5 Timed Foreground Events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg
wait % DB
Event Waits Time(s) (ms) time Wait Class
DB CPU 120 32.5
direct path read 110,371 40 0 11.0 User I/O
db file sequential read 10,026 20 2 5.5 User I/O
control file sequential read 27,409 11 0 3.1 System I/OWhy i've too high control file sequential read?
I've read note 941761.1 and i've traced a session that create snapshot to see if there is
a table that generate to many wait.
This is the end of the trace:
OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
call count cpu elapsed disk query current rows
Parse 420 0.07 0.34 0 0 8 0
Execute 852 1.19 5.70 128 2446 4602 5870
Fetch 1537 0.28 1.18 31 6939 4 1378
total 2809 1.54 7.23 159 9385 4614 7248
Misses in library cache during parse: 215
Misses in library cache during execute: 209
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
Disk file operations I/O 25 0.00 0.00
db file sequential read 178 0.32 2.00
control file sequential read 169 0.02 0.13
asynch descriptor resize 73 0.00 0.00
CSS initialization 2 0.01 0.01
CSS operation: action 2 0.01 0.02
CSS operation: query 6 0.00 0.00
kfk: async disk IO 5 0.00 0.00
direct path write 5 0.00 0.00Any ideas?Just to expand on the previous answer - your database isn't doing anything.
This is an AWR report for a 40 minute period.
You've accumulated a few seconds worth of work.
Nothing happening.
There will always be a top 5. -
RECREATE DATABASE Using CONTROL File After SUSPEND Database
Hello All,
Does someone can tell me if he does achieve recreating a database using "Backup Control File" after putting database in "suspend" mode?
The procedure looks like this :
1 - Alter DATABASE Suspend
2 - A Snapshot of the filesystem where the oracle datafile are located
3 - Copy of those files to another file systeme
4 - Startup setting a new database name
Does someone as do it successfully ?
Thanks for your answerCarlos,
I tried to do it without putting the tablespaces in backup mode and it didn't work for me. At that time adding the backup mode wasn't a big deal for me, so I didn't investigate the problem thoroughly.
Logically thinking you sould be able to do:
1. suspend database
the SCNs recored in datafiles headers could be incosistent at this point
2. make a snapshot
3. mount the backup database
4. run recover until cancel using backup controlfile - I don't think you can avoid this step in case if you have inconsistent SCNs in the datafiles headers - you'll need to synchronize them
5. open resetlogs.
the suspend database should eliminate the possibility of inconsistent data within a block during the backup.
Just out of curiosity - why don't you want to put the tablespace in the backup mode?
Mike -
Control file backup is hung.
Hi,
When I initiate control file backup it is struck. Pls. see my Rman configuration.
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/rmanbkup/cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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 DISK FORMAT '/oracle/rmanbkup/%U';
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 '/oracle/S01/102_64/dbs/snapcf_S01.f'; # default
RMAN> backup current controlfile;
Starting backup at 28-JUN-09
using channel ORA_DISK_1
It is in this situation since 4 Hrs.
I had set all the permissions as mentioned in the SAP Note : 113747. Backup was happening as normal till 25th June thru DB13.
My observation is, I had alter the oracle parameter as per the quiry results. ( i.e added the events .. I had executed the script attached in the S.Note : 1171650. ST04 --> Performance --> Additional Function --> SQL Command Editor )
O/S : AIX 5.3,
DB : Oracle 10.2.0.2.0
ECC 6.0
Backup in all other servers are happening without any problem..
I appreciate your expert suggestions.
Thanks!
Sundaresh SuryanarayanHi Surendara Jain,
Still this problem persisting.. I have tried all.. I checked all the relevent S-Notes. I updated the brtools version also..
Even if I execute BRBACKUP it starts.. It creates the folder. But, the folder will be empty.. Pls. see the *.and file below..
MBES01:oras01 10> more beayrvav.and
BR0051I BRBACKUP 7.00 (41)
BR0055I Start of database backup: beayrvav.and 2009-07-07 08.12.17
BR0484I BRBACKUP log file: /oracle/S01/sapbackup/beayrvav.and
BR0477I Oracle pfile /oracle/S01/102_64/dbs/initS01.ora created from spfile /oracle/S01/102_64/dbs/spfileS01.ora
BR0101I Parameters
Name Value
oracle_sid S01
oracle_home /oracle/S01/102_64
oracle_profile /oracle/S01/102_64/dbs/initS01.ora
sapdata_home /oracle/S01
sap_profile /oracle/S01/102_64/dbs/initS01.sap
backup_mode ALL
backup_type online
backup_dev_type disk
backup_root_dir /oracle/S01/sapbackup
compress no
disk_copy_cmd rman
cpio_disk_flags -pdcu
exec_parallel 0
rman_compress no
system_info oras01/oras01 MBES01 AIX 3 5 00CD16724C00
oracle_info S01 10.2.0.2.0 8192 2959 21202296 MBES01 UTF8 UTF8
sap_info 700 SAPSR3 0002LK0003S010011E21297128880015Maintenance_ORA
make_info rs6000_64 OCI_102 Apr 8 2009
command_line /usr/sap/S01/SYS/exe/run/brbackup -p initS01.sap -d disk -t online -m all -k no -e 0 -o dist,time -l E -U
BR0116I ARCHIVE LOG LIST before backup for database instance S01
Parameter Value
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/S01/oraarch/S01arch
Archive format %t_%s_%r.dbf
Oldest online log sequence 2956
Next log sequence to archive 2959
Current log sequence 2959 SCN: 21202296
Database block size 8192 Thread: 1
Current system change number 21209894 ResetId: 674792151
BR0118I Tablespaces and data files
Tablespace TS-Status F-Status File Size Id. Device Link Type
MaxSize IncrSize BlkSize
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_1/sr3.data1 2579505152 4 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_10/sr3.data10 1069555712 13 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_2/sr3.data2 2558533632 5 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_3/sr3.data3 3334479872 6 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_4/sr3.data4 3984596992 7 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_5/sr3.data5 3166707712 8 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_6/sr3.data6 2998935552 9 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_7/sr3.data7 2977964032 10 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_8/sr3.data8 2852134912 11 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_9/sr3.data9 2810191872 12 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_1/sr3700.data1 3523223552 14 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_2/sr3700.data2 4299169792 15 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_3/sr3700.data3 3607109632 16 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_4/sr3700.data4 3428851712 17 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3db_1/sr3db.data1 2097160192 19 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3db_2/sr3db.data2 2097160192 20 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3db_3/sr3db.data3 1048584192 21 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3USR ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3usr_1/sr3usr.data1 20979712 18 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPTEMP ONLINE# ONLINE+ /oracle/S01/sapdata1/temp_1/temp.data1 1017126912 -1 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPUNDO ONLINE- ONLINE+ /oracle/S01/sapdata1/undo_1/undo.data1 2705334272 2 3276802 NOLINK FILE 104
85760000 20971520 8192
SYSAUX ONLINE* ONLINE+ /oracle/S01/sapdata1/sysaux_1/sysaux.data1 230694912 3 3276802 NOLINK FILE 104
85760000 20971520 8192
SYSTEM ONLINE* SYSTEM+ /oracle/S01/sapdata1/system_1/system.data1 513810432 1 3276802 NOLINK FILE 104
85760000 20971520 8192
BR0119I Redo log files
File Size Group Device Status Link Type
/oracle/S01/origlogA/log_g11m1.dbf 52429312 1 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogA/log_g11m2.dbf 52429312 1 3276802 INUSE NOLINK FILE
/oracle/S01/origlogB/log_g12m1.dbf 52429312 2 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogB/log_g12m2.dbf 52429312 2 3276802 INUSE NOLINK FILE
/oracle/S01/origlogA/log_g13m1.dbf 52429312 3 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogA/log_g13m2.dbf 52429312 3 3276802 INUSE NOLINK FILE
/oracle/S01/origlogB/log_g14m1.dbf 52429312 4 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogB/log_g14m2.dbf 52429312 4 3276802 INUSE NOLINK FILE
BR0120I Control files
File Size Id. Device Link Type
/oracle/S01/origlogA/cntrl/cntrlS01.dbf 14368768 0 3276802 NOLINK FILE
/oracle/S01/origlogB/cntrl/cntrlS01.dbf 14368768 0 3276802 NOLINK FILE
/oracle/S01/sapdata1/cntrl/cntrlS01.dbf 14368768 0 3276802 NOLINK FILE
BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:
PSAPSR3, PSAPSR3700, PSAPSR3USR
BR0379I Distribution of files on volume #1:
Position Size Rate Compressed Duration Speed Name
[m:s] [MB/h]
1 2579505152* 2:19 63712 /oracle/S01/sapdata2/sr3_1/sr3.data1
2 1069555712* 0:59 62238 /oracle/S01/sapdata2/sr3_10/sr3.data10
3 2558533632* 2:19 63194 /oracle/S01/sapdata2/sr3_2/sr3.data2
4 3334479872* 2:48 68143 /oracle/S01/sapdata2/sr3_3/sr3.data3
5 3984596992* 3:19 68744 /oracle/S01/sapdata2/sr3_4/sr3.data4
6 3166707712* 2:49 64332 /oracle/S01/sapdata2/sr3_5/sr3.data5
7 2998935552* 2:38 65165 /oracle/S01/sapdata2/sr3_6/sr3.data6
8 2977964032* 2:39 64302 /oracle/S01/sapdata2/sr3_7/sr3.data7
9 2852134912* 2:28 66162 /oracle/S01/sapdata2/sr3_8/sr3.data8
10 2810191872* 2:29 64752 /oracle/S01/sapdata2/sr3_9/sr3.data9
11 3523223552* 2:49 71574 /oracle/S01/sapdata3/sr3700_1/sr3700.data1
12 4299169792* 3:38 67707 /oracle/S01/sapdata3/sr3700_2/sr3700.data2
13 3607109632* 3:09 65524 /oracle/S01/sapdata3/sr3700_3/sr3700.data3
14 3428851712* 2:48 70072 /oracle/S01/sapdata3/sr3700_4/sr3700.data4
15 2097160192* 1:59 60504 /oracle/S01/sapdata4/sr3db_1/sr3db.data1
16 2097160192* 1:58 61017 /oracle/S01/sapdata4/sr3db_2/sr3db.data2
17 1048584192* 0:59 61017 /oracle/S01/sapdata4/sr3db_3/sr3db.data3
18 20979712* 0:06 12005 /oracle/S01/sapdata4/sr3usr_1/sr3usr.data1
19 2705334272* 2:19 66820 /oracle/S01/sapdata1/undo_1/undo.data1
20 230694912* 0:19 41686 /oracle/S01/sapdata1/sysaux_1/sysaux.data1
21 513810432* 0:38 46422 /oracle/S01/sapdata1/system_1/system.data1
22 14368768 0:00 0* /oracle/S01/sapbackup/cntrlS01.dbf
Total: 51919052800* 45:29 65317
BR0284I BRBACKUP time stamp: 2009-07-07 08.12.19, elapsed time: 0:00
BR0057I Backup of database: S01
BR0058I BRBACKUP action ID: beayrvav
BR0059I BRBACKUP function ID: and
BR0110I Backup mode: ALL
BR0077I Database file for backup: /oracle/S01/sapbackup/cntrlS01.dbf
BR0061I 22 files found for backup, total size 49513.867 MB
BR0143I Backup type: online
BR0112I Files will not be compressed
BR0130I Backup device type: disk
BR0106I Files will be saved on disk in directory: /oracle/S01/sapbackup/beayrvav
BR0284I BRBACKUP time stamp: 2009-07-07 08.12.19, elapsed time: 0:00
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
BR0284I BRBACKUP time stamp: 2009-07-07 08.12.54, elapsed time: 0:35
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0370I Directory /oracle/S01/sapbackup/beayrvav created
end **************************************************
it won't move furthe after this.. I checked and compared SPFILE & init<SID>.sap with other servers (DEV,QA & PRD) all are same.. But, backup is happening on those server without any problem.
Can anybody help me on this..
Thanks!
Sundaresh Suryanarayan -
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 -
Error while creating control file
hi
i am getting following error while creating controll file
QL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 629145600 bytes
Fixed Size 1250548 bytes
Variable Size 171969292 bytes
Database Buffers 452984832 bytes
Redo Buffers 2940928 bytes
SQL> @c:\study\rose\c.sql
SP2-0042: unknown command "DATAFILE" - rest of line ignored.
SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
SP2-0734: unknown command beginning "CHARACTER ..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
1 CREATE CONTROLFILE SET DATABASE "ROSE" RESETLOGS froce logging NOARCHIVELOG
2 MAXLOGFILES 32
3 MAXLOGMEMBERS 2
4 MAXDATAFILES 32
5 MAXINSTANCES 16
6 MAXLOGHISTORY 1752
7 LOGFILE
8 GROUP 1 'C:\oracle\product\10.2.0\oradata\rose\LOG1ROSE.ORA' SIZE 50M,
9 GROUP 2 'C:\oracle\product\10.2.0\oradata\rose\LOG2ROSE.ORA' SIZE 50M,
10 GROUP 3 'C:\oracle\product\10.2.0\oradata\rose\LOG06.LOG' SIZE 25M,
11* GROUP 4 'C:\oracle\product\10.2.0\oradata\rose\LOG07.LOG' SIZE 25M
SQL>CHETAN YADAV wrote:
hi
i am getting following error while creating controll file
QL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 629145600 bytes
Fixed Size 1250548 bytes
Variable Size 171969292 bytes
Database Buffers 452984832 bytes
Redo Buffers 2940928 bytes
SQL> @c:\study\rose\c.sqlWe can't debug what we can't see. And what we can't see is the contents of "c:\study\rose\c.sql".
SP2-0042: unknown command "DATAFILE" - rest of line ignored.
SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
SP2-0734: unknown command beginning "CHARACTER ..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
1 CREATE CONTROLFILE SET DATABASE "ROSE" RESETLOGS froce logging NOARCHIVELOG
2 MAXLOGFILES 32
3 MAXLOGMEMBERS 2
4 MAXDATAFILES 32
5 MAXINSTANCES 16
6 MAXLOGHISTORY 1752
7 LOGFILE
8 GROUP 1 'C:\oracle\product\10.2.0\oradata\rose\LOG1ROSE.ORA' SIZE 50M,
9 GROUP 2 'C:\oracle\product\10.2.0\oradata\rose\LOG2ROSE.ORA' SIZE 50M,
10 GROUP 3 'C:\oracle\product\10.2.0\oradata\rose\LOG06.LOG' SIZE 25M,
11* GROUP 4 'C:\oracle\product\10.2.0\oradata\rose\LOG07.LOG' SIZE 25M
SQL> -
In case of Control File Failure, Create Control File cmd how get scn?
The following lines i picked from the
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:5033895918209
======================================================
1. We can use the 'alter database rename ' at mount stage to rename any datafile. Or is it not possible to rename the system datafile like this? Why?
2. What happens to the SCN information in the controlfile when a controlfile is recreated? How will the database sync the SCN with that of the datafiles?
If I issue a 'backup controlfile to <file>' at 8 am and then restore that controlfile binary backup at 10 am and try to open the database, it will give me a control file old error. I understand that it is because the SCN is not in sync. But if I issue a 'backup controlfile to trace' at 8 am and use that script to recreate a new controlfile at 10 am, why doesn't I get the error? Where does it get the SCN information then?
So what is the use of taking a binary copy of the controlfile. Looks like having a 'backup controlfile to trace' script is better than a binary backup. Do you agree? Why/whynot?
Followup August 16, 2002 - 2pm US/Eastern:
1) you could but I just always did it with the create controlfile statement.
When moving system -- I do it that way
When moving ANY OTHER tablespace -- i just offline it, move the files, rename the files online it.
2) it just happens.
The control file you create will read the files to figure out what is up.
I agree, I've never used a binary controlfile backup myself.
=========================================================
My Question- In the Point2 above "Where does it get the SCN information and how control file do SCN Sync with data files?
"1. The CREATE CONTROLFILE reads SCNs from the DataFiles. If the
database was last shutdown, all the datafiles are "non-fuzzy" and have the same
SCN (as of the shutdown checkpoint), If the database or some of the files are from
are hot backup, you cannot open the database because the SCN of some files is
older (lower) than others -- that is why a RECOVER (DATABASE or DATAFILE) is
required.
See http://web.singnet.com.sg/~hkchital/Incomplete_Recovery_with_BackupControlfile.doc
2. I'm not sure I agree with Tom Kyte's response
"I agree, I've never used a binary controlfile backup myself. "
to the question
"So what is the use of taking a binary copy of the controlfile. Looks like having a 'backup controlfile to trace' script is better than a binary backup. Do you agree? Why/whynot?"
If you have lost your database (storage/filesystem failure) and all your datafiles are lost,
you cannot simply do a CREATE CONTROLFILE from a Trace -- because the
CREATE CONTROLFILE has to read and verify all the datafiles specified in the
CREATE statement. If you have an RMAN Repository, you can use that to restore
your database files but otherwise, the RMAN information about backups and backupsets
are in the binary controlfile.
That is why it is important to take binary controlfile backups either manually or
using RMAN or using CONFIGURE CONTROLFILE AUTOBACKUP ON.
Maybe you are looking for
-
I upgraded to PE 9.0 (with updates) after a very frustrating experience with PE 8.0. Was looking forward to having so many problems fixed. PE 9.0 just presents a host of new problems! I am having 2 issues right now: 1) I followed Steve Grisetti's adv
-
Error when connecting to system
Hi, I have been off topic for quite a while and when I wanted to pick up today, I couldn't connect to the HANA server anymore. I haven't changed any settings since last setup, all I get is the "Error when connecting to system" in the Quick Lauch of t
-
Max. no. of sessions reached - using ITS on WAS
Hi All, We are facing an issue wherein whenever we try to create a new session in SAP GUI we are getting an error saying "Maximum no. of sessions reached" We are using ITS on WAS(webgui) i.e.using the WAS URL we are signing in where we can see the SA
-
Installing License in Solution Manager 4.0 - SAP BASIS 7.0
Hi, I installed SAP Solution Manager, I request my unlimited license at SAP Marketplace, they send me the file, however in slicense transaction - New licenses I load my file and no errors show me. However when finish load of file, license status is n
-
How to access the Microsoft Dynamics database tables for creating a DW
Hi all, I m trying to build a POC for the manufacturing industry (Dairy Industry). Hence I'm trying to install Microsoft Dynamics and access the tables available its OLTP and create a warehouse. Please let me know how we access the database tables of