This document contains information that was not included in the platform-specific or product-specific documentation for this release. This document supplements Oracle Database Readme.

This document may be updated after it is released. You can check for updates to this document and view other Oracle documentation at

http://docs.oracle.com/en/database/database.html

This document contains the following topics:

• Unsupported Products

• Product Support

• Preinstallation Requirements for Release 12.2

• Installation, Configuration, and Upgrade Issues for Release 12.2

• Other Known Issues for Release 12.2

• Documentation Accessibility

In addition to the list of unavailable products or features in section, ”Features Not Available or Restricted in This Release of Oracle Database 12c Release 2 (12.2.0.1)” in Oracle Database Readme, the following products and features are not supported:

NTFS is not supported as a highly available single file system resource for this release. NTFS is still available to run on Oracle ADVM without Oracle Grid Infrastructure support.

ASMLIB is not supported.

Resilient File System, which is a new file system available on Windows 8 and Windows Server 2012, is not supported for this release.

The SNAPSHOT COPY Clause that instructs the database to clone a source pluggable database (PDB) is not supported on Microsoft Windows platform.

For this release, IPv6 networks are not supported for Oracle Real Application Clusters (Oracle RAC) private interconnects on Microsoft Windows platform.

The list of supported products or features for Oracle Database 12c Release 2 (12.2) are as follows:

Oracle Database 12c Release 2 (12.2) is certified on Microsoft Windows Server 2016 (Standard, Datacenter, and Essentials Editions), which includes support for the database client, server, and Oracle Real Application Clusters. The following database features require patches for Microsoft Windows Server 2016 certification:

• Oracle ASM Cluster File System (ACFS)

  • Oracle ACFS on Microsoft Windows Server 2016 must apply the second bundle patch or higher to Oracle Database 12c Release 2 (12.2).

• Oracle Server Management (SRVM)

  • For some network errors, SRVM may fail on Microsoft Windows Server 2016. This issue is fixed by applying the second bundle patch or higher of Oracle Database 12c Release 2 (12.2).

• Oracle Cluster Health Monitor (CHM)

  • CHM may fail intermittently on Microsoft Windows Server 2016 due to an unexpected termination of the Microsoft's Windows Management Instrumentation service. The issue is being actively investigated with Microsoft and will be addressed in a future bundle patch.

Database Smart Flash Cache is supported only on Oracle Solaris and Oracle Linux.

Oracle Automatic Storage Management Filter Driver (Oracle ASMFD) is supported only on Linux x86-64.

Share-based Instance Caging is supported only on Oracle Solaris and Oracle Linux.

Refer to the installation guides for the preinstallation requirements.

Review the following section for information about issues that affect Oracle Database installation, configuration, and upgrade:

• Oracle Grid Infrastructure Deinstallation Error

• Oracle Real Application Clusters Database Installation Error

• Deinstallation of Oracle Home Returns Errors

• DBCA Displays an ORA-02024 Error

• Oracle ADVM Volume Incompatibility with Oracle ASM and Windows Fast FAT File System

• Deinstallation Tool Stops Responding

• Error When Installing Oracle Database Examples Software on Oracle Database Client (32-bit)

• Database Configuration Assistant Error During an Oracle Real Application Clusters Installation

• Oracle Grid Infrastructure Upgrade Fails with an ASMCMD-8102 Error

• DBCA Fails to Create a Database

• PRVF-3919 Error When Installing Oracle Database on Microsoft Windows 10

When you deinstall Oracle Grid Infrastructure for a standalone server home that is configured after cloning Oracle home, the deinstallation may fail with the following error message:

Root script execution failed on one or more nodes

Workaround:

Before deinstalling, change HA_CONFIG=false to HA_CONFIG=true in Oracle_Restart_Home\crs\config\gridconfig.bat file.

This issue is tracked with Oracle bug 18749481.

Installing Oracle Real Application Clusters Database home with a gMSA account as the Oracle Home user, fails with the following error if the gMSA account name consists of more than 15 characters (including the domain name):

[INS-32101] Specified Oracle Home user does not exist

Workaround:

Use a gMSA account name (including the domain name) that consists of less than 15 characters.

This issue is tracked with Oracle bug 20918120.

The deinstallation operation fails to remove Oracle home and displays file in use errors as the services and processes running from Oracle home are not removed completely before Oracle home removal.

Workaround:

Manually remove the Oracle home.

This issue is tracked with Oracle bug 21325903.

When creating a database, Database Configuration Assistant (DBCA) may incorrectly display an ORA-02024 error.

Workaround:

Ignore the warning message and proceed with creating the database.

This issue is tracked with Oracle bug 21888659.

If you use Oracle ASM Dynamic Volume Manager (Oracle ADVM) volumes on cluster nodes which is configured with highly available Oracle Automatic Storage Management (Oracle ASM), a deadlock may occur between Oracle ASM or Oracle ADVM and Windows Fast FAT file system. The deadlock may suspend the acfsformat.exe, acfsmount.exe, or any other tool or application attempting to open an Oracle ADVM volume.

Workaround:

Configure Windows cluster nodes with legacy Oracle ASM if FAT or FAT32 file systems are in use.

