Exalogic Patch Set Update (PSU) Release 2.0.6.2.0 (Linux

Asset ID:	1-79-1959624.1
Update Date:	2015-05-21
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1959624.1 : Exalogic Patch Set Update (PSU) Release 2.0.6.2.0 (Linux - Virtual) for January 2015

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.0 to 2.0.6.1.2
Oracle Exalogic Elastic Cloud X2-2 Hardware - Version X2 to X2 [Release X2]
Exalogic Elastic Cloud X4-2 Hardware - Version X4 to X4 [Release X4]
Exalogic Elastic Cloud X3-2 Hardware - Version X3 to X3 [Release X3]
Linux x86-64
Oracle Virtual Server(x86-64)

Purpose

Oracle Exalogic is an integrated hardware and software system designed to provide a complete platform for a wide range of application types and widely varied workloads. It combines optimized Oracle Fusion Middleware software like WebLogic server, JRockit, Coherence with industry-standard Sun Server and Storage hardware and InfiniBand networking. The purpose of this document is to provide specific information around January 2015 Patch Set Update (PSU) for that system.

Scope

The target audience of this document are engineers and system administrators who plan to apply the Exalogic PSU.

This document provides the following:

README files that are included in the January 2015 PSU for convenience. These can be used for reference without having to download the PSU first
Known issues with the PSU - these provide a list of known issues along with workarounds/solutions, if available. Engineers and administrators planning to apply the PSU should ensure to review these before applying the PSU

This document will be kept up-to-date with updates to errata and known issues.

Details

Patch Download

Released: January 2015

Product Version: 2.0.6.2.0 (on X2-2/X3-2/X4-2) for Oracle Exalogic Elastic Cloud infrastructure

PATCH 19370511 - EXALOGIC VIRTUAL 2.0.6.2.0 (on X2-2/X3-2/X4-2) PATCH SET UPDATE (PSU) FOR JANUARY 2015

Patch Readme Documentation

Refer to the readme documentation attached 19370511-Virtual.zip to this Document on how to upgrade the Exalogic infrastructure:

Exalogic X2-2, X3-2 and X4-2 Systems: Upgrading to 2.0.6.2.0

The readme content structure layout of the 19370511-Virtual.zip:

The pre-requisite step to update Weblogic Server configuration properties for non-default passwords prior to upgrading Exalogic Control Services fails

Refer to "Appendix B: Patching Known Issues" section below for information on this pre-requisite step failure known issue.

Appendices

Appendix A: Fixed Bugs List

Please review Document ID : 1959625.1 - Exalogic Infrastructure January 2015 PSU - Fixed Bugs List.

Appendix B: Patching Known Issues

Upgrading NM2 Switch Firmware on full rack Exalogic systems or multi-rack Exa systems causing Network outage

Note:

The issue does not occur when Exalogic racks (one eighth, quarter, half ) are connected to Exadata racks.

Symptoms

Network outages on the InfiniBand fiber.

Cause

The NM2 Port ID space has increased four times from firmware version 2.0 to 2.1. Therefore, port ID collisions may occur if NM2 switches with firmware version 2.0 and 2.1 are run on the same fabric. This issue can cause network outages on the InfiniBand fiber.

Solution/Workaround

In order to prevent this issue, manipulation of the switch 'GWInstance' value may be required to ensure unique port IDs are generated by performing the following steps:

Log in to each NM2-GW switch as root and run:

# showgwconfig

Note the GWInstance "Running Value" on each of the switches.

1. Ensure that all the GWInstance values are even numbers
2. Ensure that GWInstance values when multiplied by 4, are greater than the largest GWInstance value.

To change a GWInstance value to 16, run:

[root@nm2gw-ib01 ~]# setgwinstance 16
Stopping Bridge Manager.. [ OK ]
Starting Bridge Manager. [ OK ]
root@nm2gw-ib01 ~]#

For example, if the GWInstance values of four NM2 switches are 10, 20, 30 & 40, it will be necessary to change the GWInstance value of 10 to 16.

Patching Exalogic Control Services fails due to incorrect version of PC/EC vservers in post-patch checks

Symptoms

