Re: Compatible Parameter after Patching 10gR2

From: Mark D Powell <Mark.Powell_at_eds.com>
Date: Tue, 24 Jun 2008 07:12:01 -0700 (PDT)
Message-ID: <f769ed09-097c-4bb4-9819-23cdfee021b3@d77g2000hsb.googlegroups.com>


On Jun 24, 12:03 am, mc..._at_hotmail.com wrote:
> 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

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 -- Received on Tue Jun 24 2008 - 09:12:01 CDT

Original text of this message