C Issues with Oracle Database Appliance X6-2S, X6-2M, and X6-2L

The following are known issues deploying, updating, and managing Oracle Database Appliance X6-2S, X6-2M, and X6-2L:

Cannot use the -local option to upgrade GI

Upgrade of Oracle Grid Infrastructure from 12.1.0.2 to 12.2.0.1 does not work, if you specify the -local option for upgrade.

A warning message is displayed, if you specify the -local option in the upgrade command when upgrading Oracle Grid Infrastructure from 12.1.0.2 to 12.2.0.1. Specifying the -local option in the upgrade command upgrades all components other than the grid infrastructure. 
WARNING: Current GI version is 12.1.0.2.170418  
INFO: Cannot upgrade grid with local patching.  
INFO: Do not specify -local to upgrade grid.  
Do you want to continue: [Y/N]?: N

Hardware Models

Oracle Database Appliance X6-2, X5-2, X4-2, X3-2, and V1 bare metal systems

Workaround

Do not use the -local option to upgrade Oracle Grid Infrastructure from 12.1.0.2 to 12.2.0.1.

This issue is tracked with Oracle bug 27937143.

Parent topic: Issues with Oracle Database Appliance X6-2S, X6-2M, and X6-2L

Unable to patch an empty Oracle Database 12.1 dbhome

Cannot patch an empty Oracle Database Home (dbhome) due to an issue with Oracle Database auto patch.

When attempting to patch an empty dbhome, an error message similar to the following appears: 
ERROR: 2017-12-19 18:48:02: Unable to apply db patch on the following Homes :  /u01/app/oracle/product/12.1.0.2/dbhome_name

The following is an example excerpt from the dbupdate log:

  OPATCHAUTO-68036: Topology empty. 
  OPATCHAUTO-68036: The topology was empty, unable to proceed. 
  OPATCHAUTO-68036: Check the log for more information. 
  OPatchAuto failed.
opatchauto failed with error code 42

Models

Oracle Database Appliance X7-2-HA, X7-2S, X7-2M, X6-2S, X6-2M, and X6-2L.

Workaround

The issue occurs when the dbhome does not have any databases. The workaround is to create a database for the dbhome before patching.

Parent topic: Issues with Oracle Database Appliance X6-2S, X6-2M, and X6-2L

Upgrading an SE database results in an error: Failed to run datapatch

After successfully upgrading an Oracle Database Standard Edition (SE) to 12.1.0.2, the following error appears in the log file: Failed to run datapatch

Datapatch is a tool that enables automation of post-patch SQL actions for RDBMS patches. The error impacts all Standard Edition databases upgrading to release 12.1.0.2.

The following is an excerpt of the log:

...
The following patches will be applied: 25397136
(DATABASE BUNDLE PATCH 12.1.0.2.170418) 

Installing patches...
Patch installation complete.  Total patches installed: 1

Validating logfiles...
Patch 26609798 apply: WITH ERRORS
  logfile:
/u01/app/oracle/cfgtoollogs/sqlpatch/26609798/21481992/26609798_apply_XT_2017S
ep28_06_58_16.log (errors)
    Error at line 1310: Warning: Package altered with compilation errors.

Please refer to MOS Note 1609718.1 and/or the invocation log
/u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_95130_2017_09_28_06_57_51/sqlpat
ch_invocation.log
for information on how to resolve the above errors.

SQL Patching tool complete on Thu Sep 28 06:58:51 2017
2017-09-28 06:58:51,867 ERROR [Running DataPatch] []
c.o.d.a.r.s.d.DbOperations:  run datapatch
2017-09-28 06:58:51,867 WARN [Running DataPatch] [] c.o.d.a.r.s.d.DbActions:
Failed to run datapatch.

Hardware Models

Oracle Database Appliance X7-2S, X7-2M, X7-2-HA, X6-2S, X6-2M, X6-2L

Workaround

See My Oracle Support (MOS) Note: Datapatch Known Issues, Doc ID 1609718.1.

Parent topic: Issues with Oracle Database Appliance X6-2S, X6-2M, and X6-2L

After replacing a disk, the disk is not added to Oracle ASM

When replacing or adding disks to Oracle Database Appliance X6-2S, X6-2M, or X6-2L, the disk is recognized as good, but it is not added to Oracle Automatic Storage Management (ASM).

Use the procedure to add or expand storage and wait the recommended time between tasks, but the new disks are not added to Oracle ASM.

Hardware Models

Oracle Database Appliance X6-2S, X6-2M, and X6-2L

Workaround

After expanding, adding, or replacing disks, restart oakd.

This issue is tracked with Oracle bug 26283996.

Parent topic: Issues with Oracle Database Appliance X6-2S, X6-2M, and X6-2L

Unable to create an Oracle ASM Database for Release 12.1

Known issues with Oracle Automatic Storage Management (Oracle ASM) are preventing the REDO diskgroup from mounting for Oracle Database Release 12.1.

Unable to create an Oracle ASM database lower than 12.1.0.2.170117 BP (12.1.2.10).

Hardware Models

Oracle Database Appliance X7-2-HA, X7-2S, X7-2M, X6-2S, X6-2M, and X6-2L

Workaround

There is not a workaround. If you have Oracle Database 11.2 or 12.1 that is using Oracle Automatic Storage Management (Oracle ASM) and you want to upgrade to a higher release of Oracle Database, then you must be on at least Oracle Database Appliance 12.1.2.12.0 and Database Home 12.1.0.2.170814.

This issue is tracked with Oracle bug 21626377 and 21780146. The issues are fixed in Oracle Database 12.1.0.2.170814.

Parent topic: Issues with Oracle Database Appliance X6-2S, X6-2M, and X6-2L