Re: Backup trends (2): HOT or COLD

Lucyna Witkowska <ypwitkow_at_nospamcyf-kr.edu.pl> wrote in message news:<c5omr6$n60$1_at_srv.cyf-kr.edu.pl>...
> Hi,
> Thank you very much for all answers and especcially Denis for his hints.
>
> I also think that RMAN is a good product in 8.1.7, and may be it is better
> in next versions. I like its ability to manage archived redo logs
> backups (backup and when success delete).
>
> So far, I encountered one minor bug - 'delete expired' didn't delete
> one not existed backup piece with status field='X', but as this record was
> aged out of the control file by control_file_keep_time, I don't really
> mind.

There are actually a number of bugs and misfeatures, but overall I'd say it's better than the old way. Definitely better in later versions. This was kinda interesting, if obscure: http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=BUG&p_id=2238718

>
> DD <denisdo_at_yahoo.com>:
>
> > If something went wrong - you always can "set DBID = xxxxxx" and
> > recover your backup from recovered (in it's turn, before all others)
> > backup copy of controlfile. And before each backup, do "report schema"
> > - it will help you alot in future. And, if you are really desperate -
> > there is a pl/sql procedures that can restore your original backup
> > file from "backup handle" - so you will be able to apply it even
> > without rman (not all the times - but still can do it). However,
> > properly organized backup never let such pain to happen.
>
> Where can I find such pl/sql procedures (just in case ;-))?
> Best greetings,
> Lucyna

http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=60545.1 among others.

jg

--
@home.com is bogus.
o so us go sob bog bug gus