Database Backup and Recovery (MOSC)

MOSC Banner

Manual cleanup of Recovery Catalog table ROUT

edited Mar 15, 2013 7:04AM in Database Backup and Recovery (MOSC) 3 commentsAnswered
We have an Oracle Enterprise Edition version 11.2.0.3 recovery catalog and have noticed that the table ROUT contains over 90 million records.  We are experiencing issues when trying to resync the catalog since the resync issues a delete statement on that table, and if a particular database has many records in there it can fail for max extents on rollback segment.

RMAN> resync catalog;

starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync command on default channel at 03/14/2013 15:24:00
ORA-01628: max # extents (32765) reached for rollback segment _SYSSMU321_3454608026$

RMAN>

Here is the delete statement:  

DELETE FROM

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center