Following are the new features for Oracle Clusterware 12c Release 2 (12.2) and Oracle Automatic Storage Management 12c Release 2 (12.2):

The following feature is deprecated in this release, and may be desupported in another release. See Oracle Database Upgrade Guide for a complete list of deprecated features in this release.

• Deprecation of configToolAllCommands script

  The configToolAllCommands script runs in the response file mode to configure Oracle products after installation and uses a separate password response file. Starting with Oracle Database 12c Release 2 (12.2), the configToolAllCommands script is deprecated and is subject to desupport in a future release.

  To perform postinstallation configuration of Oracle products, you can now run the Oracle Database or Oracle Grid Infrastructure installer with the -executeConfigTools option. You can use the same response file created during installation to complete postinstallation configuration.

The following feature is desupported in this release. See Oracle Database Upgrade Guide for a complete list of features desupported in this release.

• Desupport of Direct File System Placement for Oracle Cluster Registry (OCR) and Voting Files

  Starting with Oracle Grid Infrastructure 12c Release 2 (12.2), the placement of Oracle Clusterware files: the Oracle Cluster Registry (OCR), and the Voting Files, directly on a shared file system is desupported in favor of having Oracle Clusterware files managed by Oracle Automatic Storage Management (Oracle ASM). You cannot place Oracle Clusterware files directly on a shared file system. If you need to use a supported shared file system, either a Network File System, or a shared cluster file system instead of native disk devices, then you must create Oracle ASM disks on supported network file systems that you plan to use for hosting Oracle Clusterware files before installing Oracle Grid Infrastructure. You can then use the Oracle ASM disks in an Oracle ASM disk group to manage Oracle Clusterware files.

  If your Oracle Database files are stored on a shared file system, then you can continue to use shared file system storage for database files, instead of moving them to Oracle ASM storage.

• Automated Root Privilege Delegation to Scripts During Installation

  You can continue to run scripts as root manually during installation, or you can enable OUI to run root scripts as needed during installation, using one of three methods: 1) providing the root password to the installer; 2) configuring Sudo access to the Oracle installation owner; 3) configuring PowerBroker access to the Oracle Installation owner.

• Cluster and Oracle RAC Diagnosability Tools Enhancements

  The Trace File Analyzer (TFA) Collector is installed automatically with Oracle Grid Infrastructure installation. The Trace File Analyzer Collector is a diagnostic collection utility to simplify diagnostic data collection on Oracle Grid Infrastructure and Oracle RAC systems.

  See Also:

  Oracle Clusterware Administration and Deployment Guide for information about using Trace File Analyzer Collector

• Automatic Installation of Grid Infrastructure Management Repository

  The Grid Infrastructure Management Repository is automatically installed with Oracle Grid Infrastructure 12c Release 1 (12.1.0.2).

• Oracle RAC Cache Fusion Accelerator

  Oracle RAC uses its Cache Fusion protocol and Global Cache Service (GCS) to provide fast, reliable, and efficient inter-instance data communication in an Oracle RAC cluster, so that the individual memory buffer caches of multiple instances can function as one global cache for the database. Using Cache Fusion provides a nearly linear scalability for most applications. This release includes accelerations to the Cache Fusion protocol that provide enhanced scalability for all applications.

• Automated Root Privilege Delegation to Scripts During Installation

  You can continue to run scripts as root manually during installation, or you can enable OUI to run root scripts as needed during installation, using one of three methods: 1) providing the root password to the installer; 2) configuring Sudo access to the Oracle installation owner; 3) configuring PowerBroker access to the Oracle Installation owner.

• Database Upgrade Automation Using DBUA

  There are three areas that are being enhanced for upgrade ease-of-use. First, in the pre-upgrade phase, the existing manual steps are eliminated and give more explicit advice or even generate a fix-up script to find issues identified in the pre-upgrade phase. Second, in the post-upgrade phase, there is a post-upgrade health check that indicates that the upgrade was successful. Finally, partner documents (such as SAP) and major customer upgrade documents are used to further identify manual steps that may be automated and generalized to a wider customer base.

  Automating the upgrade process provides major improvements in usability and ease-of-use. There is also better integration of database upgrade with Oracle Grid Infrastructure for a cluster and Oracle Enterprise Manager Cloud Control.

  See Oracle Database Upgrade Guide.

• DBCA Support for Multitenant Container Database and Pluggable Database Configurations

  Starting with Oracle Database 12c Release 1 (12.1), Oracle Database Configuration Assistant (DBCA) allows you to create either a multitenant container database (CDB) or a non-CDB. You can create the CDB with zero, one, or more pluggable databases (PDBs).

  You can also create a CDB with one PDB during the database installation.

  See Oracle Database Administrator's Guide.

• Enhancements to Cluster Health Monitor (CHM)

  CHM has been enhanced to be more efficient to support Oracle Flex Clusters implementations. These enhancements ensure that Oracle Flex Clusters run smoothly while minimizing the required resources to monitor the stack.

  See Oracle Clusterware Administration and Deployment Guide.

