Re: increasing COMPATIBLE parameter

From: Yong Huang <yong321_at_yahoo.com>
Date: Wed, 25 Mar 2015 17:05:35 +0000
Message-ID: <742201097.642701.1427303095872.JavaMail.yahoo_at_mail.yahoo.com>



Carlos Sierra said:
> As far as I know, COMPATIBLE has no effect on the CBO features
Carlos said what I wanted but didn't say because I was not 100% confident. I saved the content of the v$compatseg and v$compatibility views from Oracle 9.2.0.6: SQL> select * from v$compatseg order by 2, 1;
TYPE_ID  RELEASE   UPDATED-------- --------- ----------------BOOTSTRP 8.0.0.0.0 9.2.0.0.0COMPATSG 8.0.0.0.0 9.2.0.0.0APPCTX   8.1.0.0.0 9.2.0.0.0ASSOC    8.1.0.0.0 9.2.0.0.0DATETIME 8.1.0.0.0 9.2.0.0.0...
SQL> select * from v$compatibility order by 2, 1;
TYPE_ID  RELEASE   DESCRIPTION-------- --------- -----------------------------------------ALTERFRL 0.0.0.0.0 Alter freelistsAPPROLE  0.0.0.0.0 Application RoleBMINVPRT 0.0.0.0.0 Bitmap Index Invalidation ProtectionCARELOB  0.0.0.0.0 Cache Reads LOB...FUNCIND  8.1.0.0.0 Functional Index
...
(Full listing is at the bottom of http://yong321.freeshell.org/oranotes/CacheSegment.txt) None of the entries look like CBO related. Well, indirectly, some are related to the optimizer. For instance, if the compatible is lower than 8.1, you can't have function-based index, etc. But that's not CBO per se. Yong Huang
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Mar 25 2015 - 18:05:35 CET

Original text of this message