Re: Urgent call, user managed recovery

On Mon, 10 Jul 2006 20:30:26 +0200, "Lanying & Manfred" <manfis_at_t-online.de> wrote:

>Hello,
>
>*** A TEST ENVIRONMENT OF AN BACKUP/RECOVER BEGINNER ***
>
>Ora9.2 Win XP
>
>I've a horror scenario in archivelog modus, a consistent full database
>backup is always available.
>
>At the beginning of the database session as a sysdba, I've created a
>controlfile backup to trace.
>I've done a shutdown immediate, after that I've destroyed all the online
>redolog files and controlfiles.
>
>Having destroyed all these nice files I've copied all the backup database
>files (files of the tablespaces)
>back to the appropriate directory.
>
>With the help of these statements (out of controlfile trace file) Ii want to
>recover the database.
>---
>STARTUP NOMOUNT
>
>CREATE CONTROLFILE REUSE DATABASE "SUSHI" RESETLOGS ARCHIVELOG
>
>-- SET STANDBY TO MAXIMIZE PERFORMANCE
>
>MAXLOGFILES 50
>
>MAXLOGMEMBERS 5
>
>MAXDATAFILES 100
>
>MAXINSTANCES 1
>
>MAXLOGHISTORY 113
>
>LOGFILE
>
>GROUP 1 'C:\ORACLE\ORADATA\SUSHI\REDO01.LOG' SIZE 100M,
>
>GROUP 2 'C:\ORACLE\ORADATA\SUSHI\REDO02.LOG' SIZE 100M,
>
>GROUP 3 'C:\ORACLE\ORADATA\SUSHI\REDO03.LOG' SIZE 100M
>
>-- STANDBY LOGFILE
>
>DATAFILE
>
>'C:\ORACLE\ORADATA\SUSHI\SYSTEM01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\UNDOTBS01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\DRSYS01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\EXAMPLE01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\INDX01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\ODM01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\TOOLS01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\USERS01.DBF',
>
>'C:\ORACLE\ORADATA\SUSHI\XDB01.DBF'
>
>CHARACTER SET WE8MSWIN1252;
>
>--# Recovery is required if any of the datafiles are restored backups,
>
>--# or if the last shutdown was not normal or immediate.
>
>RECOVER DATABASE USING BACKUP CONTROLFILE
>
>--# Database can now be opened zeroing the online logs.
>
>ALTER DATABASE OPEN RESETLOGS;
>
>--# Commands to add tempfiles to temporary tablespaces.
>
>--# Online tempfiles have complete space information.
>
>--# Other tempfiles may require adjustment.
>
>---
>
>After entering this statement
>
>ALTER DATABASE OPEN RESETLOGS; I get an obviously inconsistent system
>tablespace which needs recovery.
>
>*************************************************************************
>QUESTION NOW: Can Oracle handle this horror scenario?
>*************************************************************************
>

*You* should handle it...by issuing the "RECOVER DATABASE until cancel USING BACKUP CONTROLFILE"

and then on oracle's request, apply all the archivelogs generated since the hot backup you have just restored until the point in time you would like your database to reach (you did keep those archivelogs, didn't you ?). It MUST be an incomplete/point-in-time recovery, because you deleted the online redo logs. Thus the "cancel" option above (which is not the only option for incomplete recovery, but go check the docs about that).

• Kenneth Koenraadt