rman 备份出现ORA-00245/RMAN-08132

联系:手机(+86 13429648788) QQ(107644445)QQ咨询惜分飞

标题:rman 备份出现ORA-00245/RMAN-08132

作者:惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

rman备份出现如下错误

RMAN> backup full  tag 'dbfull' format '/jfkdata1/rman_bak/full_%d_%u' database 
 2>   include current controlfile  plus archivelog  format '/jfkdata1/rman_bak/arch_%d_%u'; 


Starting backup at 13-MAR-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=297 instance=ykcdb2 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=29 RECID=43 STAMP=777808820
input archived log thread=1 sequence=30 RECID=46 STAMP=777816035
input archived log thread=2 sequence=21 RECID=45 STAMP=777816033
channel ORA_DISK_1: starting piece 1 at 13-MAR-12
channel ORA_DISK_1: finished piece 1 at 13-MAR-12
piece handle=/jfkdata1/rman_bak/arch_YKCDB_01n5p1vf tag=DBFULL comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
Finished backup at 13-MAR-12

Starting backup at 13-MAR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00002 name=/jfkdata1/oradata/ykcdb/sysaux01.dbf
input datafile file number=00001 name=/jfkdata1/oradata/ykcdb/system01.dbf
input datafile file number=00003 name=/jfkdata1/oradata/ykcdb/undotbs01.dbf
input datafile file number=00005 name=/jfkdata1/oradata/ykcdb/undotbs02.dbf
input datafile file number=00004 name=/jfkdata1/oradata/ykcdb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 13-MAR-12
channel ORA_DISK_1: finished piece 1 at 13-MAR-12
piece handle=/jfkdata1/rman_bak/full_YKCDB_02n5p209 tag=DBFULL comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 13-MAR-12
channel ORA_DISK_1: finished piece 1 at 13-MAR-12
piece handle=/jfkdata1/rman_bak/full_YKCDB_03n5p213 tag=DBFULL comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-MAR-12

Starting backup at 13-MAR-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=22 RECID=48 STAMP=777816102
input archived log thread=1 sequence=31 RECID=47 STAMP=777816101
channel ORA_DISK_1: starting piece 1 at 13-MAR-12
channel ORA_DISK_1: finished piece 1 at 13-MAR-12
piece handle=/jfkdata1/rman_bak/arch_YKCDB_04n5p217 tag=DBFULL comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 13-MAR-12
ORA-00245: control file backup operation failed

RMAN-08132: WARNING: cannot update recovery area reclaimable file list

RMAN> 

从这里可以看出数据库文件,归档日志,spfile和controlfile都备份完成,后面又出现一个controlfile失败,应该是控制文件快照备份失败。

错误原因

RMAN creates a copy of the control file for read consistency, this is the snapshot controlfile. 
Due to the changes made to the controlfile backup mechanism in 11gR2 any instances 
in the cluster may write to the snapshot controlfile. Therefore, 
the snapshot controlfile file needs to be visible to all instances.

The same happens when a backup of the controlfile is created directly from 
sqlplus any instance in the cluster may write to the backup controfile file.

In 11gR2 onwards, the controlfile backup happens without holding the control file enqueue. 
For non-RAC database, this doesn't change anything. 

But, for RAC database, the snapshot controlfile location 
must be in a shared file system that will be accessible from all the nodes.

The snapshot controlfile MUST be  accessible by all nodes of a RAC database. 

大致意思就是rman的snapshot controlfile必须放在共享存储之上。

解决方法

The snapshot controlfile MUST be accessible by all nodes of a RAC database, 
if the snapshot controlfile does not reside in on a shared device this error will raise.

1. Check the snapshot controlfile location:
RMAN> show all;

2. Configure the snapshot controlfile to a shared disk:
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '<shared_disk>/snapcf_<DBNAME>.f';
此条目发表在 rman备份/恢复 分类目录,贴了 标签。将固定链接加入收藏夹。

rman 备份出现ORA-00245/RMAN-08132》有 2 条评论

  1. 惜分飞 说:

    出现该错误,会在alert文件中留下

    ORA-00245: control file backup operation failed
    

      [引用]  [回复]

  2. 惜分飞 说:

    具体见:RAC BACKUP FAILS WITH ORA-00245: CONTROL FILE BACKUP OPERATION FAILED [ID 1268725.1]

    Applies to:
    Oracle Server - Enterprise Edition - Version: 11.2.0.2 and later   [Release: 11.2 and later ]
    Information in this document applies to any platform.
    
    Symptoms
    RMAN Backup on RAC database fails when doing controlfile autobackup fails with error:
    
    
    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 11/27/2010 10:00:31 
    ORA-00245: control file backup operation failed
    
    SQLPLUS controlfile backup  also fails with:
    
    
    alter database backup controlfile to '/oracle/backup_cntl_file' *
    ERROR at line 1:
    ORA-00245: control file backup operation failed
    
    Changes
    RAC Database  release 11.2 
     
    Cause
    The error description is:
    
    00245, 00000, "control file backup failed; target is likely on a local file system"
     // *Cause: Failed to create a control file backup because some process
     // signaled an error during backup creation. This is likely caused
     // by the backup target being on a local file system so it could not
     // be accessed by other instances. It can also be caused by other
     // I/O errors to the backup target. Any process of any instance that
     // starts a read/write control file transaction must have access
     // to the backup control file during backup creation.
     // *Action: Check alert files of all instances for further information.
     
    RMAN creates a copy of the control file for read consistency, this is the snapshot controlfile. 
    Due to the changes made to the controlfile backup mechanism in 11gR2 any instances 
    in the cluster may write to the snapshot controlfile. Therefore, 
    the snapshot controlfile file needs to be visible to all instances.
    
    The same happens when a backup of the controlfile is 
    created directly from sqlplus any instance in the cluster may write to the backup controfile file.
    
    In 11gR2 onwards, the controlfile backup happens without holding the control file enqueue. 
    For non-RAC database, this doesn't change anything. 
    
    But, for RAC database, the snapshot controlfile location must be 
    in a shared file system that will be accessible from all the nodes.
    
    The snapshot controlfile MUST be  accessible by all nodes of a RAC database. 
    
    Solution
    The snapshot controlfile MUST be accessible by all nodes of a RAC database, 
    if the snapshot controlfile does not reside in on a shared device this error will raise.
    
    1. Check the snapshot controlfile location:
    RMAN> show all;
    
    2. Configure the snapshot controlfile to a shared disk:
    RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '<shared_disk>/snapcf_<DBNAME>.f';
    

      [引用]  [回复]

发表评论

电子邮件地址不会被公开。 必填项已用 * 标注

您可以使用这些 HTML 标签和属性: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>