Common management tasks Licensing Migrating between Oracle editions DB instance class support File size limits Security SSL support Oracle 19c Oracle 18c Oracle 12c Oracle Database feature support Oracle Database parameter support Engine version management Using HugePages Using utl_http, utl_tcp, and utl_smtp Using OEM, APEX, TDE, and other options Using extended data types Public synonyms

Oracle on Amazon RDS

Amazon RDS supports DB instances that run the following versions and editions of Oracle Database:

Oracle 19c, Version 19.0.0.0
Oracle 18c, Version 18.0.0.0
Oracle 12c, Version 12.2.0.1
Oracle 12c, Version 12.1.0.2

Note

Amazon RDS also currently supports Oracle 11g, Version 11.2.0.4. This version is on a deprecation path because Oracle will no longer provide patches for 11.2.0.4 after the end-of-support date. For more information, see Deprecation of Oracle 11.2.0.4.

You can create DB instances and DB snapshots, point-in-time restores, and automated or manual backups. You can use DB instances running Oracle inside a VPC. You can also add features to your Oracle DB instance by enabling various options. Amazon RDS supports Multi-AZ deployments for Oracle as a high-availability, failover solution.

To deliver a managed service experience, Amazon RDS doesn't provide shell access to DB instances. It also restricts access to certain system procedures and tables that require advanced privileges. You can access databases on a DB instance using any standard SQL client application such as Oracle SQL*Plus. However, you can't access the host directly by using Telnet or Secure Shell (SSH).

When you create a DB instance using your master account, the account gets DBA privileges, with some limitations. Use this account for administrative tasks such as creating additional database accounts. You can't use SYS, SYSTEM, or other Oracle-supplied administrative accounts.

Before creating a DB instance, complete the steps in the Setting up for Amazon RDS section of this guide.

Common management tasks for Oracle on Amazon RDS

Following are the common management tasks you perform with an Amazon RDS Oracle DB instance, with links to relevant documentation for each task.

Task area	Relevant documentation
Instance Classes, Storage, and PIOPS If you are creating a production instance, learn how instance classes, storage types, and Provisioned IOPS work in Amazon RDS.	DB instance class support for Oracle Amazon RDS storage types
Multi-AZ Deployments A production DB instance should use Multi-AZ deployments. Multi-AZ deployments provide increased availability, data durability, and fault tolerance for DB instances.	High availability (Multi-AZ) for Amazon RDS
Amazon Virtual Private Cloud (VPC) If your AWS account has a default VPC, then your DB instance is automatically created inside the default VPC. If your account doesn't have a default VPC, and you want the DB instance in a VPC, create the VPC and subnet groups before you create the instance.	Determining whether you are using the EC2-VPC or EC2-Classic platform Working with a DB instance in a VPC
Security Groups By default, DB instances use a firewall that prevents access. Make sure you create a security group with the correct IP addresses and network configuration to access the DB instance. The security group you create depends on which Amazon EC2 platform your DB instance is on, and whether you will access your DB instance from an Amazon EC2 instance. In general, if your DB instance is on the EC2-Classic platform, you should create a DB security group. Also, if your instance is on the EC2-VPC platform, you should create a VPC security group.	Determining whether you are using the EC2-VPC or EC2-Classic platform Controlling access with security groups
Parameter Groups If your DB instance is going to require specific database parameters, you should create a parameter group before you create the DB instance.	Working with DB parameter groups
Option Groups If your DB instance will require specific database options, you should create an option group before you create the DB instance.	Options for Oracle DB instances
Connecting to Your DB Instance After creating a security group and associating it to a DB instance, you can connect to the DB instance using any standard SQL client application such as Oracle SQL*Plus.	Connecting to an Oracle DB instance
Backup and Restore You can configure your DB instance to take automated backups, or take manual snapshots, and then restore instances from the backups or snapshots.	Backing up and restoring an Amazon RDS DB instance
Monitoring You can monitor an Oracle DB instance by using CloudWatch Amazon RDS metrics, events, and enhanced monitoring.	Viewing DB instance metrics Viewing Amazon RDS events
Log Files You can access the log files for your Oracle DB instance.	Amazon RDS database log files

Task area

Relevant documentation

Instance Classes, Storage, and PIOPS

If you are creating a production instance, learn how instance classes, storage types, and Provisioned IOPS work in Amazon RDS.

DB instance class support for Oracle

Amazon RDS storage types

Multi-AZ Deployments

A production DB instance should use Multi-AZ deployments. Multi-AZ deployments provide increased availability, data durability, and fault tolerance for DB instances.

High availability (Multi-AZ) for Amazon RDS

Amazon Virtual Private Cloud (VPC)

If your AWS account has a default VPC, then your DB instance is automatically created inside the default VPC. If your account doesn't have a default VPC, and you want the DB instance in a VPC, create the VPC and subnet groups before you create the instance.

Determining whether you are using the EC2-VPC or EC2-Classic platform

