Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: RMAN: restoring autobackup spfile and controlfile

RE: RMAN: restoring autobackup spfile and controlfile

From: Allen, Brandon <>
Date: Wed, 1 Aug 2007 15:30:23 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45071FE193@NT15.oneneck.corp>

I saved myself the trouble of opening an SR by searching metalink for bugs on maxseq and found bug 3449079 already exists for this issue. Unfortunately it was closed with status "Documentation Bug Fixed", so then I checked the documentation and sure enough, this behavior is clearly documented
( 051.htm#i1036865):

"RMAN begins the search on the current day or on the day specified with the SET UNTIL. On the first day searched, the search begins with sequence number 256 (or the sequence number specified by MAXSEQ, if provided) and counts back to sequence 0. If no autobackup is found in the current or SET UNTIL day, RMAN checks preceding days, starting with sequence 256 and counting back to 0. The search continues up to MAXDAYS days (default of 7, maximum of 366) prior to the current or SET UNTIL day. If no autobackup is found within MAXDAYS days, then RMAN signals an error and the command stops."

It seems to me like it would be better to make the MAXSEQ parameter apply to EVERY day being searched, but that's just my opinion and it's not worth the effort to open an enhancement request that will probably never be fulfilled anyway, so I'll just live with it.

-----Original Message-----
From: Allen, Brandon

I just did some testing and found that setting the maxseq parameter only limits the sequence on the first day that rman searches

. . .

I'll be opening an SR with Oracle Support shortly to address this and see if there is a better solution.

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

Received on Wed Aug 01 2007 - 17:30:23 CDT

Original text of this message