Restrictions for Database Features

Restrictions for Oracle XML DB

The following describes Autonomous Database support for Oracle XML DB features. To ensure the security and the performance of your database, some Oracle XML DB features are restricted.

The following is supported, in addition to the features listed:

Full support for XMLQuery, XMLTable, and other SQL/XML standard functions
Indexing schema including functional indexes using SQL/XML expressions, Structured XMLIndex and XQuery Full Text Index

Note:

If you migrate tables containing XMLType columns to Autonomous Database using Oracle Data Pump, you need to convert to Non-Schema Binary XML prior to using Oracle Data Pump Export (expdp).

Area	XML DB Feature	Supported in Autonomous Database	More Information
Repository	XML DB Protocol	No	Repository Access Using Protocols
Repository	XML DB Resources	No	Oracle XML DB Repository Resources
Repository	XML DB ACLs	No	Repository Access Control
Storage	XML Schema Registration	No	XML Schema Registration with Oracle XML DB
Storage	CLOB	No	Deprecated
Storage	Object Relational	No	XML Schema and Object-Relational XMLType
Storage	Binary XML	Yes (Non schema-based only)	XMLType Storage Models
Index	Structured XML Index	Yes	XMLIndex Structured Component
Index	XQuery Full Text Index	Yes	Indexing XML Data for Full-Text Queries
Index	Unstructured XMLIndex	No	XMLIndex Unstructured Component
Packages	XML DOM package	Yes	PL/SQL DOM API for XMLType (DBMS_XMLDOM)
Packages	XML Parser Package	Yes	PL/SQL Parser API for XMLType (DBMS_XMLPARSER)
Packages	XSL Processor (DBMS_XSLPROCESSOR)	Yes	PL/SQL XSLT Processor for XMLType (DBMS_XSLPROCESSOR)

For details on Oracle XML DB, see Oracle XML DB Developer's Guide.

Restrictions for Oracle Text

The following describes Autonomous Database support for Oracle Text features. To ensure the security and the performance of your database, some Oracle Text features are restricted.

Oracle Text Feature	Supported in Autonomous Database	More Information
All logging, and APIs which perform logging such as `ctx_report.query_log_summary`	Not Supported	QUERY_LOG_SUMMARY
File and URL datastore	Not Supported	Datastore Type
`CREATE INDEX` with `BIG_IO` option	Not supported by default.^Foot 1	Improved Response Time Using the BIG_IO Option of CONTEXT Index
`OPTIMIZE_INDEX` in rebuild mode	Not supported by default.(see Footnote 1).	OPTIMIZE_INDEX

^Footnote 1This is supported if you grant the privilege to create a trigger to the user (GRANT CREATE TRIGGER). You must also disable parallel DML at the session level (ALTER SESSION DISABLE PARALLEL DML).

For details on Oracle Text, see Oracle Text Application Developer's Guide.

Restrictions for Oracle Spatial and Graph

The following describes Autonomous Database support for Oracle Spatial and Graph features. To ensure the security and the performance of your database, some Oracle Spatial and Graph features are restricted.

Note:

Autonomous Database does not include Oracle Spatial and Graph 3-Dimensional geometry types and related operators, functions, or utilities.

Spatial Graph Feature	Supported in Autonomous Database	More Information
2D Geometry data types	Yes	SDO_GEOMETRY Object Type
2D Spatial operators	Yes	Spatial Operators
2D Spatial functions	Yes	SDO_GEOM Package (Geometry)
Coordinate Transformation	Yes	SDO_CS Package (Coordinate System Transformation)
Spatial Utility Functions (except GML and KML conversion functions)	Yes	SDO_UTIL Package (Utility)
Spatial Aggregate Functions	Yes	Spatial Aggregate Functions
Spatial indexing and querying features	Yes	SQL Statements for Indexing Spatial Data Spatial Query
2D Linear Referencing System	Yes	SDO_LRS Package (Linear Referencing System)
GeoJSON and JSON support for Spatial data types	Yes	JSON and GeoJSON Support in Oracle Spatial and Graph JSSDO_UTIL.TO_GEOJSON SDO_UTIL.TO_JSON SDO_UTIL.TO_JSON_VARCHAR
Location Tracking Server	Yes	SDO_TRKR Package (Location Tracking)
Spatial Analysis and Mining features	Yes	Spatial Analysis and Mining SDO_SAM Package (Spatial Analysis and Mining)
Flat Model for Point Cloud data	Yes	DO_PC_PKG.CLIP_PC_FLAT
RDF Graph	Yes	RDF Graph Overview
Property Graph	Yes	Spatial and Graph Property Graph Support Overview
Network Data Model	No	Network Data Model
GeoRaster	Yes	SDO_GEOR Package Reference
Routing Engine	No	Routing Engine
Geocoder	No (See note)	Geocoding Address Data Note: While the in-database Geocoder is not supported, access to geocoding is available through Oracle Spatial Studio which leverages a hosted geocoding service. See Oracle Spatial Studio for more information.
Spatial Visualization	No	Introduction to the Map Visualization Component
Topology Data Model	No	Topology Data Model Overview
Open Geospatial Consortium Web Services (WMS, WFS-T, C-SW, WCS, OpenLS)	No	SDO_WFS_PROCESS Package (WFS Processing) SDO_OLS Package (OpenLS)
GML	No	SDO_UTIL.TO_GMLGEOMETRY
Point Cloud Object Type	No	SDO_PC_PKG Package (Point Clouds)
Triangulated Irregular Network (TIN) types	No	SDO_TIN_PKG Package (TINs)

