# Overview of Oracle on Amazon RDS
Oracle overview

You can read the following sections to get an overview of RDS for Oracle.

**Topics**
+ [

# RDS for Oracle features
](Oracle.Concepts.FeatureSupport.md)
+ [

# RDS for Oracle releases
](Oracle.Concepts.database-versions.md)
+ [

# RDS for Oracle licensing options
](Oracle.Concepts.Licensing.md)
+ [

# RDS for Oracle users and privileges
](Oracle.Concepts.Privileges.md)
+ [

# RDS for Oracle DB instance classes
](Oracle.Concepts.InstanceClasses.md)
+ [

# RDS for Oracle database architecture
](oracle-multi-architecture.md)
+ [

# RDS for Oracle initialization parameters
](Oracle.Concepts.FeatureSupport.Parameters.md)
+ [

# RDS for Oracle character sets
](Appendix.OracleCharacterSets.md)
+ [

# RDS for Oracle limitations
](Oracle.Concepts.limitations.md)

# RDS for Oracle features
Oracle features

Amazon RDS for Oracle supports most of the features and capabilities of Oracle Database. Some features might have limited support or restricted privileges. Some features are only available in Enterprise Edition, and some require additional licenses. For more information about Oracle Database features for specific Oracle Database versions, see the *Oracle Database Licensing Information User Manual* for the version you're using.

