RMAN-06207 RMAN-06208 RMAN-06214 - backup standby controlfile is missing from standby server/database

Symptoms

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Control File Copy     676    15-NOV-11          /ora01/oracle/admin/BACKUP/cisdbc3/cisdbc3_controlfile_bak_11-15-11_20:02:56

RMAN-06207: WARNING: 1 objects could not be 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   /ora01/oracle/admin/BACKUP/cisdbc3/cisdbc3_controlfile_bak_11-15-11_20:02:56

 

Cause

rman delete fails due to mismatched status of backup pieces

In this case,  backup standby controlfile is missing from standby server/database

Solution

Step 1 thru 5

Step 1

RMAN> report obsolete;

RMAN retention policy will be applied to the command

RMAN retention policy is set to redundancy 2

Report of obsolete backups and copies

Type                 Key    Completion Time    Filename/Handle

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

Control File Copy     676    15-NOV-11          /ora01/oracle/admin/BACKUP/orcl/orcl_controlfile_bak_11-15-11_20:02:56

Step 2

RMAN> crosscheck copy of controlfile;

validation failed for control file copy

control file copy filename=/ora01/oracle/admin/BACKUP/orcl/orcl_controlfile_bak_11-15-11_20:02:56 recid=676 stamp=767304177

Crosschecked 1 objects

Step 3

RMAN> delete noprompt obsolete;

RMAN retention policy will be applied to the command

RMAN retention policy is set to redundancy 2

Deleting the following obsolete backups and copies:

Type                 Key    Completion Time    Filename/Handle

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

Control File Copy     676    15-NOV-11          /ora01/oracle/admin/BACKUP/orcl/orcl_controlfile_bak_11-15-11_20:02:56

deleted control file copy

control file copy filename=/ora01/oracle/admin/BACKUP/orcl/orcl_controlfile_bak_11-15-11_20:02:56 recid=676 stamp=767304177

Deleted 1 objects

Step 4

RMAN>  crosscheck copy of controlfile;

Step 5

RMAN>  report obsolete;

RMAN retention policy will be applied to the command

RMAN retention policy is set to redundancy 2

no obsolete backups found

RMAN>

Hope this helps!Rupam

What is causing account lock

 -- check profile

col PROFILE format a10

col LIMIT format a15

select * from dba_profiles where resource_type='PASSWORD' order by 1,2;

-- options for trouble shooting

1. audit not successful connections

2. trace 1017 event

-- Steps for option 1

Reference: oracle doc # 352389.1

Reference:   oracle doc #  221944.1

-- setup audit

sqlplus / as sysdba

AUDIT CREATE SESSION BY ACCESS WHENEVER NOT SUCCESSFUL;

AUDIT CONNECT BY ACCESS WHENEVER NOT SUCCESSFUL;

-- Get information related to failed connections

col USERID format a10

col USERHOST format a25

col TERMINAL format a10

select returncode, action#, userid, userhost, terminal from aud$ where returncode='1017' and action#=100;

SELECT TO_CHAR(NTIMESTAMP# , 'DD-MON-YYYY HH24:MI:SSxFF'), SESSIONTIMEZONE   from aud$ where returncode=1017;

NOTE : TIME is in GMT, so subtract -5 hours

-- Steps for option 2

-- to trace what is locking the account

1.       Login to sqlplus as sysdba

2.       enable trace, using

                   alter system set events ‘1017 trace name errorstack level 10’;

3.       Show parameter dump

4.       Goto the udump location

5.       grep ORA – 01017 *

6.       get the timestamp and related information  from trace generated

7.       When trace is no more needed , set it off using:

              alter system set events ‘1017 trace name errorstack off’

8.       Goto the listener.log file location

9.       Get the connectivity information for the selected time from listener log file.

Hope this help. Regards Rupam