ORA-19606 issues in Oracle 11g RAC environments

This problem has plagued me for some time when I just took over Oracle, and now I'm going to share the problem solving process.

Oracle version: 11gR2

OS Environment: Centos6.4

Problem Recurrence:

1. The database was written with a backup script with the following script:

--------------------------------------------------------------------------------------------------------------- --------------------

#!/bin/bash
# Name:rmanbk_level0.sh
# Write By:datura at 2014/11/11 v1.0
# description:the script is used to make the zero level backup for the ORCL Library

# The definition of the variable
Lock_file=/tmp/rmanbk.lock
Oracleid= ' cat/etc/passwd|grep oracle|awk-f: ' {print $} '

# Check the script to run or not
If [-F $lock _file];then
Pid= ' Cat $lock _file '
PS $pid &>/dev/null
[$?-eq 0] && echo "Script is running ..." && exit 1
Fi

# Create Process Lock
echo $$ > $lock _file

# allows the Oracle to run
[$UID-ne $oracleid] && echo "Please run as Oracle!" && Exit 4

# To set environment variables
Export Oracle_base=/u01/app/oracle
Export Oracle_home= $ORACLE _base/product/11.2.0/db_1
Export path= $ORACLE _home/bin: $PATH
Export ORACLE_SID=ORCL1
Export Nls_lang=american_america. Al32utf8

echo on
Rman target/msglog=/storage/script/log/rmanbk_level0_ ' Date +%y '-'%m '-'%d '-'%H ': '%m ': '%s '. Log <<eof
RUN {
Allocate channel C1 type disk;
Allocate channel C2 type disk;
Allocate channel C3 type disk;
Allocate channel C4 type disk;
Backup as compressed Backupset incremental level 0 database format '/STORAGE/ARCH/RMAN/RMANBK_LEVEL0_%D_%I_%S_%P_%T.BKP ‘;
Crosscheck Archivelog All;
Backup Archivelog all format '/STORAGE/ARCH/RMAN/RMANBK_ARCHIVELOG_%D_%I_%S_%P_%T.BKP ';
Crosscheck backup;
Delete NoPrompt obsolete;
Delete noprompt expired backupset;
Release channel C1;
Release channel C2;
Release channel C3;
Release channel C4;
}
Exit
Eof
echo off

find/storage/arch/rman/-mtime-0.5-type f-exec zip/storage/arch/rman/rmanbk_level0 ' date +%F '. zip {} \;
Scp/storage/arch/rman/rmanbk_level0 ' Date +%f '. zip backup.demon.com:/home/oracle/orabackup
Rm-rf/storage/arch/rman/rmanbk_level0 ' Date +%f '. zip
Find/storage/script/log-mtime +7-exec rm-rf {} \;

2. One day in the backup log, the following error message appears

--------------------------------------------------------------------------------------------------------------- -----------------------------------

Rman-06207:warning:1 objects could not being deleted for DISK channel (s) due
Rman-06208:to mismatched status. Use Crosscheck command to fix status
Rman-06210:list of Mismatched objects
RMAN-06211: =========================================================
Rman-06212:object Type Filename/handle
RMAN-06213:------------------------------------------------------------------
Rman-06214:datafile Copy +DATA/ORCL/SNAPC_ORCL.F

3. Error information Processing process

--------------------------------------------------------------------------------------------------------------- -------------------------------------

Rman> Crosscheck backupset;

rman> report obsolete;

Rman Retention policy would be applied to the command
RMAN retention policy was set to recovery window of 2 days< Br>report of obsolete backups and copies
Type                 Key     Completion time    filename/handle
----------------------------------------------------------------
Control File Copy     5      12-dec-14         &NBSP;+DATA/ORCL/SNAPC_ORC L.F

rman> Delete noprompt obsolete;

RMAN-00571: ====================================================
RMAN-00569: ===============error MESSAGE STACK follows ===============
RMAN-00571: ====================================================
Rman-03009:failure of Delete command on C2 channel at 11/20/2014 09:03:14
Ora-19606:cannot copy or restore to snapshot control file