Patching Exalogic Control Services fails due to incorrect version of PC/EC vservers in post-patch checks

Cause

Caused by the presence of backup files of certain property files, due to which the patching script skips the code to upgrade version in those property files.

Solution/Workaround

The workaround is to check for the presence of the following backup files and if present, rename them to something else and reapply the patch.

/opt/sun/n1gc/lib/XVM_AGENT.properties.<old_version>
/opt/sun/n1gc/lib/XVM_PROXY.properties.<old_version>
/opt/sun/n1gc/lib/XVM_SATELLITE.properties.<old_version> (present only in EC vserver, not in PCs)
/opt/sun/n1gc/lib/XVM_SERVER.properties.<old_version>
/opt/sun/n1gc/lib/XVM.properties.<old_version>
/n1gc-setup/.version.properties.<old_version>

where <old_version> is the version of EMOC before applying the patch . For e.g. - 12.1.4.2500

Patching Exalogic Compute nodes fail due to the presence of GHOST vulnerability patch

Symptoms

Patching of Exalogic Compute node fails with "error: Failed dependencies" due to the presence of GHOST vulnerability patch

Cause

Caused by the presence of newer verrsion of RPMs conflicting with the RPMs avaialble with the PSU.

http://192.x.x.x/shares/export/common//exalogic-lcdata/patches/Virtual/19370511/Infrastructure/BaseImageOEL5Supplementary/OVS_3.2.9/RPMs/Updated/libselinux-1.33.4-5.7.el5.i386.rpm
error: Failed dependencies:
glibc = 2.5-49.el5_5.4 is needed by nscd-2.5-49.el5_5.4.x86_64
Retrieving http://192.x.x.x/shares/export/common//exalogic-lcdata/patches/Virtual/19370511/Infrastructure/BaseImageOEL5Supplementary/OVS_3.2.9/RPMs/Updated/nscd-2.5-49.el5_5.4.x86_64.rpm
ERROR: Thu Apr 16 15:07:43 PDT 2015: Upgrading: http://192.x.x.x/shares/export/common//exalogic-lcdata/patches/Virtual/19370511/Infrastructure/BaseImageOEL5Supplementary/OVS_3.2.9/RPMs/Updated/nscd-2.5-49.el5_5.4.x86_64.rpm failed
INFO: Thu Apr 16 15:07:43 PDT 2015: remove services that launch post patching procedures

Solution/Workaround

1. Go to the following directory on the ZFS share

/exalogic-lcdata/patches/Virtual/19370511/Infrastructure/BaseImageOEL5/scripts

2. you will find a file called updated_rpms.txt, make a backup copy of that file, call it updated_rpms.txt.orig

3. edit that file and remove the line which has nscd rpm

4. rerun the patch using Exapatch

The pre-requisite step to update Weblogic Server configuration properties for non-default passwords prior to upgrading Exalogic Control Services fails

Symptoms

A pre-requisite step is included in section entitled "1.1 Prerequisites" to configure Weblogic Server prior to upgrading Exalogic Control Services to handle non-default passwords configured for admin and weblogic users. Running the command as documented results in an error as shown below:

[oracle@elctrl ~]$ /u01/app/oracle/ovm-manager-3/weblogic/wlconfig.sh weblogic <non-default-password>

-bash: /u01/app/oracle/ovm-manager-3/weblogic/wlconfig.sh: Permission denied

Invoking it using sh as follows runs into ClassNotFoundException, as shown in the sample below:

[oracle@elctrl ~]$ sh /u01/app/oracle/ovm-manager-3/weblogic/wlconfig.sh weblogic welcome1
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic.WLST
   at gnu.java.lang.MainThread.run(libgcj.so.7rh)
