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基本 BugN/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-46Abstract: 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 seewith "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 Ireceive   ORA-19693 backup piece "/opt/oracle/admin/mnt/HERMES2/bkp/..." is alreadyincluded.  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 catalogsearching for all files that match the pattern /opt/oracle/admin/mnt/HERMES2/bkp/2005-07-08.16-17-01/hngp1jl4_1_1List 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.outFile 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_1List 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 corruptedFile 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 FILESFixed-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 regardsBernhard*** 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)