**Topics**
+ [

## New features in RDS for Oracle
](#Oracle.Concepts.FeatureSupport.new)
+ [

## Supported features in RDS for Oracle
](#Oracle.Concepts.FeatureSupport.supported)
+ [

## Unsupported features in RDS for Oracle
](#Oracle.Concepts.FeatureSupport.unsupported)

## New features in RDS for Oracle
New features

To see new features in RDS for Oracle, search [Document history](WhatsNew.md) for the keyword **Oracle**.

## Supported features in RDS for Oracle
Supported features

Amazon RDS for Oracle supports the following Oracle Database features:

**Note**  
The following list isn't exhaustive.
+ Advanced Compression
+ Oracle Application Express (APEX)

  For more information, see [Oracle Application Express (APEX)](Appendix.Oracle.Options.APEX.md).
+ Automatic Memory Management
+ Automatic Undo Management
+ Automatic Workload Repository (AWR)

  For more information, see [Generating performance reports with Automatic Workload Repository (AWR)](Appendix.Oracle.CommonDBATasks.AWR.md).
+ Active Data Guard with Maximum Performance in the same Amazon Region or across Amazon Regions

  For more information, see [Working with read replicas for Amazon RDS for Oracle](oracle-read-replicas.md).
+ Blockchain tables (Oracle Database 21c and higher)

  For more information, see [Managing Blockchain Tables ](https://docs.oracle.com/en/database/oracle/oracle-database/21/admin/managing-tables.html#GUID-43470B0C-DE4A-4640-9278-B066901C3926) in the Oracle Database documentation.
+ Continuous Query Notification

  For more information, see [ Using Continuous Query Notification (CQN)](https://docs.oracle.com/en/database/oracle/oracle-database/19/adfns/cqn.html#GUID-373BAF72-3E63-42FE-8BEA-8A2AEFBF1C35) in the Oracle documentation.
+ Data Redaction
+ Continuous Query Notification

  For more information, see [ Database Change Notification](https://docs.oracle.com/cd/E11882_01/java.112/e16548/dbchgnf.htm#JJDBC28815) in the Oracle documentation.
+ Database In-Memory
+ Distributed Queries and Transactions
+ Edition-Based Redefinition

  For more information, see [Setting the default edition for a DB instance](Appendix.Oracle.CommonDBATasks.DefaultEdition.md).
+ EM Express (12c and higher)

  For more information, see [Oracle Enterprise Manager](Oracle.Options.OEM.md).
+ Fine-Grained Auditing
+ Flashback Table, Flashback Query, Flashback Transaction Query
+ Gradual password rollover for applications (Oracle Database 21c and higher)

  For more information, see [Managing Gradual Database Password Rollover for Applications ](https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/configuring-authentication.html#GUID-ACBA8DAE-C5B4-4811-A31D-53B97C50249B) in the Oracle Database documentation.
+ HugePages

  For more information, see [Turning on HugePages for an RDS for Oracle instance](Oracle.Concepts.HugePages.md).
+ Import/export (legacy and Data Pump) and SQL\$1Loader

  For more information, see [Importing data into Oracle on Amazon RDS](Oracle.Procedural.Importing.md).
+ Java Virtual Machine (JVM)

  For more information, see [Oracle Java virtual machine](oracle-options-java.md).
+ JavaScript (Oracle Database 21c and higher)

  For more information, see [DBMS\$1MLE](https://docs.oracle.com/en/database/oracle/oracle-database/21/arpls/dbms_mle.html#GUID-3F5B47A5-2C73-4317-ACD7-E93AE8B8E301) in the Oracle Database documentation.
+ Label Security

  For more information, see [Oracle Label Security](Oracle.Options.OLS.md).
+ Locator

  For more information, see [Oracle Locator](Oracle.Options.Locator.md).
+ Materialized Views
+ Multitenant

  The Oracle multitenant architecture is supported for all Oracle Database 19c and higher releases. For more information, see [Working with CDBs in RDS for Oracle](oracle-multitenant.md).
+ Network encryption

  For more information, see [Oracle native network encryption](Appendix.Oracle.Options.NetworkEncryption.md) and [Oracle Secure Sockets Layer](Appendix.Oracle.Options.SSL.md).
+ Partitioning
+ Real Application Testing

  To use the full capture and replay capabilities, you must use Amazon Elastic File System (Amazon EFS) to access files generated by Oracle Real Application Testing. For more information, see [Amazon EFS integration](oracle-efs-integration.md) and the blog post [Use Oracle Real Application Testing features with Amazon RDS for Oracle](https://amazonaws-china.com/blogs/database/use-oracle-real-application-testing-features-with-amazon-rds-for-oracle/).
+ Sharding at the application level (but not the Oracle Sharding feature)
+ Spatial and Graph

  For more information, see [Oracle Spatial](Oracle.Options.Spatial.md).
+ Star Query Optimization
+ Streams and Advanced Queuing
+ Summary Management – Materialized View Query Rewrite
+ Text (File and URL data store types are not supported)
+ Total Recall
+ Transparent Data Encryption (TDE)

  For more information, see [Oracle Transparent Data Encryption](Appendix.Oracle.Options.AdvSecurity.md).
+ Unified Auditing, Mixed Mode

  For more information, see [ Mixed mode auditing](https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/introduction-to-auditing.html#GUID-4A3AEFC3-5422-4320-A048-8219EC96EAC1) in the Oracle documentation.
+ XML DB (without the XML DB Protocol Server)

  For more information, see [Oracle XML DB](Appendix.Oracle.Options.XMLDB.md).
+ Virtual Private Database

## Unsupported features in RDS for Oracle
Unsupported features

Amazon RDS for Oracle doesn't support the following Oracle Database features:

**Note**  
The following list isn't exhaustive.
+ Automatic Storage Management (ASM)
+ Database Vault
+ Flashback Database
**Note**  
For alternative solutions, see the Amazon Database Blog entry [Alternatives to the Oracle flashback database feature in Amazon RDS for Oracle](https://amazonaws-china.com/blogs/database/alternatives-to-the-oracle-flashback-database-feature-in-amazon-rds-for-oracle/).
+ FTP and SFTP
+ Hybrid partitioned tables
+ Messaging Gateway
+ Oracle Enterprise Manager Cloud Control Management Repository
+ Real Application Clusters (Oracle RAC)
+ Real Application Security (RAS)
+ Unified Auditing, Pure Mode
+ Workspace Manager (WMSYS) schema

**Warning**  
In general, Amazon RDS doesn't prevent you from creating schemas for unsupported features. However, if you create schemas for Oracle features and components that require SYSDBA privileges, you can damage the data dictionary and affect the availability of your DB instance. Use only supported features and schemas that are available in [Adding options to Oracle DB instances](Appendix.Oracle.Options.md).

# RDS for Oracle releases
Oracle versions

RDS for Oracle for Oracle supports multiple Oracle Database releases.

**Note**  
For information about upgrading your releases, see [Upgrading the RDS for Oracle DB engine](USER_UpgradeDBInstance.Oracle.md).

**Topics**
+ [

## Oracle Database 21c with Amazon RDS
](#Oracle.Concepts.FeatureSupport.21c)
+ [

## Oracle Database 19c with Amazon RDS
](#Oracle.Concepts.FeatureSupport.19c)

## Oracle Database 21c with Amazon RDS
Oracle Database 21c

Amazon RDS supports Oracle Database 21c, which includes Oracle Enterprise Edition and Oracle Standard Edition 2. Oracle Database 21c (21.0.0.0) includes many new features and updates from the previous version. A key change is that Oracle Database 21c supports only the multitenant architecture: you can no longer create a database as a traditional non-CDB. To learn more about the differences between CDBs and non-CDBs, see [Limitations of RDS for Oracle CDBs](Oracle.Concepts.CDBs.md#Oracle.Concepts.single-tenant-limitations).

In this section, you can find the features and changes important to using Oracle Database 21c (21.0.0.0) on Amazon RDS. For a complete list of the changes, see the [Oracle database 21c](https://docs.oracle.com/en/database/oracle/oracle-database/21/index.html) documentation. For a complete list of features supported by each Oracle Database 21c edition, see [ Permitted features, options, and management packs by Oracle database offering](https://docs.oracle.com/en/database/oracle/oracle-database/21/dblic/Licensing-Information.html) in the Oracle documentation.

### Amazon RDS parameter changes for Oracle Database 21c (21.0.0.0)


Oracle Database 21c (21.0.0.0) includes several new parameters and parameters with new ranges and new default values.

**Topics**
+ [

#### New parameters
](#Oracle.Concepts.FeatureSupport.21c.parameters.new)
+ [

#### Changes for the compatible parameter
](#Oracle.Concepts.FeatureSupport.21c.parameters.compatible)
+ [

#### Removed parameters
](#Oracle.Concepts.FeatureSupport.21c.parameters.removed)

#### New parameters


The following table shows the new Amazon RDS parameters for Oracle Database 21c (21.0.0.0).


****  

|  Name  |  Range of values  | Default value |  Modifiable  |  Description  | 
| --- | --- | --- | --- | --- | 
|    [blockchain\$1table\$1max\$1no\$1drop](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/BLOCKCHAIN_TABLE_MAX_NO_DROP.html#GUID-26AF15B2-5621-4602-AA6E-D92842E4285C)    |  `NONE \| 0`  |  `NONE`  |  Y  |  Lets you control the maximum amount of idle time that can be specified when creating a blockchain table.  | 
|  [dbnest\$1enable](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/DBNEST_ENABLE.html#GUID-2F30C9D3-808E-42CD-ADA6-595FAE518A60)  |  `NONE \| CDB_RESOURCE_PDB_ALL`  |  `NONE`  |  N  |  Allows you to enable or disable dbNest. DbNest provides operating system resource isolation and management, file system isolation, and secure computing for PDBs.   | 
|  [dbnest\$1pdb\$1fs\$1conf](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/DBNEST_PDB_FS_CONF.html)  |  `NONE \| pathname`  |  `NONE`  |  N  |  Specifies the dbNest file system configuration file for a PDB.   | 
|  [diagnostics\$1control](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/DIAGNOSTICS_CONTROL.html)  |  `ERROR \| WARNING \| IGNORE`  | IGNORE |  Y  |  Allows you to control and monitor the users who perform potentially unsafe database diagnostic operations.  | 
|  [drcp\$1dedicated\$1opt](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/DRCP_DEDICATED_OPT.html)  |  `YES \| NO`  | YES |  Y  |  Enables or disables the use of dedicated optimization with Database Resident Connection Pooling (DRCP).  | 
|  [enable\$1per\$1pdb\$1drcp](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/ENABLE_PER_PDB_DRCP.html)  |  `true \| false`  |  `true`  |  N  |  Controls whether Database Resident Connection Pooling (DRCP) configures one connection pool for the entire CDB or one isolated connection pool for each PDB.  | 
|  [inmemory\$1deep\$1vectorization](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/INMEMORY_DEEP_VECTORIZATION.html#GUID-59E87FDC-1DB4-4ACD-A807-D0C1AE44210D)  |  `true \| false`  |  `true`  |  Y  |  Enables or disables the deep vectorization framework.  | 
|  [mandatory\$1user\$1profile](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/MANDATORY_USER_PROFILE.html)  |  *profile\$1name*  |  N/A  |  N  |  Specifies the mandatory user profile for a CDB or PDB.  | 
|  [optimizer\$1capture\$1sql\$1quarantine](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/OPTIMIZER_CAPTURE_SQL_QUARANTINE.html)  |  `true \| false`  |  `false`  |  Y  |  Enables or disables the deep vectorization framework.  | 
|  [optimizer\$1use\$1sql\$1quarantine](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/OPTIMIZER_CAPTURE_SQL_QUARANTINE.html#GUID-9DBBDBD3-2AA3-4627-9D3A-5330F447BEBB)  |  `true \| false`  |  `false`  |  Y  |  Enables or disables the automatic creation of SQL Quarantine configurations.   | 
|  [result\$1cache\$1execution\$1threshold](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/RESULT_CACHE_EXECUTION_THRESHOLD.html)  |  `0` to `68719476736`  |  `2`  |  Y  |  Specifies the maximum number of times a PL/SQL function can be executed before its result is stored in the result cache.   | 
|  [result\$1cache\$1max\$1temp\$1result](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/RESULT_CACHE_MAX_TEMP_RESULT.html)  |  `0` to `100`  |  `5`  |  Y  |  Specifies the percentage of `RESULT_CACHE_MAX_TEMP_SIZE` that any single cached query result can consume.   | 
|  [result\$1cache\$1max\$1temp\$1size](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/RESULT_CACHE_MAX_TEMP_SIZE.html)  |  `0` to `2199023255552`  |  `RESULT_CACHE_SIZE * 10`  |  Y  |  Specifies the maximum amount of temporary tablespace (in bytes) that can be consumed by the result cache.   | 
|  [sga\$1min\$1size](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/SGA_MIN_SIZE.html)  |  `0` to `2199023255552` (maximum value is 50% of `sga_target`)  |  `0`  |  Y  |  Indicates a possible minimum value for SGA usage of a pluggable database (PDB).  | 
|  [tablespace\$1encryption\$1default\$1algorithm](https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/TABLESPACE_ENCRYPTION_DEFAULT_ALGORITHM.html)  |  `GOST256 \| SEED128 \| ARIA256 \| ARIA192 \| ARIA128 \| 3DES168 \| AES256 \| AES192 \| AES128`  | AES128 |  Y  |  Specifies the default algorithm the database uses when encrypting a tablespace.   | 

#### Changes for the compatible parameter


The `compatible` parameter has a new maximum value for Oracle Database 21c (21.0.0.0) on Amazon RDS. The following table shows the new default value.


****  

|  Parameter name  |  Oracle Database 21c (21.0.0.0) maximum value  | 
| --- | --- | 
|  [ compatible](https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/COMPATIBLE.html#GUID-6C57EE11-BD06-4BB8-A0F7-D6CDDD086FA9)  |  21.0.0  | 

#### Removed parameters


The following parameters were removed in Oracle Database 21c (21.0.0.0):
+ `remote_os_authent`
+ `sec_case_sensitive_logon`
+ `unified_audit_sga_queue_size`

## Oracle Database 19c with Amazon RDS
Oracle Database 19c

Amazon RDS supports Oracle Database 19c, which includes Oracle Enterprise Edition and Oracle Standard Edition Two.

Oracle Database 19c (19.0.0.0) includes many new features and updates from the previous version. In this section, you can find the features and changes important to using Oracle Database 19c (19.0.0.0) on Amazon RDS. For a complete list of the changes, see the [Oracle database 19c](https://docs.oracle.com/en/database/oracle/oracle-database/19/index.html) documentation. For a complete list of features supported by each Oracle Database 19c edition, see [ Permitted features, options, and management packs by Oracle database offering](https://docs.oracle.com/en/database/oracle/oracle-database/19/dblic/Licensing-Information.html#GUID-0F9EB85D-4610-4EDF-89C2-4916A0E7AC87) in the Oracle documentation. 

### Amazon RDS parameter changes for Oracle Database 19c (19.0.0.0)


Oracle Database 19c (19.0.0.0) includes several new parameters and parameters with new ranges and new default values.

**Topics**
+ [

#### New parameters
](#Oracle.Concepts.FeatureSupport.19c.Parameters.new)
+ [

#### Changes to the compatible parameter
](#Oracle.Concepts.FeatureSupport.19c.Parameters.compatible)
+ [

#### Removed parameters
](#Oracle.Concepts.FeatureSupport.19c.Parameters.compatible.removed-parameters)

#### New parameters


The following table shows the new Amazon RDS parameters for Oracle Database 19c (19.0.0.0).


****  

|  Name  |  Values  |  Modifiable  |  Description  | 
| --- | --- | --- | --- | 
|   [ lob\$1signature\$1enable](https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/lob_signature_enable.html#GUID-62997AB5-1084-4C9A-8258-8CB695C7A1D6)   |  TRUE, FALSE (default)  |  Y  |  Enables or disables the LOB locator signature feature.  | 
|   [ max\$1datapump\$1parallel\$1per\$1job](https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/MAX_DATAPUMP_PARALLEL_PER_JOB.html#GUID-33B1F962-B8C3-4DCE-BE68-66FC5D34ECA3)   |  1 to 1024, or AUTO  |  Y  |  Specifies the maximum number of parallel processes allowed for each Oracle Data Pump job.  | 

#### Changes to the compatible parameter


The `compatible` parameter has a new maximum value for Oracle Database 19c (19.0.0.0) on Amazon RDS. The following table shows the new default value. 


****  

|  Parameter name  |  Oracle Database 19c (19.0.0.0) maximum value  | 
| --- | --- | 
|  [ compatible](https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/COMPATIBLE.html#GUID-6C57EE11-BD06-4BB8-A0F7-D6CDDD086FA9)  |  19.0.0  | 

#### Removed parameters


The following parameters were removed in Oracle Database 19c (19.0.0.0):
+ `exafusion_enabled`
+ `max_connections`
+ `o7_dictionary_access`

# RDS for Oracle licensing options
Oracle licensing

Amazon RDS for Oracle has two licensing options: License Included (LI) and Bring Your Own License (BYOL). After you create an Oracle DB instance on Amazon RDS, you can change the licensing model by modifying the DB instance. For more information, see [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md).

**Important**  
Make sure that you have the appropriate Oracle Database license, with Software Update License and Support, for your DB instance class and Oracle Database edition. Also make sure that you have licenses for any separately licensed Oracle Database features.

**Topics**
+ [

## License Included model for SE2
](#Oracle.Concepts.Licensing.LicenseIncluded)
+ [

## Bring Your Own License (BYOL) for EE and SE2
](#Oracle.Concepts.Licensing.BYOL)
+ [

## Licensing Oracle Multi-AZ deployments
](#Oracle.Concepts.Licensing.MAZ)

## License Included model for SE2


In the License Included model, you don't need to purchase Oracle Database licenses separately. Amazon holds the license for the Oracle database software. The License Included model is only supported on Amazon RDS for Oracle Database Standard Edition 2 (SE2).

In this model, if you have an Amazon Web Services Support account with case support, contact Amazon Web Services Support for both Amazon RDS and Oracle Database service requests. Your use of RDS for Oracle the LI option is subject to Section 10.3.1 of the [Amazon Service Terms](https://aws.amazon.com/service-terms/).

## Bring Your Own License (BYOL) for EE and SE2


In the BYOL model, you can use your existing Oracle Database licenses to deploy databases on Amazon RDS. Amazon RDS supports the BYOL model only for Oracle Database Enterprise Edition (EE) and Oracle Database Standard Edition 2 (SE2).

Make sure that you have the appropriate Oracle Database license (with Software Update License and Support) for the DB instance class and Oracle Database edition you wish to run. You must also follow Oracle's policies for licensing Oracle Database software in the cloud computing environment. For more information on Oracle's licensing policy for Amazon EC2, see [ Licensing Oracle software in the cloud computing environment](http://www.oracle.com/us/corporate/pricing/cloud-licensing-070579.pdf).

In this model, you continue to use your active Oracle support account, and you contact Oracle directly for Oracle Database service requests. If you have an Amazon Web Services Support account with case support, you can contact Amazon Web Services Support for Amazon RDS issues.

### Integrating with Amazon License Manager


To make it easier to monitor Oracle license usage in the BYOL model, [Amazon License Manager](https://www.amazonaws.cn/license-manager/) integrates with Amazon RDS for Oracle. License Manager supports tracking of RDS for Oracle engine editions and licensing packs based on virtual cores (vCPUs). You can also use License Manager with Amazon Organizations to manage all of your organizational accounts centrally.

The following table shows the product information filters for RDS for Oracle.

[\[See the AWS documentation website for more details\]](http://docs.amazonaws.cn/en_us/AmazonRDS/latest/UserGuide/Oracle.Concepts.Licensing.html)

To track license usage of your Oracle DB instances, you can create a self-managed license using Amazon License Manager. In this case, RDS for Oracle resources that match the product information filter are automatically associated with the self-managed license. Discovery of Oracle DB instances can take up to 24 hours. You can also track a license across accounts by using Amazon Resource Access Manager.

#### Console


**To create a self-managed license in Amazon License Manager to track the license usage of your RDS for Oracle DB instances**

1. Go to [https://console.amazonaws.cn/license-manager/](https://console.amazonaws.cn/license-manager/).

1. Choose **Create self-managed license**.

   For instructions, see [Create a self-managed license](https://docs.amazonaws.cn/license-manager/latest/userguide/create-license-configuration.html) in the *Amazon License Manager User Guide*.

   Add a rule for an **RDS Product Information Filter** in the **Product Information** panel.

   For more information, see [ProductInformation](https://docs.amazonaws.cn/license-manager/latest/APIReference/API_ProductInformation.html) in the *Amazon License Manager API Reference*.

1. (Cross-account tracking only) Use Amazon Resource Access Manager to share your self-managed licenses with any Amazon account or through Amazon Organizations. For more information, see [Sharing your Amazon resources](https://docs.amazonaws.cn/ram/latest/userguide/getting-started-sharing.html).

#### Amazon CLI


To create a self-managed license by using the Amazon CLI, call the [create-license-configuration](https://docs.amazonaws.cn/cli/latest/reference/license-manager/create-license-configuration.html) command. Use the `--cli-input-json` or `--cli-input-yaml` parameters to pass the parameters to the command.

**Example**  
The following example creates a self-managed license for Oracle Enterprise Edition.   

```
aws license-manager create-license-configuration --cli-input-json file://rds-oracle-ee.json
```
The following is the sample `rds-oracle-ee.json` file used in the example.  

```
{
    "Name": "rds-oracle-ee",
    "Description": "RDS Oracle Enterprise Edition",
    "LicenseCountingType": "vCPU",
    "LicenseCountHardLimit": false,
    "ProductInformationList": [
        {
            "ResourceType": "RDS",
            "ProductInformationFilterList": [
                {
                    "ProductInformationFilterName": "Engine Edition",
                    "ProductInformationFilterValue": ["oracle-ee"],
                    "ProductInformationFilterComparator": "EQUALS"
                }
            ]
        }
    ]
}
```

For more information about product information, see [Automated discovery of resource inventory](https://docs.amazonaws.cn/license-manager/latest/userguide/automated-discovery.html) in the *Amazon License Manager User Guide*.

For more information about the `--cli-input` parameter, see [Generating Amazon CLI skeleton and input parameters from a JSON or YAML input file](https://docs.amazonaws.cn/cli/latest/userguide/cli-usage-skeleton.html) in the *Amazon CLI User Guide*.

### Migrating between Oracle Database editions
Migrating between Oracle Database editions

If you have an unused BYOL Oracle Database license appropriate for the edition and class of DB instance that you plan to run, you can migrate from Standard Edition 2 (SE2) to Enterprise Edition (EE). You can't migrate from EE to other editions.

**To change your Oracle Database edition and retain your data**

1. Create a snapshot of the DB instance.

   For more information, see [Creating a DB snapshot for a Single-AZ DB instance for Amazon RDS](USER_CreateSnapshot.md).

1. Restore the snapshot to a new DB instance, and select the Oracle database edition you want to use.

   For more information, see [Restoring to a DB instance](USER_RestoreFromSnapshot.md).

1. (Optional) Delete the old DB instance, unless you want to keep it running and have the appropriate Oracle Database licenses for it.

   For more information, see [Deleting a DB instance](USER_DeleteInstance.md).

## Licensing Oracle Multi-AZ deployments


Amazon RDS supports Multi-AZ deployments for Oracle as a high-availability, failover solution. We recommend Multi-AZ for production workloads. For more information, see [Configuring and managing a Multi-AZ deployment for Amazon RDS](Concepts.MultiAZ.md). 

If you use the Bring Your Own License model, you must have a license for both the primary DB instance and the standby DB instance in a Multi-AZ deployment. 

# RDS for Oracle users and privileges
Oracle users and privileges

When you create an Amazon RDS for Oracle DB instance, the default master user has most of the maximum user permissions on the DB instance. Use the master user account for any administrative tasks, such as creating additional user accounts in your database. Because RDS is a managed service, you aren't allowed to log in as `SYS` and `SYSTEM`, and thus don't have `SYSDBA` privileges.

**Topics**
+ [

## Limitations for Oracle DBA privileges
](#Oracle.Concepts.dba-limitations)
+ [

## How to manage privileges on SYS objects
](#Oracle.Concepts.Privileges.SYS-objects)

## Limitations for Oracle DBA privileges


In the database, a role is a collection of privileges that you can grant to or revoke from a user. An Oracle database uses roles to provide security. For more information, see [Configuring Privilege and Role Authorization](https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/configuring-privilege-and-role-authorization.html#GUID-89CE989D-C97F-4CFD-941F-18203090A1AC) in the Oracle Database documentation.

The predefined role `DBA` normally allows all administrative privileges on an Oracle database. When you create a DB instance, your master user account gets DBA privileges (with some limitations). To deliver a managed experience, an RDS for Oracle database doesn't provide the following privileges for the `DBA` role: 
+ `ALTER DATABASE`
+ `ALTER SYSTEM`
+ `CREATE ANY DIRECTORY`
+ `DROP ANY DIRECTORY`
+ `GRANT ANY PRIVILEGE`
+ `GRANT ANY ROLE`

For more RDS for Oracle system privilege and role information, see [Master user account privileges](UsingWithRDS.MasterAccounts.md).

## How to manage privileges on SYS objects


You can manage privileges on `SYS` objects by using the `rdsadmin.rdsadmin_util` package. For example, if you create the database user `myuser`, you could use the `rdsadmin.rdsadmin_util.grant_sys_object` procedure to grant `SELECT` privileges on `V_$SQLAREA` to `myuser`. For more information, see the following topics:
+ [Granting SELECT or EXECUTE privileges to SYS objects](Appendix.Oracle.CommonDBATasks.TransferPrivileges.md)
+ [Revoking SELECT or EXECUTE privileges on SYS objects](Appendix.Oracle.CommonDBATasks.RevokePrivileges.md)
+ [Granting privileges to non-master users](Appendix.Oracle.CommonDBATasks.PermissionsNonMasters.md)

# RDS for Oracle DB instance classes
Oracle instance classes

The computation and memory capacity of an RDS for Oracle DB instance is determined by its instance class. The DB instance class you need depends on your processing power and memory requirements.



## Supported RDS for Oracle DB instance classes
Supported instance classes

The supported RDS for Oracle instance classes are a subset of the RDS DB instance classes. For the complete list of RDS instance classes, see [DB instance classes](Concepts.DBInstanceClass.md).



### RDS for Oracle preconfigured DB instance classes
Preconfigured instance classes

RDS for Oracle also offers instance classes that are preconfigured for workloads that require additional memory, storage, and I/O per vCPU. These instance classes use the following naming convention.

```
db.r5b.instance_size.tpcthreads_per_core.memratio
db.r5.instance_size.tpcthreads_per_core.memratio
```

The following is an example of an instance class that is preconfigured for additional memory:

```
db.r5b.4xlarge.tpc2.mem2x
```

The components of the preceding instance class name are as follows:
+ `db.r5b.4xlarge` – The name of the instance class.
+ `tpc2` – The threads per core. A value of 2 means that multithreading is turned on. A value of 1 means that multithreading is turned off. 
+ `mem2x` – The ratio of additional memory to the standard memory for the instance class. In this example, the optimization provides twice as much memory as a standard db.r5.4xlarge DB instance. 

**Note**  
For the normalization factors of the preconfigured RDS for Oracle DB instance classes, see [Hardware specifications for DB instance classes](Concepts.DBInstanceClass.Summary.md).

### Supported edition, instance class, and licensing combinations in RDS for Oracle


If you're using the RDS console, you can find out whether a specific edition, instance class, and license combination is supported by choosing **Create database** and specifying different option. In the Amazon CLI, you can run the following command:

```
aws rds describe-orderable-db-instance-options --engine engine-type --license-model license-type
```

The following table lists all editions, instance classes, and license types supported for RDS for Oracle. For information about the memory attributes of each type, see [ RDS for Oracle instance types](https://www.amazonaws.cn//rds/oracle/instance-types). For information about pricing, see [Amazon RDS for Oracle pricing models](https://www.amazonaws.cn/rds/oracle/pricing/#Pricing_models).


****  
<a name="rds-oracle-instance-class-reference"></a>[\[See the AWS documentation website for more details\]](http://docs.amazonaws.cn/en_us/AmazonRDS/latest/UserGuide/Oracle.Concepts.InstanceClasses.html)

## Deprecated RDS for Oracle DB instance classes
Deprecated Oracle instance classes

The following DB instance classes are deprecated for RDS for Oracle:
+ db.m1, db.m2, db.m3, db.m4
+ db.t1, db.t2
+ db.r1, db.r2, db.r3, db.r4
+ db.x1, db.x1e

The preceding DB instance classes have been replaced by better performing DB instance classes that are generally available at a lower cost. If you have DB instances that use deprecated DB instance classes, you have the following options:
+ Allow Amazon RDS to modify each DB instance automatically to use a comparable non-deprecated DB instance class. For deprecation timelines, see [DB instance class types](Concepts.DBInstanceClass.Types.md).
+ Change the DB instance class yourself by modifying the DB instance. For more information, see [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md). 

**Note**  
If you have DB snapshots of DB instances that were using deprecated DB instance classes, you can choose a DB instance class that is not deprecated when you restore the DB snapshots. For more information, see [Restoring to a DB instance](USER_RestoreFromSnapshot.md).

# RDS for Oracle database architecture
Oracle database architecture

The Oracle multitenant architecture, also known as the CDB architecture, enables an Oracle database to function as a multitenant container database (CDB). A CDB can include customer-created pluggable databases (PDBs). A non-CDB is an Oracle database that uses the traditional architecture, which can't contain PDBs. For more information about the multitenant architecture, see [https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/introduction-to-the-multitenant-architecture.html#GUID-267F7D12-D33F-4AC9-AA45-E9CD671B6F22](https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/introduction-to-the-multitenant-architecture.html#GUID-267F7D12-D33F-4AC9-AA45-E9CD671B6F22).

For Oracle Database 19c and higher, you can create an RDS for Oracle DB instance that uses the CDB architecture. In RDS for Oracle, PDBs are referred to as tenant databases. Your client applications connect at the tenant database (PDB) level rather than the CDB level. RDS for Oracle supports the following configurations of the CDB architecture:

**Multi-tenant configuration**  
Amazon RDS allows a CDB instance to contain between 1–30 tenant databases, depending on the database edition and any required option licenses. You can use RDS APIs to add, modify, and remove tenant databases. The multi-tenant configuration in RDS for Oracle doesn't support application PDBs or proxy PDBs, which are special types of PDBs. For more information about application PDBs and proxy PDBs, see [Types of PDBs](https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/overview-of-the-multitenant-architecture.html#GUID-D0F40745-FC70-4BE0-85D3-3745DE3312AC) in the Oracle Database documentation.  
The Amazon RDS configuration is called "multi-tenant" rather than "multitenant" because it is a capability of Amazon RDS, not just the Oracle DB engine. Similarly, the RDS term "tenant" refers to any tenant in an RDS configuration, not just Oracle PDBs. In the RDS documentation, the unhyphenated term "Oracle multitenant" refers exclusively to the Oracle database CDB architecture, which is compatible with both on-premises and RDS deployments.

**Single-tenant configuration**  
Amazon RDS limits an RDS for Oracle CDB instance to 1 tenant database (PDB). You can't add more PDBs using RDS APIs. The single-tenant configuration uses the same RDS APIs as the non-CDB architecture. Thus, the experience of working with a CDB in the single-tenant configuration is mostly the same as working with a non-CDB.  
You can convert a CDB that uses the single-tenant configuration to the multi-tenant configuration, thus allowing you to add PDBs to your CDB. This architecture change is permanent and irreversible. For more information, see [Converting the single-tenant configuration to multi-tenant](oracle-single-tenant-converting.md).

**Note**  
You can't access the CDB itself.

In Oracle Database 21c and higher, all databases are CDBs. In contrast, you can create an Oracle Database 19c DB instance as either a CDB or non-CDB. You can't upgrade a non-CDB to a CDB, but you convert an Oracle Database 19c non-CDB to a CDB, and then upgrade it. You can't convert a CDB to a non-CDB.

For more information, see the following resources:
+ [Working with CDBs in RDS for Oracle](oracle-multitenant.md)
+ [Limitations of RDS for Oracle CDBs](Oracle.Concepts.CDBs.md#Oracle.Concepts.single-tenant-limitations)
+ [Creating an Amazon RDS DB instance](USER_CreateDBInstance.md)

# RDS for Oracle initialization parameters
Oracle parameters

In Amazon RDS, you manage parameters using a DB parameter group. Using this group, you can customize initialization parameters. For example, you can configure the sort area size with `sort_area_size`. All RDS for Oracle DB instances associated with a specific DB parameter group use the same parameter settings. For more information, see [Parameter groups for Amazon RDS](USER_WorkingWithParamGroups.md). 

## Supported initialization parameters in RDS for Oracle
Supported parameters

Supported parameters for your DB instance depend on your Oracle Database edition and version. To view the supported initialization parameters for a specific Oracle Database edition and version, run the Amazon CLI command [https://docs.amazonaws.cn/cli/latest/reference/rds/describe-engine-default-parameters.html](https://docs.amazonaws.cn/cli/latest/reference/rds/describe-engine-default-parameters.html). For example, to list names of the supported initialization parameters for the Enterprise Edition of Oracle Database 19c, run the following command (sample output included).

```
aws rds describe-engine-default-parameters \
    --db-parameter-group-family oracle-ee-19 \
    --output json | jq -r '.EngineDefaults.Parameters[].ParameterName'

_add_col_optim_enabled
_adg_parselock_timeout
_allow_insert_with_update_check
_allow_level_without_connect_by
_always_semi_join
_autotask_max_window
_awr_disabled_flush_tables
_awr_mmon_cpuusage
_awr_mmon_deep_purge_all_expired
_b_tree_bitmap_plans
_bct_bitmaps_per_file
_bloom_filter_enabled
_buffered_publisher_flow_control_threshold
_bug29394014_allow_triggers_on_vpd_table
_cleanup_rollback_entries
_client_enable_auto_unregister
_clusterwide_global_transactions
_complex_view_merging
_connect_by_use_union_all
_cost_equality_semi_join
_cursor_features_enabled
_cursor_obsolete_threshold
_datafile_write_errors_crash_instance
_db_block_buffers
...
```

To describe a single initialization parameter, use the following command, replacing `sga_max_size` with the name of your parameter (sample output included).

```
aws rds describe-engine-default-parameters \
    --db-parameter-group-family oracle-ee-19 \
    --query 'EngineDefaults.Parameters[?ParameterName==`sga_max_size`]' \
    --output json

[
    {
        "ParameterName": "sga_max_size",
        "Description": "max total SGA size",
        "Source": "engine-default",
        "ApplyType": "static",
        "DataType": "integer",
        "AllowedValues": "0-2199023255552",
        "IsModifiable": true
    }
]
```

To find general documentation for the Oracle database initialization parameters, see [Initialization Parameters](https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/initialization-parameters.html#GUID-6F1C3203-0AA0-4AF1-921C-A027DD7CB6A9) in the Oracle Database documentation. Note that the parameter `ARCHIVE_LAG_TARGET` has special considerations in RDS for Oracle. This parameter forces an online redo log switch after the specified time elapses. In RDS for Oracle, `ARCHIVE_LAG_TARGET` is set to `300` because the recovery point objective (RPO) is 5 minutes. To honor this objective, RDS for Oracle switches the online redo log every 5 minutes and stores it in an Amazon S3 bucket. 

If the frequency of the online redo log switch degrades the performance of your RDS for Oracle database, you can scale your DB instance and storage to use higher IOPS and throughput. Alternatively, if you use RDS Custom for Oracle or deploy an Oracle database on Amazon EC2, you can adjust the setting of the `ARCHIVE_LAG_TARGET` initialization parameter.

## Valid parameter values in RDS for Oracle
Valid parameter values

In RDS for Oracle, only the following characters are valid for parameter values:
+ Letters (`A-Z` and `a-z`)
+ Numbers (`0-9`)
+ Whitespace (spaces, tabs, and line breaks)
+ The following special characters: `_ / . : + = ( ) ' * , % $ -` (hyphen)

# RDS for Oracle character sets
Oracle character sets

RDS for Oracle supports two types of character sets: the DB character set and national character set.

## DB character set


The Oracle database character set is used in the `CHAR`, `VARCHAR2`, and `CLOB` data types. The database also uses this character set for metadata such as table names, column names, and SQL statements. The Oracle database character set is typically referred to as the DB character set. 

You set the character set when you create a DB instance. You can't change the DB character set after you create the database.

### Supported DB character sets


The following table lists the Oracle DB character sets that are supported in Amazon RDS. You can use a value from this table with the `--character-set-name` parameter of the Amazon CLI [create-db-instance](https://docs.amazonaws.cn/cli/latest/reference/rds/create-db-instance.html) command or with the `CharacterSetName` parameter of the Amazon RDS API [CreateDBInstance](https://docs.amazonaws.cn/AmazonRDS/latest/APIReference/API_CreateDBInstance.html) operation.

**Note**  
The character set for a CDB is always AL32UTF8. You can set a different character set for the PDB only.


****  

| Value | Description | 
| --- | --- | 
|  AL32UTF8  |  Unicode 5.0 UTF-8 Universal character set (default)  | 
|  AR8ISO8859P6  |  ISO 8859-6 Latin/Arabic  | 
|  AR8MSWIN1256  |  Microsoft Windows Code Page 1256 8-bit Latin/Arabic  | 
|  BLT8ISO8859P13  |  ISO 8859-13 Baltic  | 
|  BLT8MSWIN1257  |  Microsoft Windows Code Page 1257 8-bit Baltic  | 
|  CL8ISO8859P5  |  ISO 88559-5 Latin/Cyrillic  | 
|  CL8MSWIN1251  |  Microsoft Windows Code Page 1251 8-bit Latin/Cyrillic  | 
|  EE8ISO8859P2  |  ISO 8859-2 East European  | 
|  EL8ISO8859P7  |  ISO 8859-7 Latin/Greek  | 
|  EE8MSWIN1250  |  Microsoft Windows Code Page 1250 8-bit East European  | 
|  EL8MSWIN1253  |  Microsoft Windows Code Page 1253 8-bit Latin/Greek  | 
|  IW8ISO8859P8  |  ISO 8859-8 Latin/Hebrew  | 
|  IW8MSWIN1255  |  Microsoft Windows Code Page 1255 8-bit Latin/Hebrew  | 
|  JA16EUC  |  EUC 24-bit Japanese  | 
|  JA16EUCTILDE  |  Same as JA16EUC except for mapping of wave dash and tilde to and from Unicode  | 
|  JA16SJIS  |  Shift-JIS 16-bit Japanese  | 
|  JA16SJISTILDE  |  Same as JA16SJIS except for mapping of wave dash and tilde to and from Unicode  | 
|  KO16MSWIN949  |  Microsoft Windows Code Page 949 Korean  | 
|  NE8ISO8859P10  |  ISO 8859-10 North European  | 
|  NEE8ISO8859P4  |  ISO 8859-4 North and Northeast European  | 
|  TH8TISASCII  |  Thai Industrial Standard 620-2533-ASCII 8-bit  | 
|  TR8MSWIN1254  |  Microsoft Windows Code Page 1254 8-bit Turkish  | 
|  US7ASCII  |  ASCII 7-bit American  | 
|  UTF8  |  Unicode 3.0 UTF-8 Universal character set, CESU-8 compliant  | 
|  VN8MSWIN1258  |  Microsoft Windows Code Page 1258 8-bit Vietnamese  | 
|  WE8ISO8859P1  |  Western European 8-bit ISO 8859 Part 1  | 
|  WE8ISO8859P15  |  ISO 8859-15 West European  | 
|  WE8ISO8859P9  |  ISO 8859-9 West European and Turkish  | 
|  WE8MSWIN1252  |  Microsoft Windows Code Page 1252 8-bit West European  | 
|  ZHS16GBK  |  GBK 16-bit Simplified Chinese  | 
|  ZHT16HKSCS  |  Microsoft Windows Code Page 950 with Hong Kong Supplementary Character Set HKSCS-2001. Character set conversion is based on Unicode 3.0.  | 
|  ZHT16MSWIN950  |  Microsoft Windows Code Page 950 Traditional Chinese  | 
|  ZHT32EUC  |  EUC 32-bit Traditional Chinese  | 

### NLS\$1LANG environment variable


A locale is a set of information addressing linguistic and cultural requirements that corresponds to a given language and country. Setting the NLS\$1LANG environment variable in your client's environment is the simplest way to specify locale behavior for Oracle. This variable sets the language and territory used by the client application and the database server. It also indicates the client's character set, which corresponds to the character set for data entered or displayed by a client application. For more information on NLS\$1LANG and character sets, see [What is a character set or code page?](http://www.oracle.com/technetwork/database/database-technologies/globalization/nls-lang-099431.html#_Toc110410570) in the Oracle documentation.

### NLS initialization parameters


You can also set the following National Language Support (NLS) initialization parameters at the instance level for an Oracle DB instance in Amazon RDS:
+ NLS\$1COMP
+ NLS\$1DATE\$1FORMAT
+ NLS\$1LENGTH\$1SEMANTICS
+ NLS\$1NCHAR\$1CONV\$1EXCP
+ NLS\$1SORT
+ NLS\$1TIME\$1FORMAT
+ NLS\$1TIME\$1TZ\$1FORMAT
+ NLS\$1TIMESTAMP\$1FORMAT
+ NLS\$1TIMESTAMP\$1TZ\$1FORMAT

For information about modifying instance parameters, see [Parameter groups for Amazon RDS](USER_WorkingWithParamGroups.md).

You can set other NLS initialization parameters in your SQL client. For example, the following statement sets the NLS\$1LANGUAGE initialization parameter to GERMAN in a SQL client that is connected to an Oracle DB instance:

```
ALTER SESSION SET NLS_LANGUAGE=GERMAN;
```

For information about connecting to an Oracle DB instance with a SQL client, see [Connecting to your Oracle DB instance](USER_ConnectToOracleInstance.md).

## National character set


The national character set is used in the `NCHAR`, `NVARCHAR2`, and `NCLOB` data types. The national character set is typically referred to as the NCHAR character set. Unlike the DB character set, the NCHAR character set doesn't affect database metadata.

The NCHAR character set supports the following character sets:
+ AL16UTF16 (default)
+ UTF8

You can specify either value with the `--nchar-character-set-name` parameter of the [create-db-instance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/create-db-instance.html) command (Amazon CLI version 2 only). If you use the Amazon RDS API, specify the `NcharCharacterSetName` parameter of [CreateDBInstance](https://docs.amazonaws.cn/AmazonRDS/latest/APIReference/API_CreateDBInstance.html) operation. You can't change the national character set after you create the database.

For more information about Unicode in Oracle databases, see [Supporting multilingual databases with unicode](https://docs.oracle.com/en/database/oracle/oracle-database/19/nlspg/supporting-multilingual-databases-with-unicode.html) in the Oracle documentation.

# RDS for Oracle limitations
Oracle limitations

In the following sections, you can find important limitations of using RDS for Oracle. For limitations specific to CDBs, see [Limitations of RDS for Oracle CDBs](Oracle.Concepts.CDBs.md#Oracle.Concepts.single-tenant-limitations).

**Note**  
This list is not exhaustive.

**Topics**
+ [

## Oracle file size limits in Amazon RDS
](#Oracle.Concepts.file-size-limits)
+ [

## Block size limits in RDS for Oracle
](#Oracle.Concepts.block-size-limits)
+ [

## Public synonyms for Oracle-supplied schemas
](#Oracle.Concepts.PublicSynonyms)
+ [

## Schemas for unsupported features in RDS for Oracle
](#Oracle.Concepts.unsupported-features)
+ [

## Limitations for DBA privileges in RDS for Oracle
](#Oracle.Concepts.dba-limitations)
+ [

## Deprecation of TLS 1.0 and 1.1 Transport Layer Security in RDS for Oracle
](#Oracle.Concepts.tls)

## Oracle file size limits in Amazon RDS
File size limits

The maximum size of a single file on RDS for Oracle DB instances is 16 TiB (tebibytes). This limit is imposed by the ext4 filesystem used by the instance. Thus, Oracle bigfile data files are limited to 16 TiB. If you try to resize a data file in a bigfile tablespace to a value over the limit, you receive an error such as the following.

```
ORA-01237: cannot extend datafile 6
ORA-01110: data file 6: '/rdsdbdata/db/mydir/datafile/myfile.dbf'
ORA-27059: could not reduce file size
Linux-x86_64 Error: 27: File too large
Additional information: 2
```

## Block size limits in RDS for Oracle
File size limits

RDS for Oracle DB instances are created with a default database block size (`DB_BLOCK_SIZE`) of 8 KB. The default database block size is set at database creation and cannot be changed. The `SYSTEM` and temporary tablespaces always use the default database block size. You can create additional tablespaces with non-default block sizes by configuring the corresponding `DB_nK_CACHE_SIZE` parameter (for example, `DB_16K_CACHE_SIZE`) to allocate a buffer cache for that block size, and then specifying the `BLOCKSIZE` clause in your `CREATE TABLESPACE` statement.

## Public synonyms for Oracle-supplied schemas
Public synonyms

Don't create or modify public synonyms for Oracle-supplied schemas, including `SYS`, `SYSTEM`, and `RDSADMIN`. Such actions might result in invalidation of core database components and affect the availability of your DB instance.

You can create public synonyms referencing objects in your own schemas.

## Schemas for unsupported features in RDS for Oracle


In general, Amazon RDS doesn't prevent you from creating schemas for unsupported features. However, if you create schemas for Oracle features and components that require SYS privileges, you can damage the data dictionary and affect your instance availability. Use only supported features and schemas that are available in [Adding options to Oracle DB instances](Appendix.Oracle.Options.md).

## Limitations for DBA privileges in RDS for Oracle


In the database, a role is a collection of privileges that you can grant to or revoke from a user. An Oracle database uses roles to provide security.

The predefined role `DBA` normally allows all administrative privileges on an Oracle database. When you create a DB instance, your master user account gets DBA privileges (with some limitations). To deliver a managed experience, an RDS for Oracle database doesn't provide the following privileges for the `DBA` role: 
+ `ALTER DATABASE`
+ `ALTER SYSTEM`
+ `CREATE ANY DIRECTORY`
+ `DROP ANY DIRECTORY`
+ `GRANT ANY PRIVILEGE`
+ `GRANT ANY ROLE`

Use the master user account for administrative tasks such as creating additional user accounts in the database. You can't use `SYS`, `SYSTEM`, and other Oracle-supplied administrative accounts. 

## Deprecation of TLS 1.0 and 1.1 Transport Layer Security in RDS for Oracle
Deprecation of TLS 1.0 and 1.1

Transport Layer Security protocol versions 1.0 and 1.1 (TLS 1.0 and TLS 1.1) are deprecated. In accordance with security best practices, Oracle has deprecated the use of TLS 1.0 and TLS 1.1. To meet your security requirements, we strongly recommends that you use TLS 1.2 instead.