首遇ORA-00245
今天看A类和B类的數據庫的日誌裏面都出現了如下錯誤：
節點1日誌：
Tue Jul 31 03:02:50 2012
Errors in file/soft/oracle/diag/rdbms/a1qzdb/a1qzdb1/trace/a1qzdb1_ora_5374100.trc:
ORA-00245: control file backup operation failed
Tue Jul 31 09:08:37 2012
Thread 1 advanced to log sequence 346 (LGWRswitch)
Current log# 1 seq# 346 mem# 0:+DATA/a1qzdb/onlinelog/group_1.259.786961989
Tue Jul 31 09:08:37 2012
LNS: Standby redo logfile selected forthread 1 sequence 346 for destination LOG_ARCHIVE_DEST_2
Tue Jul 31 09:08:40 2012
Archived Log entry 1132 added for thread 1sequence 345 ID 0x1f7e84e dest 1:
Tue Jul 31 09:27:34 2012
Control file backup creation failed.
Backup target file size found to be zero.
Errors in file/soft/oracle/diag/rdbms/a1qzdb/a1qzdb1/trace/a1qzdb1_arc2_15073292.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
節點2日誌：
Tue Jul 31 03:02:50 2012
Control file backup creation failed.
Backup target file size found to be zero.
Errors in file/soft/oracle/diag/rdbms/a1qzdb/a1qzdb2/trace/a1qzdb2_ckpt_7602620.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No suchfile or directory
Additional information: 3
Tue Jul 31 09:16:27 2012
Thread 2 advanced to log sequence 284 (LGWRswitch)
Current log# 6 seq# 284 mem# 0:+DATA/a1qzdb/onlinelog/group_6.275.786964219
Tue Jul 31 09:16:27 2012
LNS: Standby redo logfile selected forthread 2 sequence 284 for destination LOG_ARCHIVE_DEST_2
Tue Jul 31 09:16:30 2012
Archived Log entry 1134 added for thread 2sequence 283 ID 0x1f7e84e dest 1:
Tue Jul 31 09:27:29 2012
Expanded controlfile section 19 from 818 to1636 records
Requested to grow by 818 records; added 2blocks of records
Tue Jul 31 09:27:34 2012
Errors in file/soft/oracle/diag/rdbms/a1qzdb/a1qzdb2/trace/a1qzdb2_ora_15204484.trc:
ORA-00245: control file backup operation failed
相應的trace日誌：
/soft/oracle/diag/rdbms/a1qzdb/a1qzdb1/trace/a1qzdb1_ora_5374100.trc:
*** 2012-07-31 03:02:50.674
*** SESSION ID:(541.7217) 2012-07-3103:02:50.675
*** CLIENT ID:() 2012-07-31 03:02:50.675
*** SERVICE NAME:(SYS$USERS) 2012-07-3103:02:50.675
*** MODULE NAME:(rman@qza1db1 (TNS V1-V3))2012-07-31 03:02:50.675
*** ACTION NAME:(0000011 STARTED114)2012-07-31 03:02:50.675
/soft/oracle/diag/rdbms/a1qzdb/a1qzdb1/trace/a1qzdb1_arc2_15073292.trc:
ORA-00245: control file backup operationfailed
*** 2012-07-31 09:27:34.107
IBM AIX RISC System/6000 Error: 2: No suchfile or directory
Additional information: 3
/soft/oracle/diag/rdbms/a1qzdb/a1qzdb2/trace/a1qzdb2_ckpt_7602620.trc:
*** 2012-07-31 09:27:34.382
*** SESSION ID:(885.58917) 2012-07-3109:27:34.383
*** CLIENT ID:() 2012-07-31 09:27:34.383
*** SERVICE NAME:(SYS$USERS) 2012-07-3109:27:34.383
*** MODULE NAME:(rman@qza1db2 (TNS V1-V3))2012-07-31 09:27:34.383
*** ACTION NAME:(0000021 STARTED114)2012-07-31 09:27:34.383
ORA-00245: control file backup operationfailed
/soft/oracle/diag/rdbms/a1qzdb/a1qzdb2/trace/a1qzdb2_ora_15204484.trc:
*** 2012-07-31 03:02:50.508
IBM AIX RISC System/6000 Error: 2: No suchfile or directory
Additional information: 3
Google了一下，發現這是Oracle11.2.0.2.0以後的一個“特性”：
从oracle 11.2.0.2.0开始，控制文件的快照文件必须能够被所有节点的数据实例访问到，并且必须放在共享的位置。否则，使用RMAN进行备份控制文件的时候会报如下错误：
ORA-00245: control file backup operationfailed。
当使用备份脚本备份的时候，这个错误可能会导致备份工作中断。
METALINK 中的两篇文档：
RAC BACKUP FAILS WITH ORA-00245: CONTROLFILE BACKUP OPERATION FAILED [ID1268725.1]【這篇文字沒找到】
RMAN Snapshot Controlfile Must Reside onShared Device for RAC database in 11G [ID 1263621.1]【這篇文字沒找到】
解释并解决了此问题！摘要如下：
"RMAN creates a copy of the controlfile for read consistency, this is the snapshot controlfile. Due to the changesmade to the controlfile backup mechanism in 11gR2 any instances in the clustermay write to the snapshot controlfile. Therefore, the snapshot controlfile fileneeds to be visible to all instances.
The same happens when a backup of thecontrolfile is created directly from sqlplus any instance in the cluster maywrite to the backup controfile file.
In 11gR2 onwards, the controlfile backuphappens without holding the control file enqueue. For non-RAC database, thisdoesn't change anything.
But, for RAC database, the snapshotcontrolfile location must be in a shared file system that will be accessible fromall the nodes."
当前的控制文件配置：
RMAN> show all;
using target database control file insteadof recovery catalog
RMAN configuration parameters for databasewith db_unique_name OSDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;# default
CONFIGURE BACKUP OPTIMIZATION OFF; #default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; #default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; #default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FORDEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICETYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FORDEVICE 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' ASOF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TONONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO'/soft/product/11.2.0.2/dbh/dbs/snapcf_osdb1.f'; # default
由於我們使用的是ASM，所以可以使用如下配置解决此问题，也可以把ASM替換成共享目錄：
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+SFRA/sncforcl_osdb.ora';
new RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+SFRA/sncforcl_osdb.ora';
new RMAN configuration parameters aresuccessfully stored
RMAN> show all;
RMAN configuration parameters for databasewith db_unique_name OSDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;# default
CONFIGURE BACKUP OPTIMIZATION OFF; #default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; #default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; #default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FORDEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICETYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FORDEVICE 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' ASOF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TONONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+SFRA/sncforcl_osdb.ora';
附件：
| In RAC environment from 11.2 onwards Backup Or Snapshot controlfile needs to be in shared location [ID 1472171.1] |
||
|
|
||
|
|
修改时间 13-JUL-2012 类型 ALERT 状态 PUBLISHED |
|
In this Document
| Description |
| Occurrence |
| Symptoms |
| Workaround |
| Patches |
| History |
| References |
Applies to:
Oracle Server - Enterprise Edition - Version 11.2.0.1.0 and later
Information in thisdocument applies to any platform.
This issue is onlyapplicable to RAC database.
From 11gR2 onwards,the controlfile backup happens without holding the controlfile enqueue. Fornon-RAC database, this doesn't change anything. But for RAC database, due tothe changes made to the controlfile backup mechanism in 11gR2, any instance inthe cluster may write to the snapshot controlfile. Due to this snapshotcontrolfile need to be visible to all instances.
The snapshotcontrolfile MUST be accessible by all nodes of a RAC database, if the snapshotcontrolfile does not reside on a shared device error will be raised at the timeof RMAN backup while taking snapshot of controlfile.
This applies tobacking up controlfile using sqlplus / having autobackup of controlfileconfigured on non
shared location.
ORA-245 errormessage description
----------------------------------------
00245, 00000,"control file backup operation failed"
*Cause: Failed tocreate a control file backup because some process
signaled an errorduring backup creation.
*Action: Checkalert files for further information. This usually happens
because someprocess could not access the backup file during
backup creation.Any process of any instance that starts a
read/write controlfile transaction must have an access to the
backup control fileduring backup creation.
Description
1. In RACenvironment controlfile autobackup fails with ora-0245
Autobackupof controlfile in RMAN is failing with error:
RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-3009: failure of Control File and SPFILE Autobackup command on
ORA_DISK_1 channel at 10/27/2010 12:13:31
ORA-245: control file backup operation failed
2. In RAC environment, backupcontrolfile to non shared location fails
SQL>ALTER DATABASE BACKUP CONTROLFILE TO '/home/rac1122/test/control.bk' REUSE
*
ERROR at line 1:
ORA-245: control file backup operation failed
3. In RAC environment backing upstandby controlfile to non shared location fails
SQL>alter database create standby controlfile as '/home/oracle/renostdbycntrl.ctl';
alterdatabase create standby controlfile as
'/home/oracle/renostdbycntrl.ctl'
*
ERROR at line 1:
ORA-245: control file backup operation failed
4. In RAC environment copy currentcontrolfile to '${DB_BACKUP_DIR}/rac_tnctv_control.bak';
channelch1: starting datafile copy
copying current control file
RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-3009: failure of backup command on 10/07/2011 11:36:42 channel at ch1
ORA-245: control file backup operation failed
5. In RAC environment, Rman backupfails if snapshot controlfile is not in shared location.
RMAN-00571:========================================================
RMAN-00569: ============ ERROR MESSAGE STACK FOLLOWS =============
RMAN-00571: =========================================================
RMAN-03009: failure of resync command on default channel at 03/13/2012 10:19:41
ORA-00245: control file backup operation failed
Occurrence
Only affect Real application Cluster (RAC ), 11.2 specific.
Symptoms
In RAC environment any form of controlfile backup may failwith ORA-0245 if the location of the Snapshot Controlfile is not a sharedlocation.
The backup of the controlfile actualy makes a backup of theSNAPSHOT controlfile. The Snapshot controlfile is created when the controlfileis about to be backed up.
The Snapshot controlfile is a read-consistent copy of thecontrolfile.
Workaround
It is changed behaviour which requires that the snapshotcontrolfile in a RAC environment, is on a shared location.
1. Check the snapshot controlfile location:
RMAN> show snapshot controlfile name;
2. Configure the snapshot controlfile to a shared disk:
RMAN>CONFIGURE SNAPSHOT CONTROLFILE NAME TO'<shared_disk>/snapcf_<DBNAME>.f';
Or in case of ASM use
RMAN>CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+<DiskGroup>/snapcf_<DBNAME>.f';
Patches
NA
History
02-07-2012created and Published alert