You are on page 1of 1

Quarantining of runaway SQL statements.

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

Built-in privilege analysis. A good DBA likes to give database users the least
amount of privileges needed for them to be able to perform their jobs. Oracle's
privilege analysis feature reports on privileges that users have been assigned but
haven't used; DBAs can use this information to create a stricter security policy
without taking away any privileges that users need. The feature was originally
released in 2014 as part of Oracle Database 12c, but it previously required the
extra-cost Oracle Database Vault software. The Enterprise Edition of Oracle 19c now
includes privilege analysis as a core feature.

Read/write Oracle Multitenant source databases. If you use the optional Oracle
Multitenant architecture technology, you can clone a pluggable database (PDB) to
create a duplicate one. Previously, if the clone was a snapshot copy that used
sparse files without much data in them, the source PDB needed to be set to read-
only and had to stay that way for the life of the clone. With Oracle 19c, the
source PDB can now support both reads and writes.

You might also like