• Oracle Database supplied user accounts are now schema only accounts

Most of the Oracle Database supplied user accounts, except SYS and sample schemas are now schema only accounts, that is, these accounts are created without passwords. This prevents malicious users from logging into these accounts. You can assign passwords to these accounts whenever you want them to be authenticated. To find the status of an account, query the ACCOUNT_STATUS column of the DBA_USERS data dictionary view. If the account is schema only, then the status is NONE.

  • Automatic indexing

The automatic indexing feature automates the index management tasks, such as creating, rebuilding, and dropping indexes in an Oracle database based on changes in the application workload. This feature improves database performance by managing indexes automatically in an Oracle database.

  • Quarantine for SQL statements consuming excessive system resources

You can now configure quarantine for SQL statements terminated by the Resource Manager due to their excessive consumption of system resources, such as CPU and I/O. The quarantined SQL statements are not allowed to run again, thus protecting the database from performance degradation.

  • Memoptimized Rowstore – Fast Ingest

The fast ingest feature of the Memoptimized Rowstore optimizes the processing of high-frequency, single-row data inserts from applications, such as Internet of Things (IoT).

  • Hybrid partitioned tables

Oracle Database now supports a new type of table called hybrid partitioned table. A hybrid partitioned table is a partitioned table in which some partitions reside in the database and some partitions reside outside the database in external files, such as operating system files or Hadoop Distributed File System (HDFS) files.

  • New features in DBCA in the silent mode

The following are the new features in DBCA in the silent mode:

  • Create a PDB by cloning a remote PDB

You can use the createFromRemotePDB parameter of the DBCA command createPluggableDatabase to create a PDB by cloning a remote PDB.

  • Relocate a PDB to another CDB

You can use the DBCA command relocatePDB to relocate a PDB to another CDB.

  • Create a duplicate of an Oracle database

You can use the DBCA command createDuplicateDB to create a duplicate of an Oracle database.

  • New features related to SQL statements diagnosibility

The SQL diagnostics and repair tools, such as SQL Test Case Builder and SQL Repair Advisor have been enhanced to provide better diagnosis and repair capabilities for managing problematic SQL statements.

  • New SQL Repair Advisor function DBMS_SQLDIAG.SQL_DIAGNOSE_AND_REPAIR

The new SQL Repair Advisor function DBMS_SQLDIAG.SQL_DIAGNOSE_AND_REPAIR creates a diagnostic task, executes it, and accepts SQL patch recommendation for a SQL statement that is generating a critical error.

  • New options to control SQL Test Case Builder output

You can specify the new options – compress, diag_event, and problem_type – in the DBMS_SQLDIAG.EXPORT_SQL_TESTCASE procedure to control the output of SQL Test Case Builder.

  • New view V$SQL_TESTCASES

You can view the information about all the test cases generated by SQL Test Case Builder by querying the V$SQL_TESTCASES view.

  • New SQL script catpcat.sql for building the data dictionary

After creating a database using CREATE DATABASE statement, you can run catctl.pl with the new script catpcat.sql in place of running the scripts catalog.sql and catproc.sql for building the data dictionary. The script catpcat.sql runs the scripts catalog.sql and catproc.sql with parallel processes, thus improving the performance of building the data dictionary manually.

  • New ALTER SYSTEM statement clause – FLUSH PASSWORDFILE_METADATA_CACHE

If the database password file name or location has changed, then you must run the ALTER SYSTEM statement with the FLUSH PASSWORDFILE_METADATA_CACHE clause for the changes to take effect.

  • Oracle Database Resource Manager automatically enabled for Oracle Database In-Memory

The Resource Manager is automatically enabled when Oracle Database In-Memory is enabled by setting the INMEMORY_SIZE initialization parameter to a value greater than 0.

  • New view DBA_REGISTRY_BACKPORTS

The new view DBA_REGISTRY_BACKPORTS shows the bugs that have been fixed by the patches applied to the database. Only the bug fixes that have modified the data dictionary are displayed in this view.

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel: https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.