Oracle Database 19c New Features for DBAs and Developers.pptx
0 likes426 views
Oracle Database 19c introduces various enhancements, including automatic indexing using machine learning, support for DML redirection in Active Data Guard, and improved resource management for concurrent Data Pump jobs. New features also include automatic flashback for standby databases, hybrid partitioned tables for big data SQL, and simplified client installation as an image file. Additionally, real-time statistics are now collected during DML operations to optimize query performance.
Oracle Database 19c New Features for DBAs and Developers.pptx
- 1. Oracle Database 19c New Features for DBAs and Developers
- 2. When using the DBMS INMEMORY ADMIN.POPULATE command, the WAIT function will hold off until a certain percentage of objects with a given priority have been populated. Database In-Memory Wait on Populate:
- 3. MAX_DATAPUMP_JOBS_PER_JOB limits job count in multitenant container databases: Default: 100, Range: 0 - 250, or Auto: 50% SESSIONS. The MAX_DATAPUMP_PARALLEL_PER_JOB parameter controls Data Pump job’s parallel workers. These parameters improve resource control for concurrent Data Pump jobs. Oracle Data Pump Support for Resource Usage Limitations:
- 4. Starting with this release, you no longer need the FILE_NAME_CONVERT clause for Transparent Data Encryption online conversion in non-Oracle-managed files mode. The file maintains its original name. This enhancement helps prevent you from having to rename files to the original name, sometimes missing files. Transparent Online Conversion Support for Auto- Renaming in Non-Oracle-Managed Files Mode:
- 5. Automatic Indexing is a new feature in Oracle Database 19c that uses machine learning algorithms to identify and create indexes on tables. The DBMS_AUTO_INDEX package in Oracle 19c automatically creates candidate indexes for tables. Oracle Database will test and verify the index for improved query performance. If successful, it will be applied for use in applications. Automatic Indexing
- 6. Active Data Guard in Oracle Database 19c now supports DML redirection for read- write workloads. Active Data Guard standby databases allow DML operations. Applications can gain from using an Active Data Guard standby database with writes. DML redirection aids load balancing between primary and standby databases. Incidental DML on a standby database is executed on the primary database. The redo updates the standby database and control is returned to the application. DML redirection support in Active Data Guard:
- 7. Oracle Data Guard automatically resolves outages by detecting and terminating hung processes. Use the parameters DATA_GUARD_MAX_IO_TIME and DATA_GUARD_MAX_LONGIO_TIME to tune wait times for specific Oracle Data Guard configurations, based on user network and disk I/O behavior. New Parameters to Tune Automatic Outage Resolution with Oracle Data Guard:
- 8. Oracle’s Resource Manager automatically quarantines resource-heavy SQL queries. The DBMS_SQLQ package allows you to define thresholds for quarantining SQL statements. SQL Quarantines:
- 9. When using the DBMS INMEMORY ADMIN.POPULATE command, the WAIT function will hold off until a certain percentage of objects with a given priority have been populated. Database In-Memory Wait on Populate:
- 10. In a multitenant environment, you have the ability to utilize Automatic Database Diagnostic Monitor (ADDM) analysis for pluggable databases (PDBs). Automatic Database Diagnostic Monitor (ADDM) Support for Pluggable Databases (PDBs):
- 11. MAX_IDLE_BLOCKER_TIME determines the idle time limit for terminating sessions with needed resources. MAX_IDLE_TIME limits all idle sessions, while MAX_IDLE_BLOCKER_TIME only limits idle sessions consuming resources. MAX_IDLE_TIME can cause issues for connection pools by repeatedly recreating terminated sessions. MAX_IDLE_BLOCKER_TIME Parameter:
- 12. The ALTER SYSTEM clause FLUSH PASSWORDFILE_METADATA_CACHE refreshes the metadata cache with the latest details of the database password file, useful when the file name or location is changed. New ALTER SYSTEM Clause FLUSH PASSWORDFILE_METAD ATA_CACHE:
- 13. Starting with this release, you no longer need the FILE_NAME_CONVERT clause for Transparent Data Encryption online conversion in non-Oracle-managed files mode. The file maintains its original name. This enhancement helps prevent you from having to rename files to the original name, sometimes missing files. Transparent Online Conversion Support for Auto- Renaming in Non-Oracle-Managed Files Mode:
- 14. Only AES128 encryption was supported for offline tablespace encryption in previous releases. This release adds support for AES192, AES256, ARIA, GOST, and 3DES encryption algorithms for offline tablespace encryption. This enhancement is beneficial for concerns regarding auxiliary space usage in online tablespace encryption. Additional Algorithms for Offline Tablespace Encryption:
- 15. Oracle Database schema-only accounts no longer have passwords for authentication. The enhancement has no impact on the sample schemas. Default passwords remain for sample schemas. Passwords Removed from Oracle Database Accounts:
- 16. Oracle Clusterware enables cluster-based failover for Standard Edition Oracle Databases. Oracle Standard Edition High Availability benefits from Oracle Grid Infrastructure’s cluster capabilities and storage solutions like Oracle Clusterware, Oracle ASM, and Oracle ACFS. Standard Edition High Availability:
- 17. The standby database in Oracle Data Guard can be automatically flashed back during a primary database flashback operation. Flashback operation on primary database desynchronizes standby. Previous releases required specific steps to sync the standby with the primary. This feature allows for automatic flashback of the standby database during a primary database flashback. It saves time, effort, and reduces errors, resulting in faster synchronization and reduced recovery time. Flashback Standby Database When Primary Database is Flashed Back:
- 18. In-Memory Column Store and Data Guard Multi-Instance Redo Apply can be enabled together on an Active Data Guard standby. The two features were previously exclusive. Use the fastest redo apply and analytical query technologies on the same Active Data Guard standby for optimal performance. Multi-Instance Redo Apply speeds up apply using In-Memory Column Store on the Active Data Guard standby. Oracle Data Guard Multi-Instance Redo Apply Works with the In-Memory Column Store:
- 19. Oracle Data Guard automatically resolves outages by detecting and terminating hung processes. Use the parameters DATA_GUARD_MAX_IO_TIME and DATA_GUARD_MAX_LONGIO_TIME to tune wait times for specific Oracle Data Guard configurations, based on user network and disk I/O behavior. New Parameters to Tune Automatic Outage Resolution with Oracle Data Guard:
- 20. Oracle Database automatically collects statistics during DML operations. Statistics can become stale between DBMS_STATS jobs. The database enhances statistics by collecting them automatically during DML operations. Current statistics enhance plan optimization. Real-Time Statistics:
- 21. This feature allows partitions to be stored in both Oracle Database segments and external files. This feature improves partitioning for Big Data SQL with external partitions. Hybrid partitioned tables combine internal and external partitions in one table. This feature allows you to move non-active partitions to cheaper storage solutions. Hybrid Partitioned Tables:
- 22. Use DBCA’s createDuplicateDB command to make a silent duplicate of an Oracle Database. Developers can work on identical copies of an Oracle Database. Ability to Create a Duplicate of an Oracle Database Using DBCA in Silent Mode:
- 23. Oracle Database 19c onwards, the client software is downloadable as an image file. Extract the image software into the desired directory and run the runInstaller script to install the Oracle Database client. Oracle Database client installation files are still offered in the non-image zip format. Simplified Image-Based Oracle Database Client Installation:
- 24. • •Oracle Database 19c installer allows automatic setup of permissions for root configuration scripts during installation. You can still manually run the root configuration scripts. • •Enabling automated execution of root configuration scripts simplifies database installation and prevents permission errors. Root Scripts Automation Support for Oracle Database Installation:
- 25. • •Starting with Oracle Grid Infrastructure 19c, use gridSetup.sh for installation. • •The wizard checks if your system is ready for upgrade in dry-run mode. This mode does not execute upgrades. Anticipating system setup problems helps avoid upgrade failures. Support for Dry-Run Validation of Oracle Clusterware Upgrade:
- 26. The new OMIT_ENCRYPTION_CLAUSE parameter in Data Pump can eliminate encryption clauses for objects with encrypted columns. Non-cloud databases with encrypted columns can now be more easily migrated to Oracle Cloud. Oracle Data Pump Ability to Exclude ENCRYPTION Clause on Import:
- 27. • •AutoUpgrade allows upgrading multiple Oracle Database instances with a single command and configuration file. • •AutoUpgrade handles pre-upgrade tasks, automated fix-ups, and post-upgrade tasks. It offers automatic retry, scheduled upgrades, and customizable initialization parameters. AutoUpgrade for Oracle Database:
- 28. • •You can determine export duration and uncover unreported issues. • •TTSs test mode exports metadata-only or performs full transportable export/import. It no longer requires read-only mode for the source database tablespaces. Oracle Data Pump Test Mode for Transportable Tablespaces:
- 29. • •Multiple table families can be created in a sharded database, each with a different sharding key. • • • •One sharded database can now host multiple applications accessing different table families. Only system-managed sharded databases have this feature. Multiple Table Family Support for System-Managed Sharding:
- 30. • • Update JSON documents using SQL function JSON_MERGEPATCH, applying changes to multiple documents with one statement. • • This feature enhances JSON update flexibility. JSON Update Operations: