Oracle 19c Features

-

Oracle Database 19c, is the long term support release of the Oracle Database 12c and 18c family of products, offering customers Premier and Extended Support through to March 2023 and March 2026 respectively. It is available on Linux, Windows, Solaris, HP/UX and AIX platforms as well as the Oracle Cloud. Oracle Database 19c offers customers the best performance, scalability, reliability and security for all their operational and analytical workloads.

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

Comments

Post a Comment

Popular posts from this blog

Step by Step: How to troubleshoot a slow running query in Oracle

-
This is a day to day task of a DBA. Someone from application team comes to our desk and simply says a query is running slow. We may question him on many things but ultimately a DBA has to tune the query at the end. This is also very popular and known question for the DBA's who are attending interviews. This question is simply asked again and again. I have also been asked this question multiple times. After a pause, interviewer simply asks...so suppose a user comes and reports that his query is running slow, what will be your approach to tune this. There is no absolute or concrete answer to this question because there might be multiple way to tune a slow running query. Everyone can have a different approach. So here is my approach: Very first thing we have to find which type of query is running slow. Whether it is SELECT query of DML statements(insert, update, delete and merge). So first we will see how to tune a SELECT query Step 1 – Find the SQL_ID of the
Read more

Register Archive log file manually in standby Database

-
  Some time, the archive logs are not shipping to standby location due to network issue.  There may be  several  archive logs are waiting in standby location for one archive log file. For instance, Archive log sequence # 100 is not shipped to standby location. But other archive logs(sequence#101 to sequence#200) were shipped to standby and it is waiting to ship the sequence# 100.  In this scenario, DBA can copy the archive log file and register manually. Once manually registered, the sequence#101 to sequence#200 will apply automatically on standby database. Step 1 Let us assume, the archive log file devdb12_1_283_801988635.arc is not shipped to standby due to some reason. Copy the archive log file devdb12_1_283_801988635.arc manually from primary to standby archive destination location. Step  2 Run the below command in standby database. ALTER DATABASE REGISTER LOGFILE '/dbArch/oradata/devdb12/ devdb12_1_283_801988635.arc';   Step  3 Verify the standby database and see if the co
Read more

How to check UNDO tablespace usage and who is using more undo

-
Query To check UNDO tablespace usage: ================================ set linesize 152 col tablespace_name for a20 col status for a10 select tablespace_name,status,count(extent_id) "Extent Count", sum(blocks) "Total Blocks",sum(bytes)/(1024*1024*1024) spaceInGB from   dba_undo_extents group by  tablespace_name, status having tablespace_name=upper('&TSNAME') order by tablespace_name; Query To check who is using more UNDO space: ===================================== SET termout ON SET heading ON SET PAGESIZE   6000 SET LINESIZE   200 COLUMN pgm_notes    FORMAT a80        HEADING 'Notes' COLUMN rbs          FORMAT a16         HEADING 'RBS'             JUST center COLUMN oracle_user  FORMAT a12        HEADING 'Oracle|Username' COLUMN sid_serial   FORMAT a12        HEADING 'SID,Serial' COLUMN unix_pid     FORMAT a6         HEADING 'O/S|PID' COLUMN Client_User  FORMAT a14        HEADING 'Cl
Read more