My Oracle Support Banner

Delete noprompt force obsolete does not remove ALL Obsolete entries in catalog (Doc ID 982996.1)

Last updated on MARCH 17, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.0 [Release 10.2 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 30-Nov-2012***


Symptoms

Using Oracle 10gR2 Database and RMAN with a recovery catalog we are unable to remove all
obsolete records. The command 'DELETE FORCE OBSOLETE' executes and completes without error
or warning but there are still 1000s of obsolete records.

Changes

CONTROL_FILE_RECORD_KEEP_TIME=0  # causes the problem because the record sections in the
controlfile cannot expand when the parameter value is 0. Changing the value back to 7 resolved the problem.
The solution section explains why.

Cause

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
Symptoms
Changes
Cause
Solution
References

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