What’s New in Oracle Database 19c - Part 1

What’s New in Oracle Database 19c- Part1
Database Overall
Satishbabu Gunukula, Oracle ACE
• 20+ Years of Experience in Database Technologies and
specialized in high availability solutions.
• Masters Degree in Computer Applications
• Written articles for major publications
• Oracle Certified Professional Oracle 8i,9i,10g
• Oracle Certified Expert Oracle 10g RAC
http://www.oracleracexpert.com

Program Agenda
• Overview of Oracle Database 19c
• Oracle 19c New Features
– Application Development
– Availability
– Big Data and Data Warehousing
– Database Overall
– Diagnosability
– Performance
– RAC and Grid
– Security
• Database Overall
– Automated Installation, Configuration and Patching
– AutoUpgrade and Database Utilities
• Q& A

Overview of Oracle 19c
• Oracle Database 19c is the final release of Oracle Database 12c family of
products. It comes with 4 years premium support and 3 years of min
extended support
• Oracle 19c advances of previous release features such as In-Memory, Oracle
autonomous Database cloud, JSON Support for developers, Sharding and also
introduces other new features and functionality

Oracle 19c New features
Oracle release 19c has many new features and functionalities
in below areas
– Application Development
– Availability
– Big Data and Data Warehousing
– Database Overall
– Diagnosability
– Performance
– RAC and Grid
– Security

Application Development
• Application Express
– Improved Create Application Wizard
– REST Enabled SQL Support
– Social Sign-In Authentication
– Web Source Modules
– Improved Create Page Wizard
– New REST Workshop
• General
– Application Continuity for Java: Declarative Request Demarcation
– Application Continuity for Java: New States Management
– Easy Connect Plus
– Oracle Network Log File Segmentation
– SQL*Net: Auto-Detection of Support for Out-of-Band Breaks
• JSON
– Materialized View Support for Queries Containing JSON_TABLE
– JSON Update Operations
– SQL/JSON Syntax Simplifications
– JSON Object Mapping
– New SQL/JSON Function JSON_SERIALIZE and JSON Data Guide Support for GeoJSON Data
• SQL
– DISTINCT Option for LISTAGG Aggregate

Availability
• General
– Dynamically Change Oracle Data Guard Broker Fast-Start Failover Target
– Simplified Database Parameter Management in Oracle Data Guard Broker
– Observe-only Mode for Oracle Data Guard Broker's Fast-Start Failover
– Propagate Restore Points from Primary to Standby Site
– Flashback Standby Database When Primary Database is Flashed Back
– Oracle Data Guard Multi-Instance Redo Apply Works with the In-Memory Column Store
– Active Data Guard DML Redirection
– PDB Recovery Catalog
– Clear Flashback Logs Periodically for Increased Fast Recovery Area Size Predictability
– New Parameters to Tune Automatic Outage Resolution with Oracle Data Guard
– Finer Granularity Supplemental Logging
• Sharding
– Support for Multi-Shard Query Coordinators on Shard Catalog Standby Databases
– Generation of Unique Sequence Numbers Across Shards
– Support for Multiple PDB Shards in the Same CDB
– Multiple Table Family Support for System-Managed Sharding
– Propagation of Parameter Settings Across Shards

Big Data and Data Warehousing
• Big Data and Data Warehousing New Features
– Automatic Indexing
– SQL Diagnostics and Repair Enhancements
– Bitmap Based Count Distinct SQL Function
– Big Data and Performance Enhancements for In-Memory External Tables
– Automatic SQL Plan Management
– Real-Time Statistics
– High-Frequency Automatic Optimizer Statistics Collection
– Hybrid Partitioned Tables

