|Oracle® XML DB Developer's Guide
12c Release 1 (12.1)
|PDF · Mobi · ePub|
This appendix describes the restrictions associated with Oracle XML DB.
Thin JDBC Driver Not Supported by Some XMLType Functions –
createXML() with a stream argument,
existsNode() work only with the OCI driver. Not all
oracle.xdb.XMLType functions are supported by the thin JDBC driver. If you do not use
oracle.xdb.XMLType classes and the OCI driver, you can lose performance benefits.
NCHAR, NVARCHAR2, and NCLOB Not Supported – Oracle XML DB does not support the use of SQL data types
NCLOB for any of the following:
Mapping XML elements or attributes to these data types using the
SQLType annotation in an XML schema
Generating XML data from these data types using SQL/XML functions
Within SQL/XML functions
XMLTable, using XQuery functions
fn:collection on tables that contain columns with these data types
To handle, store, or generate XML data that contains multibyte characters, Oracle strongly recommends that you use AL32UTF8 as the database character set.
XML Identifier Length Limit – Oracle XML DB supports only XML identifiers that are a maximum of 32767 bytes or 4000 bytes, depending on the value of initialization parameter
MAX_STRING_SIZE. See Oracle Database SQL Language Reference.
Repository File Size Limit – The maximum size of a file in Oracle XML DB Repository is 4 gigabytes. This implies the following limits for different kinds of file data:
4 gigabytes for any LOB, which means 2 gigacharacters for a
CLOB stored in the database character set AL32UTF8.
4 gigabytes for binary XML encoded data, which typically means more than 4 gigabytes of external XML data before encoding.
Indeterminate for XML data stored object-relationally.
Repository-Wide Resource Configuration File Limit – You cannot create more than 125 resource configuration files for repository-wide configuration.
Recursive Folder Deletion – You cannot delete more than 50 levels of nested folders using the option for recursive deletion.
No Hybrid Columnar Compression – Hybrid columnar compression, which is available only for Oracle Exadata Storage Server Software, cannot be used with an
XMLType column that is stored object-relationally or with an
XMLType table (no matter which storage model is used).
XMLType supports only basic compression and compression for OLTP.
No Column-Level Encryption for
XMLType – Column-level encryption is not supported for
XMLType. Tablespace-level encryption is supported for all
XMLType storage models.
No Composite Partitioning of Virtual Columns for Binary XML – Composite partitioning of virtual columns is not supported for binary XML storage.
XMLType Access over Database Links – Access to remote
XMLType tables or columns is not supported.
Oracle JVM Needed for Some Features – In general, the behavior of Oracle XML DB does not depend on whether or not you have Oracle JVM (Java Virtual Machine) installed. However, if you use Java servlets or PL/SQL package
DBMS_XMLQUERY then you must install Oracle JVM.
Editioning Views Not Compatible with XMLType – Editioning views are not compatible with
XMLType data that is stored object-relationally. They cannot be enabled in database schemas that contain persisted object types.
Transportable tablespaces and database consolidation – If your Oracle XML DB Repository in Oracle Database 11g Release 2 (11.2) has existing data then you cannot use transportable tablespaces to plug that database directly into a multitenant container database (CDB). Instead, upgrade the 11.2 database to 12.1, unplug it, and then plug it in.
"Oracle XML DB Support for XQuery" for information about Oracle XML DB support for XQuery
Oracle Exadata Storage Server Software User's Guide for information about Oracle Exadata Storage Server