Re: compatible parameter after upgrade

From: Kumar Madduri <ksmadduri_at_gmail.com>
Date: Wed, 5 Oct 2011 06:00:38 -0700
Message-ID: <CAHDOOG6+NWeevYpcGeAweokJZmeUU2pAsjydii2L436PLO8L+g_at_mail.gmail.com>

Thank you Sidney for the links.
I was also going through this
http://download.oracle.com/docs/cd/E11882_01/server.112/e23633/intro.htm#CEGJDHGI and Table 1-1 gives the maximum value you could set. So in my case why would any one set 11.2.0.2.2 instead of 11.2.0 I understand we cannot revert it back to lower value once we bring up the database with the higher value.
This link above also says
controls the behavior of your database. For example, if you run an Oracle Database 11g Release 2 (11.2) database with the COMPATIBLE initialization parameter set to 10.1.0, then it generates database structures on disk that are compatible with Oracle Database 10g Release 1 (10.1).* Therefore, the COMPATIBLE initialization parameter enables or disables the use of features. If you try to use any new features that make the database incompatible with the COMPATIBLE initialization parameter, then an error is displayed. However, any new features that do not make incompatible changes on disk are enabled.
*- Kumar*
*
On Wed, Oct 5, 2011 at 1:04 AM, Sidney Chen <huanshengchen_at_gmail.com> wrote:

> 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 - 08:00:38 CDT