Database Overall
• Automated Installation, Configuration and Patching
– Ability to Create a Duplicate of an Oracle Database Using DBCA in Silent Mode
– Ability to Relocate a PDB to Another CDB Using DBCA in Silent Mode
– Ability to Create a PDB by Cloning a Remote PDB Using DBCA in Silent Mode
– Simplified Image-Based Oracle Database Client Installation
– Root Scripts Automation Support for Oracle Database Installation
– Support for Dry-Run Validation of Oracle Clusterware Upgrade
• AutoUpgrade and Database Utilities
– Oracle Data Pump Ability to Exclude ENCRYPTION Clause on Import
– Oracle Data Pump Allows Tablespaces to Stay Read-Only During TTS Import
– Oracle Data Pump Support for Resource Usage Limitations
– Oracle Data Pump Test Mode for Transportable Tablespaces
– Oracle Data Pump Prevents Inadvertent Use of Protected Roles
– Oracle Data Pump Loads Partitioned Table Data One Operation
– Oracle Data Pump Allows Wildcards for Dump File in Object Store
– Oracle Data Pump Import Supports More Object Store Credentials

Diagnosability
• Diagnosability New features
– Oracle Trace File Analyzer Support for Using an External SMTP Server for Notifications
– Oracle Cluster Health Advisor Integration into Oracle Trace File Analyzer
– Oracle Trace File Analyzer REST API Support
– Oracle Trace File Analyzer Search Extended to Support Metadata Searches
– Oracle ORAchk and Oracle EXAchk REST Support
– Oracle ORAchk and Oracle EXAchk Support for Encrypting Collection Files
– Oracle ORAchk and Oracle EXAchk Support for Remote Node Connections Without Requiring
Passwordless SSH
– Oracle ORAchk and Oracle EXAchk Now Show Only the Most Critical Checks by Default
– Oracle Trace File Analyzer Supports New Service Request Data Collections

Performance
• Performance new features
– SQL Quarantine
– Database In-Memory Wait on Populate
– Resource Manager Automatically Enabled for Database In-Memory
– Memoptimized Rowstore Fast Ingest
– Automatic Database Diagnostic Monitor (ADDM) Support for Pluggable Databases (PDBs)
– Resource Manager Automatically Enabled for Database In-Memory
– High-Frequency SQL Plan Management Evolve Advisor Task
– Workload Capture and Replay in a PDB

RAC and Grid
• Oracle RAC and Grid new features
– Standard Edition High Availability
– Parity Protected Files
– Secure Cluster Communication
– Automated PDB Relocation
– Zero-Downtime Oracle Grid Infrastructure Patching
– Automated Transaction Draining for Oracle Grid Infrastructure Upgrades
– Oracle Restart Patching and Upgrading
– Colocation Tag for Client Routing
– Optional Install for the Grid Infrastructure Management Repository
– Resupport of Direct File Placement for OCR and Voting Disks
– Dynamic Services Fallback Option

Security
• Security new features
– New ALTER SYSTEM Clause FLUSH PASSWORDFILE_METADATA_CACHE
– Transparent Online Conversion Support for Auto-Renaming in Non-Oracle-Managed Files
Mode
– Support for Additional Algorithms for Offline Tablespace Encryption
– Key Management of Encrypted Oracle-Managed Tablespaces in Transparent Data Encryption
– Support for Host Name-Based Partial DN Matching for Host Certificates
– New PDB_GUID Audit Record Field for SYSLOG and the Windows Event Viewer
– New EVENT_TIMESTAMP_UTC Column in the UNIFIED_AUDIT_TRAIL View
– Passwords Removed from Oracle Database Accounts
– Signature-Based Security for LOB Locators
– Unified Auditing Top-Level Statements
– Privilege Analysis Now Available in Oracle Database Enterprise Edition
– Support for Oracle Native Encryption and SSL Authentication for Different Users Concurrently
– Ability to Grant or Revoke Administrative Privileges to and from Schema-Only Accounts
– Automatic Support for Both SASL and Non-SASL Active Directory Connections
– Database Vault Operations Control for Infrastructure Database Administrators
– Database Vault Command Rule Support for Unified Audit Policies

Database Overall
Automated Installation, Configuration and Patching
 Ability to Create a Duplicate of an Oracle Database Using DBCA in Silent Mode
 By using DBCA in slient mode you can create a duplicate database by
