Re: RMAN report need backup unexpected results
- From: Kenneth Fowler <kenneth.r.fowler@xxxxxxxxx>
- To: Seth Miller <sethmiller.sm@xxxxxxxxx>
- Date: Wed, 3 Sep 2014 11:02:22 -0400
Seth,
I am not using a recovery catalog however CONTROL_FILE_RECORD_KEEP_TIME has
been raised to 60 to make sure we have enough history. In any case I have
opened a SR to see if Oracle can shed some light.
Thanks,
Ken.
On Tue, Sep 2, 2014 at 5:23 PM, Seth Miller <sethmiller.sm@xxxxxxxxx> wrote:
> Ken,
>
> Are you using a recovery catalog? If not, chances are your control file
> has not maintained enough RMAN records to satisfy your query. The
> CONTROL_FILE_RECORD_KEEP_TIME parameter dictates the minimum amount of days
> of records to keep and defaults to 7. It is likely that RMAN simply does
> not have enough information.
>
> You can try creating a catalog or you can simply increase the
> CONTROL_FILE_RECORD_KEEP_TIME to 31, make sure all of your backups are
> cataloged and try the query again.
>
> Seth Miller
>
>
>
> On Wed, Jul 30, 2014 at 4:29 PM, Kenneth Fowler <
> kenneth.r.fowler@xxxxxxxxx> wrote:
>
>> Hi All,
>>
>>
>>
>> I need to create some monitoring scripts to make sure that all of our
>> database have adequate RMAN backups. All of our databases are set to
>> recovery window of 14 days...
>>
>> RMAN> show retention policy;
>>
>> RMAN configuration parameters for database with db_unique_name BIOOCT1
>> are:
>> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
>>
>>
>>
>> Obsolete backups are regularly purged as part of the backup script. For
>> this particular database the oldest level 0 backup is from 12 July...
>>
>>
>>
>> RMAN> list backup summary;
>>
>>
>> List of Backups
>> ===============
>> Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
>> ------- -- -- - ----------- --------------- ------- ------- ---------- ---
>> 2453 B 0 A DISK 12-JUL-14 1 1 YES
>> 2014-07-12_062414_LEV0
>> 2454 B 0 A DISK 12-JUL-14 1 1 YES
>> 2014-07-12_062414_LEV0
>> 2456 B A A DISK 12-JUL-14 1 1 YES
>> 2014-07-12_062414_LEV0
>> 2457 B 1 A DISK 14-JUL-14 1 1 YES
>> 2014-07-14_181501_LEV1
>> 2458 B 1 A DISK 14-JUL-14 1 1 YES
>> 2014-07-14_181501_LEV1
>> 2459 B A A DISK 14-JUL-14 1 1 YES
>> 2014-07-14_181501_LEV1
>> 2460 B A A DISK 14-JUL-14 1 1 YES
>> 2014-07-14_181501_LEV1
>> 2461 B A A DISK 14-JUL-14 1 1 YES
>> 2014-07-14_181501_LEV1
>>
>>
>>
>> I figured that I would use "report need backup" to determine if there is
>> an issue and alert via email however I tried the following as a test...
>>
>>
>>
>> RMAN> report need backup recovery window of 30 days;
>>
>> Report of files that must be backed up to satisfy 30 days recovery window
>> File Days Name
>> ---- ----- -----------------------------------------------------
>>
>>
>>
>> It came back with nothing. I do not have backups old enough to support
>> recovery to a point in time 30 days back so am wondering why the "report
>> need backup recovery window of 30 days;" did not list all of the data
>> files? The functionality is described in the docs as follows...
>>
>>
>>
>> RECOVERY WINDOW OF integer DAYS
>>
>> Reports datafiles for which there are not sufficient backups to satisfy a
>> recovery window-based retention policy for the specified number of days,
>> that is, datafiles without sufficient backups for point-in-time recovery to
>> any point back to the time SYSDATE - integer. See Table 2-31 for
>> description of output.
>>
>>
>>
>> So seems to me that it should list all data files in this case. Has
>> anyone else seen this seemingly incorrect behavior? This is for Oracle
>> Enterprise Edition 11.2.0.2 on OEL 5.5.
>>
>>
>>
>> Thanks,
>> Ken.
>>
>>
>
Other related posts:
