Bug 4483368 : SEVERAL RMAN CATALOG START WITH CREATES DUPLICATE CATALOG ENTRIES

Bug 属性

---

类型	B - Defect	已在产品版本中修复
严重性	3 - Minimal Loss of Service	产品版本	10.1.0.4.0
状态	31 - Could Not Reproduce. To Filer	平台	46 - Linux x86
创建时间	2005-7-8	平台版本	RH AS 2.1
更新时间	2008-12-16	基本 Bug	N/A
数据库版本	10.1.0.4.0	影响平台	Generic
产品源	Oracle

相关产品

---

产品线	Oracle Database Products	系列	Oracle Database
区域	Oracle Database	产品	5 - Oracle Database - Enterprise Edition

Hdr: 4483368 10.1.0.4.0 RDBMS 10.1.0.4.0 RMAN PRODID-5 PORTID-46
Abstract: SEVERAL RMAN CATALOG START WITH CREATES DUPLICATE CATALOG ENTRIES
 
*** 07/08/05 08:15 am ***
TAR:
----
SR:4423759.994
 
PROBLEM:
--------
After several "RMAN  catalog start with "
we have several copies of the same backuppiece in our catalog which we can 
see
with "list backup;" and also "list backup summary;". This is defined 
behaviour.
    
However, when I now try to restore with that controlfile instead of a catalog 
I
receive 
  ORA-19693 backup piece "/opt/oracle/admin/mnt/HERMES2/bkp/..." is already
included.
 
 
Of course I went through the docs, but
- the delete command refuses to work because it finds several catalog (!)
  copies and it cannot address a single copy of a backup piece.
- the report and the list command do not give me an easy method of removing 
all
 the overcount copies. The problem is that they list several copies, e. g.
 copies 1 - 10, but I have to delete the single copies all by their backup 
piece
 key. 
 
 Because the backup pieces are not copied physically but just catalogued 
several 
 times they are not  physical copies but just "Duplicate catalog entries".
 
 
o Usually if you try to CATALOG a PIECE which is already in the Catalog 
  you should get:
  
    "no files found unknown to the database"
 
  But in customer case its cataloged twice !!! (not throwing the message)
´
o the second run should usually detect that the backuppiece: 'hngp1jl4_1_1'  
is
  already cataloged !!
  
  But it did not and catalog the file again, which leads to 2 entries
  in catalog for same Piece 
 
DIAGNOSTIC ANALYSIS:
--------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#1'st run of 'RMAN> catalog start with ..   '
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
RMAN> catalog start with 
      /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1 ;  
!!**
RMAN> 
using target database controlfile instead of recovery catalog
searching for all files that match the pattern 
/opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1
List of Files Unknown to the Database
=====================================
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1
 
List of Cataloged Files
=======================
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1 
**
    
RMAN> 
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time    
------- ---------- ----------- ------------ -------------------
13641   99M        DISK        00:00:00     2005-07-08.19-16-52
        BP Key: 68295   Status: AVAILABLE  Compressed: NO  Tag: 
TAG20050708T191642
        Piece Name: 
/opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1
 
  List of Archived Logs in backup set 13641
  Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
  ---- ------- ---------- ------------------- ---------- ---------
  1    974     1123433369 2005-07-08.11-52-48 1124144241 2005-07-08.15-15-44
 
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#2'nd run of 'RMAN> catalog start with ..   '
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RMAN> catalog start with 
       /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01
  
List of Files Unknown to the Database
=====================================
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/prot.out
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hogp1k6l_1_1
 
List of Cataloged Files
=======================
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1
List of Files Which Where Not Cataloged
=======================================
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/prot.out
  Reason: The file header is corrupted
File Name: /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hogp1k6l_1_1
 
RMAN> 
List of Backup Sets
===================
 
BS Key  Size
------- ----------
13641   99M
 
  List of Archived Logs in backup set 13641
  Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
  ---- ------- ---------- ------------------- ---------- ---------
  1    974     1123433369 2005-07-08.11-52-48 1124144241 2005-07-08.15-15-44
 
  Backup Set Copy #1 of backup set 13641
  Device Type Elapsed Time Completion Time     Compressed Tag
  ----------- ------------ ------------------- ---------- ---
  DISK        00:00:00     2005-07-08.23-10-29 NO         TAG20050708T191642
 
    List of Backup Pieces for backup set 13641 Copy #1
    BP Key  Pc# Status      Piece Name
    ------- --- ----------- ----------
*   68295   1   AVAILABLE   
/opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1
 
  Backup Set Copy #2 of backup set 13641
  Device Type Elapsed Time Completion Time     Compressed Tag
  ----------- ------------ ------------------- ---------- ---
  DISK        00:00:00     2005-07-08.23-14-01 NO         TAG20050708T191642
 
    List of Backup Pieces for backup set 13641 Copy #2
    BP Key  Pc# Status      Piece Name
    ------- --- ----------- ----------
*   68296   1   AVAILABLE   
/opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1
 
WORKAROUND:
-----------
Ct used own written Unix shel script to uncatalog .
 
RELATED BUGS:
-------------
Bug:3434136 CATALOG START WITH / RECOVERY AREA REPORTS ASM ALIAS FILES
Fixed-Releases:     A200
 
REPRODUCIBILITY:
----------------
At customer site
 
TEST CASE:
----------
n/a
 
STACK TRACE:
------------
see uploaded RMAN debug tracefiles
 
SUPPORTING INFORMATION:
-----------------------
 
24 HOUR CONTACT INFORMATION FOR P1 BUGS:
----------------------------------------
 
DIAL-IN INFORMATION:
--------------------
 
IMPACT DATE:
------------
 
*** 07/08/05 08:17 am ***
Environment: 
 o RAC
 o ASM
 
I will upload the related RMAN.log and debugged traces 
regards
Bernhard
*** 07/08/05 08:22 am *** (CHG: Sta->16)
*** 07/08/05 08:22 am ***
*** 07/21/05 06:56 am ***
*** 08/03/05 04:29 am *** 
*** 08/04/05 01:09 pm *** (CHG: Sta->11)
*** 08/04/05 01:09 pm ***
*** 08/04/05 01:09 pm *** 
*** 08/04/05 01:09 pm ***
*** 12/05/05 11:16 pm *** 
*** 06/18/07 11:24 am *** 
*** 06/18/07 11:24 am *** 
*** 02/26/08 10:29 am *** 
*** 12/16/08 09:15 am *** 
*** 12/16/08 09:15 am ***
Bug is over three years old and I cannot duplicate this behavior in 11g. Is 
this still a problem for the customer?
*** 12/16/08 09:16 am *** (CHG: Sta->31)