Re: Compatible Parameter after Patching 10gR2

From: Palooka <nobody_at_nowhere.com>
Date: Wed, 25 Jun 2008 02:23:55 +0100
Message-ID: <N6h8k.13880$ft1.10171@newsfe14.ams2>

mccmx_at_hotmail.com wrote:

>> It is possible where new features are introduced in a patch such as
>> with 10.2 from 10.1 where leaving the compatible setting at the lower
>> level that the new feature is disabled.

>
> As far as I know there were no features introduced between 10.2.0.1
> and 10.2.0.3 (minor patch release).
>
> Also the Oracle docs (http://download.oracle.com/docs/cd/B19306_01/
> server.102/b14237/initparams028.htm#sthref88) show the following for
> the 'compatible' parameter:
>
> Default value 10.0.0
> Range of values 9.2.0 to default release
>
> This suggests to me that the general practice is to specify only 3
> significant digits. That would mean that there is no difference
> between 10.2.0.1 and 10.2.0.3.
>
> Matt
>

I recently patched 10.2.0.1 to 10.2.0.4 (AIX 5L 64 bit, in case it matters), and used dbua to upgrade the database. In its infinite wisdom Oracle kept the compatible parameter at the earlier release. I'm going to assume they had reasons, and stick with that unlrss I hear or read otherwise.

HTH,
Palooka Received on Tue Jun 24 2008 - 20:23:55 CDT