Asset ID:	1-79-2316967.1
Update Date:	2018-01-19
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 2316967.1 : Oracle Database Quarterly Full Stack Download Patch for SuperCluster Oct 2017 Known Issues

Applies to:

Oracle SuperCluster T5-8 Half Rack
Oracle SuperCluster M7 Hardware
Oracle SuperCluster M6-32 Hardware
SPARC SuperCluster T4-4
Oracle SuperCluster Specific Software
Information in this document applies to any platform.

Purpose

This document lists the known issues for Oracle Database Quarterly Full Stack Download Patch for SuperCluster October 2017. These known issues are in addition to the issues listed in the README for Quarterly Full Stack Download Patch for SuperCluster.

Details

Oracle Database Quarterly Full Stack Download Patch for SuperCluster (Oct 2017) Known Issues

Platform: Solaris.SPARC64

My Oracle Support

Released: , 2017

This document lists the known issues and other notes for Oracle Database Quarterly Full Stack Download Patch for SuperCluster (Oct 2017) Patches.

This document includes the following sections:

Section 1, "Notes and Known Issues"
Section 2, "Modification History"
Section 3, "Documentation Accessibility"

1 Notes and Known Issues

1.1 SuperCluster Pre-Installation Notes

The following are general SuperCluster QFSDP pre-installation notes:

1.1.1 - Installation of patch 22336131 (Jan 2016 Quarterly Full Stack Download Patch for Oracle SuperCluster), or a later QFSDP, is a prerequisite to installing this patch.

1.1.2 - Pay particular attention to the installation order prescribed in sub-section 4 ”Required Installation Order for QFSDP Components”, which is part of ”Section 2. Installing Quarterly Full Stack (Oct 2017 - 11.2, 12.2 and 12.1)”.

1.1.3 - Oracle recommends running Exachk before and after performing planned maintenance to review and cross reference collected data against supported version levels and recommended Oracle Exadata best practices. See My Oracle Support <Note 1070954.1> "Oracle Exadata Database Machine exachk or HealthCheck".

1.1.4 - Beginning with the Oct 2016 QFSDP, management of Solaris 11 IDRs is simplified by replacing IDRs with a supercluster-solaris Custom Incorporation (CI). This is a superset of the Solaris 'entire' incorporation, and includes the payloads from the recommended SuperCluster IDRs.

Additional critical fixes may be released after the QFSDP is first published. Please periodically check MOS <Note 2086278.1>, "SuperCluster Recommended Custom Incorporations, IDRs, and CVEs Addressed" for the latest recommended Custom Incorporation (if any) to install with this QFSDP to all Solaris 11 instances. A later Custom Incorporation can be downloaded and added to the SuperCluster's Solaris IPS repository and used by the QFSDP install_smu script in place of the Custom Incorporation included in the QFSDP itself. This saves having to first install the QFSDP and then update to a later recommended Custom
Incorporation afterwards.

Please refer to the SCMU README.solaris file for instructions on how to add a downloaded Custom Incorporation version to the Solaris IPS repository.

1.1.5 - Execution of the install_smu script included with the October QFSDP may fail to apply due to erroneous IPS dependency being declared on the '/solaris/library/libfuse' pkg in Custom Incorporations v1.6 & v1.7 for SRU 16 and v1.5 & v1.6 for SRU 19.

In addition the following bug was affecting the use of the Interdom utility on the first control domain of the first Physical Node of SuperCluster systems installed with build 2.0 (or later) and using Client Hostnames:
27239054 osc-interdom fails in get_control_uuid() and goes into maintenance state

When following the instructions in README.solaris for all Solaris instances; use the version of install_smu attached to this document as follows to address these issues:

# ./install_smu_2017.10-1 --aux-iso <path-to>/aux_2017.10-1.iso --check
# ./install_smu_2017.10-1 --aux-iso <path-to>/aux_2017.10-1.iso --install --accept

1.1.6 - The attached install_smu_2017.10-1 script also addresses an issue whereby the IPS exa-family package osc-svacomagent was not getting installed/upgraded correctly on all control domains.

1.1.7 - Where the instructions in the QFSDP READMEs contradict instructions in the individual patch READMEs of included components, the QFSDP READMEs have precedence in a SuperCluster context.