using command CreateDuplicateDB command
 The following are the prerequisites
 Database must in archive log mode
 If duplicate on remote server then source and destination servers
must have connectivity
For Syntax Refer https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/creating-and-
configuring-an-oracle-database.html#GUID-7F4B1A64-5B08-425A-A62E-854542B3FD4E

Database Overall
 Ability to Relocate a PDB to Another CDB Using DBCA in Silent Mode
 By using DBCA in slient mode you can relocate PDB from a remote
CDB to local CDB using relocatePDB command
 The following are the prerequisites
 The local and remove PDB’s must be in archive log mode
 The local PDB must have CREATE PLUGGABLE DATABASE Privilege
in the local CDB root
 The Remote CDB must be in local undo mode
 The remote PDB must have the CREATE PUGGABLE DATABASE,
SESSION and SYSOPER privileges
 The installed options for both local and remote PDB’s must be
same
For Syntax Referhttps://docs.oracle.com/en/database/oracle/oracle-database/19/admin/creating-
and-configuring-an-oracle-database.html#GUID-8DD80A8A-DDE1-471F-8CBB-013D85CFE28F

Database Overall
 Ability to Create a PDB by Cloning a Remote PDB Using DBCA in Silent Mode
 By using DBCA in slient mode you can now create a PDB by cloning a remote PDB
using createFromRemotePDB parameter of the CreatePluggableDatabase
command
 To Create a PDB by cloning a remote PDB you need to specify following parameters
 -pdbName: Name of the local PDB to create.
 -sourceDB: Database name of the local PDB.
 -remotePDBName: Name of the remote PDB to clone.
 -remoteDBConnString: Database connection string of the remote PDB.
 -sysDBAUserName: Name of the SYSDBA user.
 -sysDBAPassword: Password of the SYSDBA user.
 -dbLinkUsername: Name of the database link user of the remote PDB.
 -dbLinkUserPassword: Password of the database link user of the remote PDB.
For Syntax Refer https://docs.oracle.com/en/database/oracle/oracle-
database/19/admin/creating-and-configuring-an-oracle-database.html#GUID-6EDDC43D-9BD6-
4096-8192-7E548B826360

Database Overall
 Simplified Image-Based Oracle Database Client Installation
 From Oracle 19c, Oracle client software is available in image file for download
 User needs to extract the image software into a directory and run the runInstaller
script to start Oracle client installation
$ cd /home/oracle_sw_image/
$ ./runInstaller
 During the client install you will be asked to run a script as root user.
 Root Scripts Automation Support for Oracle Database Installation
 From Oracle 19c, you will have an option to setup up the permissions to run the
root configurations scripts by database installer or wizard or run the script
manually.
 To run root scripts automatically select “Automatically run configuration scripts”
during the installation, but you need to provide one the below
 Use sudo - provide the username and password of the user who is member of
sudoers
 Use root user – provide root user password
 Support for Dry-Run Validation of Oracle Clusterware Upgrade
 From Oracle Grid infrastructure 19c, the gridsetup.sh allows you to perform dry-
run mode upgrade for system readiness check
$/oracle/19.0.0/grid/gridSetup.sh -dryRunForUpgrade

Database Overall
AutoUpgrade for Oracle Database
 Oracle Data Pump Ability to Exclude ENCRYPTION Clause on Import
 The OMIT_ENCRYPTION_CLAUSE parameter helps to suppress any
encryption clauses associated with objects using encrypted columns.
 OMIT_ENCRYPTION_CLAUSE is a new transform parameter and provide
values Y or N. By default it is set to N, if you need to suppress encryption
clauses set to Y.
TRANSFORM = OMIT_ENCRYPTION_CLAUSE :Y
 Oracle Data Pump Allows Tablespaces to Stay Read-Only During TTS Import
 This option helps to make import faster but database doesn’t reclaim the
space during the import because the bitmaps cannot be rebuilt.
 The option allows a tablespace data file to be mounted on a two
databases as long as it remains read-only
 The source and target databases must have same daylight saving time
(DST) version
TRANSPORTABLE = KEEP_READ_ONLY

