共計(jì) 4101 個(gè)字符，預(yù)計(jì)需要花費(fèi) 11 分鐘才能閱讀完成。
丸趣 TV 小編給大家分享一下如何解決 ORA-00245 和 RMAN-08132 問題，相信大部分人都還不怎么了解，因此分享這篇文章給大家參考一下，希望大家閱讀完這篇文章后大有收獲，下面讓我們一起去了解一下吧！
從 Oracle11gR2 開始，在備份控制文件時(shí)，不在需要鎖住 controlfile enqueue。對于非 RAC 的數(shù)據(jù)庫，沒有任何改變，但對于 RAC 數(shù)據(jù)庫，因?yàn)榭刂莆募浞輽C(jī)制的改變，集群中的任何 instance 可以需要寫入到快照控制文件，因此 snapshot controlfile 需要對所有實(shí)例是可見的。
在 RAC 環(huán)境下，如果 snapshot controlfile 不在共享的位置，控制文件任何形式的都可能報(bào) ORA-245 的錯(cuò)誤。
快照控制文件必須能被所有節(jié)點(diǎn)訪問，如果快照控制不是存放在共享設(shè)備上，那么在 RMAN 進(jìn)行控制文件的快照備份時(shí)就會(huì)報(bào)錯(cuò)。
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:
解決方案：
配置 snapshot controlfile 到共享位置
CONFIGURE SNAPSHOT CONTROLFILENAME TO shared_disk /snapcf_ DBNAME .f
如果使用了 ASM，就指定到對應(yīng)的 ASM disk group：
CONFIGURE SNAPSHOT CONTROLFILENAME TO + DiskGroup /snapcf_ DBNAME .f
例子：
RMAN show all
2
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name RACDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 14;
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 PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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/oracle/11g/dbs/snapcf_RACDB1.f # default
RMAN CONFIGURE SNAPSHOT CONTROLFILE NAME TO +DATA1/snapcf_RACBD.F
old RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO +DATA1/snapcf.f
new RMAN configuration parameters:
CONFIGURE SNAPSHOT CONTROLFILE NAME TO +DATA1/snapcf_RACBD.F
new RMAN configuration parameters are successfully stored
RMAN show all;
RMAN configuration parameters for database with db_unique_name RACDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 14;
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 PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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 +DATA1/snapcf_RACBD.F
以上是“如何解決 ORA-00245 和 RMAN-08132 問題”這篇文章的所有內(nèi)容，感謝各位的閱讀！相信大家都有了一定的了解，希望分享的內(nèi)容對大家有所幫助，如果還想學(xué)習(xí)更多知識，歡迎關(guān)注丸趣 TV 行業(yè)資訊頻道！
