On May 5, 10:00 am, "gba...@[EMAIL PROTECTED]
" <gba...@[EMAIL PROTECTED]
>
wrote:
> > Where have you read you can open the database in READONLY mode without
> > any resetlogs in this situation?
>
> Oracle=AE Database Backup and Recovery
Basics:http://download.oracle.com/d=
ocs/cd/B19306_01/backup.102/b14192/toc.htm
>
> Sections 7.6.4 and 7.6.5.
>
> 7.6.4 Database Point-in-Time Recovery Within the Current Incarnation.
>
> "If the operation completes without errors, then your DBPITR has
> succeeded. You can open the database read-only and perform queries as
> needed to ensure that the effects of the logical corruption have been
> reversed. If not, you may have chosen the wrong target SCN."
>
> 7.6.5 Options After Database Point-in-Time Recovery.
>
> "After a successful DBPITR, your choices are:
>
> * Ex****t one or more objects from your database using an Oracle
> ex****t utility such as Data Pump Ex****t. You can then recover the
> database to the current point in time and re-im****t the ex****ted
> objects, as a way to return these objects to their state prior to the
> unwanted change without abandoning all other changes.
> * Open your database for read-write, abandoning all changes
> after the target SCN. In such a case, you must open the database with
> the RESETLOGS option, as shown here:
> RMAN> ALTER DATABASE OPEN RESETLOGS; "
Thanks. That was a new feature of RMAN 10g apparently.
I haven't tested it so I have not any clue about your problem.
|
