Re: lgwr dies after recovery

In the v$recover_file view is a column that has all the datafile change# listed.
If you haven't incremented recovery to or beyond those change# then some files will still need more recovery. Recover until time is better unless you are absolutely sure of the highest possible change#.

From Oracle's Backup and Recovery class there is a page that shows how to query the online redologs to see what logs have what ranges of changes and the SEQ. number. This would be helpful if you want to recover past what is available in archived redo logs.

Matt -

joerg.plaum_at_gmx.de wrote in article <7d07tb$9nr$1_at_nnrp1.dejanews.com>...
> hi there,
> after a recovery from an online backup using backup controlfile,
> our lgwr dies with ora-0600 [3705] during alter database open resetlogs.
> the most recent part of the alert-log is included.
> any suggestions ?
> regards
> joerg
> >>>>>>> snip
>
> Completed: ALTER DATABASE RECOVER CANCEL Sat Mar 20 13:02:42 1999 alter
> database open resetlogs Sat Mar 20 13:02:43 1999 RESETLOGS after
incomplete
> recovery UNTIL CHANGE 4133727 Sat Mar 20 13:03:17 1999 Errors in file
> /oracle/DG1/saptrace/background/dg1_lgwr_716.trc: ORA-00600: internal
error
> code, arguments: [3705], [1], [12], [12], [1], [], [], [] Sat Mar 20
> 13:03:18 1999 ORA-449 signalled during: alter database open resetlogs...
> <<<<<<<< snap
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
 

>
Received on Sun Mar 21 1999 - 05:46:47 CST