RE: DB recovery question

From: Mark W. Farnham <>
Date: Mon, 27 Sep 2010 16:55:22 -0400
Message-ID: <>

Exactly what Jeremiah wrote, but one addition:

Nothing should prevent you from using the PREVIOUS level 0 backup and rolling it forward. That will be a time after the previous level 0 backup finished. Now I realize that is NOT what you asked, but it sounds like it may be the answer to your current dilemma.

This was a frequent misunderstanding folks had about recovering physical backups as well: You can't stop within a hot backup from the current set of backup files. But you can stop within a younger hot backup from a set of older hot backup files, since the "end of backup" I'm not fuzzy any more markers will have been reached.

Good luck.


-----Original Message-----
From: [] On Behalf Of Jeremiah Wilton
Sent: Monday, September 27, 2010 12:52 AM To:
Subject: Re: DB recovery question

On Sep 26, 2010, at 7:52 PM, Steve Baldwin wrote:

> I'm trying to restore the database to a point in time after the
> level 0 backup started but before it completed.


I think that's going to be a problem. If you don't recover to a point in time after the backup completed, some of the data is going to be inconsistent. If any data changed in the not-yet-backed-up datafiles after your target PIT but before the backup completed, those changed blocks will be from a time ahead of your target PIT.

You can open the database inconsistent using _allow_resetlogs_corruption, but that's only for in a pinch. With that option, the data may be internally inconsistent, and you can also get ORA-00600 and ORA-07445 errors in the opened database. Also the resulting database is unsupportable.

There are plenty of notes on using this parameter out in the public domain.


Jeremiah Wilton
Blue Gecko, Inc.


Received on Mon Sep 27 2010 - 15:55:22 CDT

Original text of this message