The 'options' and features of a pluggable database must be fully supported by the entire environment, the CDB. As a result, Oracle had been 'encouraging' that all options and features be available for the event that a PDB requires them. Perhaps that is the "behaviour by design" to which they are alluding?
That, in turn, has an associated licensing nightmare, but that's a horse of a different colour.
XDB is not an option, in the for-fee sense of option that Oracle uses. It is (was, apparently) a selectable feature - meaning that you did not pay for the capabiliity, however you could select to not install it. Interesting note you highlight.
In 11gR2, part of XDB was available without forcing JVM. Express Edition includes APEX and LOCATOR, and APEX uses significant components of XDB, including the listener. However Express Edition did not include the JVM. That in turn gave a limit to what could be included in LOCATOR, as LOCATOR is the mainly subset SPATIAL GEOMETRY that does not need JVM. (Recursive definition ...)
A lot of Multimedia requires JVM, most of Spatial requires JVM, some edge components of XDB and it's Web Service interface need JVM. (The Web Services stuff http://docs.oracle.com/cd/B28359_01/java.111/b31225/chtwelve.htm#CBBEGBEI ... 11gR1 docs, but that iis what I have bookmarked ... feel free to get a newer link.)
On 09/03/2015 8:59 AM, Yong Huang (Redacted sender yong321@xxxxxxxxx for DMARC) wrote:
> Doesn't 12c require the JVM because of the mandatory XDB component? Maybe you're referring toCONTAINER DATABASE creation using DBCA no option to uncheck the database components (Doc ID 1590570.1)It doesn't say it's due to XDB. But it says "This has been done by design and an expected behaviour.".Yong
