Re: Compatibility parameter

Compatible determines the behaviour of the Oracle version you're running. Setting it to the same version like the release you have installed enabled all of its features.

After an upgrade the compatible plays a special role. In your case, after upgrading from Oracle9 to 10g (or higher), opening the database with compatible set to 10+ for the first time, will update the datafile headers to the new 10g format. Thereby making a direct downgrade no longer possible, as the 9i binaries can no longer read the files.

In general, unless there's very specific bugs forcing you to do otherwise (which happens rarely), it should be set to the same version as the software you're running, 10.2.0.4.0 in your case.

For some more info, see ML Notes *444709.1 **30699.1 or **733987.1 ... *there's
more on metalink

Cheers

Stefan

Stefan P Knecht
CEO & Founder
s_at_10046.ch

10046 Consulting GmbH
Schwarzackerstrasse 29
CH-8304 Wallisellen
Switzerland

Phone +41-(0)8400-10046
Cell +41 (0) 79 571 36 27
info_at_10046.ch
http://www.10046.ch

On Sun, Feb 8, 2009 at 6:07 PM, Luka Grah <luka.grah_at_gmail.com> wrote:

> ALoha!
>
>
> I have a question about setting compatibility parameter. I upgraded
> database from 9.2.0.8 to 10.2.0.4. I my pfile the compatibility
> parameter is set to 9.2.0.0.0. I want to perform compressed rman
> backup and that way I have to raise the compatibility parameter.
> To which number should I raise the parameter?How will this affect the
> database?
>
>
> Regards,
> Luka Grah
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

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