My Oracle Support Banner

Top RMAN 11.2 issues (Doc ID 1473914.1)

Last updated on JANUARY 18, 2022

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


Purpose

This document discuss the Top known rman issues in 11.2, The purpose is to generate awareness among customers, engineers and whoever wantes to implement RMAN in 11.2.

Scope

 Its intended audience is DBA, Support engineer and Technical management. It discuss TOP known issues of RMAN reported on 11.2.x.x.x

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Top RMAN issues in 11GR2  
 Few structural changes in 11gR2 with wide impact on RMAN setup
 1. Snapshot / Backup controlfile location, must be shared location in RAC environment.
 2. MMON process takes Auto backup of the controlfile after structural Changes
 3. Recovery area backup can be taken to Disk
 Hot BUGS in 11GR2 impacting RMAN stability.
 1. BUG 9877980: SR11.2.0.2CSHAR_FORCE - TRC - KKSLMARKLITERALBINDS
 2. Bug 8482162: SNAPSHOT CONTROLFILE STILL NEED NOAC ON NFS MOUNT POINT
 3. Bug 9577583: FALSE ORA-942 OR OTHER ERRORS WITH MULTIPLE SCHEMAS HAVING IDENTICAL OBJECTS
 4. BUG 10635701 - BACKUP OF FRA CONSUMES 15GB OF PGA AND FAIL WITH ORA-4030
 5. BUG 12370722 - CATUPGRD.SQL HANGS WITH ARCH ERROR ORA-600 [KRR_HIGHEST_SCN_TIM_8]
 6. BUG 10170431 - CTWR CONSUMING LOTS OF CPU CYCLES
 7. BUG 13000553 - RMAN BACKUP FAILS WITH RMAN-20999 ERROR AT STANDBY DATABASE
 8. BUG 12312133 - RMAN INCREMENTAL BACKUP WITH BLOCK CHANGE TRACKING MAY CAUSE STANDBY DB CRASH
 9. BUG 10318078 - RMAN COREDUMPS ON EXIT : BACKUP (TO TAPE) COMPLETES SUCCESFULLY
 10. BUG 13602883 - BLOCK CHANGE TRACKING NOT USED FOR INCREMENTAL BACKUPS
 11. MML Incompatibility Issue: ORA-07445 [Strcpy()+48] during RMAN backup or restore to tape using Oracle 11.2
 12. Bug 11694127 - RMAN DUPLICATE not honoring TIME portion of date for "UNTIL TIME" [ID 11694127.8]
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.