Re: Lost partition containing indexes

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:<3f0bcb57$0$18489$ed9e5944_at_reading.news.pipex.net>...
> "Donald Thompson" <dlt_at_checkmysigforemail.com> wrote in message
> news:Pine.LNX.4.52.0307080921050.25177_at_junior.lunanet.biz...
> >
> > On Tue, 8 Jul 2003, Niall Litchfield wrote:
> >
> > > "Donald Thompson" <dlt_at_checkmysigforemail.com> wrote in message
> > > news:Pine.LNX.4.52.0307080902150.24034_at_junior.lunanet.biz...
> > > > I've lost the partition containing all of the oracle indexes due to a
> > > > drive failure. Is it possible to get oracle up without this and
> rebuild
> > > > the indexes? Anyone have pointers to docs describing how to recover
> from
> > > > something like this? TIA.
> > >
> > > Do you have a backup?
> >
> > I have an oracle backup, but not a filesystem backup for the indexes. I
> > sort of assumed that the oracle backups just contained the data for the
> > DB, not necessarily the indexes.
>
> A valid backup and all the archive logs from that time to the time of the
> crash means that you can perform a recovery. This is what I was getting at.
> As it sounds like you have not performed a recovery before I'd strongly
> advise you to call Oracle support and get them to talk you through it.
>
> On the other hand if you have *only* lost indexes (i.e. all the tables are
> there) then Sybrands suggestion could also make sense. you would drop the
> tablespaces that are unavailable, create new ones and recreate the indexes
> in the new tablespaces. This doesn't require backup and recovery, but you do
> lose all objects in those lost datafiles, so you better be sure you don't
> have required objects in them that cannot be recreated.

Two things:

select owner, index_name, tablespace_name from dba_indexes to be sure they all were where you thought (it seems inevitable that some are in the user default ts or, gulp, system ts).

See:

http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=1020181.6

And rename any user indices that have SYS... for a name when you get the scripts out.

jg

--
@home.com is bogus.
http://www.signonsandiego.com/news/uniontrib/wed/currents/news_1c9sciqa.html