This issue is tracked with Oracle bug 19269068.

If you run the deinstallation tool from the 12.2 installation media to remove the Oracle software from an existing 11.2.0.4 Oracle home, the deinstallation tool stops responding.

Workaround:

Ensure that you run the deinstallation tool from the same release to remove the Oracle software. You should not run the deinstallation tool from a later release to remove the Oracle software from an earlier release.

This issue is tracked with Oracle bug 23630511.

When installing Oracle Database Examples software on a Oracle Database Client home (32-bit), you may encounter the following error:

SEVERE: [FATAL] [INS-52001] Oracle Database Examples can only be installed into an existing Oracle Database Home of version 12.2.0.1.0.

Workaround:

Restart Oracle Database Examples installer with the -skipOHCOmpatibilityCheck switch and proceed with the installation.

This issue is tracked with Oracle bug 22579138.

During an Oracle Real Application Clusters (Oracle RAC) installation on Microsoft Windows Server 2012 R2, Database Configuration Assistant fails with an INS-20802 error. You may also encounter the following additional errors:

DIM-00019: create service error
O/S-Error: (OS 1305) The revision level is unknown.

Workaround:

Perform the following steps:

1. You must log out of your current session and log in as the same user.

2. Start Database Configuration Assistant from the Oracle_home\bin directory.

3. Proceed with the Oracle RAC database creation process.

This issue is tracked with Oracle bug 22571230.

During an Oracle Grid Infrastructure upgrade on Microsoft Windows Server 2012, the DLL path is set to an unexpected value, and the upgrade fails with an ASMCMD-8102 error.

Workaround:

Perform the following steps:

1. Manually upgrade Oracle Grid Infrastructure by running the gridSetup.bat -upgrade upgrade on all the nodes. Ensure that you exit the current installer session prior to running the gridSetup.bat.

2. After the gridSetup.bat -upgrade on all the nodes is complete, launch the installer to run the configuration tools using the following command:

   gridSetup.bat -executeConfigTools

   This issue is tracked with Oracle bug 22637209.

If the install username has a space when installing Oracle Database 12.2.0.1.0, Database Configuration Assistant (DBCA) fails to create the database.

Workaround:

To prevent the DBCA failure, ensure that the install username has no space during the Oracle Database installation.

Alternatively, you may add ORA_DBA group manually and then retry DBCA.

This issue is tracked with Oracle bug 25050422.

When installing Oracle Database 12c Release 2 (12.2) server or client on Microsoft Windows 10 (version 1703), you may encounter the following error:

Environment variable: "PATH" - This test checks whether the length of the environment variable "PATH" does not exceed the recommended length.

Details:  PRVF-3919 : Failed to retrieve value of environment variable "PATH" Cause:  Environment variable value could not be determined.

Action:  Check user equivalence and whether the user has administrative privileges on the node.

Workaround

Upgrade the operating system to Windows 10 Fall Creators Update (Version 1709) or later. Microsoft has fixed this bug:

https://blogs.msdn.microsoft.com/winsdk/2017/08/24/openservice-fails-on-a-service-marked-for-deletion-on-windows-10-version-1703-os-build-15063/

This issue is tracked with Oracle bug 26438878.

The following section contains information about issues related to Oracle Database 12c and associated products:

• ORA-03707 Error When Executing the Create Shard Command

• Download Microsoft Handle Utility When Using Oracle ACFS

• Replication Fails Due to Incorrect acfsutil Commands

When using the new 12.2 sharding feature, if you execute the create shard command from the gdsctl utility, then it shows the following ORA-03707 error:

ORA-03707: mandatory environment variable not set at destination: ORACLE_HOME

Workaround:

Perform the following steps:

1. After an agent installation, start a cmd session in which ORACLE_HOME, ORACLE_BASE, and ORACLE_SID environment variables are set.

2. Run the -net stop OracleSchedulerExecutionAgent command.

3. Run the reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleSchedulerExecutionAgent /v Environment /t REG_MULTI_SZ /d ORACLE_HOME=%ORACLE_HOME%\0ORACLE_BASE=%ORACLE_BASE%\0ORACLE_SID=%ORACLE_SID% command.

4. Next, run the - net start OracleSchedulerExecutionAgent command.

This issue is tracked with Oracle bug 22066161.

The Microsoft handle utility is required for proper operation of Oracle ACFS High Availability resources managed by Oracle Clusterware. Oracle Clusterware resources may not shut down properly if this command is not included.

Workaround:

Download the Microsoft Handle utility from:

http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx

After downloading, place the Handle utility in the BIN directory of your Grid home.

This issue is tracked with Oracle bug 9349433.

The commands to automate upgrading an existing replication relationship do not work correctly on Microsoft Windows x64 (64-bit) for 12c Release 2 (12.2.0.1).  The incorrect commands are acfsutil repl upgrade prepare, acfsutil repl upgrade standby, and acfsutil repl upgrade primary.

Workaround:

Users with an existing replication relationship which they want to continue using must terminate and re-initiate replication as described in the Oracle ACFS Command-Line Tools for Replication section in the Oracle Automatic Storage Management Administrator's Guide.

This issue is tracked with Oracle bug 25066932.

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.