Compatible Parameter after Patching 10gR2

[mc...@hotmail.com]

I've recently upgraded to 10.2.0.3 (from 10.2.0.1) on Linux x86_64.

My compatible parameter is still set to 10.2.0.1. The patch set
documentation doesn't refer to setting the compatible parameter to
10.2.0.3 anywhere.

What is the general approach to setting this parameter after applying
a patch. Do you set it to the exact version (i.e. 10.2.0.3).

Are we effectively disabling some functionality by running our
10.2.0.3 DB with a 10.2.0.1 compatible parameter...?

Thanks

Matt

[Mark D Powell]

Generally after bringing the database up successfully on a new patch
release the DBA then updates the database parameter compatibility
setting to the exact release.

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.

HTH -- Mark D Powell --

[mc...@hotmail.com]

> 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

[Palooka]

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

[mc...@hotmail.com]

> 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.

Fair point.

The 10.2.0.3 patch document doesn't mention changing the parameter
after a successful patch application either. So I think its safe to
assume that it makes no difference for minor patch releases.

Matt