• Oracle Flex ASM Servers

  Oracle Flex ASM enables the Oracle ASM instance to run on a separate physical server from the database servers. Many Oracle ASM instances can be clustered to support a large number of database clients.

  Note that Oracle Flex ASM can apply to a collection of databases, each one a single instance but running in an Oracle Flex ASM Cluster.

  See Oracle Automatic Storage Management Administrator's Guide.

• Oracle Flex Clusters

  Oracle Flex Cluster is a new concept, which joins together a traditional closely coupled cluster with a modest node count with a large number of loosely coupled nodes. To support various configurations that can be established using this new concept, SRVCTL provides new commands and command options to ease the installation and configuration.

  See Oracle Clusterware Administration and Deployment Guide.

• IPv6 Support for Public Networks

  Oracle Clusterware 12c Release 1 (12.1) supports IPv6-based public IP and VIP addresses.

  IPv6-based IP addresses have become the latest standard for the information technology infrastructure in today's data centers. With this release, Oracle RAC and Oracle Grid Infrastructure support this standard. You can configure cluster nodes during installation with either IPv4 or IPv6 addresses on the same network. Database clients can connect to either IPv4 or IPv6 addresses. The Single Client Access Name (SCAN) listener automatically redirects client connects to the appropriate database listener for the IP protocol of the client request.

  See Oracle Grid Infrastructure Installation Guide.

• Multiprocess Multithreaded Oracle Database

  Starting with Oracle Database 12c, Oracle Database may use operating system threads to allow resource sharing and reduce resource consumption.

  See Oracle Database Concepts.

• Oracle Enterprise Manager Database Express 12c

  Oracle Database 12c introduces Oracle Enterprise Manager Database Express, a web management product built into Oracle Database without any need for special installation or management. Using Oracle Enterprise Manager Database Express, you can perform administrative tasks such as managing user security, and managing database memory and storage. You can also view performance and status information about your database.

  Note that starting with Oracle Database 12c, Oracle Enterprise Manager Database Control is deprecated.

  See Oracle Database 2 Day DBA.

• Policy-Based Cluster Management and Administration

  Oracle Grid Infrastructure allows running multiple applications in one cluster. Using a policy-based approach, the workload introduced by these applications can be allocated across the cluster using a policy. In addition, a policy set enables different policies to be applied to the cluster over time as required. Policy sets can be defined using a web-based interface or a command-line interface.

  Hosting various workloads in the same cluster helps to consolidate the workloads into a shared infrastructure that provides high availability and scalability. Using a centralized policy-based approach allows for dynamic resource reallocation and prioritization as the demand changes.

  See Oracle Clusterware Administration and Deployment Guide.

• Simplified Oracle Database Vault Installation

  Starting with Oracle Database 12c, Oracle Database Vault is installed by default as part of the Oracle Database installation. However, you can configure, enable, or disable Oracle Database Vault after the Oracle Database installation, either using DBCA, or by running SQL statements.

  See Oracle Database Vault Administrator's Guide.

• Support for Separation of Database Administration Duties

  Oracle Database 12c provides support for separation of administrative duties for Oracle Database by introducing task-specific and least-privileged administrative privileges that do not require the SYSDBA administrative privilege. These new privileges are: SYSBACKUP for backup and recovery, SYSDG for Oracle Data Guard, and SYSKM for encryption key management.

  See Oracle Database Security Guide.

• Unified Database Audit Configuration

  Starting with Oracle Database 12c, you can create named audit policies. An audit policy contains a set of audit options, which is stored in the database as an object. The advantage of creating a named audit policy is that it reduces the number of commands that are required to create a database audit policy, and it simplifies the implementation of an audit configuration for security and compliance with conditional auditing. This new audit policy framework is included with the database installation.

  See Oracle Database Security Guide.

The following features are deprecated in this release, and may be desupported in another release. See Oracle Database Upgrade Guide for a complete list of deprecated features in this release.

• Deprecation of single-letter SRVCTL command-line interface (CLI) options

  All SRVCTL commands have been enhanced to accept full-word options instead of the single-letter options. All new SRVCTL command options added in this release support full-word options, only, and do not have single-letter equivalents. The use of single-letter options with SRVCTL commands might be desupported in a future release.

• Change for Standalone Deinstallation Tool

  The deinstallation tool is now integrated with the database installation media.

• Deprecation of -cleanupOBase

  The -cleanupOBase flag of the deinstallation tool is deprecated in this release. There is no replacement for this flag.

• Oracle Enterprise Manager Database Control is replaced by Oracle Enterprise Manager Database Express.

• The deinstall standalone utility is replaced with a deinstall option using Oracle Universal Installer (OUI).

The following features are no longer supported by Oracle. See Oracle Database Upgrade Guide for a complete list of features desupported in this release.

• Oracle Enterprise Manager Database Control

• CLEANUP_ORACLE_BASE property removed and does not support an Oracle base removal during silent or response file mode deinstalls.