1.1.8 - Starting with the April 2017 QFSDP, two NM2 IB switch firmware versions will be included with the QFSDP: IB FW 2.1.8-1 supporting Exadata cell version 12.1.2.3.x only and IB FW 2.2.x-y for Exadata cell versions 12.2.1.1.x & 18.1.1.0.x. IB FW 2.1.8-1 is part of the SuperClusterMaintenanceUpdate and should be applied following the instructions in the README files under SCMU_2017.10, IB FW 2.2.x-y is part of the ExadataStorageServer 12.2.1.1.x & 18.1.1.0.x bundles and the Exadata procedures apply for updates to this FW version.

1.1.9 - Quorum Disk Manager functionality has been introduced with the Jan 2017 QFSDP. For further information, please refer to the SuperCluster documentation on http://docs.oracle.com/cd/E58626_01/index.html and search for "quorum".

1.1.10 - For information on the use of the osc-config-backup utility, including Known Issues, please see MOS <Note 1934129.1>

1.1.11 - If you are doing ZFSSA replication, or have shares off the ZFSSA to external hosts, using the management interface, plan on taking an outage for these services during QFSDP application. Before applying the ZFSSA patch take note of which storage head is servicing such operations and ensure it is the active head when your patching activities are over.

1.1.12 - ZFSSA Deferred Updates should be applied. This is particularly relevant for older SuperCluster T4, T5, M6 systems. See https://docs.oracle.com/cd/E56021_01/html/E55850/goxdn.html#scrolltoc. In particular, "Multiple Initiator Groups per LUN" and "Support for Large Block Sizes" are required for SuperCluster and must be applied. For other Deferred Updates, if the system is being upgraded from a version later than the Deferred Update, apply it as it's applicable to both the "from" and "to" versions and hence won't prevent rollback to the earlier version in the unlikely event that it is necessary. Where the Deferred Update is later than the version "from" which you are upgrading, you may wish to wait several weeks to ensure the version updated "to" is working well, before applying the Deferred Update in the unlikely case there's a need to revert to the version you upgraded "from".

1.1.13 - General SuperCluster documentation updates are now available from http://docs.oracle.com/en/engineered-systems/ and will no longer be included in the QFSDP.

1.1.14 - The Oct 2017 QFSDP includes Exa-family v2.4 of the SuperCluster Virtual Assistant via the osc-domcreate package. This version was first included in the July 2017 QFSDP. For further information on the latest v2.4 features, please refer to the SuperCluster I/O Domain Administartion Guide at https://docs.oracle.com/cd/E58626_01/html/E53172/index.html.

1.1.15 - Please review the issues detailed in the SuperCluster Critical Issues (MOS <Note 1452277.1>) prior to applying this QFSDP.

1.2 SuperCluster Known Issues for this release

The following are known issues for this QFSDP release:

1.2.1 - If the Oct 2016 QFSDP was ever installed on the system and the system configuration contains IO domains, please follow the steps outlined in MOS <Note 2223954.1> "Remediation steps for 25386898 for SuperClusters with the Oct 2016 QFSDP applied" before installing this QFSDP.

1.2.2 - Install picl in any Database non global zones using 'pkg install picl' (if not already installed) prior to running opatch to update the Database as opatch now uses jre-8 and installing picl improves performance.

1.2.3 - Solaris 11.3 SRU11 and later include LDoms 3.4.0.1 which by default sets verfied boot_policy=warn. Due to Bug 21463646, the warning messages such as the following may be seen in /var/adm/messages on boot:

Aug 3 09:02:47 etc7m7-exa2-n1 unix: [ID 711624 kern.notice] WARNING:
Signature verification of module /usr/kernel/drv/sparcv9/oracleoks failed
Aug 3 09:02:47 etc7m7-exa2-n1 unix: [ID 711624 kern.notice] WARNING:
Signature verification of module /usr/kernel/drv/sparcv9/oracleadvm failed
Aug 3 09:02:48 etc7m7-exa2-n1 unix: [ID 711624 kern.notice] WARNING:
Signature verification of module /usr/kernel/drv/sparcv9/oracleacfs failed

These warnings can be ignored. Do not set verified boot_policy=fail. If desired, the warning messages can be suppressed as follows, but it is not necessary to do so:

On the control domain:
ldm set-domain boot-policy=none <domain_name>
save the SP config
Then reboot the guest domain.