Rman> Show snapshot controlfile name;

RMAN configuration parameters for database with Db_unique_name ORCL is:
CONFIGURE SNAPSHOT controlfile NAME to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f '; # Default

Rman> Configure snapshot Controlfile name to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f_bak ';

New RMAN configuration parameters:
CONFIGURE SNAPSHOT controlfile NAME to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f_bak ';
New RMAN configuration parameters is successfully stored

rman> crosscheck controlfilecopy '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f ';

Released Channel:ora_disk_1
Allocated Channel:ora_disk_1
Channel ora_disk_1:sid=80 INSTANCE=ORCL1 Device Type=disk
Validation failed for control file copy
Control file Copy file Name=/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f recid=2 stamp=863884566
Crosschecked 1 Objects

rman> Delete Expired controlfilecopy '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f ';

Released Channel:ora_disk_1
Allocated Channel:ora_disk_1
Channel ora_disk_1:sid=80 INSTANCE=ORCL1 Device Type=disk
List of Control File Copies
=========================================================================================
Key S Completion time CKP SCN CKP time
------- - --------------- ---------- ---------------
2 X 17-nov-14 67553950 17-nov-14
Name:/U01/APP/ORACLE/PRODUCT/11.2.0/DB_1/DBS/SNAPCF_ORCL1.F
tag:tag20141117t155602

Really want to delete the above objects (enter YES or NO)? Yes
Deleted control File copy
Control file Copy file Name=/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f recid=2 stamp=863884566
Deleted 1 EXPIRED objects

Rman> Configure snapshot Controlfile name to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f ';

Old RMAN configuration parameters:
CONFIGURE SNAPSHOT controlfile NAME to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f_bak ';
New RMAN configuration parameters:
CONFIGURE SNAPSHOT controlfile NAME to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f ';
New RMAN configuration parameters is successfully stored

Rman> Configure snapshot Controlfile name clear;

Old RMAN configuration parameters:
CONFIGURE SNAPSHOT controlfile NAME to '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcl1.f ';
RMAN configuration parameters is successfully reset to default value

4. The problem is resolved temporarily by the above general operation, but the same problem will occur again in a few days.

--------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------

RMAN-00571: ==========================================================
RMAN-00569: ================= ERROR MESSAGE, STACK follows ===================
RMAN-00571: ==========================================================
Rman-03009:failure of Control File and SPFILE autobackup command on C1 channel at 12/12/2014 01:05:19
Ora-00245:control file backup failed; Target is likely on a local file system

5. The above general operation only temporarily solves the problem, does not solve the fundamental problem, then browses the official document to obtain the following information

--------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------

Starting with 11GR2, you no longer need to lock controlfile when backing up your control files Enqueue
No changes to the database for non-RAC environments
For RAC environments, however, because the control file backup mechanism changes
All nodes in the cluster must have access to the snapshot control file, so the snapshot control file is visible to all instances
If the snapshot control file is not placed on the shared device, the above error occurs when Rman backs up the snapshot control file

6. Make the following adjustments based on the information obtained

--------------------------------------------------------------------------------------------------------------- ---------------------------

Rman> Show snapshot controlfile name;

Rman> Configure snapshot Controlfile name to '/STORAGE/SNAP_CONTROL/SNAPCF_%D_%I_%S_%P_%T.F ';

Rman> Configure snapshot Controlfile name to ' +DATA/ORCL/SNAPCF_ORCL.F '; --can also be specified to the corresponding ASM disk group (disk group does not support wildcard naming)

After you put the control file snapshot on the shared storage, there is no more error.

In the event of problems, we are accustomed to using our own experience to use conventional methods to solve the problem

But sometimes it's a good idea to flip through official documents.

Although the official file can not tell you the specific steps

Can give the right guidance to solve the fundamental problem

-------------------------------------------------------above is a personal point of view, if inappropriate, Welcome to the-----------------------------------------------------------------------

This article is from the "Operations Management" blog, please make sure to keep this source http://datura.blog.51cto.com/8962530/1612949

ORA-19606 issues in Oracle 11g RAC environments