New Features in Oracle Database 19c

Simplified Image-based installation of the client as well

RPM Based Installation install Oracle 19c Database using RPM method with Vagrant Virtual box and
via ansible-playbook
Docker Container for Oracle 19c
Auto Upgrade Utility for Oracle Database
DryRun mode for GridSetup in Clusterware Installation

Clear flashback logs periodically

Multimodel partitioning with Hybrid partitioning allowing some partitions in the database and some
as external partitions even in hdfs
Passwords removed from schema accounts (default accounts)
Schema-only accounts - Passwords Removed from Oracle Database Accounts
Flush Metadata Cache for Passwords
Hybrid Partitioned Tables - to integrate internal partitions and external partitions into a single
partition table. partitions to reside in both Oracle Database segments and in external files and
sources
New ALTER SYSTEM statement clause FLUSH PASSWORDFILE_METADATA_CACHE

Creation Duplicate of an Oracle Database, CreateDuplicateDB command, in DBCA Silent Mode

Ability to Create a PDB by Cloning a Remote PDB Using DBCA in Silent Mode
Ability to relocate a PDB to another CDB Using DBCA in Silent Mode
ADDM Analysis at PDB Level

Oracle Data Pump Ability to Exclude ENCRYPTION Clause on Import - new transform parameter
OMIT_ENCRYPTION_CLAUSE
Oracle Data Pump Support for Resource Usage Limitations - new parameter
MAX_DATAPUMP_PARALLEL_PER_JOB
Oracle Data Pump Test Mode for Transportable Tablespaces (TTS)
Oracle Data Pump Prevents Inadvertent Use of Protected Roles - new ENABLE_SECURE_ROLES
parameter is available
Oracle Data Pump Loads Partitioned Table Data One Operation - GROUP_PARTITION_TABLE_DATA, a
new value for the Import DATA_OPTIONS command line parameter
Oracle Data Pump Allows Tablespaces to Stay Read-Only During TTS Import
Oracle Data Pump Import Supports More Object Store Credentials
SQL Quarantine - Starting Oracle 19c, SQL Quarantine features helps to prevent reuse of the same
execution plan which was terminated by resource managers due to resource limits. This will help not
to run the rouge queries again on the database if the resource manager is active. SQL Quarantine
will need to set up configuration and define thresholds for a specific execution plan for given sql_id
or for all plans for sql_id. The thresholds are similar like resource manager threshold ex: cpu limit,
elapsed_time limit, etc. To define the thresholds you can use the DBMS_SQLQ package. quarantine
configuration for an execution plan for a SQL statement
Automatic Indexing - Manage Auto Indexes with Advisory tasks like MOnitor, Capture, Identify,
Verify, Decide - to enable auto index mode is below, we have options "Implement", "Report-Only",
"OFF".
select * from dba_auto_index_config;
SQL Statement Diagnosability with SQL Advisor repair and SQL Test case for procedures
Automatic Database Diagnostic Monitor (ADDM) Support for Pluggable Databases (PDBs)
Realtime statistics for DML Operations - Oracle Database 19c introduces real-time statistics, which
extend online support to conventional DML statements
Statistics Collection on custom frequency automatically - From 19c onwards, High-frequency
automatic optimizer statistics collection complements the standard statistics collection job
Workload Capture and Replay in a PDB

Replicate Restore Points from Primary to Standby

Dynamically change Fast-Start Failover (FSFO) target standby database to another standby database
in the target list without disabling FSFO.
Automatic Flashback of Standby
Re-creation of broker configuration
Propagate Restore Points from Primary to Standby site
DML redirect to standby/ADG for read-mostly applications
Simplified Dataguard broker parameter configurations
Flashback Standby Database when Primary Database is Flashed Back - Oracle 19c onwards, DBA can
put the standby database in MOUNT mode without managed recovery and then flashback primary
database; the standby will also be reverted, thus keeping it in sync with the primary.
Observe Only Mode for Data Guard Broker's Fast-Start Failover (FSFO)
Oracle Data Guard Multi-Instance Redo Apply Works with the In-Memory Column Store
Finer Granularity Supplemental Logging for logical standby databases

"_optimizer_gather_stats_on_conventional_dml" and
"_optimizer_use_stats_on_conventional_dml" which are true by default
_optimizer_stats_on_conventional_dml_sample_rate (at 100%)
DATA_GUARD_MAX_IO_TIME
DATA_GUARD_MAX_LONGIO_TIME
ADG_REDIRECT_DML (TRUE or FALSE)
MAX_DATAPUMP_JOBS_PER_PDB
aws_pdb_autoflush_enabled (TRUE or FALSE)
dba_auto_index_config
dba_sql_quarantine
V$SQL_TESTCASES
DBA_REGISTRY_BACKPORTS

dbms_auto_index
dbms_auto_index_internal
DBMS_SQL