Working with a DB instance in a VPC

Security Groups

By default, DB instances use a firewall that prevents access. Make sure you create a security group with the correct IP addresses and network configuration to access the DB instance. The security group you create depends on which Amazon EC2 platform your DB instance is on, and whether you will access your DB instance from an Amazon EC2 instance.

In general, if your DB instance is on the EC2-Classic platform, you should create a DB security group. Also, if your instance is on the EC2-VPC platform, you should create a VPC security group.

Determining whether you are using the EC2-VPC or EC2-Classic platform

Controlling access with security groups

Parameter Groups

If your DB instance is going to require specific database parameters, you should create a parameter group before you create the DB instance.

Working with DB parameter groups

Option Groups

If your DB instance will require specific database options, you should create an option group before you create the DB instance.

Options for Oracle DB instances

Connecting to Your DB Instance

After creating a security group and associating it to a DB instance, you can connect to the DB instance using any standard SQL client application such as Oracle SQL*Plus.

Connecting to an Oracle DB instance

Backup and Restore

You can configure your DB instance to take automated backups, or take manual snapshots, and then restore instances from the backups or snapshots.

Backing up and restoring an Amazon RDS DB instance

Monitoring

You can monitor an Oracle DB instance by using CloudWatch Amazon RDS metrics, events, and enhanced monitoring.

Viewing DB instance metrics

Viewing Amazon RDS events

Log Files

You can access the log files for your Oracle DB instance.

Amazon RDS database log files

There are also advanced tasks and optional features for working with Oracle DB instances. For more information, see the following documentation.

For information on common DBA tasks for Oracle on Amazon RDS, see Common DBA tasks for Oracle DB instances.
For information on Oracle GoldenGate support, see Using Oracle GoldenGate with Amazon RDS.
For information on Siebel Customer Relationship Management (CRM) support, see Installing a Siebel database on Oracle on Amazon RDS.

Oracle licensing options

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.

License Included

In the License Included model, you don't need to purchase Oracle licenses separately. AWS holds the license for the Oracle database software. In this model, if you have an AWS Support account with case support, contact AWS Support for both Amazon RDS and Oracle Database service requests.

The License Included model is supported on Amazon RDS for the following Oracle database editions:

Oracle Database Standard Edition One (SE1)
Oracle Database Standard Edition Two (SE2)

Note

The Oracle Database SE1 License Included model isn't supported in the following opt-in AWS Regions:

Africa (Cape Town)
Asia Pacific (Hong Kong)
Europe (Milan)
Middle East (Bahrain)

Bring Your Own License (BYOL)

In the BYOL model, you can use your existing Oracle Database licenses to run Oracle deployments on Amazon RDS. You must 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.

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 AWS Support account with case support, you can contact AWS Support for Amazon RDS issues. Amazon Web Services and Oracle have a multi-vendor support process for cases that require assistance from both organizations.

The Bring Your Own License model is supported on Amazon RDS for the following Oracle database editions:

Oracle Database Enterprise Edition (EE)
Oracle Database Standard Edition (SE)
Oracle Database Standard Edition One (SE1)
Oracle Database Standard Edition Two (SE2)

Integrating with AWS License Manager

To make it easier to monitor Oracle license usage in the BYOL model, AWS 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 AWS Organizations to manage all of your organizational accounts centrally.

Note

RDS for Oracle integration with License Manager isn't supported in the Asia Pacific (Osaka-Local) Region.

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

Filter	Name	Description
Engine Edition	`oracle-ee`	Oracle Database Enterprise Edition (EE)
	`oracle-se`	Oracle Database Standard Edition (SE)
	`oracle-se1`	Oracle Database Standard Edition One (SE1)
	`oracle-se2`	Oracle Database Standard Edition Two (SE2)
License Pack	`data guard`	See Working with Oracle replicas for Amazon RDS (Oracle Active Data Guard)
	`olap`	See Oracle OLAP
	`ols`	See Oracle Label Security
	`diagnostic pack sqlt`	See Oracle SQLT
	`tuning pack sqlt`	See Oracle SQLT

To track license usage of your Oracle DB instances, you can create a license configuration. In this case, RDS for Oracle resources that match the product information filter are automatically associated with the license configuration. Discovery of Oracle DB instances can take up to 24 hours.

To create a license configuration to track the license usage of your Oracle DB instances

Go to https://console.aws.amazon.com/license-manager/.
Create a license configuration.

For instructions, see Create a license configuration in the AWS License Manager User Guide.

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

For more information, see ProductInformation in the AWS License Manager API Reference.

To create a license configuration by using the AWS CLI, call the create-license-configuration command. Use the --cli-input-json or --cli-input-yaml parameters to pass the parameters to the command.

Example

The following code creates a license configuration 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 in the AWS License Manager User Guide.

For more information about the --cli-input parameter, see Generating AWS CLI skeleton and input parameters from a JSON or YAML input file in the AWS CLI User Guide.

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 High availability (Multi-AZ) for Amazon RDS.

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.

