从oracle 11.2.0.2.0开始，控制文件的快照文件必须能够被所有节点的数据实例访问到，并且必须放在共享的位置。否则，使用RMAN进行
今天看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]
MySQL: BLOB and other no-sql storage, what are the differences?May 13, 2025 am 12:14 AMMySQL'sBLOBissuitableforstoringbinarydatawithinarelationaldatabase,whileNoSQLoptionslikeMongoDB,Redis,andCassandraofferflexible,scalablesolutionsforunstructureddata.BLOBissimplerbutcanslowdownperformancewithlargedata;NoSQLprovidesbetterscalabilityand
MySQL Add User: Syntax, Options, and Security Best PracticesMay 13, 2025 am 12:12 AMToaddauserinMySQL,use:CREATEUSER'username'@'host'IDENTIFIEDBY'password';Here'showtodoitsecurely:1)Choosethehostcarefullytocontrolaccess.2)SetresourcelimitswithoptionslikeMAX_QUERIES_PER_HOUR.3)Usestrong,uniquepasswords.4)EnforceSSL/TLSconnectionswith
MySQL: How to avoid String Data Types common mistakes?May 13, 2025 am 12:09 AMToavoidcommonmistakeswithstringdatatypesinMySQL,understandstringtypenuances,choosetherighttype,andmanageencodingandcollationsettingseffectively.1)UseCHARforfixed-lengthstrings,VARCHARforvariable-length,andTEXT/BLOBforlargerdata.2)Setcorrectcharacters
MySQL: String Data Types and ENUMs?May 13, 2025 am 12:05 AMMySQloffersechar, Varchar, text, Anddenumforstringdata.usecharforfixed-Lengthstrings, VarcharerForvariable-Length, text forlarger text, AndenumforenforcingdataAntegritywithaetofvalues.
MySQL BLOB: how to optimize BLOBs requestsMay 13, 2025 am 12:03 AMOptimizing MySQLBLOB requests can be done through the following strategies: 1. Reduce the frequency of BLOB query, use independent requests or delay loading; 2. Select the appropriate BLOB type (such as TINYBLOB); 3. Separate the BLOB data into separate tables; 4. Compress the BLOB data at the application layer; 5. Index the BLOB metadata. These methods can effectively improve performance by combining monitoring, caching and data sharding in actual applications.
Adding Users to MySQL: The Complete TutorialMay 12, 2025 am 12:14 AMMastering the method of adding MySQL users is crucial for database administrators and developers because it ensures the security and access control of the database. 1) Create a new user using the CREATEUSER command, 2) Assign permissions through the GRANT command, 3) Use FLUSHPRIVILEGES to ensure permissions take effect, 4) Regularly audit and clean user accounts to maintain performance and security.
Mastering MySQL String Data Types: VARCHAR vs. TEXT vs. CHARMay 12, 2025 am 12:12 AMChooseCHARforfixed-lengthdata,VARCHARforvariable-lengthdata,andTEXTforlargetextfields.1)CHARisefficientforconsistent-lengthdatalikecodes.2)VARCHARsuitsvariable-lengthdatalikenames,balancingflexibilityandperformance.3)TEXTisidealforlargetextslikeartic
MySQL: String Data Types and Indexing: Best PracticesMay 12, 2025 am 12:11 AMBest practices for handling string data types and indexes in MySQL include: 1) Selecting the appropriate string type, such as CHAR for fixed length, VARCHAR for variable length, and TEXT for large text; 2) Be cautious in indexing, avoid over-indexing, and create indexes for common queries; 3) Use prefix indexes and full-text indexes to optimize long string searches; 4) Regularly monitor and optimize indexes to keep indexes small and efficient. Through these methods, we can balance read and write performance and improve database efficiency.
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Zend Studio 13.0.1
Powerful PHP integrated development environment
SublimeText3 Linux new version
SublimeText3 Linux latest version
DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software
SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.
SublimeText3 English version
Recommended: Win version, supports code prompts!
