Setting COMPATIBLE when upgrading to 10.2.0.3
Date: Wed, 05 Mar 2008 14:17:53 -0900
Does anyone have any opinions about this parameter?
We've typically left it at the major release value, even after upgrading to point releases. I'm trying to find out exactly what would not be available if we leave COMPATIBLE=10.2.0.0.0 instead of changing it to the point release to which we upgraded, 10.2.0.3.0. It seems like if we patched the rdbms, the bug fixes should be included, but is there something that would actually exclude important things like that if one doesn't change the value of COMPATIBLE?
Any comments/insights are much appreciated.
- Maureen -- http://www.freelists.org/webpage/oracle-l