Oracle Database 18c new features

 

Versions

18.1.0

18.2.0

18.3.0

General  Features in 18C

  • we can configure ORACLE_HOME in read-only mode.
  • we can CANCEL any database session SQL query (instead of terminating entire session).
  • we can see the SQL_ID for each SQL statement using, SET FEEDBACK ON SQL_ID option.
  • RESTART clause can be used in an ALTER SEQUENCE statement to reset a sequence number to a specific value.
  • Private temporary tables are stored in memory and each one is visible only to the session that created it.
  • Default location for Oracle Database password file is ORACLE_BASE directory (instead of ORACLE_HOME). This change supports read-only Oracle home
  • In DBCA silent mode, copy of a database template can be created using the -createTemplateFromTemplate command
  • Database can connect directly to Microsoft Active Directory and authenticate and authorize users.

 

Pluggable Databases

 

  • In DBCA silent mode, copy of a multitenant container database (CDB) can be created using the -createDuplicateDB command.
  • A copy of a PDB can be created using -createPluggableDatabase command option -createPDBFrom with the value of PDB.
  • Cloning a multitenant pluggable database (PDB) with Oracle Automatic Storage Management (Oracle ASM).

 

 

 

Automatic In Memory

 

  • In 18c, Oracle furthers development on In-Memory by introducing Automatic In-Memory (AIM).
  • AIM works by building a heat map of the in-memory enabled objects and makes room for those objects that are more frequently accessed.
  • AIM will only kick in when there is not enough space to add another object to the memory store.

 

Oracle Data Guard

 

  • A new initialization parameter, ADG_ACCOUNT_INFO_TRACKING, extends control of user account security against login attacks across a production database and all Oracle Active Data Guard standby databases.

 

  • Enhancements have been made to Data Guard broker support for upgrades performed using the DBMS_ROLLING PL/SQL package

 

  • Global temporary tables can be dynamically created on an Oracle ADG (Active Data Guard standby database).
  • In DBCA silent mode, standby database can be created from an existing database using -createDuplicateDB command option -createAsStandby.
  • A new view V$DATAGUARD_PROCESS (which replaces V$MANAGED_STANDBY) provides information that can be queried to verify that redo is being transmitted from the primary database and applied to the standby database.

 

  • Metadata for private/local temporary tables can be stored in memory, to be enabled on read-only databases, hence allowing reporting applications to run on Oracle Active Data Guard standby databases
  • Database nologging has been extended with two new modes: Standby Nologging for Load Performance and Standby Nologging for Data Availability. These modes provide better support for use in an Oracle Active Data Guard environment without significantly increasing the amount of redo generated.

 

 

RMAN

 

  • Block Change Tracking is supported with multi-instance redo apply.
  • A standby database can be refreshed over network using one RMAN command, RECOVER STANDBY DATABASE.
  • Using RMAN backup, we can recover a table also, that is, point in time recovery for single table.

 

Added New init parameters

 

  • ADG_ACCOUNT_INFO_TRACKING
  • MEMOPTIMIZE_POOL_SIZE (in SGA)
  • OPTIMIZER_IGNORE_HINTS (TRUE/FALSE)
  • OPTIMIZER_IGNORE_PARALLEL_HINTS (TRUE/FALSE)
  • PRIVATE_TEMP_TABLE_PREFIX (ORA$PTT_)
  • FORWARD_LISTENER

 

Added New views

 

  • V$DATAGUARD_PROCESS
Recent Posts

Start typing and press Enter to search