Release Notes
12c Release 2 (12.2.2.0.0)
E38533-05
December 2014
Oracle Enterprise Manager Ops Center is Oracle's comprehensive system management solution for managing the physical and virtual operating systems, servers, and network and storage devices (or assets) in your data center. With Oracle Enterprise Manager Ops Center you can use the discovery and management features to add your data center assets to the list of managed assets in Oracle Enterprise Manager Ops Center. You can provision, update (patch), monitor, and manage the physical and virtually-managed assets in one or more of your data centers from a single console, regardless of where the asset is located.
Caution:
If you are upgrading an existing version of Oracle Enterprise Manager Ops Center, refer to the Oracle Enterprise Manager Ops Center Upgrade Guide before attempting to upgrade. All instructions must be followed as stated in the Upgrade document.Caution:
During installation, Java7u51 and Java 6_71 causes failures in some components. See the following bugs in the Known Issues section in this document for more information and workarounds:JDK Issue 8035283 — Breaks Oracle Enterprise Manager Ops Center In SPARC LDoms
JDK Issue 8030956 — Breaks Oracle Enterprise Manager Ops Center Proxy Controller Database
This document includes the following information about the Oracle Enterprise Manager Ops Center 12c Release 2 (12.2.2.0.0) software:
The following documents are related to installing or upgrading to Oracle Enterprise Manager Ops Center 12c Release 2 (12.2.2.0.0). You can download the documents from the Oracle Enterprise Manager Ops Center Documentation Library at http://docs.oracle.com/cd/E40871_01/index.htm.
Oracle Enterprise Manager Ops Center Release Notes (this document): This document provides links to other documentation for installing and uninstalling the software. It also includes a list of known issues related to installation and postinstallation configuration.
Oracle Enterprise Manager Ops Center Readme: This document provides instructions on installing the software.
Oracle Enterprise Manager Ops Center Installation Guide for Oracle Solaris Operating System: This document provides detailed instructions on performing a new installation of Oracle Enterprise Manager Ops Center on Oracle Solaris systems.
Oracle Enterprise Manager Ops Center Installation Guide for Linux Operating Systems: This document provides detailed instructions on performing a new installation of Oracle Enterprise Manager Ops Center on Oracle Linux or Red Hat Enterprise Linux systems.
Oracle Enterprise Manager Ops Center Upgrade Guide: This document provides instructions and prerequisites necessary to upgrade to Oracle Enterprise Manager Ops Center 12c Release 2 (12.2.2.0.0) and provides upgrade procedures for each environment.
Oracle Enterprise Manager Ops Center Administration Guide: This document provides instructions on administering, managing, and uninstalling Oracle Enterprise Manager Ops Center.
Uninstalling Oracle Enterprise Manager Ops Center: You can uninstall the components of Oracle Enterprise Manager Ops Center. See the Uninstalling and Unconfiguring chapter of the Oracle Enterprise Manager Ops Center Administration Guide for uninstallation procedures.
Oracle Enterprise Manager Ops Center 12c Release 2 (12.2.2.0.0) contains multiple new features and enhancements. See the Oracle Enterprise Manager Ops Center What's New In This Release document for an overview of the new features and enhancements.
You can download the product for installation from the Oracle Technology Network at http://www.oracle.com/technetwork/oem/ops-center/index.html.
Before installing the Oracle Enterprise Manager Ops Center software, you should plan for the installation and how you will use the software. See the Preparing Your Environment chapter in Oracle Enterprise Manager Ops Center Installation Guide for Oracle Solaris Operating System or the Preparing Your Environment chapter in Oracle Enterprise Manager Ops Center Installation Guide for Linux Operating Systems for prerequisite information.
OCDoctor is a tool utility that checks systems for installation prerequisites, troubleshoots issues, and tunes systems for the Oracle Enterprise Manager Ops Center installation. For more information, see the OCDoctor chapter in Oracle Enterprise Manager Ops Center Administration Guide. The guide is available in the Oracle Enterprise Manager Ops Center Documentation Library at http://docs.oracle.com/cd/E40871_01/index.htm.
This section explains the issues that you might encounter when installing, or upgrading to, Oracle Enterprise Manager Ops Center 12c Release 2 and the possible workarounds available.
Upgrades After Version 12.2.0.0.0 Not Visible In User Interface
JDK Issue 8030956 — Breaks Oracle Enterprise Manager Ops Center Proxy Controller Database
JDK Issue 8035283 — Breaks Oracle Enterprise Manager Ops Center In SPARC LDoms
OS Configuration Fails When a Network is Associated With Two Proxy Controllers
Unable to Detach Multiple Networks From a Guest in a Single Job
Automatic Failover Is Not Triggered For a Co-located Proxy Controller
Agent Does Not Check For Delayed Reconfiguration State Of Control Domain
Manually Migrate Report Service Data After Upgrade To Version 12.2.0.0.0
Oracle Solaris 11.1 Operating System Provisioning Fails on Some Systems Due To a Firmware Bug
Logical Domain Relationship Is Lost After Automatic Recovery
OS Provisioning Fails With DHCP Error After Upgrading to Version 12.2.0.0.0
Hardware Components Do Not Display Enhanced View After Upgrading to Version 12.2.0.0.0
Some Zones Do Not Display Correct Version After Upgrade to Version 12.2.0.0.0
No Server Pool in Target Selector of a Combined Plan After Upgrade
The "Number of Networks" Field Allows Alphanumeric Characters During the Edit Attributes Action
Newly Configured Network From Outside of Ops Center is Not Displayed in User Interface
Remote Proxy Controller Caching MSR Issue With Custom Publishers
ZFS Storage Appliance Discovery Requires Additional User Permissions
Virtualization Agent Controller Memory Requirements Have Increased
Migrate Branded Zone Wizard Does Not Have Value for Address Allocation
Zone Migration Check For Opaque Storage Checks Script Existence On Enterprise Controller
Remove SuperCluster Action Does Not Uninstall or Unconfigure Agent Controllers
Zone Migration Wizard Incorrectly Reports That No Zone Update Is Required
Oracle Solaris Suffers Performance Issues With High Number of LUNs
Interface in Routing Table is Wrong When Setting IPMP For Oracle Solaris 11 Systems
Association of Network to Oracle Solaris 11 Control Domain Fails With Contradictory Result
Oracle Solaris 10 Branded Zone Creation Fails: Global Zone Cannot Find OS Image
Discovery of M6 Server Can Fail if PDOM Does Not Respond Correctly
Adding Storage to an LDOM When NFS Base Disk is Not On Primary Leads to Job Error
Delete Oracle SuperCluster From Asset Tree Action Does Not Delete Assets
Newly Configured Network From Outside Ops Center Does Not Appear in the User Interface
ILOM Hostname Is Displayed Instead of OS Hostname For Exadata Cell Asset Name
The Power Status of ILOM Assets Sometimes Shows an Incorrect Status
Execute Operation Is Not Enabled For Groups of Assets if One Asset Is Offline
Unable to Use Console for Manually Created Zone in Agent-Managed Control Domain
Install Fails With Permission Error While Installing SUNWuces.pkg
Switch From Agent Managed to Agentless Fails With Unclear Message For Unprivileged User
Ops Center Installation Fails on Oracle Solaris 10 With Java 6 Patch 125137-75
Refresh Removes Network-Server Association For Guest With Untagged Network and VNET With PVID
Oracle VM Servers for SPARC Not Displayed After Control Domain Agent Provisioning Failure
NFS Metadata Library Cannot be Added Using IP Address in Overlapping Network Environment
Discovery of an Operating System Fails During the PopulateModel Task
Enterprise Controller Upgrade From Version 12.2.1 With JIDR2 to Version 12.2.2 Fails
In an environment using Oracle Enterprise Manager Ops Center version 12.2.0.0.0, no later upgrades are visible in the Ops Center Downloads wizard, preventing the download of upgrades through the user interface. You can still download upgrades outside of the user interface and apply them from the command line.
You can fix this issue by applying an IDR to your environment before upgrading. See MOS Note 1908726.1 for this procedure.
The issue is encountered in Java 6u71 which is included in Oracle Solaris 11.1 SRU 15.4 and higher. It causes various problems with the Proxy Controller and might corrupt the Oracle Enterprise Manager Ops Center configuration. This version of Java must not be used with the Proxy Controller. The issue is fixed in Java 6U75, which is included in Oracle Solaris 11.1.18.5, and in build 32 or later of Java 6U71, which is included in Oracle Solaris 11.1.17.5.
To find the version of Java 6 installed on the system, use the following command:
Oracle Solaris:
# /usr/jdk/instances/jdk1.6.0/bin/java -version
Linux:
/usr/java/jdk1.6*/bin/java -version
The following output displays the version 71, which has the bug.
java version "1.6.0_71" Java(TM) SE Runtime Environment (build 1.6.0_71-b12) Java HotSpot(TM) Server VM (build 20.71-b01, mixed mode)
If the Proxy Controller is started with Java 6u71, the following error is written to the cacao log file in /var/cacao/instances/scn-proxy/logs/cacao.
SEVERE: thr#11:"cacao-starter" Java version 1.6.0_71 is not supported due to bug https://bugs.openjdk.java.net/browse/JDK-8030956
Note:
(Applies to Oracle Solaris 11 only) Operating system updates also update the Java environment. Always check the Java version after you update the operating system. To downgrade the Java environment to an older version, see <Sun Alert>.This workaround is only specific to Oracle Solaris 11.1.15.4.0 or later.
Use a version of Java 6 that does not have the specified issue, for example, a version older than Java 6u71 or newer than Java 6u74. Java 6u71 Build 32 also includes a fix for the issue.
If you want the operating system of a Proxy Controller host to be upgraded to a version that includes Java 6u71, disable the Proxy Controller before applying the upgrade and rebooting to prevent the Proxy Controller from starting automatically when the system reboots.
Perform the following steps to downgrade Java:
Stop the Proxy Controller if it is running.
Oracle Solaris:
/opt/SUNWxvmoc/bin/proxyadm stop -w
Linux:
/opt/sun/xvmoc/bin/proxyadm stop -w
Unlock the Java 6 incorporation from the system constraints.
pkg change-facet facet.version-lock.consolidation/ub_javavm-6/ub_javavm-6-incorporation=false
Downgrade the packages using the pkg update command.
If the developer/java/jdk-6 is not installed:
pkg update \ consolidation/ub_javavm-6/ub_javavm-6-incorporation@1.6.0.65.0-0 \ runtime/java@1.6.0.65,5.11-0.175.1.12.0.5.0 \ runtime/java/jre-6@1.6.0.65,5.11-0.175.1.12.0.5.0 \ consolidation/ub_javavm/ub_javavm-incorporation@0.5.11-0.175.1.12.0.5.0
If the developer/java/jdk-6 is installed:
pkg update \ consolidation/ub_javavm-6/ub_javavm-6-incorporation@1.6.0.65.0-0 \ runtime/java@1.6.0.65,5.11-0.175.1.12.0.5.0 \ runtime/java/jre-6@1.6.0.65,5.11-0.175.1.12.0.5.0 \ developer/java/jdk-6@1.6.0.65,5.11-0.175.1.12.0.5.0 \ consolidation/ub_javavm/ub_javavm-incorporation@0.5.11-0.175.1.12.0.5.0
This issue exists in Java 7u51 which is included in Oracle Solaris 11.1.15.4 and higher. You might encounter this issue on OVM for SPARC guests if the cpu-arch is different than native. The result is that the Enterprise Controller, Proxy Controller, and Agent Controller do not work with Java 7u51 on OVM for SPARC guests. This issue is fixed in Java 7u55, which is included in Oracle Solaris 11.1.18.5.
To find the version of Java 7 installed on the system, use the following command:
# /usr/jdk/instances/jdk1.7.0/bin/java -version
This workaround does not apply for Oracle Solaris 10 or lower and Linux.
If using Oracle Solaris 11.1, use a lower version than SRU 15.4.
Use an earlier version of Java, such as Java 7u45 or install an older or fixed version of Java 7 using the procedure described at http://www.oracle.com/technetwork/articles/servers-storage-admin/sol-howto-update-only-java-1948328.html.
Do not upgrade an existing Oracle Solaris 11.1 system running Oracle Enterprise Manager Ops Center to Oracle Solaris 11.1.15.4 or higher that is running in an Oracle VM Server for SPARC logical domain without native CPU-type, unless it contains a version of Java with a fix for this issue.
If a system with Oracle VM Server for SPARC logical domains and the Oracle Enterprise Manager Ops Center agent is upgraded to use Java 7u51, then change the agent's Java configuration.
Perform the following steps:
Stop the agent.
/opt/SUNWxvmoc/bin/agentadm stop
Change the java-flags to include the option -XX:-UseCBCond.
cacaoadm set-param `cacaoadm get-param java-flags -i scn-agent | sed 's/=/=-XX:-UseCBCond /'` -i scn-agent
Start the agent.
/opt/SUNWxvmoc/bin/agentadm start
Beginning in version 12.2.0.0.0, the Find Assets action is disabled by default, because in large environments it can cause the Enterprise Controller to shut down.
You can use the following procedure to enable the Find Assets action.
In the Navigation pane, click Administration, then click Enterprise Controller.
In the center pane, select the Configuration tab.
In the Configuration Management section, select Discovery from the Subsystem drop-down list.
Set the value of the service-tags-discovery-enabled property file to true.
Probe-based IPMP groups configured during OS provisioning do not operate after a reboot in the following cases:
Provisioning Oracle Solaris 10 on a control domain fails with a timeout after the task that reboots the operating system.
An Oracle Solaris 10 logical domain or OS asset is provisioned and operates successfully until a reboot.
This condition is caused by the way the IPMP group was created; the network interfaces were not configured to be available by default and are not restored after the reboot.
Re-define the network interfaces to run after a reboot. To ensure new probe-based IPMP groups are configured properly, use version 4.29 or later of the OCDoctor utility to update the script that creates IPMP groups.
If you have already created probe-based IPMP groups, edit the network interfaces in the IPMP group of the Oracle Solaris 10 OS asset.
Perform the following steps:
Log in to the Oracle Solaris 10 OS.
Locate the /etc/hostname.vnetID file and edit it.
Locate the definition of the hostname:
192.168.223.201 netmask + broadcast + group ipmp1 addif 192.168.223.203 deprecated -failover netmask + broadcast + up
Edit the definition to add the up keyword to the position after the IPMP group name. For example:
192.168.223.201 netmask + broadcast + group ipmp1 up addif 192.168.223.203 deprecated -failover netmask + broadcast + up
Repeat the same steps for the other network interfaces in the IPMP group, vnetID
Save and close.
For the OVM for SPARC Control Domain, deploy the agent on the control domain's operating system using the Add Asset action.
You will not be able to move the storage of a non-global zone if the SUNWocmu package is installed on a global zone. Likewise, if this package is installed on a global zone where you try to migrate or recover your non-global zone, the job fails in the ZoneAttach task with the following message:
These packages installed on this system were not installed on the source system:
SUNWocmu (11.11,REV=2012.11.13.16.42)
SUNWperl-xml-parser (2.34,REV=10.0.3.2004.12.15.14.13)
Delete the SUNWocmu package from:
The global zone that is hosting the non-global zone if you try to move its storage
The global zone where the non-global zone will be migrated before starting a migration.
Any global zone in the server pool if the non-global zone is used for automatic recovery.
If a move storage, migration, or automatic recovery job fails with the previous message before applying this workaround, then perform the following:
Delete the SUNWocmu package from the global zones.
Reattach the SUNWocmu package to the global zone that is hosting the non-global zone.
zoneadm -z <zone name> attach
Using the Oracle Enterprise Manager Ops Center User Interface, refresh the package on the global zone that is hosting it.
When you try to stop the OS Provisioning job while the Monitor OS Installation task is running, the job takes long time to stop.
If the OSP and OSC target IP address are the same, it takes up to a maximum of 2 hours
If the OSP and OSC target IP address are different, it takes up to a maximum of 10 minutes.
Invoke the stop job on the subsequent Verify Agent Install task.
Note:
This issue is fixed in version 12.2.1.0.0.When the same network is associated with two Proxy Controllers, the OS configuration task of an OS provisioning job fails when all tasks are not targeted to the same Proxy Controller.
Temporarily disable the boot network for one of the proxy controllers, so that no jobs targeted at that network will use that Proxy Controller.
Perform the following to disable the network:
In the Navigation pane, click Administration.
Select the Proxy Controller.
In the Actions pane, click Enable/Disable Networks and disable the boot network.
Re-enable the network once the job starts to make the network available for discovery and for inter-Proxy Controller asset migration.
The system runs out of memory sometimes due to ZFS Adaptive Replacement Cache (ARC) and the Oracle Enterprise Manager Ops Center's self monitoring times out and restarts the Enterprise Controller or Proxy Controller cacao instances.
Tune the ZFS ARC on the Oracle Solaris Enterprise Controller and Proxy Controllers to make sure enough memory is available for them to run reliably.
Set the ZFS maximum ARC value to no more than 1 GB if the system has less than 10 GB of physical memory, or 10 GB less than the system memory value if the system has more than 10 GB of physical memory.
To set the ZFS max ARC value, edit the /etc/system file and add the following line:
set zfs:zfs_arc_max=<max_arc_size_in_bytes>
Reboot the system after making this change.
When you have a guest with multiple network connections, you cannot detach all connections in a single job. When you run a job to remove multiple networks, the first connection is removed and the job fails with an error message that indicates Oracle Enterprise Manager Ops Center cannot detach the network because it cannot find a vNIC with the MAC address.
Run a separate job for each network to remove it from the guest. For example, when you have two networks attached to a guest, create a job to remove the first network from the guest and then start a new job to remove the second network.
The OS profiles based on JET templates have a subtype of JET-template instead of the required subtype of Logical Domain. As a result, these OS profiles cannot be used to provision a logical domain.
Only failure of remote Proxy Controllers triggers a failover of assets to a standby Proxy Controller. Because the Enterprise Controller's Operating System is running, it does not treat loss of the co-located Proxy Controller as a fatal error requiring recovery.
Note:
This issue is fixed in version 12.2.2.0.0.Changes to the configuration of logical domains are not permitted when the Logical Domain Manager is in Delayed Configuration state. Oracle Enterprise Manager Ops Center does not check for this state and allows operations to be attempted, resulting in failure.
See Logical Domains Administration Guide for more information.
When you use a local database for the Enterprise Controller, an SMF service, svc:/application/scn/db:remote, is configured on the Oracle Solaris operating system. This service is automatically enabled if a remote database is configured. When you try to manually enable the service, it causes conflicting SMF service state transitions, requiring a reboot.
The format of database tables used by historical data service is improved in this release to save space in the database. The upgrade process converts the database to the new format automatically. However, if the report service tables are very large, a warning message is displayed on the command and in the /var/opt/sun/xvm/update-saved-state/update_EC_minor_bundle_12.2.0.<build number>/updatelog.txt file. If you get the warning, you must update the database manually.
Perform the following steps to manually migrate the Report Service Data:
Start the Oracle Enterprise Manager Ops Center CLI and connect to the Enterprise Controller.
/opt/SUNWoccli/bin/oc xvmSh > connect
Use the report service CLI.
localhost > reports
List the existing partitions.
localhost/reports > list
For example:
localhost/reports > list Daily partition 20140122 (with 0/0/0/0/0 values) state is : 1 Daily partition 20140204 (with 1200/0/0/0/0 values) state is : 0 Daily partition 20140205 (with 605/0/0/0/0 values) state is : 0 Daily partition 20140206 (with 6205/0/0/0/0 values) state is : 0 Daily partition 20140207 (with 0/0/0/0/0 values) state is : 0 Older samples (outside partitions) : 0/16416/1368/684/684
Run the check command to display the partitions that have to be converted.
localhost/reports > check
For example:
localhost/reports > check @ Partition 20140122 : no conversion is needed @ Partition 20140204 : a conversion is needed for 1200 old samples @ Partition 20140205 : no conversion is needed @ Partition 20140206 : no conversion is needed @ Partition 20140207 : no conversion is needed
For each partition that requires a conversion, run the following command:
localhost/reports > convert -p <partition name>
For example:
localhost/reports > convert -p 20140204 This operation may take time : please be patient and wait... Conversion of old samples : starting ... 1200 old format samples converted for partition 20140204 in table rm_resource_daily_trend in 261 ms 0 old format samples converted for partition 20140204 in table rm_resource_1hour_trend in 11 ms 0 old format samples converted for partition 20140204 in table rm_resource_12hour_trend in 3 ms 0 old format samples converted for partition 20140204 in table rm_resource_24hour_trend in 1 ms 0 old format samples converted for partition 20140204 in table rm_resource_24hour_stats in 1 ms Old format sample conversion for partition 20140204 : done in 318 ms with 1200 samples : perf = 0 samples / seconds
Verify that all the partitions have been converted.
localhost/reports > check
For example:
localhost/reports > check Partition 20140122 : no conversion is needed Partition 20140204 : no conversion is needed Partition 20140205 : no conversion is needed Partition 20140206 : no conversion is needed Partition 20140207 : no conversion is needed All samples have been converted : please run the convert command with no argument to finish the migration
Finalize the migration using the convert command.
localhost/reports > convert
For example:
localhost/reports > convert This operation may take time : please be patient and wait... Conversion of old samples : starting ... 0 old format samples converted for partition null in table rm_resource_daily_trend in 5 ms Suppressing useless column and index for table rm_resource_daily_trend 16416 old format samples converted for partition null in table rm_resource_1hour_trend in 3674 ms Suppressing useless column and index for table rm_resource_1hour_trend 1368 old format samples converted for partition null in table rm_resource_12hour_trend in 315 ms Suppressing useless column and index for table rm_resource_12hour_trend 684 old format samples converted for partition null in table rm_resource_24hour_trend in 183 ms Suppressing useless column and index for table rm_resource_24hour_trend 684 old format samples converted for partition null in table rm_resource_24hour_stats in 106 ms Suppressing useless column and index for table rm_resource_24hour_stats Old format sample conversion : done in 5139 ms with 19152 samples : perf = 3830 samples / seconds
Verify that the migration has completed.
localhost/reports > check
For example:
localhost/reports > check Table rm_resource_daily_trend is already at new format Table rm_resource_1hour_trend is already at new format Table rm_resource_12hour_trend is already at new format Table rm_resource_24hour_trend is already at new format Table rm_resource_24hour_stats is already at new format All conversions have been performed : migration is DONE !
Exit the CLI.
localhost/reports > exit
The Report Service Data is now migrated.
Note:
This issue is fixed in version 12.2.1.0.0.Provisioning job for Oracle Solaris 11 on Oracle SPARC T5-series, Oracle SPARC M5, and Oracle SPARC M6 servers, fails at the Reset to Factory Default task if the system is powered on with the operating system running. In addition, some Oracle Solaris 10 ISC/DHCP operating system provisioning jobs fail at the Netboot step with no further workaround. A bug in the firmware versions 9.1.1 and 9.1.1.a on all Oracle SPARC T5-series, Oracle SPARC M5, and Oracle SPARC M6 servers causes this issue.
Upgrade or downgrade the firmware to avoid using version 9.1.1. If you encounter the error, rerun the job or manually power off the system.
When a Logical Domain reboots after some of its guests have been automatically recovered to another system, some of the Oracle Enterprise Manager Ops Center information about guests running on the system might be lost, thus missing from the user interface. This issue is encountered in Oracle Solaris 11 only.
Automatic recovery of an LDom guest results in loss of information, such as the current name and associations with other assets. This issue is encountered only on systems running older versions of Oracle Solaris. The issue is resolved in Oracle Solaris 11.1.16.
File a service request to recover this data.
When you upgrade large environments to version 12.2.0.0.0, too many Auto Service Request (ASR) jobs might be created.
Perform the following steps before beginning the upgrade:
Click Administration in the Navigation pane, then select the Enterprise Controller.
Click Disable ASR in the Actions pane.
Upgrade your environment.
Click Administration in the Navigation pane, then select the Enterprise Controller.
In the Actions pane, click Enable ASR.
The installation does not check for the required packages such as ksh and zlib.i686 on Oracle Linux.
Install the ksh and zlib.i686 RPM before or after the installation.
After upgrading to version 12.2.0.0.0, OS provisioning fails with an error message indicating that DHCP is not initialized. This issue is encountered only on Oracle Solaris 11 Proxy Controllers.
Disable DHCP on the networks and re-enable them. In some cases, the Configure DHCP button is disabled because the DHCP configuration is marked as in use in the database. Run the following commands on the Enterprise Controller host and then re-run the OS Provisioning job.
/opt/SUNWxvmoc/bin/ecadm sqlplus
SQL>delete from as_dhcp_config;
SQL>exit
When reusing an existing Oracle Solaris 11 Package Repository source during configuration of Oracle Enterprise Manager Ops Center, the Oracle Solaris 11 source repository step fails.
In the Storage Libraries section, when you click Initialize Oracle Solaris 11 Software Update Library and enter the URL, an error message is displayed and the job fails.
Perform the following steps:
In the user interface, delete the current Oracle Solaris 11 Library.
On the system command line, create a new library directory for the existing Oracle Solaris 11 Library contents.
Go to the existing library directory, then change to the Ops Center-created directory named for your UUID.
Copy the <Library>/<UUID>/data/pkg5.repository and <Library>/<UUID>/data/publisher files to the new library directory.
On the user interface, click Initialize Oracle Solaris 11 Software Update Library.Enter the URL of the new library location.
After upgrading to version 12.2.0.0.0, some hardware component names differ from those seen in a new installation. Also, some PCI devices are not displayed in the upgraded Enterprise Controller.
Delete the access point, then rediscover the ILOM.
Perform the following:
In the Navigation pane, under All Assets, select the asset.
In the center pane, click the Configuration tab.
Click the Delete Access Point icon in the Access Points section.
Re-discover the ILom of each hardware asset.
In the Enterprise Controller configuration wizard, provide a source repository for the Oracle Solaris 11 Package Repository during initial configuration. Otherwise, when you click Next, the wizard page for providing the source repository details hangs and the libraries are left in the following condition:
The Oracle Solaris 11 Software library is not configured.
The Linux/Oracle Solaris 8-10 Software Update Library is not fully configured.
Perform the following:
Reload the browser.
Log in to Oracle Enterprise Manager Ops Center.
Complete the library configuration using the Libraries section of the user interface.
After upgrading the Enterprise Controller, Proxy Controllers, and Agent Controllers, some non-global zones are not displayed as upgraded.
Retry the Agent Controller upgrade on the non-global zone.
Restart the Agent Controller on the non-global zone. Change to the directory (/opt/SUNWxvmoc/bin) containing the agentadm command.
./agentadm stop
./agentadm start
After upgrading to the latest version, server pool assets are not visible and thus cannot be selected when a combined Logical domain + OS provisioning plan is chosen.
A workaround is to edit the deployment plan:
Select the deployment plan.
Click Edit Deployment Plan in the actions pane.
Click Save without making any changes.
The Server Pools are now shown when applying the deployment plan.
On a SPARC SuperCluster T4-4 (Multirack), the "Number of Networks" field allows alphanumeric characters during the Edit Attribute action and does not throw any error upon clicking Save.
The change is reflected in the Details tab after clicking the Save icon.
Also, no Edit Attribute job is initiated.
After installing the Enterprise Controller, a new network created and configured on the OS level outside of Ops Center does not appear in the user interface. The OS Refresh action and Network Refresh action do not show the new network. Only an automatic refresh, with a long time interval, causes the network to appear.
Restart the Enterprise Controller.
When Oracle Enterprise Manager Ops Center is deployed in a remote Proxy Controller configuration, the mod info of the Proxy Controller caches data. The IPS clients use this as a reverse proxy for the IPS data, but the catalog.attrs file is dynamic and can change, and therefore should not be cached.
It is unlikely that users will encounter this issue since the cache times out.
Add your publishers to the following file: /var/opt/sun/xvm/uce/etc.opt/server/uce_server/proxy.conf
Search for CacheDisable and add your publisher by adding a line using the following format:
CacheDisable /IPS/<publisher name>/catalog
Stop and restart the Proxy Controller using the following commands:
/opt/SUNWxvmoc/bin/proxyadm stop -w;
/opt/SUNWxvmoc/bin/proxyadm start -w;
Note:
This issue is fixed in version 12.2.2.0.0.The Server Pool options allow you to create instances when all members have no connectivity to the private resources, such as instances with a private network that is not connected to any PC.
On Oracle Supercluster systems, you should not create Server Pools using members from 2 or more Supercluster systems (racks) and attach private (internal) networks to such systems. You can create a Server Pool using members from 2 or more Supercluster systems and attach public-only networks. It is safe to attach a private network to a Server Pool if the Server Pool consists of members belonging to the same Supercluster system (rack).
If you are using Ethernet, you should only attach private networks to Server Pools only if you are sure that all members physically have access to these private networks. Otherwise, the Server Pool will have the issues described above.
The Enterprise Controller, Proxy Controller, or Agent fails to start after an upgrade of the Common agent container (Cacao) on Solaris 10 (SUNWcacaort) or S11.1 (library/cacao) and the corresponding SMF service does not exist or is not online.
You can check the SMF services by running the following command:
svcs -l svc:/application/management/common-agent-container-1
The Enterprise Controller, Proxy Controller, and Agent SMF service names are:
svc:/application/management/common-agent-container-1:oem-ec
svc:/application/management/common-agent-container-1:scn-proxy
svc:/application/management/common-agent-container-1:scn-agent
Stop the Enterprise Controller and co-located Proxy Controller using the ecadm and proxyadm commands.
/opt/SUNWxvmoc/bin/ecadm stop -w
/opt/SUNWxvmoc/bin/proxyadm stop -w
Verify that no Cacao process is running.
ps -ef|grep cacao_launcher
Run: 'cacaoadm prepare-uninstall' to clean up any SMF services and mark cacao as not configured.
/usr/sbin/cacaoadm prepare-uninstall
Restart Ops Center or resume installing Ops Center.
In the Discover a Sun ZFS Storage Appliance and Configure Storage Libraries How-To, the "Create an Account for Oracle Enterprise Manager Ops Center" procedure creates an account on the Sun ZFS Storage Appliance for the use of Oracle Enterprise Manager Ops Center. If this account is used to discover the appliance, the discovery will fail as the account does not have the correct permissions.
Edit the Basic Administrator to add the required permissions.
In the storage appliance user interface, click Configure, then click Users.
Click Edit Entry for the Basic Administrator role.
From the Scope drop-down list, select Workflow and then select the modify and read check boxes.
Click Add, then click Apply.
From an Enterprise Controller installed on Oracle Linux 6.4, terminal opening fails through the UI to all Oracle Solaris 10 and 11 Agents. The following error is shown:
"Error - Connection reset"
SSH connection to the target servers is working.
Remove the following file on the Enterprise Controller:
/opt/sun/xvm/ajaxterm/connectionTest.py
Restart the Enterprise Controller.
/opt/sun/xvmoc/bin/ecadm stop -w
/opt/sun/xvmoc/bin/ecadm start -w
To prevent Agent configuration problems, the amount of memory used by Virtualization Agent Controllers has been increased to 1024 MB of memory in version 12.2.1.0.0.
When trying to migrate a branded zone the Ops Center UI does not have a value for "Address Allocation Method" in the "Specify Network Interfaces" screen.
Deselect the network in the migration wizard.
Add the network again.
Click next.
If a zone has an opaque storage that is not of LOFS type (for example, a filesystem added in zonecfg with type "zfs") Ops Center will check if the user provides a script under "/var/opt/sun/oc/public/guest-operations" to manage these opaque filesystems.
This check is correct in the job itself when using it but in the migration wizard it's targeted on the satellite and not on the global zone. As a result the migration wizard will return : "Guest is not in migratable state (72078)".
Create the following empty file on the Enterprise Controller:
/var/opt/sun/oc/public/guest-operations
Agents installed on Supercluster's servers are not uninstalled/unregistered from the PC when "Remove Super Cluster" action triggered. After Supercluster removal these assets are not present in the All Assets tree due to limitation that assets tagged with Engineered system are visible only under the related Engineered system tree.
Go to Servers view, choose the desired asset, and delete it.
Note:
This issue is fixed in version 12.2.2.0.0.OCCLI will crash on Oracle Solaris 11 Update 1 SRU 19.5 with JDK8 installed.
On a machine where both JDK 7 and JDK 8 are installed, the CLI uses JDK8 by default. Edit the JAVA_HOME variable to force the use of JDK 7:
JAVA_HOME=<path to JDK7> /opt/SUNWoccli/bin/oc
For example:
JAVA_HOME=/usr/jdk/jdk1.7.0_51 /opt/SUNWoccli/bin/oc
This issue appears in an environment with two Oracle Solaris 10 global zones, which differ only by one patch which requires an update of a zone when migrated between them.
This patch is not installed on the target zone, so it must be backed out. However, the wizard does not present this, but reports that nothing is required which will result in a failed migration.
When using MPxIO in Oracle Solaris 11 with 1600 or more LUNs, Ops Center's xvmluinfo utility suffers performance problems due to an Oracle Solaris issue.
When provisioning an IPMP group on a LDOM guest, the default route shows net0 as the interface for the default destination, when it should show ipmp1.
One workaround is to reboot the system.
Another workaround is to run the following commands to correct the route:
route -p delete default <default gateway> -ifp net0
route -p add default <default gateway> -ifp ipmp1
Note:
This issue is fixed in version 12.2.2.The Create Server Pool wizard hangs at the Associate Networks step if all networks (IPoIB-default, IPoIB-storage, eth-admin and external-mgmt) are selected.
Do not select the IB networks at the Associate Networks step and create the Server Pool without them, then attach the IB networks to the Server Pool.
In an environment with two Control Domains and a network attached to both CDOMs using the statically allocated IPs, attaching the network again using NICs that are not interconnected and with the default IP assignment fails with a contradictory error message:
- plumbing on cdom1 was reported as successful
- plumbing on cdom2 was reported as successful
- job failed complaining that one or more Virtualization Hosts are not properly plumbed on given network.
The CDOMs are left in an intermediate state - a new VNIC is created, but no IP is assigned.
Rerun the job, but provide IP addresses instead of using system assigned IP addresses.
If you have already encountered this issue, use the following procedure to clean up before rerunning the job:
Log in to the CDOM.
Remove the IP:
ipadm delete-ip <wrong_vnic>
Remove the vnic:
dladm delete-vnic <wrong_vnic>
Remove the virtual switch:
ldm remove-vswitch <wrong_vswitch>
Navigate to the Oracle Enterprise Manager Ops Center user interface.
Select the CDOM and run the Refresh action from the Actions pane.
If you have an Oracle SuperCluster system with one rack, and you remove the rack in the Oracle Enterprise Manager Ops Center UI, there is no way to recreate the rack.
Delete all of the ILOMs of discovered servers within the Oracle SuperCluster.
Repeat the discovery of the Oracle SuperCluster system.
The rack and its server assets are added.
Add all remaining assets into the rack, using the Place/Remove assets in Rack and Place/Remove PDU(s) in Rack actions.
Importing ISO images of Oracle Solaris 11.2 intermittently fails with a "Cannot Be Cast" exception.
Apply the workaround found in MOS Note 1663862.1: Memory Management Between ZFS and Applications in Oracle Solaris 11.2.
In an environment with multiple Control Domains that are directly interconnected using statistically allocated IPs, attempting to attach a new network can fail with an inconsistent error message. The job indicates that the network plumbing was successful, then fails with an error saying that one or more hosts were not plumbed correctly. The Control Domains are actually left in an intermediate state with a new VNIC, but no IP address assigned.
Log in to the Control Domain.
Remove the IP address. For example:
ipadm delete-ip <wrong_vnic>
Remove the VNIC. For example:
dladm delete-vnic <wrong_vnic>
Remove the virtual switch. For example:
ldm remove-vswitch <wrong_vswitch>
Log in to the Ops Center UI.
Select the Control Domain and click Refresh in the actions pane.
Rerun the job, but provide IP addresses rather than using system-generated IP addresses.
If a Global Zone is in a private network and cannot directly access the Enterprise Controller, it cannot use ISO images stored in the Enterprise Controller library.
Copy the ISO image to the target system and use the local copy.
If the PDOM hangs or is slow to respond during an M6 discovery, the system can be displayed as a generic server.
When adding storage to a LDOM guest using a NFS library provided by an alternate root domain (not the primary), the CreateVirtDiskImage job fails in the Create Concrete task on the non-primary root domain.
The Delete Rack action deletes the Oracle SuperCluster rack from the asset tree but does not delete assets such as servers, switches, or storage that belong to the rack.
If you configure a private network on the OS level outside of Oracle Enterprise Manager Ops Center, and the OS instance is the Enterprise Controller OS which is not agent managed, the newly configured network does not appear in the user interface.
Restart the Enterprise Controller.
On an Oracle SuperCluster system, in some cases the ILOM hostname is displayed instead of OS hostname for Exadata cells.
The power status of ILOM assets sometimes shows "Off" at Dashboard tab in the user interface, even though the current power status is "On".
When this occurs, the Power On icon in the Actions pane is active and the Power Off icon is inactive.
The "Execute Operation" action is greyed out for groups of Operating System assets if at least one of them is in an unknown/offline state.
Select the Operational Plan first and then select the group as a target.
If you manually create a zone in an agent-managed control domain, the console access user is given an incorrect role and cannot access the console.
The first workaround is to connect to the control domain console, then connect to the zone.
The second workaround is to give the user the correct role.
Select Administration in the Navigation pane.
Click the Roles tab.
The Roles page is displayed.
Select the oemOCxxxx user from the list of users, where xxxx is a number set by the system.
Click the Manage User Roles icon.
Add the Zone Management role, then click Next.
The Summary page is displayed. Click Finish.
For an LDOM system, the Network Connectivity sub-tab in the Network tab shows no data, even though the Port Connectivity sub-tab correctly shows the ports.
An installation can fail during the Install application packages step when SUNWuces.pkg failed to install. This occurs when the "users" group is an LDAP managed group, not a local group.
The first workaround is to continue the installation if it is in progress, or restart the installation if it has been interrupted.
The second workaround is to manually create a local "users" group and manually install the SUNWuces.pkg.
On systems which are currently Agent-managed, switching to agentless management using the Switch Management Access action can fail with a message indicating a missing /var/tmp/agentadm.log file.
The problem occurs because a non-privileged user is used for agentless management.
Note:
This issue is fixed in version 12.2.2.0.0.Ops Center installation failed on Oracle Solaris 10 at step #21 if 125137-75 (java 6 version 75) was installed in the OS.
Uninstall the 1.6.0_65 SUNWj6rt package.
Install the 1.6.0_75 SUNWj6rt package.
Start the Enterprise Controller using the 'ecadm start -w' command.
Archive the installer image.
If the /var/opt/sun/xvm/EnterpriseController_installer_12.2.1.810 directory does not exist, create it, then copy the installer image to this directory using the following command:
cp -rp <location of Enterprise Controller installation bundle>/xvmoc_full_bundle/ */var/opt/sun/xvm/EnterpriseController_installer_12.2.1.810
Update the /n1gc-setup/.version.properties file to correct the following properties:
product.version=12.2.1.810 product.installLocation=/var/opt/sun/xvm/EnterpriseController_installer_12.2.1.810
A VLAN network is connected to the Control Domain in untagged Mode (the LDOM vsw has a pvid). A LDOM guest is created with an untag connection on this network. The VNET is also created with the same pvid.
This configuration leads the refresh mechanism to incorrectly remove the NetworkToServer association for the server representing the Ldom Guest.
As a consequence, in the UI, the Network Connectivity table of the guest Network folder is empty, and the Boot Interface Resource Assignments step of the Guest OSP wizard is not able to list the network.
Define the virtual switch in the Control domain in Tag mode.
After an upgrade, the OCDoctor and Product Metadata Update jobs appear twice. If they are deleted, they are recreated when the Enterprise Controller is restarted.
Select the older versions of the two jobs in the jobs pane and delete them using the delete icon.
Select the scheduled versions of the same two jobs in the jobs pane and delete them using the delete icon.
When discovering and managing Oracle VM Servers for SPARC, if an Agent provisioning job is launched on the control domain, the guest domains are not displayed in the UI if the Agent provisioning job fails.
The first workaround is to repeat the Agent provisioning on the control domain. The guests are discovered and displayed normally if the Agent provisioning job is successful.
The second workaround is to discover and manage the control domain agentlessly.
During NFS library creation on an Oracle SuperCluster system, an NFS metadata library cannot be created using an Storage IP address in an overlapping network setup.
Use the storage IB hostname instead of the storage IB IP address during the NFS library creation.
When configuring the Enterprise Controller in disconnected mode the UCETask fails with the following error:
Task : UCETask
Task Run ID : 124
Target : SatelliteTarget->EC
Status : FAILED
Result : Task failed. (15030)
Logs :
<timestamp> INFO Initializing Library Directory:
/swlibs/swlib2/8332899c-85c3-488c-b650-af7fd1137bb1/data
<timestamp> INFO No Update bundle specified.
<timestamp> ERROR Software Update Service is not configured. Please verify MOS Credentials (35660)
Upload a Knowledge Base Bundle through the user interface.
Activate the channels for the operating systems you plan to update and provision.
Find the channel number in the following list:
SOLARIS8_SPARC – 20
SOLARIS9_SPARC – 46
SOLARIS10_SPARC – 40
SOLARIS10_X86 – 50
OEL_5_IA32_L2 – 86
OEL_5_AMD64_L2 – 87
OEL_6_IA32_L2 – 96
OEL_6_AMD64_L2 – 97
Run the following commands on the Enterprise Controller to activate the channel:
su - uce-sds cd cgi-bin ./server.cgi addChannelCmd <channel number> ./server.cgi parentUpdateCmd <channel number>
Repeat the procedure for each additional channel.
On an Oracle Solaris 10 system, upgraded from 12.2.1 to 12.2.2, the following error sometimes appears when discovering ILOM assets:
11/07/2014 06:14:51 AM UTC ERROR Discovery driver reported: Fail to retrieve the ethernet ports IPMI for host 10.133.246.6 exit with errors:
Invalid command: /opt/sun/n1gc/pkgs/usr/sbin/ipmitool
Commands:
raw Send a RAW IPMI request and print response
i2c Send an I2C Master Write-Read comma..., driver={1}, at target {2}. (10137)
Remove the duplicate value of /opt/sun/n1gc/pkgs/usr/sbin/ipmitool from the platformproperties.ipmitoolpath property in the /opt/sun/n1gc/os/platform.properties file. For example:
bash-3.2# grep ipmitool /opt/sun/n1gc/os/platform.properties platformproperties.ipmitoolpath: /opt/sun/n1gc/pkgs/usr/sbin/ipmitool /opt/sun/n1gc/pkgs/usr/sbin/ipmitool
Restart the Proxy Controller using the proxyadm command.
Using the command line to make changes to the vswitches or networks of a control domain, after the control domain has been added to a Server Pool, can cause inconsistencies in the modeling of these objects.
You can prevent this issue by making any such changes through the user interface rather than the command line.
If you have encountered this issue, use this procedure to correct the inconsistencies on the affected systems.
Remove the Control Domain from the Server Pool.
(Optional) Perform any additional command line changes.
Refresh the Control Domain using the Refresh action in the Actions Pane.
Add the Control Domain to the Server Pool.
When using the "Add Asset" action to discover an Oracle Solaris 11 Control Domain or Oracle Solaris 10 OS, the job is successful in the "DriverDiscovery" task but fails at the "PopulateModel" task with the following error message:
<timestamp> ERROR Failed to prepare agent for <system>: No Service Tag data available on com.sun.hss.domain:name=NORM-<IP>,type=OperatingSystem. (80301). The asset is currently managed agentlessly. To convert to agent management, select the OS and perform Switch Management Access after correcting the problem. (10213)
The workaround is to manually install the Agent Controller on the target system.
After restoring a Proxy Controller from a backup, some update functionality does not function correctly and the Oracle Solaris 11 publishers are not set correctly because the Apache configuration is not restored by the Proxy Controller restore.
Shut down the Proxy Controller using the proxyadm command with the stop subcommand and the -w option.
Edit the proxy.conf file. This file is located in the /var/opt/sun/xvm/uce/etc.opt/server/uce_server/ directory on Oracle Solaris systems and in the /var/opt/sun/xvm/uce/etc/uce_server directory on Linux systems.
The following two lines appear in the file:
ProxyPass / https://0.0.0.0:443/uce/uce/ ProxyPassReverse https://0.0.0.0:443/uce/uce/ /
Edit these lines to include the IP address of the Enterprise Controller:
ProxyPass / https://<Enterprise Controller IP>:443/uce/uce/ ProxyPassReverse https://<Enterprise Controller IP>:443/uce/uce/ /
Restart the Proxy Controller using the proxyadm command with the start subcommand and the -w option.
When JIDR2 is installed, it creates a new index in the database, which remains even if JIDR2 is uninstalled. If this index is present during an attempted upgrade of an Enterprise Controller to version 12.2.2, the upgrade fails with the following error in the update logs:
<timestamp> ERROR: Failed update_schema_12.2.2.0.sql Non-zero return code=1 <timestamp> /disk1/enterprise-controller/12.2.2/xvmoc_update_bundle/scripts/database/update: ERROR: failed to perform migration script: /opt/sun/xvm/dbupdates/update.ORCLsysman-db.12.2.2.1103 <timestamp> DEBUG: Component:_execit: cmd return code 512(0x200) <timestamp> ERROR: Update of component "database" failed, status=2 <timestamp> DEBUG: main: state after apply():2 <timestamp> WARNING: Update failure; backing out update (update status 2)
The OCDoctor.sh utility checks for this index when it is run with the --troubleshoot option.
As root, drop the index before attempting the upgrade. For example, on an Oracle Solaris system:
# echo 'DROP INDEX PERSISTENTALERT_RESOURCENAME2;' | /opt/SUNWxvmoc/bin/ecadm sqlplus
On a Linux system:
# echo 'DROP INDEX PERSISTENTALERT_RESOURCENAME2;' | /opt/sun/xvmoc/bin/ecadm sqlplus
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.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Enterprise Manager Ops Center Release Notes, 12c Release 2 (12.2.2.0.0)
E38533-05
Copyright © 2007, 2014, Oracle and/or its affiliates. All rights reserved.
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, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
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 of The Open Group.
This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.