Re: compatible parameter after upgrade

From: Sidney Chen <huanshengchen_at_gmail.com>
Date: Wed, 5 Oct 2011 16:04:58 +0800
Message-ID: <CAM_ddu8wQeD1s4OtbctV5sbbNotShbWzhgaVKh=BFPcKMojwqA_at_mail.gmail.com>

Kumar,
This parameter specifies the release with which Oracle must maintain compatibility, it control data format oracle write to the disk, including datafile/control file/redo file. unless there are new feature pre-request the version greater than "11.2.0", i think it's ok to keep it as 11.2.0.

note 444709.1 have a general guideline or you can refer to asktom for a detail descussion

"compatible simply tells us what we can write to disk. We won't use new redo log formats, we won'twrite new block level information, we won't create datafiles that have anything 9ir2 didn't have." http://goo.gl/b5Xqb

the new feature/bugfix related to query optimizer is controlled by another parameter: optimizer_features_enable.

On Wed, Oct 5, 2011 at 12:53 AM, Kumar Madduri <ksmadduri_at_gmail.com> wrote:

> Hello:
> As per "Database Initialization Parameters for Oracle Applications Release
> 12 [ID 396009.1]" the compatible parameter is always recommended to either
> 10.2.0 or 11.1.0 or 11.2.0 depending on the upgrade path.
> I have seen other recommendations where the compatible set to 11.2.0.2.2 or
> to the 4 digits of your version number.
> Have any of you set this parameter to 11.2.0.2.2 in an Oracle Ebiz
> environment.
> My concern is all the features/bugs fixed in 11.2.0.2.2 would not be
> available if we set to 11.2.0
>
> Thank you
> Kumar
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

• Sidney Chen

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

Received on Wed Oct 05 2011 - 03:04:58 CDT