Re: resetlogs after Backup control file

I do not agree - it becomes an incomplete recovery if you are not able to apply the current online redolog.
If you have to open with resetlogs than that means that problably the current online redolog was not available (or worse, you forgot to apply it) and as a result, you will have to perform a resetlogs.

From the manual
(http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96519/glossary.htm#432745)

The recovery of a database in which you do not apply all of the changes generated since you created the restored backup. Incomplete recovery is usually performed when:

  a.. The online logs are lost due to hardware failure. In this case, you recover the database until the last archived log generated before the failure.
  b.. A user error necessitates recovery up until just before the error occurred.

  The requirement is to recover up until some point in time before an incorrect action occurred in the database. For example, a user mistakenly deletes payroll transactions before the transactions are sent to the payroll agency. In this example, the DBA will need to restore the whole database and then perform incomplete recovery up until the point just before the user deleted the transactions.

  c.. An archived redo log required for recovery is missing

  An archived redo log which is needed for complete recovery was not backed up, or the archived redo log contents are corrupt. In this case, you only option is to recover up to the missing log.

In each case, open the database with the RESETLOGS option after performing media recovery.

<Hans.Wijte_at_mail.ing.nl> wrote in message news:1123073785.741304.165760_at_g47g2000cwa.googlegroups.com...
> Any recovery "using backup controlfile" is by definition an incomplete
> recovery and therefore requires "open resetlogs"
>
Received on Wed Aug 03 2005 - 08:44:04 CDT