Caused by: java.lang.ClassNotFoundException: weblogic.WLST not found in gnu.gcj.runtime.SystemClassLoader{urls=[file:./], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
   at java.net.URLClassLoader.findClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at gnu.java.lang.MainThread.run(libgcj.so.7rh)
[oracle@elctrl ~]

Cause

A step to set the WLS environment variables is missing in the documentation. Also, the wlconfig.sh script is not executable; it needs to be invoked using "sh".

Solution/Workaround

Login as root to the Exalogic Control VServer
Switch to user oracle

[root@elctrl ~]# su - oracle
[oracle@elctrl ~]$
Run the following command to set the WLS environment variables:

[oracle@elctrl ~]$ cd /u01/app/oracle/Middleware/wlserver_10.3/server/bin
[oracle@elctrl bin]$ . ./setWLSEnv.sh

CLASSPATH=/u01/app/oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/app/oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/app/oracle/java/lib/tools.jar:/u01/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/u01/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/u01/app/oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/u01/app/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/u01/app/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/u01/app/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:

PATH=/u01/app/oracle/Middleware/wlserver_10.3/server/bin:/u01/app/oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/u01/app/oracle/java/jre/bin:/u01/app/oracle/java/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oracle/bin

Your environment has been set.

NOTE: Ensure that the above command is run with a dot and a space preceding ./setELSEnv.sh as shown.
Run the wlsconfig.sh command to configure the non-default password for the weblogic user

[oracle@elctrl bin]$ /u01/app/oracle/ovm-manager-3/weblogic
[oracle@elctrl weblogic]$ sh ./wlconfig.sh weblogic <non-default-password>

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_adf_domain'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Using existing user key file...
The username and password that were used for this WebLogic Server connection are stored in wlconfig.properties and wlkey.properties.
[oracle@elctrl weblogic]$
Configure Weblogic server with the non-default password for the admin user

[oracle@elctrl weblogic]$ sh ./wlconfig.sh admin <non-default-password>

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Connecting to t3://localhost:7001 with userid admin ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_adf_domain'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

Using existing user key file...
The username and password that were used for this WebLogic Server connection are stored in wlconfig.properties and wlkey.properties.
[oracle@elctrl weblogic]$

After above steps you may proceed with updating Exalogic Control Services.

ZFS Upgrade fails due to pre-patch check failure on Readzillas

For information on this known issue refer to Exalogic Infrastructure PSU Upgrade Known Issues <Note 1571367.1>, section "ZFS Upgrade fails while applying Jan 2015 PSU due to pre-patch check failure on Readzillas".

Appendix C: Errata

1. Migration of assets managed by Proxy Controllers

In the troubleshooting MOS note section "Problem: components are listed under both the ProxyControllers(PC)"

Original Text

In the Exalogic Control BUI, if it is observed that any of the component asset is listed under both the Proxy Controllers (PC), they need to be migrated to a single PC.

Updated Text

For a given switch (NM2-GW switches, NM2-36p switch), only one proxy controller needs to be managing it. If a particular switch appears to be managed by both PC1 and PC2, it must be migrated to one of the proxy controllers. It does not matter whether it is migrated to PC1 or PC2.

One or more compute nodes may appear in the Managed Assets list of both proxy controllers. For instance, el01cn01.example.com may appear as being managed by both PC1 and PC2. This is expected behavior; no migration is required for the compute nodes.

Other non-switch assets, such as ZFS storage heads and PDU may also appear in the Managed Assets list of both proxy controllers. Migration is not required for these assets prior to applying the April 2014 PSU; migration is required only for switches.

Login to EMOC BUI and navigate to "Administration" item in the left panel and find the entries for 'PC1' and 'PC2' vServers.

Select a Proxy Controller say, "PC1" in the left panel. In the center panel click on the "Managed Assets" tab and set the Asset Type Filter to "Network Switches" to get list of switches managed by the 'PC1' Proxy Controller.

Select the switch that you wish to migrate to the other ProxyController "PC2". Click on the icon that provides the option to "Migrate Assets". A confirmation dialog shows up, select 'Migrate' button to proceed.

Once the migration completes finishes, a notification pop-up appears at the bottom right corner of the EMOC BUI, confirming the successful migration.

References

<NOTE:1329262.1> - How to Perform a Healthcheck on Exalogic
<NOTE:1449226.1> - Exachk Health-Check Tool for Exalogic
<NOTE:1314535.1> - Exalogic Patch Set Updates (PSU) Master Note
<NOTE:1571367.1> - Exalogic Infrastructure PSU Upgrade - Known Issues

Attachments

This solution has no attachment