Ronny Egner ??????????:
> Arno Seidel schrieb:
>> Maxim Tkachenko schrieb:
>>>
>>>> recover database;
>>>> rman stops after some time and says:
>>>> RMAN-06025: no backup of log thread 1 seq found to restore
>>>> several times ... these requested log sequences are older than 3
>>>> weeks and i don?t have them any more.
>>>> Why does Rman want this old logs???
>>>> And how can i recover the database without these old logs?
>>>>
>>>> any help would be great.
>>>>
>>>> regards from germany
>>>>
>>>> Arno Seidel
>>>>
>>>>
>>> use "restore archivelog time " or "restore archivelog sequence XXXX".
>>> Number of sequence may give from backup.log or  use "list backup"
>>> on rman.
>>>
>>>
>> list backup only shows the highest missing archived_log sequwnce and
>> these backupsets are marked as
>> expired (they are over 3 weeks old and happend before 3 full backups
>> of the database).
>>
>> There must be a way to tell rman to skip these verry old archived_logs.
>> crosscheck backup
>> and delete expired backup does not change the behavior of the recover
>> command ...
>
> I??m sorry but this behavior is completely anormal. I??ve never
> seen that before.
> Could you show the complete script please and the complete output?
>
>
When use after backup
CROSSCHECK BACKUPSET;
DELETE NOPROMPT EXPIRED BACKUP OF DATABASE;
DELETE NOPROMPT EXPIRED BACKUP OF archivelog until time 'SYSDATE-1';
delete noprompt expired backupset;

Backup of archivelog don't delete from contorlfile. :( and I use
restore with time label or from seguence number of begin hot backup
else I have error .




--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting