Release Notes
Release 10.3.8.1
E37288-03
July 2013
Oracle Configuration Manager is used to personalize and enhance the support experience by collecting configuration information and uploading it to the Management Repository. When the configuration data is uploaded on a regular basis, customer support representatives can analyze this data and provide better service to customers.
Oracle Configuration Manager collection software is self contained and does not affect the contents of the existing Oracle software installation. The configuration collections occur once a day and have negligible impact on the operations of the system and Oracle products including production deployments.
These Release Notes list the important features of Oracle Configuration Manager and the known issues in this release.
The steps to install and configure Oracle Configuration Manager are documented in the Oracle Configuration Manager Installation and Administration Guide.
This document contains the following sections:
The Oracle Configuration Manager Installation and Administration Guide can be downloaded from the following URL:
http://www.oracle.com/technetwork/documentation/ocm-092152.html
This document corresponds to the most recent release of Oracle Configuration Manager and supports earlier releases.
Online documentation is available to respond to concerns surrounding security implications of Oracle Configuration Manager. The My Oracle Support Knowledge Base articles (728982.1 or 728982.5) answer common questions about how Oracle Configuration Manager ensures its operations are performed in a secure manner.
This section lists the new features in Oracle Configuration Manager.
The new features in the 10.3.8.1.0 release include:
Support for Oracle Enterprise Manager Cloud Control 12c Release 3 (12.1.0.3)
Harvester Support for Target Level Feature Usage from Enterprise Manager Repository into OCM CCR
Support for Fusion MiddleWare 12c
Support for Oracle Database 12
Container Database/Pluggable Database (CDB/PDB) Support
Discovery and Collection of Oracle DB 12
The new features in the 10.3.8.0.0 release include:
Oracle Configuration Manager Now Supports Configuring a Collector as a Central Collector
The central collector collects data for Oracle homes that were not previously configured or left in disconnected mode. The central collector uploads these Oracle homes under their own My Oracle Support credentials.
[ER 14283977]
Oracle Configuration Manager Supports Oracle Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2).
Support for NTLM
Oracle Configuration Manager when used with Java version 1.6 or higher now supports the NTLM (NT LAN Manager) authorization scheme for proxy servers.
[ER 14314300]
Data Masking Supported for Oracle Configuration Manager Harvester
Oracle Configuration Manager now supports data masking for Harvester.
[ER 14258759]
OCM Now Has a Native 64-bit Client for Oracle Linux x86_64
Configurations for the Following Targets from Oracle Enterprise Manager Cloud Control:
Exalogic
BI
Siebel
See "Supported Targets in Oracle Harvester" in the Oracle® Configuration Manager Installation and Administration Guide for a complete list of targets supported.
The new features in the 10.3.7.0.0 release include:
Support for Oracle Exalogic
To support patch recommendations in My Oracle Support, Oracle Configuration Manager collects patch information from WebLogic Server, Oracle JRockit, and Oracle Coherence environments in Oracle Exalogic.
Support for Oracle Exadata Cell Server
To support configuration-driven software request workflow in My Oracle Support, Oracle Configuration Manager collects the serial number for the host of the Oracle Exadata Cell server.
Oracle Configuration Manager now supports collections for IBM AIX releases 6.1 and 7.1.
Support for Expanded Oracle Solaris Configuration Collection
Oracle Configuration Manager installs based on Oracle Solaris now support the collection of hardware component data, installed OS patches and firmware. See the Oracle Configuration Manager Collection Overview manual for additional information.
The new features in the 10.3.6.0.0 release include:
Oracle Configuration Manager Supports Oracle Enterprise Manager Cloud Control Release 12.1
Oracle Configuration Manager now supports Oracle Enterprise Manager Cloud Control release 12.1.
Oracle Enterprise Manager Ops Center Harvester
In addition to Oracle Configuration Manager and Oracle Enterprise Manager Harvester, data is now automatically collected by the Oracle Enterprise Manager Ops Center Harvester. The Oracle Enterprise Manager Ops Center Harvester runs on the Oracle Enterprise Manager Ops Center Enterprise Controller and collects data from managed Oracle Enterprise Manager Ops Center systems.
Oracle Configuration Manager Supports Oracle Database Machine
Oracle Configuration Manager now discovers and collects configuration data for Oracle Database Machine.
Expanded Oracle Enterprise Manager Harvester Collections
Oracle Enterprise Manager Harvester is now expanded to collect the configurations for the following targets from Oracle Enterprise Manager Cloud Control release 12.1:
Oracle Exadata Storage Server
Oracle Database Machine
Management Repository
Oracle Management Service (OMS)
Management Agent
Oracle SOA Suite
Oracle Fusion Middleware
The known issues are as follows:
This section lists the generic known issues pertaining to this release.
Oracle Harvester makes associations based on a target property called "DBMachineID' and it is the same for all partitions. Therefore every partition comes under one Database Machine target on Oracle Configuration Manager. (A partitioned DB Machine can be a single rack machine or multi-rack machine.)
Because Oracle Harvester for Oracle Database Machine does not support a partitioned rack, users must set a unique value for the split_no target property.
To enable Oracle Harvester to collect each partition as a separate Database Machine, you need to set a unique value for the split_no target property for each partitioned Exadata target on Enterprise Manager.
Follow these steps to set the target property:
Collect all the partitioned Database Machine names of a single Exadata hardware.
Add a new target property split_no in the OMS
$ORACLE_HOME/emcli/bin/emcli add_target_property -target_type="oracle_dbmachine" -property="split_no";
Set a unique value of the split_no target property for each partitioned Database Machine:
$ORACLE_HOME/emcli/bin/emcli set_target_property_value -property_records="<target name of dbmachine>:oracle_dbmachine:split_no:<unique String>" For example: ORACLE_HOME/emcli/bin/emcli set_target_property_value -property_records="DB Machine slcb06.us.oracle.com_2:oracle_dbmachine:split_no:2"
(Bug 14697857)
As of release 10.3.8, OCM has a native 64-bit client for Oracle Linux x86_64. Therefore, the 32-bit libraries are no longer required for Oracle Linux x86_64.
Using deriveCCR to clone an Oracle Configuration Manager installation that was originally setup in compatibility mode (ORACLE_HOME environment variable was set to the same directory as ORACLE_CONFIG_HOME), to a cloned home that is NOT setup in compatibility mode fails.
To alleviate this problem, edit the collector.properties file located in <cloned_home>/ccr/hosts/<your_hostname>/config where <cloned_home> is the cloned directory. Change the ccr.binHome property to the full path of the cloned home.
For example, change:
ccr.binHome=/scratch/testocm/original/ccr to ccr.binHome=/scratch/testocm/cloned/ccr
When an Oracle Database is configured with Oracle Database Vault, instrumenting the database for collection of configuration information fails. The instrumentation is performed through the command:
$ORACLE_HOME/ccr/admin/scripts/installCCRSQL collectconfig
The SYS account used to perform the instrumentation does not have access to the SYS privileges needed in an Oracle Database Vault configuration. The following error is reported when reviewing the log file referred to in the error message:
ORA-20006: ORA-01031: insufficient privileges
(Bug 9956595)
If you install Siebel with localhost as the host name of the machine, the Siebel hierarchy under the Enterprise System will not display any entries under that Siebel server in My Oracle Support. Although the Siebel server hierarchy will not display any entries, all details under this Siebel server are still collected and available through their respective targets under the Targets region in My Oracle Support.
(Bug 9532616)
If you manually installed the Oracle Configuration Manager collector in the server and gateway server directory trees, you should:
Stop and decommission those Oracle Configuration Manager collectors in the gateway server and server directories using the command configCCR -r
Login to My Oracle Support and disable the targets that were collected by the collector that was decommissioned.
Deploy the collector to the Siebel root directory if not already done.
Note: The current Oracle Configuration Manager release has been certified for 7.7, 7.8, 8.0, and 8.1 releases of CRM.
When a virtual machine changes from a running state to a halted state or vice versa, it takes a maximum of 24 hours to reflect the updated information in My Oracle Support.
For example, if the running Guest Virtual Machine (GVMA) is halted, then GVMA is no longer associated to a Virtual Server but to the parent Virtual Server Pool. However, while viewing this relationship in My Oracle Support, one might see GVMA associated to the Virtual Server (implying a running GVMA) as well as to Virtual Server Pool (implying halted GVMA). Although Oracle Configuration Manager has collected new configuration data capturing these associations, the new snapshot is ignored because the collection time stamp of the Virtual Server snapshot does not change and is the same as the previous snapshot. Every 24 hours, a new snapshot is uploaded to Oracle with a new collection time stamp. When this new snapshot is uploaded to Oracle, the new data is reflected in My Oracle Support.
When using JDK 1.4.2 and Oracle Configuration Manager version 10.3.3 or later to create a response file that contains an authenticated proxy server, the response file cannot be used with earlier versions of Oracle Configuration Manager.
When using a response file that contains an authenticated proxy server and it was created using JDK version 1.4.2 or later, you must use JDK version 1.4.2 or later. Otherwise, you will get an error message and Oracle Configuration Manager will exit.
An abnormal termination such as a Control C during the invocation of setupCCR or reconfiguration using configCCR may result in subsequent attempts returning the message:
This installation is already configured for OCM. Please remove existing configuration first.
To manually reset the environment, remove the config and state directories located under the $ORACLE_HOME/ccr/hosts/<hostname> directory. If ORACLE_CONFIG_HOME is set, remove the config and state directories in the $ORACLE_CONFIG_HOME/ccr directory.
If this is a fresh installation, delete the ccr directory and unzip the Oracle Configuration Manager distribution into the ORACLE_HOME and issue the setupCCR command again.
The relationship between the deployment of a Siebel Server and dependent database is collected only for Oracle database.
Oracle Configuration Manager requires a Java home being present in the $ORACLE_HOME/jdk directory or in the $ORACLE_HOME/jre directory. The minimum version required is 1.2.2. (Microsoft Windows releases require 1.3.1 at a minimum). If the $ORACLE_HOME does not contain this version or the directory does not exist, an alternate JAVA installation can be used.
To resolve this issue, ensure that the JAVA_HOME environment variable points to the valid jdk or jre directory.
Note: If you are using a proxy server that uses NTLM authentication, then you must use Java version 1.6 at minimum.
The Java Development Kit (JDK) distributed by the GNU Free Software Foundation is not supported by Oracle Configuration Manager. The GNU version of JDK does not support either required command qualifiers or class loader capabilities.
For Oracle database installations prior to 9.0, the Oracle inventory data cannot be collected. This is because the collection mechanism relies on the newer XML format for the product inventory which is available for 9.0 and later versions.
When you run the $ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh script, you may encounter the following error:
An error had occurred For details, check the log file at /u01/app/oracle/10.2.0/db/ccr/log/collectconfigasmdb.log
The contents of the log file identified contains the output:
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Oct 17 17:54:35 2005 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. Connected to an idle instance.
The log file ends with the text:
ERROR at line 1: ORA-01034: ORACLE not available
This error may occur if the $ORACLE_HOME environmental variable used to start the database instance ended with a '/' character.
To resolve this issue, stop the database instance and redefine the ORACLE_HOME so that it does not include the trailing slash and restart the database. Once the database is restarted, re-run the installCCRSQL.sh script.
The emCCR status command displays the state of the scheduler, when a collection was last performed, when the next collection will run and the schedulers start time. These times may appear to be inconsistent.
The system's TZ variable affects how the time stamps are stored. Collections performed manually vs. automatically store their collection times based upon the TZ variable of the process invoking the collection.
To resolve this inconsistency, insure the cron daemon is started with the correct system time zone.
Mozilla contains a bug that does not recognize XSL stylesheets correctly. The aforementioned error is displayed as a result.
Configure Mozilla by selecting the Edit -> Preferences... item from the menu. Add a New Type under the Navigator -> Helper Applications entry for a MIME type of 'text/xml' and an extension of 'xsl'. Click on 'Proceed anyway' when the warning message indicating 'Mozilla can handle this type' is presented.
The My Oracle Support Knowledge Base article 1313506.1 explains this issue in detail. You can access this article at:
https://support.oracle.com
The OCM collector may not discover the Oracle Database target in the Database home. This might be due to the directory object created as part of OCM database instrumentation has an invalid path. The form of the invalid path could be:
$ORACLE_HOME/ccr/hosts//state
If you find the directory object is created like this, the OCM database instrumentation job will generate errors in the alert log. You can check the path of the directory object by running the following command in SQL*Plus while connected as a suitably-privileged user:
SQL> select directory_name, directory_path from dba_directories
where directory_name like 'ORACLE_OCM%';
There are two possible workarounds:
Recreate the directory object with the correct directory path. For example:
SQL> create or replace directory <DIRECTORY_NAME> as '<CORRECT PATH>';
Re-run the OCM database instrumentation script. For example:
/bin/sh $ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig
(Bug 16575976)
For Fusion MiddleWare 12.1.2, a mini version of the OCM collector kit is included. This version of the kit includes a minimal set of components that are needed for initial configuration. During configuration if the OCM is connected, the remaining components are download and installed.
If the OCM is not connected, the remaining components must be installed manually. You can download the full OCM collector kit from My Oracle Support (download the latest version of the patch for bug 5567658):
https://support.oracle.com
Once you have downloaded the patch, update OCM with the following command:
cd $FMW_HOME/oracle_common/ccr/bin/emCCR update_components -distribution=/scratch/distribution/ccr-Production-10.3.8.0.0-Linux-i386.zip
For more details, refer to Section 6.16, "emCCR update_components" of the Oracle® Configuration Manager Installation and Administration Guide:
http://docs.oracle.com/cd/E37284_01/doc.1038/e37289/manage.htm#CACGEHHJ
(Bug 15875776)
This section lists the Windows-specific known issues pertaining to this release.
For some installs on Windows platforms, Oracle Configuration Manager cannot consistently get the Oracle Home name from the registry. This causes problems with the name of the service that is created to control the Oracle Configuration Manager scheduler.
To resolve this issue: Prior to running setupCCR or configCCR, remove any existing OCM Service names, set the ORACLE_HOME_NAME environment variable to the name of the home as provided to OUI during installation. This allows the variable to be propagated to the service name. For example, the service name will now become Oracle%ORACLE_HOME_NAME%ConfigurationManager.
(Bug 7243846)
When executing setupCCR or configCCR on a Windows system with Japanese set as the input language, we recommend credentials be specified using the CSI and User Name format.
(Bug 12559581)
When you execute the command emCCR update_components -distribution=<OCM1035 zip file path>, you may see the following error:
<OCM1035 zip file path> is not a valid OCM distribution.
To resolve this issue, perform the following steps:
Unzip the 10.3.5 Oracle Configuration Manager collector kit to a temporary directory, for example, c:\temp-ccr.
Copy the contents of the c:\temp-ccr\inventory\pending directory to a different directory, for example, c:\ccr-packages.
Run the command emCCR update_components -staged_dir=c:\ccr-packages
Once this command completes successfully, both the c:\temp-ccr\ and c:\ccr-packages directories can be deleted.
(Bug 12539188)
When using the deriveCCR command on the Windows operating system, if Oracle Configuration Manager in the source home is in disconnected mode, then Oracle Configuration Manager in the cloned home will be left in disconnected mode.
To change the Oracle Configuration Manager collector to connected mode, execute the configCCR command from the cloned home after deriveCCR completes.
(Bug 11723395)
When using the deriveCCR command on the Windows operating system, in the following conditions the Oracle Configuration Manager in the cloned home is left in Disconnected Mode:
If the Oracle Configuration Manager in the source home was in disconnected mode at the time it was copied to the cloned home.
If no connectivity to the end point can be achieved.
If the credentials cannot be verified.
Generally, the deriveCCR command will not prompt the user for information. Hence, Oracle Configuration Manager collector in the cloned home is left as disconnected.
To change the Oracle Configuration Manager collector to connected mode, execute the configCCR command from the cloned home after the deriveCCR command completes.
(Bug 13830065; associated Bug 11723395)
When using the deriveCCR command on non-English Windows environments, deriveCCR may freeze when prompting for input. To alleviate this problem, execute deriveCCR and supply a response file with the command.
(Bug 11939132)
On all Windows platforms, the following metrics for the specified targets in the Oracle Fusion Middleware Application Server Release 11 instance are only partially collected:
| Target Type | Metric Name |
|---|---|
| oracle_webcache | MGMT_WEBCACHE_CONFIGFILES |
| oracle_apache | MGMT_OHS_CONFIGFILES |
| oc4j | MGMT_OC4J_CONFIGFILES |
Quoting the directory path specification when setting the ORACLE_CONFIG_HOME environmental variable is not required and will result in the aforementioned error being displayed. Set the ORACLE_CONFIG_HOME variable to the directory specification without quotes.
Installation of Oracle Configuration Manager on a RAW device is not supported. Configuration of the software will result in the following error being returned.
Unable to Determine Oracle Configuration Manager content receiver endpoint Oracle Configuration Manager endpoint unknown
When installing Oracle Configuration Manager, an error occurs indicating there is no file extension in a directory. The directory indicated in the error is a substring corresponding to the current directory, whose path contains spaces.
The condition occurs if the following Windows Registry key is set to 1:
HKLM/SYSTEM/CurrentControlSet/Control/FileSystem/NtfsDisable8dot3NameCreation
If this setting is not critical to your operations, you can set the registry key to 0.
Note:
You must restart Windows if you chose to make changes to the registry key effective.If this setting is critical to your operations, you must install Oracle Configuration Manager in a directory whose path does not contain spaces.
When installing Oracle Configuration Manager, an error indicating that the JAVA version was not able to be identified is returned, however, one of the following is true:
JAVA_HOME is defined and the following command returns the JDK version %JAVA_HOME%\bin\java -version
The current directory is the install root and the following command also returns the JDK version jdk\bin\java -version
The condition occurs if the TMP environmental variable contains a directory specification containing a space and the Windows Registry key is set to 1:
HKLM/SYSTEM/CurrentControlSet/Control/FileSystem/NtfsDisable8dot3NameCreation
Set the registry key to 0 and the TMP environmental variable for the user to a value that does not contain a space.
Note:
You must restart Windows if you chose to make changes to the registry key effective.This error may come on some Microsoft operating systems especially on Windows 2000 and Windows NT systems. It is primarily due the fact that the service under consideration is marked for deletion. During the upgrade process the Oracle Configuration Manager removes the old service and creates a new one.
If the old service is selected in the Windows Service Control Manager (Services) interface in Control Panel or he/she is looking at the old service properties then service removal fails to completely remove the old service.
To correct this problem, close the Service Control Manager (Services) interface and retry the upgrade operation.
This section lists the UNIX-specific known issues pertaining to this release.
When you install the Oracle Configuration Manager using a CRON script, you may encounter the following error:
Error occurred during initialization of VM Unable to load native library: .../jdk/jre/lib/i386/libjava.so: symbol __libc_ wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
The problem occurs when Java is invoked without the LD_PRELOAD variable being set. This is normally required on Redhat Advanced server configurations. (Refer to Oracle Patch 3006854).
To resolve this issue, define LD_PRELOAD to the preload module prior to invoking the installation of the Oracle Configuration Manager.
The execution of a collection may result in the error:
Failed to execute command - "<ORACLE_HOME>/ccr/engines/Linux/perl/bin/perl" <ORACLE_HOME>/ccr/sysman/admin/scripts/hostosfile.pl"
The Oracle Configuration Manager times out individual configuration collections if the collection does not complete within 5 minutes. This specific case manifests itself on LINUX if a NFS mount point is not responding to a df -k command.Identify the failing mount point by iterating through the listed filesystems in /etc/mtab by doing a ls on the location. Resolve the problem with the failing NFS server. Alternatively you can remove the entry from the mtab file and the NFS file service will not be monitored. This file is re-created when a filesystem is mounted.
emCCR CommandRunning either the setupCCR or configCCR command configures Oracle Cofiguration Manager (OCM). If you run these commands from a directory and then delete the directory, you may encounter an error when running the emCCR command.
The error would look like:
<ocm_install_root>/ccr/bin/emCCR collect
Oracle Configuration Manager - Release: 10.3.8.1.0 - Production
Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved.
-------------------------------------------------------------------------------
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current working directory.
at java.lang.System.initProperties(Native Method)
at java.lang.System.initializeSystemClass(System.java:1070)
If you encounter this error, you can run the following commands as a workaround:
<ocm_install_root>/ccr/bin/emCCR stop <ocm_install_root>/ccr/bin/emCCR start
To avoid this error, always run the setupCCR or configCCR commands from the <ocm_install_root>/ccr/bin directory.
(Bug 16677401)
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 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 Configuration Manager Release Notes, Release 10.3.8.1
E37288-03
Copyright © 2005, 2013, 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, 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 of The Open Group.
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.