Migrating between Oracle editions

For the BYOL model, you can migrate from any Standard Edition (SE, SE1, or SE2) to Enterprise Edition (EE), assuming you have an unused Oracle license appropriate for the edition and class of DB instance that you plan to run. You can't migrate from Enterprise Edition to other editions.

To change the edition and retain your data

Create a snapshot of the DB instance.

For more information, see Creating a DB snapshot.
Restore the snapshot to a new DB instance, and select the Oracle database edition you want to use.

For more information, see Restoring from a DB snapshot.
(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.

DB instance class support for Oracle

The computation and memory capacity of a DB instance is determined by its DB instance class. The DB instance class you need depends on your processing power and memory requirements. For more information, see DB instance classes.

The following are the DB instance classes supported for Oracle.

Oracle edition	19c, 18c, and 12c version 12.2.0.1 support	12c version 12.1.0.2 support	11g version 11.2.0.4 support
Enterprise Edition (EE) Bring Your Own License (BYOL)	db.m5.large–db.m5.24xlarge db.m4.large–db.m4.16xlarge db.z1d.large–db.z1d.12xlarge db.x1e.xlarge–db.x1e.32xlarge db.x1.16xlarge–db.x1.32xlarge db.r5.large–db.r5.24xlarge db.r4.large–db.r4.16xlarge db.t3.small–db.t3.2xlarge	db.m5.large–db.m5.24xlarge db.m4.large–db.m4.16xlarge db.z1d.large–db.z1d.12xlarge db.x1e.xlarge–db.x1e.32xlarge db.x1.16xlarge–db.x1.32xlarge db.r5.large–db.r5.24xlarge db.r4.large–db.r4.16xlarge db.t3.micro–db.t3.2xlarge	db.m5.large–db.m5.24xlarge db.m4.large–db.m4.16xlarge db.z1d.large–db.z1d.12xlarge db.x1e.xlarge–db.x1e.32xlarge db.x1.16xlarge–db.x1.32xlarge db.r5.large–db.r5.24xlarge db.r4.large–db.r4.16xlarge db.t3.micro–db.t3.2xlarge
Standard Edition 2 (SE2) Bring Your Own License (BYOL)	db.m5.large–db.m5.4xlarge db.m4.large–db.m4.4xlarge db.z1d.large–db.z1d.3xlarge db.x1e.xlarge–db.x1e.4xlarge db.r5.large–db.r5.4xlarge db.r4.large–db.r4.4xlarge db.t3.small–db.t3.2xlarge	db.m5.large–db.m5.4xlarge db.m4.large–db.m4.4xlarge db.z1d.large–db.z1d.3xlarge db.x1e.xlarge–db.x1e.4xlarge db.r5.large–db.r5.4xlarge db.r4.large–db.r4.4xlarge db.t3.micro–db.t3.2xlarge	—
Standard Edition 2 (SE2) License Included	db.m5.large–db.m5.4xlarge db.m4.large–db.m4.4xlarge db.r5.large–db.r5.4xlarge db.r4.large–db.r4.4xlarge db.t3.small–db.t3.2xlarge	db.m5.large–db.m5.4xlarge db.m4.large–db.m4.4xlarge db.r5.large–db.r5.4xlarge db.r4.large–db.r4.4xlarge db.t3.micro–db.t3.2xlarge	—
Standard Edition 1 (SE1) Bring Your Own License (BYOL)	—	—	db.m5.large–db.m5.4xlarge db.m4.large–db.m4.4xlarge db.z1d.large–db.z1d.3xlarge db.x1e.xlarge–db.x1e.4xlarge db.r5.large–db.r5.4xlarge db.r4.large–db.r4.4xlarge db.t3.micro–db.t3.2xlarge
Standard Edition 1 (SE1) License Included	—	—	db.m5.large–db.m5.4xlarge db.m4.large–db.m4.4xlarge db.r5.large–db.r5.4xlarge db.t3.micro–db.t3.2xlarge
Standard Edition (SE) Bring Your Own License (BYOL)	—	—	db.m5.large–db.m5.8xlarge db.m4.large–db.m4.4xlarge db.z1d.large–db.z1d.6xlarge db.x1e.xlarge–db.x1e.8xlarge db.r5.large–db.r5.8xlarge db.r4.large–db.r4.8xlarge db.t3.micro–db.t3.2xlarge

Oracle edition

19c, 18c, and 12c version 12.2.0.1 support

12c version 12.1.0.2 support

11g version 11.2.0.4 support

Enterprise Edition (EE)

Bring Your Own License (BYOL)

db.m5.large–db.m5.24xlarge

db.m4.large–db.m4.16xlarge

db.z1d.large–db.z1d.12xlarge

db.x1e.xlarge–db.x1e.32xlarge

db.x1.16xlarge–db.x1.32xlarge

db.r5.large–db.r5.24xlarge

db.r4.large–db.r4.16xlarge

db.t3.small–db.t3.2xlarge

db.m5.large–db.m5.24xlarge

db.m4.large–db.m4.16xlarge

db.z1d.large–db.z1d.12xlarge

db.x1e.xlarge–db.x1e.32xlarge

db.x1.16xlarge–db.x1.32xlarge

db.r5.large–db.r5.24xlarge

db.r4.large–db.r4.16xlarge

db.t3.micro–db.t3.2xlarge

db.m5.large–db.m5.24xlarge

db.m4.large–db.m4.16xlarge

db.z1d.large–db.z1d.12xlarge

db.x1e.xlarge–db.x1e.32xlarge

db.x1.16xlarge–db.x1.32xlarge

db.r5.large–db.r5.24xlarge

db.r4.large–db.r4.16xlarge

db.t3.micro–db.t3.2xlarge

Standard Edition 2 (SE2)

Bring Your Own License (BYOL)

db.m5.large–db.m5.4xlarge

db.m4.large–db.m4.4xlarge

db.z1d.large–db.z1d.3xlarge

db.x1e.xlarge–db.x1e.4xlarge

db.r5.large–db.r5.4xlarge

db.r4.large–db.r4.4xlarge

db.t3.small–db.t3.2xlarge

db.m5.large–db.m5.4xlarge

db.m4.large–db.m4.4xlarge

db.z1d.large–db.z1d.3xlarge

db.x1e.xlarge–db.x1e.4xlarge

db.r5.large–db.r5.4xlarge

db.r4.large–db.r4.4xlarge

db.t3.micro–db.t3.2xlarge

—

Standard Edition 2 (SE2)

License Included

db.m5.large–db.m5.4xlarge

db.m4.large–db.m4.4xlarge

db.r5.large–db.r5.4xlarge

db.r4.large–db.r4.4xlarge

db.t3.small–db.t3.2xlarge

db.m5.large–db.m5.4xlarge

db.m4.large–db.m4.4xlarge

db.r5.large–db.r5.4xlarge

db.r4.large–db.r4.4xlarge

db.t3.micro–db.t3.2xlarge

—

Standard Edition 1 (SE1)

Bring Your Own License (BYOL)

—

db.m5.large–db.m5.4xlarge

db.m4.large–db.m4.4xlarge

db.z1d.large–db.z1d.3xlarge

db.x1e.xlarge–db.x1e.4xlarge

db.r5.large–db.r5.4xlarge

db.r4.large–db.r4.4xlarge

db.t3.micro–db.t3.2xlarge

Standard Edition 1 (SE1)

License Included

—

db.m5.large–db.m5.4xlarge

db.m4.large–db.m4.4xlarge

db.r5.large–db.r5.4xlarge

db.t3.micro–db.t3.2xlarge

Standard Edition (SE)

Bring Your Own License (BYOL)

—

db.m5.large–db.m5.8xlarge

db.m4.large–db.m4.4xlarge

db.z1d.large–db.z1d.6xlarge

db.x1e.xlarge–db.x1e.8xlarge

db.r5.large–db.r5.8xlarge

db.r4.large–db.r4.8xlarge

db.t3.micro–db.t3.2xlarge

Note

We encourage all bring-your-own-license customers to consult their licensing agreement to assess the impact of Amazon RDS for Oracle deprecations. For more information on the compute capacity of DB instance classes supported by Amazon RDS for Oracle, see DB instance classes and Configuring the processor for a DB instance class.

Deprecated db.t2 DB instance classes for Oracle

The db.t2 DB instance classes are deprecated for Amazon RDS for Oracle. The db.t2 DB instance classes have been replaced by the better performing db.t3 DB instance classes that are generally available at a lower cost. Starting on January 15, 2020, Amazon RDS for Oracle will automatically scale db.t2 DB instances to comparable db.t3 DB instance classes.

If you have DB instances that use db.t2 DB instance classes, Amazon RDS will modify each one automatically to use a comparable DB instance class that is not deprecated. You can change the DB instance class for a DB instance yourself by modifying the DB instance. For more information, see Modifying an Amazon RDS DB instance.

If you have DB snapshots of DB instances that were using db.t2 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 from a DB snapshot.

Note

The db.t3 DB instance classes have hyper-threading enabled by default. When DB instances running the db.t2 DB instance class are migrated, the number of vCPUs is set automatically to the default number of the comparable db.t3 DB instance class. To learn more about the vCPU management features available on Amazon RDS for Oracle, and the default settings for each db.t3 DB instance class, see Configuring the processor for a DB instance class.

Deprecated db.m3 and db.r3 DB instance classes for Oracle

The db.m3 and db.r3 DB instance classes are deprecated for Amazon RDS for Oracle. These DB instance classes have been replaced by better performing DB instance classes that are generally available at a lower cost. Starting on September 30, 2019, Amazon RDS for Oracle will automatically scale DB instances to DB instance classes that are not deprecated.

If you have DB instances that use db.m3 and db.r3 DB instance classes, Amazon RDS will modify each one automatically to use a comparable DB instance class that is not deprecated. You can change the DB instance class for a DB instance yourself by modifying the DB instance. For more information, see Modifying an Amazon RDS DB instance.

If you have DB snapshots of DB instances that were using db.m3 or db.r3 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 from a DB snapshot.

Deprecated db.m1 and db.m2 DB instance classes for Oracle

The db.m1 and db.m2 DB instance classes are deprecated for Amazon RDS for Oracle. These DB instance classes have been replaced by better performing DB instance classes that are generally available at a lower cost. Starting on September 12, 2018, Amazon RDS for Oracle will automatically scale DB instances to DB instance classes that are not deprecated.

If you have DB instances that use db.m1 and db.m2 DB instance classes, Amazon RDS will modify each one automatically to use a comparable DB instance class that is not deprecated. You can change the DB instance class for a DB instance yourself by modifying the DB instance. For more information, see Modifying an Amazon RDS DB instance.

If you have DB snapshots of DB instances that were using db.m1 or db.m2 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 from a DB snapshot.

Oracle file size limits in Amazon RDS

The maximum file size on Amazon RDS Oracle DB instances is 16 TiB (tebibytes). 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

Oracle security

The Oracle database engine uses role-based security. A role is a collection of privileges that can be granted to or revoked from a user. A predefined role, named DBA, normally allows all administrative privileges on an Oracle database. The following privileges are not available for the DBA role on an Amazon RDS DB instance using the Oracle engine:

ALTER DATABASE
ALTER SYSTEM
CREATE ANY DIRECTORY
DROP ANY DIRECTORY
GRANT ANY PRIVILEGE
GRANT ANY ROLE

When you create a DB instance, the master user account that you use to create the instance gets DBA privileges (with some limitations). Use the master user account for any administrative tasks such as creating additional user accounts in the database. You can't use the SYS user, SYSTEM user, and other Oracle-supplied administrative accounts.

Amazon RDS Oracle supports SSL/TLS encrypted connections and also the Oracle Native Network Encryption (NNE) option to encrypt connections between your application and your Oracle DB instance. For more information about using SSL with Oracle on Amazon RDS, see Using SSL with an Oracle DB instance. For more information about the Oracle Native Network Encryption option, see Oracle native network encryption.

Using SSL with an Oracle DB instance

Secure Sockets Layer (SSL) is an industry-standard protocol for securing network connections between client and server. After SSL version 3.0, the name was changed to Transport Layer Security (TLS), but it is still often referred to as SSL and we refer to the protocol as SSL. Amazon RDS supports SSL encryption for Oracle DB instances. Using SSL, you can encrypt a connection between your application client and your Oracle DB instance. SSL support is available in all AWS regions for Oracle.

You enable SSL encryption for an Oracle DB instance by adding the Oracle SSL option to the option group associated with the DB instance. Amazon RDS uses a second port, as required by Oracle, for SSL connections. Doing this allows both clear text and SSL-encrypted communication to occur at the same time between a DB instance and an Oracle client. For example, you can use the port with clear text communication to communicate with other resources inside a VPC while using the port with SSL-encrypted communication to communicate with resources outside the VPC.

For more information, see Oracle Secure Sockets Layer.

Note

You can't use both SSL and Oracle native network encryption (NNE) on the same DB instance. Before you can use SSL encryption, you must disable any other connection encryption.

Oracle 19c with Amazon RDS

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

Oracle 19c version 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 19c version 19.0.0.0 on Amazon RDS. For a complete list of the changes, see the Oracle database 19c documentation. For a complete list of features supported by each Oracle 19c edition, see Permitted features, options, and management packs by Oracle database offering in the Oracle documentation.

Amazon RDS parameter changes for Oracle 19c version 19.0.0.0

Oracle 19c version 19.0.0.0 includes several new parameters and parameters with new ranges and new default values.

The following table shows the new Amazon RDS parameters for Oracle 19c version 19.0.0.0.

Name	Values	Modifiable	Description
lob_signature_enable	TRUE, FALSE (default)	Y	Enables or disables the LOB locator signature feature.
max_datapump_parallel_per_job	1 to 1024, or AUTO	Y	Specifies the maximum number of parallel processes allowed for each Oracle Data Pump job.

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

Parameter name	Oracle 19c version 19.0.0.0 maximum value	Oracle 18c version 18.0.0.0 maximum value
compatible	19.0.0	18.0.0

The following parameters were removed in Oracle 19c Version 19.0.0.0:

exafusion_enabled
max_connections
o7_dictionary_access

Oracle 18c with Amazon RDS

Amazon RDS supports Oracle version 18c, which includes Oracle Enterprise Edition and Oracle Standard Edition Two.

Oracle 18c version 18.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 18c version 18.0.0.0 on Amazon RDS. For a complete list of the changes, see the Oracle database 18c. For a complete list of features supported by each Oracle 18c edition, see Permitted features, options, and management packs by Oracle database offering in the Oracle documentation.

Amazon RDS parameter changes for Oracle 18c version 18.0.0.0

Oracle 18c version 18.0.0.0 includes several new parameters and parameters with new ranges and new default values.

The following table shows the new Amazon RDS parameters for Oracle 18c version 18.0.0.0.

Name	Values	Modifiable	Description
adg_account_info_tracking	LOCAL (default), GLOBAL	N	Controls login attempts of users on Active Data Guard Standby databases. It extends the control of user account security information.
inmemory_optimized_arithmetic	ENABLE, DISABLE (default)	Y	Encodes the `NUMBER` data type in in-memory tables compressed with `QUERY LOW` as a fixed-width native integer scaled by a common exponent.
optimizer_ignore_hints	TRUE, FALSE (default)	Y	Specifies whether embedded hints are ignored.
optimizer_ignore_parallel_hints	TRUE, FALSE (default)	Y	Specifies that embedded parallel hints are ignored.
parallel_min_degree	1 (default) and higher or CPU	Y	Controls the minimum degree of parallelism computed by automatic degree of parallelism.

The compatible parameter has a new default value for Oracle 18c version 18.0.0.0 on Amazon RDS. The following table shows the new default value.

Parameter name	Oracle 18c version 18.0.0.0 default value	Oracle 12c version 12.2.0.1 default value
compatible	18.0.0	12.2.0

The following parameters were removed in Oracle 18c Version 18.0.0.0:

standby_archive_dest
utl_file_dir

Oracle 12c with Amazon RDS

Amazon RDS supports Oracle version 12c, which includes Oracle Enterprise Edition and Oracle Standard Edition Two. Oracle version 12c includes two major versions:

Oracle 12c version 12.2.0.1 with Amazon RDS

Oracle 12c version 12.2.0.1 includes many new features and updates from the previous version. In this section, you can find the features and changes important to using Oracle 12c version 12.2.0.1 on Amazon RDS. For a complete list of the changes, see the Oracle 12c version 12.2 documentation. For a complete list of features supported by each Oracle 12c edition, see Permitted features, options, and management packs by Oracle database offering in the Oracle documentation.

Amazon RDS parameter changes for Oracle 12c version 12.2.0.1

Oracle 12c version 12.2.0.1 includes 20 new parameters in addition to several parameters with new ranges and new default values.

The following table shows the new Amazon RDS parameters for Oracle 12c version 12.2.0.1.

Name	Values	Modifiable	Description
allow_global_dblinks	TRUE, FALSE (default)	Y	Specifies whether LDAP lookup for database links is allowed for the database.
approx_for_aggregation	TRUE, FALSE (default)	Y	Replaces exact query processing for aggregation queries with approximate query processing.
approx_for_count_distinct	TRUE, FALSE (default)	Y	Automatically replaces `COUNT (DISTINCT expr)` queries with `APPROX_COUNT_DISTINCT` queries.
approx_for_percentile	NONE (default), PERCENTILE_CONT, PERCENTILE_CONT DETERMINISTIC, PERCENTILE_DISC, PERCENTILE_DISC DETERMINISTIC, ALL, ALL DETERMINISTIC	Y	Converts exact percentile functions to their approximate percentile function counterparts.
cursor_invalidation	DEFERRED, IMMEDIATE (default)	Y	Controls whether deferred cursor invalidation or immediate cursor invalidation is used for DDL statements by default.
data_guard_sync_latency	0 (default) to the number of seconds specified by the NET_TIMEOUT attribute for the LOG_ARCHIVE_DEST_n parameter	Y	Controls how many seconds the Log Writer (LGWR) process waits beyond the response of the first in a series of Oracle Data Guard SYNC redo transport mode connections.
data_transfer_cache_size	0 – 512M, rounded up to the next granule size	Y	Sets the size of the data transfer cache (in bytes) used to receive data blocks (typically from a primary database in an Oracle Data Guard environment) for consumption by an instance when an RMAN RECOVER ... NONLOGGED BLOCK command is running.
inmemory_adg_enabled	TRUE (default), FALSE	Y	Indicates whether in-memory for Active Data Guard is enabled in addition to the in-memory cache size.
inmemory_expressions_usage	STATIC_ONLY, DYNAMIC_ONLY,ENABLE (default), DISABLE	Y	Controls which In-Memory Expressions (IM expressions) are populated into the In-Memory Column Store (IM column store) and are available for queries.
inmemory_virtual_columns	ENABLE, MANUAL (default), DISABLE	Y	Controls which In-Memory Expressions (IM expressions) are populated into the In-Memory Column Store (IM column store) and are available for queries.
instance_abort_delay_time	0 (default) and higher	Y	Specifies how much time to delay an internally initiated instance shutdown (in seconds), such as when a fatal process dies or an unrecoverable instance error occurs.
instance_mode	READ-WRITE (default), READ-ONLY, READ-MOSTLY	N	Indicates whether the instance is read-write, read-only, or read-mostly.
long_module_action	TRUE (default), FALSE	Y	Enables the use of longer lengths for modules and actions.
max_idle_time	0 (default) to the maximum integer. The value of 0 indicates that there is no limit.	Y	Specifies the maximum number of minutes that a session can be idle. After that point, the session is automatically terminated.
optimizer_adaptive_plans	TRUE (default), FALSE	Y	Controls adaptive plans. Adaptive plans are execution plans built with alternative choices that are decided at run time based on statistics collected as the query executes.
optimizer_adaptive_statistics	TRUE, FALSE (default)	Y	Controls adaptive statistics. Some query shapes are too complex to rely on base table statistics alone, so the optimizer augments these statistics with adaptive statistics.
outbound_dblink_protocols	ALL (default), NONE, TCP, TCPS, IPC	N	Specifies the network protocols allowed for communicating for outbound database links in the database.
resource_manage_goldengate	TRUE, FALSE (default)	Y	Determines whether Oracle GoldenGate apply processes in the database are resource managed.
standby_db_preserve_states	NONE (default), SESSION, ALL	N	Controls whether user sessions and other internal states of the instance are retained when a readable physical standby database is converted to a primary database.
uniform_log_timestamp_format	TRUE (default), FALSE	Y	Specifies that a uniform timestamp format be used in Oracle Database trace (.trc) files and log files (such as the alert log).

The compatible parameter has a new default value for Oracle 12c version 12.2.0.1 on Amazon RDS. The following table shows the new default value.

Parameter name	Oracle 12c version 12.2.0.1 default value	Oracle 12c version 12.1.0.2 default value
compatible	12.2.0	12.0.0

The optimizer_features_enable parameter has a new value range for Oracle 12c version 12.2.0.1 on Amazon RDS. For the old and new value ranges, see the following table.

Parameter name	12c version 12.2.0.1 range	12c version 12.1.0.2 range
optimizer_features_enable	8.0.0 to 12.2.0.1	8.0.0 to 12.1.0.2

The following parameters were removed in Oracle 12c Version 12.2.0.1:

global_context_pool_size
max_enabled_roles
optimizer_adaptive_features
parallel_automatic_tuning
parallel_degree_level
use_indirect_data_buffers

The following parameter is not supported in Oracle 12c Version 12.2.0.1 and later:

sec_case_sensitive_logon

Amazon RDS security changes for Oracle 12c version 12.2.0.1

In Oracle 12c version 12.2.0.1, direct grant of the privilege ADMINISTER DATABASE TRIGGER is required for the owners of database-level triggers. During a major version upgrade to Oracle 12c version 12.2.0.1, Amazon RDS grants this privilege to any user that owns a trigger so that the trigger owner has the required privileges. For more information, see the My Oracle Support document 2275535.1.

Oracle 12c version 12.1.0.2 with Amazon RDS

Oracle 12c version 12.1.0.2 brings over 500 new features and updates from the previous version. In this section, you can find the features and changes important to using Oracle 12c version 12.1.0.2 on Amazon RDS. For a complete list of the changes, see the Oracle 12c version 12.1 documentation. For a complete list of features supported by each Oracle 12c edition, see Permitted features, options, and management packs by Oracle database edition in the Oracle documentation.

Oracle 12c version 12.1.0.2 includes 16 new parameters that impact your Amazon RDS DB instance, and also 18 new system privileges, several no longer supported packages, and several new option group settings. For more information on these changes, see the following sections.

Amazon RDS parameter changes for Oracle 12c version 12.1.0.2

Oracle 12c version 12.1.0.2 includes 16 new parameters in addition to several parameters with new ranges and new default values.

The following table shows the new Amazon RDS parameters for Oracle 12c version 12.1.0.2.

Name	Values	Modifiable	Description
connection_brokers	CONNECTION_BROKERS = broker_description[,...]	N	Specifies connection broker types, the number of connection brokers of each type, and the maximum number of connections per broker.
db_index_compression_inheritance	TABLESPACE, TABL, ALL, NONE	Y	Displays the options that are set for table or tablespace level compression inheritance.
db_big_table_cache_percent_target	0-90	Y	Specifies the cache section target size for automatic big table caching, as a percentage of the buffer cache.
heat_map	ON, OFF	Y	Enables the database to track read and write access of all segments and modification of database blocks that are due to data manipulation language (DML) and data definition language (DDL) statements.
inmemory_clause_default	INMEMORY, NO INMEMORY	Y	INMEMORY_CLAUSE_DEFAULT enables you to specify a default In-Memory Column Store (IM column store) clause for new tables and materialized views.
inmemory_clause_default_memcompress	NO MEMCOMPRESS, MEMCOMPRESS FOR DML, MEMCOMPRESS FOR QUERY, MEMCOMPRESS FOR QUERY LOW, MEMCOMPRESS FOR QUERY HIGH, MEMCOMPRESS FOR CAPACITY, MEMCOMPRESS FOR CAPACITY LOW, MEMCOMPRESS FOR CAPACITY HIGH	Y	See INMEMORY_CLAUSE_DEFAULT.
inmemory_clause_default_priority	PRIORITY LOW, PRIORITY MEDIUM, PRIORITY HIGH, PRIORITY CRITICAL, PRIORITY NONE	Y	See INMEMORY_CLAUSE_DEFAULT.
inmemory_force	DEFAULT, OFF	Y	INMEMORY_FORCE allows you to specify whether tables and materialized view that are specified as INMEMORY are populated into the In-Memory Column Store (IM column store) or not.
inmemory_max_populate_servers	Null	N	INMEMORY_MAX_POPULATE_SERVERS specifies the maximum number of background populate servers to use for In-Memory Column Store (IM column store) population, so that these servers don't overload the rest of the system.
inmemory_query	ENABLE (default), DISABLE	Y	INMEMORY_QUERY is used to enable or disable in-memory queries for the entire database at the session or system level.
inmemory_size	0, 104857600-274877906944	Y	INMEMORY_SIZE sets the size of the In-Memory Column Store (IM column store) on a database instance.
inmemory_trickle_repopulate_servers_percent	0 to 50	Y	INMEMORY_TRICKLE_REPOPULATE_SERVERS_PERCENT limits the maximum number of background populate servers used for In-Memory Column Store (IM column store) repopulation. This limit is applied because trickle repopulation is designed to use only a small percentage of the populate servers.
max_string_size	STANDARD (default), EXTENDED	N	Controls the maximum size of VARCHAR2, NVARCHAR2, and RAW. For more information, see Using extended data types.
optimizer_adaptive_features	TRUE (default), FALSE	Y	Enables or disables all of the adaptive optimizer features.
optimizer_adaptive_reporting_only	TRUE, FALSE (default)	Y	Controls reporting-only mode for adaptive optimizations.
pdb_file_name_convert	There is no default value.	N	Maps names of existing files to new file names.
pga_aggregate_limit	0-max of memory	Y	Specifies a limit on the aggregate PGA memory consumed by the instance.
processor_group_name	There is no default value.	N	Instructs the database instance to run itself within the specified operating system processor group.
spatial_vector_acceleration	TRUE, FALSE	N	Enables or disables the spatial vector acceleration, part of spatial option.
temp_undo_enabled	TRUE, FALSE (default)	Y	Determines whether transactions within a particular session can have a temporary undo log.
threaded_execution	TRUE, FALSE	N	Enables the multithreaded Oracle model, but prevents OS authentication.
unified_audit_sga_queue_size	1 MB - 30 MB	Y	Specifies the size of the system global area (SGA) queue for unified auditing.
use_dedicated_broker	TRUE, FALSE	N	Determines how dedicated servers are spawned.

Several parameters have new value ranges for Oracle 12c version 12.1.0.2 on Amazon RDS. For the old and new value ranges, see the following table.

Parameter name	12c version 12.1.0.2 range	11g range
audit_trail	os \| db [, extended] \| xml [, extended]	os \| db [, extended] \| xml [, extended] \| true \| false
compatible	Following are the requirements for `COMPATIBLE`: If you upgrade to 12.1.0.2, `COMPATIBLE` must be 12.0 or higher. For new 12.1.0.2 DB instances, `COMPATIBLE` is set to 12.1.0.2. If you upgrade to 12.2.0.1, 18c, or 19c, `COMPATIBLE` must be 11.2.0 or higher. If `COMPATIBLE` is not explicitly set, Amazon RDS automatically sets this parameter to 12.0.0.	Starts with 11.2.0 on Amazon RDS
db_securefile	PERMITTED \| PREFERRED \| ALWAYS \| IGNORE \| FORCE	PERMITTED \| ALWAYS \| IGNORE \| FORCE
db_writer_processes	1-100	1-36
optimizer_features_enable	8.0.0 to 12.1.0.2	8.0.0 to 11.2.0.4
parallel_degree_policy	MANUAL,LIMITED,AUTO,ADAPTIVE	MANUAL,LIMITED,AUTO
parallel_min_server	0 to parallel_max_servers	CPU_COUNT * PARALLEL_THREADS_PER_CPU * 2 to parallel_max_servers

One parameter has a new default value for Oracle 12c on Amazon RDS. The following table shows the new default value.

Parameter name	Oracle 12c default value	Oracle 11g default value
job_queue_processes	50	1000

Amazon RDS system privileges for Oracle 12c version 12.1.0.2

Several new system privileges have been granted to the system account for Oracle 12c version 12.1.0.2. These new system privileges include the following:

ALTER ANY