Re: What controls RMAN history size in controlfile?

From: Robert Freeman <>
Date: Tue, 29 Sep 2009 13:10:53 -0700 (PDT)
Message-ID: <>

Hmmmm..... are you doing any backups using the keep option?

 Robert G. Freeman
Oracle ACE
Oracle Database 11g RMAN Backup and Recovery (Oracle Press) - ON IT'S WAY SOON! OCP: Oracle Database 11g Administrator Certified Professional Study Guide (Sybex) Oracle Database 11g New Features (Oracle Press) Portable DBA: Oracle (Oracle Press)
Oracle Database 10g New Features (Oracle Press) Oracle9i RMAN Backup and Recovery (Oracle Press) Oracle9i New Features (Oracle Press)
Other various titles out of print now... Blog: The LDS Church is looking for DBA's. You do have to be a Church member in good standing. A lot of kind people write me, concerned I may be breaking the law by saying you have to be a Church member. It's legal I promise! :-)

  • Original Message ---- From: Rich Jesse <> To: Oracle L <> Sent: Tuesday, September 29, 2009 10:36:32 AM Subject: What controls RMAN history size in controlfile?

Howdy all,

In on AIX I have two DBs, PROD and DEV. Each are backed up using RMAN with no catalog. Each has it's CONTROL_FILE_RECORD_KEEP_TIME to the default of 7. PROD has it's MAXLOGHISTORY at 908, while DEV is 2272.

However, when querying V$BACKUP_PIECE, PROD has the default 7 days of info, but DEV currently has 167 days. V$CONTROLFILE_RECORD_SECTION shows BACKUP PIECE at 32720 RECORDS TOTAL and RECORDS USED for DEV, while PROD is only 886.

One major difference in DEV is that it has tablespaces excluded from being backed up in RMAN, but that's about all I can think of.

I can't find any docs on why this would happen to DEV or how to change it. I believe it's causing delays in RMAN processing, especially dealing with V$RMAN_STATUS, based on traces I've run.

Thoughts? Pointers to docs? I'm stumped.


-- Received on Tue Sep 29 2009 - 15:10:53 CDT

Original text of this message