I am going to try that, but the reason it is set up this way is to satisfy certain SOX requirements that needs to have our catalog info saved for 45 days. They both compliment each other and hence set to 45 days at both levels. ________________________________ From: Crisler, Jon [mailto:Jon.Crisler@xxxxxxx] Sent: Wednesday, July 21, 2010 12:52 PM To: jkstill@xxxxxxxxx; Amit Verma (IT - Otterbase) Cc: oracle-l@xxxxxxxxxxxxx Subject: RE: Controlfile Section 28 - denied expansion of controlfile Good point Jared. In my case that would not work as we rely mostly on control file info. From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Wednesday, July 21, 2010 12:41 PM To: averma@xxxxxxxxxxxxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: Controlfile Section 28 - denied expansion of controlfile On Tue, Jul 20, 2010 at 1:37 PM, Amit Verma (IT - Otterbase) <averma@xxxxxxxxxxxxxxxxxxx> wrote: I can't set the control_file_record_keep_time (currently set to 45) to 0 since I have my RMAN retention set to 45 days. As you are using a recovery catalog database, why not set control_file_record_keep_time to a lower value? The catalog will still have the backup information, even if the controlfile does not. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com