您好，登录后才能下订单哦！
密码登录
登录注册
点击 登录注册 即表示同意《亿速云用户服务条款》
今天朋友巡检遇到了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
类型:ALERT
In this Document
Description
Occurrence
Symptoms
Workaround
Patches
History
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1.0 and later
Information 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 non
shared location.
| ORA-245 error message description ---------------------------------------- 00245, 00000, "control file backup operation failed" *Cause: Failed to create a control file backup because some process signaled an error during backup creation. *Action: Check alert files for further information. This usually happens |
because some process could not access the backup file during
backup creation. Any process of any instance that starts a
read/write control file transaction must have an access to the
backup control file during backup creation.
DESCRIPTION
| 1. In RAC environment controlfile autobackup fails with ora-0245 Autobackup 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:31 ORA-245: control file backup operation failed
2. In RAC environment, backup controlfile 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 up standby controlfile to non shared location fails SQL> 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 failed
4. In RAC environment copy current controlfile to '${DB_BACKUP_DIR}/rac_tnctv_control.bak'; channel ch2: 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 ch2 ORA-245: control file backup operation failed
5. 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: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 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.
WORKAROUND
SOLUTION:
This is a RAC specific 'configuration' issue and the correct configuration is as described below
It 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 '<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-2012 created and Published alert
REFERENCES
BUG:10263733 - SNAPSHOT CONTROLFILE USED BY RMAN MUST RESIDE ON SHARED DEVICE FOR RAC DATABASE
BUG:10252378 - CONTROLFILE AUTOBACKUP FAILS WITH ORA-00245: CONTROL FILE BACKUP OPERATION FAILE
BUG:12311429 - ALTER DATABASE BACKUP CONTROLFILE FAILS WITH ORA-245
BUG:13085539 - ORA-245 OCCURS DURING RMAN COPY CORRENT CONTROLFILE.
BUG:13780443 - CONTROLFILE BACKUP MUST RESIDE ON SHARED DEVICE WITH RAC DATABASE
NOTE:265623.1 - RESYNC CATALOG fails with ORA-15045
免责声明：本站发布的内容（图片、视频和文字）以原创、转载和分享为主，文章观点不代表本网站立场，如果涉及侵权请联系站长邮箱：is@yisu.com进行举报，并提供相关证据，一经查实，将立刻删除涉嫌侵权内容。