Re: Error recovering a database with a read-only tablespace

David,

Is it possible that after the duplicate that tablespace was still in READONLY mode and then a "nid" was issued for the database (I believe RMAN duplicate does that by derfault)? If so that tablespace would not have had its header updated. I suppose any subsequent backup's/restores would then experience the problem you're seeing.

Finn

On 4/17/08, David Lord <dlordster_at_gmail.com> wrote:
>
> Niall,
>
> Thanks for your reply. The database was created by an RMAN DUPLICATE
> and was opened RESETLOGS (its in NOARCHIVELOG mode so I don't suppose
> there's an alternative). The backup was taken after the OPEN
> RESETLOGS.
>
> Regards
> David Lord
>
> On 16/04/2008, Niall Litchfield <niall.litchfield_at_gmail.com> wrote:
> > David did the db have an OPEN RESETLOGS operation in the mean time -
> > or is this a clone RMAN DUPLICATE db? Either of these should give
> > your error
> > --
> > Niall Litchfield
> > Oracle DBA
> > http://www.orawin.info
> >
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l