Database Overall
 Oracle Data Pump Support for Resource Usage Limitations
 A new paratmer MAX_DATAPUMP_PARALLEL_PER_JOB helps to control number
of parallel workers that you can use for a data pump job
 This parameter mainly helps in multitenant container database environment over
resource utilization.
 Default: 100, Range: 0 to 250, or Auto: 50% of SESSIONS.
 You can able to modify this parameter using ALTER SYSTEM
MAX_DATAPUMP_PARALLEL_PER_JOB = AUTO
 Oracle Data Pump Test Mode for Transportable Tablespaces
 The Test mode option helps to determine how much time an export takes
 TTS_CLOSURE_CHECK parameter will be used only for export operation.
TTS_CLOSURE_CHECK parameter supports the following options:
 ON - self-containment closure check be performed
 OFF - No closure check be performed
 FULL - Full bidirectional closure check be performed
 TEST_MODE - Tablespaces are not required to be in read-only mode

Database Overall
 Oracle Data Pump Prevents Inadvertent Use of Protected Roles
 By using ENABLE_SECURE_ROLES PARAMTER you can prevents inadvertent
use of protected roles and default value is “NO”
 Some Oracle roles require authorization and if you need to use those roles
then you must explicitly enable this parameter the value to YES
ENABLE_SECURE_ROLES PARAMTER: YES
 Oracle Data Pump Loads Partitioned Table Data One Operation
 Instead of separate operations for each partition now you can import all
partitions of a table as one operation
 To use this feature use value GROUP_PARTITION_TABLE_DATA with import
DATA_OPTIONS command
 The default behavior is to import each table partition as separate operation
DATA_OPTIONS = GROUP_PARTITION_TABLE_DATA

Database Overall
 Oracle Data Pump Allows Wildcards for Dump File in Object Store
 By allowing wildcards you can import multiple dump files into oracle
Autonomous Database
 The URL-based dump file name can be simplified in the import command
 Use wildcards on object store service and do not use in the bucket-name
component
$ impdp admin/xxxxxx@orcl
directory=data_pump_dir credential=my_db_cred
dumpfile= https://objectstorage.oraclecloud.com/orcl/exp%.dmp"

Database Overall
 Oracle Data Pump Import Supports More Object Store Credentials
 Oracle 19c offers import support for more object sore credentials beyond
DEFAULT_CREDENTIAL
 A New CREDENTIAL parameter allows support for more object store
credentials for Oracle Autonomous Database
 Oracle Cloud Infrastructure (OCI) Object Storage credential created by
using the DBMS_CLOUD.CREATE_CREDENTIAL() procedure
 The default value is None
$ impdp admin/xxxxxx@orcl
directory=data_pump_dir
CREDENTIAL=user_accessible_credential
dumpfile= “https://objectstorage.cloud.com/orcl/exp%.dmp"

Database Overall
 Oracle Data Pump Import Supports More Object Store Credentials
 The below example shows how to creates a new user-defined credential
in the Oracle Autonomous Database
SQL> BEGIN
DBMS_CLOUD.CREATE_CREDENTIAL(
credential_name => ‘my_db_cred’,
username => ‘orcluser@cloud.com’,
password => ‘auth token' );
END;
$ impdp admin/xxxxxxx@orcl
directory=data_pump_dir
credential=my_db_cred
dumpfile= “https://objectstorage.cloud.com/orcl/exp%.dmp"

Summary
• Oracle Database 19c, builds upon key architectural,
distributed data and performance innovations established
in earlier versions Oracle Database 12c and 18c releases.
Oracle 19c has many new features, in this presentation we
have covered below areas
– Automated Installation, Configuration and Patching
– AutoUpgrade and Database Utilities

What’s New in Oracle Database 19c - Part 1

More Related Content

What's hot (20)

Similar to What’s New in Oracle Database 19c - Part 1 (20)

More from Satishbabu Gunukula (14)

Recently uploaded (20)

What’s New in Oracle Database 19c - Part 1

Editor's Notes