1.2.4 - Solaris 11.3 SRU11 and later includes LDoms 3.4.0.1 which by default sets verified boot_policy=warn. On Solaris 10 guest domains, "Unsupported bootblk image" messages may be seen (Bug 24825049). These can be ignored.

If desired, the messages can be suppressed as follows, but it is not necessary to do so:

On the control domain:
ldm set-domain boot-policy=none <S10_domain_name>
save the SP config
Then reboot the guest domain.

1.2.5 - The following messages which may be seen on the console can be ignored (bug 24923073):

<date> <system name> ip: net<number>: DL_BIND_REQ failed: DL_BADADDR
<date> <system name> ip: net<number>: DL_UNBIND_REQ failed: DL_OUTSTATE

1.2.6 - Oracle SuperCluster IO Domains may fail to boot after upgrading to Solaris 11.3 SRU 11 or later if the system has already been configured with more than 127 mac addresses per PF. Please refer to MOS <Note 2235476.1> for details and solution.

1.2.7 - Some customers temporarily modify passwords during maintenance windows, for example to enable Platinum Patching, and set them back when patching is complete. If this is the case, it is recommended to temporarily disable monitoring of the Exadata storage cells in the Oracle Engineered System Hardware Monitoring OESHM) utility or update the passwords. This is necessary as otherwise OESHM attempts to login to the storage cells will fail and, by default, the cells will lock out for 10 minutes after repeated failed login attempts. To temporarily disable storage cell monitoring in OESHM, login to https://<IP of master root domain>:8001, go to the Storage Server tab, select each storage cell in turn, and click the "Stop Monitoring" button and confirm. The cell Hardware Health and Configuration status will change to "In Maintenance". After reverting to the original passwords at the end of the maintenance window, re-enable monitoring of the cells by repeating the process, clicking the "Start Monitoring" button.

1.2.8 - When running OEDA, bug 24945782 "STEP 11 : INITIALIZE CLUSTER SOFTWARE HANGING INTERMITTENTLY" may occasionally be encountered. The workaround is simply to run the step again.

1.2.9 - Mitigation issues can occur with ZFSSA after updating ssctuner and osc-domcreate to the Jul 2017 QFSDP. For details and workaround, please see MOS <Note 2297850.1.>

1.2.10 - Due to bug 26678971 in some cases it may not be recommended to update IB switch 2.2.x-y firmware. Please refer to MOS <Note 2280595.1> "Infiniband switch running 2.2.x will not boot..." and <Note 2301054.1> "How to prevent an Infiniband Switch being rendered un-bootable..." for details and how to determine if a IB switch might be vulnerable to this issue.

1.2.11 - If running Solaris Cluster 3.3_u2, then it is you will need to download and install the "Oracle ZFS Storage Appliance Network File System Plug-in for Oracle Solaris Cluster, v1.0.5" with the Oct 2017 QFSDP. Version 1.0.5 of the ZFS SA NFS Plugin will also require Java 7 Update 151 (or later Java 7 Updates) to be installed and made the default system-wide Java version (i.e. via symlink to /usr/java). For more information on this issue and details of how to install the required components please follow the instructions in MOS <Note 2326715.1>.

1.2.12 - If upgrading IB switch version to 2.2.7-1, then please review MOS <Note 2202721.1> (Infiniband Gateway Switch Stays In Pre-boot Environment During Upgrade/Reboot) in advance.

1.2.13 - Bug 24429841 (Missing pkg:/system/picl as a dependency from runtime/java/jre-* pkgs) has been seen during OEDA deployment with OCT QFSDP. If you encounter this issue, the workaround is to manually install picl packages in DB Zones & DB IO Domains.

1.2.14 - Please also review the issue detailed in <Note 2085653.1>: 12.1 : Datapatch Fails with ERROR "KUP-04004,KUP-04017,KUP-04118,KUP-04095,ORA-29913"," fatal: libjli.so or libpicl.so.1: open failed"

2 Modification History

Table 1 lists the modification history for this document.

Table 1 Modification History

Date	Modification
Oct 2017	Released

3 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/us/corporate/accessibility/support/index.html if you are hearing impaired.

Oracle Database Quarterly Full Stack Download Patch for SuperCluster (Jul2017) Known Issues

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Attachments

This solution has no attachment