Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: getting RMAN to mark and delete obsolete

Re: getting RMAN to mark and delete obsolete

From: Glen <stromqueat_at_teldotnet.com>
Date: Wed, 15 Nov 2006 19:58:06 GMT
Message-ID: <ijK6h.10951$gy2.1540@edtnps90>


Glen wrote:
> Volker Hetzer wrote:
>

>> Glen schrieb:
>>
>>> Volker Hetzer wrote:
>>
>>
>>
>>>> One beginners mistake is to have not enough space in the control file.
>>>> Does the parameter "control_file_record_keep_time" ring a bell?
>>>>
>>>> Lots of Greetings!
>>>> Volker
>>>
>>>
>>>
>>> ah! cfrkt is set at 7, just reading up on it a bit now, although the 
>>> doc's are a tad confusing so far... do I increase the cfrkt to have a 
>>> larger recovery window?
>>
>>
>> No. You have to increase cfrkt in order to make rman remember the 
>> records for longer. If you want rman to delete then, rman needs to 
>> know about them.
>>
>>> I'm thinking at the default cfrkt of 7 I should still be able to 
>>> issue a "delete obsolete recovery window of 3 days", correct?
>>
>>
>> Yes, it should. However, all backups older than 7 days will have to be 
>> deleted manually.
>>
>> Lots of Greetings!
>> Volker

>
>
> I manually deleted the backups older than 7 days, and set cfrkt to a
> higher number for future. In the meantime, it is not even letting me
> delete backups newer than 7 days.
>
> Getting some strange stuff here:
> RMAN> list backup summary;
>
>
> List of Backups
> ===============
> Key TY LV S Device Type Completion Time #Pieces #Copies Tag
> ------- -- -- - ----------- --------------- ------- ------- ---
> 62 B 0 A DISK 05-NOV-06 1 1 TAG20061105T230005
> 63 B A A DISK 05-NOV-06 1 1 TAG20061105T230253
> 65 B 1 A DISK 06-NOV-06 1 1 TAG20061106T020006
> 66 B A A DISK 06-NOV-06 1 1 TAG20061106T020053
> 68 B 1 A DISK 07-NOV-06 1 1 TAG20061107T020006
> 69 B A A DISK 07-NOV-06 1 1 TAG20061107T020103
> 71 B 1 A DISK 08-NOV-06 1 1 TAG20061108T020005
> 72 B A A DISK 08-NOV-06 1 1 TAG20061108T020053
> 74 B 1 A DISK 09-NOV-06 1 1 TAG20061109T020006
> 75 B A A DISK 09-NOV-06 1 1 TAG20061109T020054
> 77 B 1 A DISK 10-NOV-06 1 1 TAG20061110T020005
> 78 B A A DISK 10-NOV-06 1 1 TAG20061110T020103
> 80 B 1 A DISK 11-NOV-06 1 1 TAG20061111T020006
> 81 B A A DISK 11-NOV-06 1 1 TAG20061111T020054
> 82 B F A DISK 11-NOV-06 1 1
> 83 B 1 A DISK 13-NOV-06 1 1 TAG20061113T020006
> 84 B A A DISK 13-NOV-06 1 1 TAG20061113T020053
> 85 B F A DISK 13-NOV-06 1 1
> 86 B 1 A DISK 14-NOV-06 1 1 TAG20061114T020006
> 87 B A A DISK 14-NOV-06 1 1 TAG20061114T020055
> 88 B F A DISK 14-NOV-06 1 1
> 89 B 1 A DISK 15-NOV-06 1 1 TAG20061115T020005
> 90 B A A DISK 15-NOV-06 1 1 TAG20061115T020052
> 91 B F A DISK 15-NOV-06 1 1
>
> RMAN> report obsolete;
>
> RMAN retention policy will be applied to the command
> RMAN retention policy is set to recovery window of 7 days
> no obsolete backups found
>
> RMAN> report obsolete recovery window of 1 days;
>
> Report of obsolete backups and copies
> Type Key Completion Time Filename/Handle
> -------------------- ------ ------------------ --------------------
> Backup Set 82 11-NOV-06
> Backup Piece 82 11-NOV-06
> E:\BACKUP\RMAN\ONLINE\C-2040268233-20061111-00
> Backup Set 85 13-NOV-06
> Backup Piece 85 13-NOV-06
> E:\BACKUP\RMAN\ONLINE\C-2040268233-20061113-00
>
> RMAN> report obsolete recovery window of 4 days;
>
> no obsolete backups found
>
> RMAN>
>
> In any case I have opened up a SR, we'll see what they say..
  I see the problem now, for some reason a level 0 backup had failed, therefore none are obsolete as RMAN needs that older level 0 to recover from.. Received on Wed Nov 15 2006 - 13:58:06 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US