Oracle 19c New Features For Dba

 Hello Friend's,

In this post we will discuss about the new features of 19c for DBA.

Installation and Upgrades

  • RPM Based Installation  install Oracle 19c Database using RPM method
  • Simplified Image based installation of client as well
  • Auto Upgrade Utility for Oracle Database
  • Docker Container for Oracle 19c
  • DryRun mode for GridSetup in clusterware Installation
General
  • Clear flashback logs from time to time
  • Passwords removed from user accounts (default accounts)
  • Flush Metadata Cache for Passwords
  • Multi-model partitioning with Hybrid partitioning allowing some partitions in database and some as external partitions even in HDFS
  • New ALTER SYSTEM statement clause FLUSH PASSWORDFILE_METADATA_CACHE
  • 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.
  • Schema-only accounts – Passwords Removed from Oracle Database Accounts

Database Performance
  • SQL Quarantine – Using Oracle’s Resource Manager tool is a great way to make sure SQL statements don’t become resource hogs and slow down database performance for everyone. If a statement asks for more system resources than the DBA allows, Resource Manager kills it. However, in existing versions of Oracle Database, nothing stops users from executing problematic SQL statements again. In Oracle 19c, Resource Manager can automatically quarantine the statements; should a user try to issue one again, it won’t run at all.
  • Automatic Indexing – This new feature puts Oracle’s automation capabilities to work. If Oracle 19c thinks a database table would benefit from an index, the system will automatically create the index and initially mark it as invisible so it can’t be used. Oracle 19c will then run SQL statements from your application to see if the index improves query execution. If the index does help, it will be made visible for application use; if it doesn’t do so, the index will become unusable and eventually be removed. You can control this feature with DBMS_AUTO_INDEX, a new PL/SQL package that’s included in 19c.
  • 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
  • Automatic flashback of standby databases. In prior versions, if DBAs wanted to use Oracle’s flashback features to return a primary database to a previous state, they needed to manually rebuild an associated standby database before it could resume normal operations. In Oracle 19c, a DBA can put the standby database in MOUNT mode with no managed recovery and then flash back the primary one; the standby will also be reverted, thus keeping it in sync with the primary.
  • Statistics Collection on custom frequency automatically – From 19c onwards,  High-frequency automatic optimizer statistics collection complements the standard statistics collection job

Data Pump
  • Oracle Data Pump Test Mode for Transportable Tablespaces (TTS)
  • Oracle Data Pump Allows Tablespaces to Stay Read-Only During TTS Import
  • Oracle Data Pump Import Supports More Object Store Credentials
  • 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 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

Pluggable Databases

  • Creation Duplicate of an Oracle Database, 
  • create duplicatedb command, in DBCA silent mode
  • Ability to relocate a PDB to another CDB Using DBCA in silent mode
  • Create a PDB by Cloning a Remote PDB Using DBCA in silent mode
  • ADDM Analysis at PDB Level

Data Guard

  • 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.
  • 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
  • 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

New initialization parameters in Oracle Database 19c
  • “_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
  • MAX_DATAPUMP_JOBS_PER_PDB

Hope this helps,

Regards
Sultan Khan

Previous
Next Post »