Restrictions for SQL Commands

Autonomous Database allows most of the SQL commands available in Oracle Database. To ensure the security and the performance of Autonomous Database, some SQL commands are restricted.

This section provides a list of SQL command limitations that are required to protect security and for the performance integrity of Autonomous Databases. Most of the standard SQL and PL/SQL syntax and constructs available with Oracle Database work in Autonomous Databases.

Note:

If you try to use a restricted SQL command the system reports:

ORA-01031: insufficient privileges

This error indicates that you are not allowed to run the SQL command in Autonomous Database.

The following SQL statements are not available in Autonomous Database:

SQL Statements with Restrictions in Autonomous Database

The following DDL statements are available in Autonomous Database with restrictions:

SQL Command Restrictions

ALTER PLUGGABLE DATABASE and ALTER DATABASE

Only the following clauses are allowed:

DATAFILE AUTOEXTEND ON

DATAFILE AUTOEXTEND OFF

DATAFILE RESIZE

DEFAULT EDITION

SET TIME_ZONE

SET CMU_WALLET

ALTER PROFILE

PASSWORD_VERIFY_FUNCTION

See Manage Password Complexity on Autonomous Database for more information.

Using ALTER PROFILE, the optional CONTAINER clause is ignored if specified.

See Create Users on Autonomous Database - Connecting with a Client Tool for information on the password parameter values defined in the default profile.

ALTER SESSION

Only the following clauses are allowed:

ADVISE COMMIT, ADVISE ROLLBACK, ADVISE NOTHING

CLOSE DATABASE LINK

ENABLE COMMIT IN PROCEDUREDISABLE COMMIT IN PROCEDURE

ENABLE PARALLEL <QUERY|DDL|DML>, DISABLE PARALLEL <QUERY|DDL|DML>, FORCE PARALLEL <QUERY|DDL|DML>

ENABLE RESUMABLE, DISABLE RESUMABLE

SET DEFAULT_COLLATION

SET EDITION

SET ISOLATION_LEVEL

SET ROW ARCHIVAL VISIBILITY

SET TIME_ZONE

ALTER SYSTEM

ALTER SYSTEM is not allowed except ALTER SYSTEM SET and ALTER SYSTEM KILL SESSION

SET can only be used to set parameters listed in Restrictions for Database Initialization Parameters.

ALTER USER

The following clause is ignored: DEFAULT TABLESPACE

The IDENTIFIED with the EXTERNALLY clause is not supported.

The IDENTIFIED BY VALUES clause is not allowed.

ALTER TABLE

For restrictions, see ALTER TABLE Restrictions.

CREATE PROFILE

PASSWORD_VERIFY_FUNCTION

See Manage Password Complexity on Autonomous Database for more information.

Using ALTER PROFILE, the optional CONTAINER clause is ignored if specified.

See Create Users on Autonomous Database - Connecting with a Client Tool for information on the password parameter values defined in the default profile.

CREATE TABLE

For restrictions, see CREATE TABLE Restrictions.

CREATE USER

The following clause is ignored:

  • DEFAULT TABLESPACE

IDENTIFIED with the EXTERNALLY clause is not supported.

The IDENTIFIED BY VALUES clause is not allowed.

CREATE TABLE Restrictions

XMLType tables using XML schema-based storage are not allowed. See Restrictions for Oracle XML DB for more information.

The clauses not in this list are allowed.

Clause Comment

cluster

Ignored

ilm_clause

Ignored

inmemory_table_clause

Ignored

LOB_storage_clause

Ignored

logging_clause

Ignored

organization external

Ignored

organization index

Creates a regular table with a primary key. Using the organization index clause does not create an index-organized table. You should test and verify the performance of the generated table for your application.

physical_properties

Ignored

Note:

For more information on CREATE TABLE, see Database SQL Language Reference.

ALTER TABLE Restrictions

The clauses not in this list are allowed.

Clause Comment

allocate_extent_clause

Ignored

alter_iot_clauses

Ignored

deallocate_unused_clause

Ignored

ilm_clause

Ignored

inmemory_table_clause

Ignored

logging_clause

Ignored

modify_LOB_storage_clause

Ignored

physical_attributes_clause

Ignored

shrink_clause

Ignored

Note:

For more information on ALTER TABLE, see Database SQL Language Reference.