For details on Oracle Spatial and Graph, see Oracle Spatial and Graph Developer's Guide.

Restrictions for Oracle Application Express

Autonomous Database supports Oracle Application Express. To ensure the security and the performance of Autonomous Database, some Oracle Application Express features are restricted.

See Restrictions and Limitations for Oracle Application Express with Autonomous Database for details.

Restrictions for Oracle Flashback

Oracle Flashback Technology is a group of Oracle Database features that let you view past states of database objects or to return database objects to a previous state without using point-in-time media recovery.

To restore and recover your database to a point in time, see Restore and Recover your Autonomous Database.

Oracle Flashback Feature	Supported in Autonomous Database
`DBMS_FLASHBACK`	Yes except the procedure: `DBMS_FLASHBACK.TRANSACTION_BACKOUT`
Flashback Data Archive	No
Flashback Drop	Yes
Flashback Query	Yes
Flashback Table	Yes
Flashback Transaction	No
Flashback Transaction Query	Yes
Flashback Version Query	Yes

See About Oracle Flashback Technology for information on using Flashback features.

Restrictions for Fast Application Notification (FAN)

Subscribing to Fast Application Notification (FAN) events is not supported with Autonomous Database and is not needed. The functionality provided by FAN is provided out of the box with Autonomous Database. You do not need to enable your application for FAN or subscribe to FAN events.

You can use Application Continuity to mask outages from your applications. See Enable and Disable Application Continuity for more information.

Recommended Client Settings for Common Drivers

ODP.Net: The Oracle Data Provider for .NET (ODP.Net) unmanaged provider supports Application Continuity out of the box. When connecting an ODP.Net application to your Autonomous Database, do not explicitly set HA events, application continuity, or onsConfig; accept the default settings.
JDBC (thin) driver: When using the Universal Connection Pool (UCP), disable Fast Connection Failover. For example:
```
PoolDataSource.setFastConnectionFailoverEnabled(false)
```

Oracle Call Interface (OCI): Do not configure ONS servers in oraaccess.xml:

<ons>
   <servers> 
   <!—Do not enter any values --> 
   </servers> 
</ons>

Also, do not configure the <fan> section:

<fan>  
<!-- only possible values are "trace" or "error" -->  
    <subscription_failure_action>
   </subscription_failure_action>  
</fan>

Restrictions for Oracle Database Real Application Security

Oracle Database Real Application Security is a database authorization model that: supports declarative security policies, enables end-to-end security for multitier applications, provides an integrated solution to secure database and application resources, and advances the security architecture of Oracle Database to meet existing and emerging demands of applications developed for the Internet.

See Introducing Oracle Database Real Application Security more information.

Real Application Security works the same on Autonomous Database as on an on-premise database except you need to perform the following ADMIN tasks before using Real Application Security on Autonomous Database:

To create Real Application Security users/roles, you need the PROVISION system privilege. As the ADMIN user run the following command to grant this privilege to a database user:
```
SQL> EXEC XS_ADMIN_CLOUD_UTIL.GRANT_SYSTEM_PRIVILEGE('PROVISION','DB_USER');
```
In this example, DB_USER is a database user.

Running this command on Autonomous Database replaces the following on-premise database command (note the _CLOUD_ is not in the following package name):
```
SQL> EXEC SYS.XS_ADMIN_UTIL.GRANT_SYSTEM_PRIVILEGE('PROVISION', 'DB_USER', XS_ADMIN_UTIL.PTYPE_XS);
```
See General Procedures for Creating Application User Accounts for more information.
To create Real Application Security data controls, you need the ADMIN_ANY_SEC_POLICY privilege. As the ADMIN user run the following command to grant this privilege:
```
EXEC XS_ADMIN_CLOUD_UTIL.GRANT_SYSTEM_PRIVILEGE('ADMIN_ANY_SEC_POLICY','DB_USER');
```
In this example, DB_USER is a database user.

Running this command on Autonomous Database replaces the following on-premise database command (note the _CLOUD_ is not in the following package name):
```
SQL> EXEC SYS.XS_ADMIN_UTIL.GRANT_SYSTEM_PRIVILEGE('ADMIN_ANY_SEC_POLICY','DB_USER');
```
See Creating Roles and Application Users for more information.

List of Restricted and Removed Oracle Features

Lists the Oracle Database features that are not available in Autonomous Database. Additionally, database features designed for administration are not available.

List of Removed Oracle Features

Oracle Real Application Testing
Oracle Real Application Security Administration Console (RASADM)
Oracle OLAP
Oracle R capabilities of Oracle Advanced Analytics
Oracle Industry Data Models
Oracle Tuning Pack
Oracle Database Lifecycle Management Pack
Oracle Data Masking and Subsetting Pack
Oracle Cloud Management Pack for Oracle Database
Oracle Multimedia
Java in DB
Oracle Workspace Manager