Re: Standby database and UNRECOVERABLE

Karsten Farell <kfarrell_at_medimpact.com> wrote in news:acnn9.745$5u3.62169313_at_newssvr13.news.prodigy.com:

> Simply: yes and/or no.
>
> For the 'yes': As you mentioned, copying the data files will require a
> recovery to sync the control files (that step would be the same as if
> you lost the disk on which the index tablespaces were located). That
> means you have to copy more than the data files (ie, some/all of the
> redo or archive log files).
>
> For the 'no': Depending on the current contents of your standby
> database, you could mess things up even more by copying just certain
> pieces of the database. What you're likely to end up with is a
> database that Oracle can't figure out how to properly recover ... the
> indexes will be newer/older than the data they index ... constraints
> might be violated ... and on and on. Oracle recovery (by restoring
> data files of any kind - data/index) is meant to be done against the
> same database they were hot backup'd from.
>
> Conclusion: drop the indexes and recreate them (or rebuild them) ...
> but only if you can find a day or so that you can have the database to
> yourself (it can't be quick to create a 10g+ index).
>

I know that index creation can be "speeded up" (relatively speaking) by 1) Running on an SMP box & using PARALLEL option 2) Setting SORT_AREA_SIZE to a BIG value; assuming plenty of RAM. Whether or not either or both might help the original poster can likely only be proven by some hands on experimentation.

HTH & YMMV HAND! Received on Fri Oct 04 2002 - 20:35:59 CDT