ORA-00245: control file backup operation failed

今天朋友巡检遇到了ORA-00245的报错，下面来看看MOS关于RAC环境中ORA-00245报错的说明。ORA-245: In RAC environment from 11.2 onwards Backup Or Snapshot controlfile needs to be in shared location (文档 ID 1472171.1)修改时间:2013-11-11类型:ALERTIn this DocumentDescriptionOccurrenceSymptomsWorkaroundPatchesHistoryReferencesAPPLIES TO:Oracle Database – Enterprise Edition – Version 11.2.0.1.0 and laterInformation in this document applies to any platform.This issue is only applicable to RAC database.From 11gR2 onwards, the controlfile backup happens without holding the controlfile enqueue. For non-RAC database, this doesn’t change anything. But for RAC database, due to the changes made to the controlfile backup mechanism in 11gR2, any instance in the cluster may write to the snapshot controlfile. Due to this snapshot controlfile need to be visible to all instances.The snapshot controlfile MUST be accessible by all nodes of a RAC database, if the snapshot controlfile does not reside on a shared device error will be raised at the time of RMAN backup while taking snapshot of controlfile.This applies to backing up controlfile using sqlplus / having autobackup of controlfile configured on nonshared location.ORA-245 error message description—————————————-00245, 00000, “control file backup operation failed”*Cause: Failed to create a control file backup because some processsignaled an error during backup creation.*Action: Check alert files for further information. This usually happensbecause some process could not access the backup file duringbackup creation. Any process of any instance that starts aread/write control file transaction must have an access to thebackup control file during backup creation.DESCRIPTION1. In RAC environment controlfile autobackup fails with ora-0245Autobackup of 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:31ORA-245: control file backup operation failed2. In RAC environment, backup controlfile to non shared location fail免费云主机域名sSQL> ALTER DATABASE BACKUP CONTROLFILE TO ‘/home/rac1122/test/control.bk’ REUSE*ERROR at line 1:ORA-245: control file backup operation failed3. In RAC environment backing up standby controlfile to non shared location failsSQL> alter database create standby controlfile as ‘/home/oracle/renostdbycntrl.ctl’;alter database create standby controlfile as ‘/home/oracle/renostdbycntrl.ctl’*ERROR at line 1:ORA-245: control file backup operation failed4. In RAC environment copy current controlfile to ‘${DB_BACKUP_DIR}/rac_tnctv_control.bak’;channel ch2: starting datafile copycopying current control fileRMAN-571: ===========================================================RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-571: ===========================================================RMAN-3009: failure of backup command on 10/07/2011 11:36:42 channel at ch2ORA-245: control file backup operation failed5. In RAC environment, Rman backup fails 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:41ORA-00245: control file backup operation failedOCCURRENCEOnly affect Real application Cluster (RAC ), 11.2 specific.SYMPTOMSIn RAC environment any form of controlfile backup may fail with ORA-0245 if the location of the Snapshot Controlfile is not a shared location.The backup of the controlfile actualy makes a backup of the SNAPSHOT controlfile. The Snapshot controlfile is created when the controlfile is about to be backed up.The Snapshot controlfile is a read-consistent copy of the controlfile.WORKAROUNDSOLUTION:This is a RAC specific ‘configuration’ issue and the correct configuration is as described belowIt is changed behaviour which requires that the snapshot controlfile 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 ‘/snapcf_.f’;Or in case of ASM useRMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘+/snapcf_.f’;PATCHES NAHISTORY 02-07-2012 created and Published alertREFERENCESBUG:10263733 – SNAPSHOT CONTROLFILE USED BY RMAN MUST RESIDE ON SHARED DEVICE FOR RAC DATABASEBUG:10252378 – CONTROLFILE AUTOBACKUP FAILS WITH ORA-00245: CONTROL FILE BACKUP OPERATION FAILEBUG:12311429 – ALTER DATABASE BACKUP CONTROLFILE FAILS WITH ORA-245BUG:13085539 – ORA-245 OCCURS DURING RMAN COPY CORRENT CONTROLFILE.BUG:13780443 – CONTROLFILE BACKUP MUST RESIDE ON SHARED DEVICE WITH RAC DATABASENOTE:265623.1 – RESYNC CATALOG fails with ORA-15045

相关推荐: 使用sql baseline替换执行计划

1.分别执行下列SQL 点击(此处)折叠或打开 2.查看SQL_ID和PLAN_HASH_VALUE 点击(此处)折叠或打开 3.查看执行计划 点击(此处)折叠或打开 4.从库缓存中为SQL1创建baseline 点击(此处)折叠或打开 5.将符合我们预期的S…