Re: index rebuild online and compatible mode

Whenever you make a change to the COMPATIBLE parameter, you should take a full, cold backup - both before and after.

The compatible info is written to all files that make up your database, so it is also written to any archive log files which are created.

In order to go 'backwards' you need to use a ddl command "alter database reset compatibility" or something like that. Then - the next time you start up with the 8.0 compatible parameter, this info will be written to the file headers.

A few questions:
- Why not leave the database at compatible = 8.1.0? - This absolutely should be tested in a TEST environment before you use in production.
- I'd also suggest contacting oracle support for confirmation.

xiangz_at_rocketmail.com (Xiang Zhao) wrote in message news:<7c33c36d.0209162304.4bf6eac0_at_posting.google.com>...
> Hi all,
>
> We are currently running a huge oracle 8.1.7 database with a few
> tables having 70 million rows.
>
> And our compatible in init file is set to 8.0.5. and the index rebuild
> takes a lot of time. Now we'd like to try the new features introduced
> in 8i: rebuild index ONLINE.
> I'm wondering whether we can change the compatible back to 8.0.5 after
> we change the compatible to 8.1.7 just to use this rebuild index
> online new feature?
> I mean if something get wrong after we change it to 8.1.7, can we
> change it back? we won't use any other 8i features except index
> rebuilding online.
>
> Your kind help will be most appreciated.
>
>
> Thanks alot.
>
> -Xiang Zhao
Received on Tue Sep 17 2002 - 09:46:56 CDT