Oracle Configuration Manager Release Notes Version: 10.3.1.0.

0 Date: Jan 15, 2009

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. About Oracle Configuration Manager ---------------------------------Oracle Configuration Manager is used to collect client configuration information and upload it to Oracle. When the client 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. Oracle Configuration Manager Documentation -----------------------------------------The Oracle Configuration Manager Installation and Administration Guide can be downloaded from http://www.oracle.com/technology/documentation/ocm.html. This document corresponds to the most recent release of Oracle Configuration Manager and supports earlier releases. Country Codes ----------------The configuration of the Oracle Configuration Manager requires a Customer Support Identifier (CSI), My Oracle SUpport User Name and valid country code. The country code is the country the support contract was issued under. For a list of valid country codes, refer to the Oracle Configuration Manager Installation and Administration Guide. 10.3.0.0.0 New Features ======================= Installation response file generator -----------------------------------Oracle Configuration Manager now distributes a installation/deployment response file generator. The utility (ccr/bin/emocmrsp) steps the user through an install experience prompting for user input. The utility generates a response file that is used with setupCCR in conjunction with a new -R command line qualifier.

Installation Requirement requiring CSI removed ---------------------------------------------Oracle Configuration Manager no longer requires the CSI, My Oracle Support user Id and Country Code to be specified as part of the installation process. The user can choose to specify the CSI if known on the command line. Alternatively, the installation process prompts for the My Oracle Support username and password alone. Users may not immediately see configurations in My Oracle Support. (https://mmyoraclesupport.oracle.com) if their user profile contains more than 1 CSI. The configurations must be manually associated with a single CSI through the My Oracle Support 'Task: Associate Collectors' region. Proxy specification no longer supported as a command line option -----------------------------------------------------------------The setupCCR and configCCR command line interfaces no longer support the specification of a proxy for connectivity. The user is prompted for the proxy if it is determined that direct connectivity to Oracle is not possible from the system. Oracle Configuration Manager response file generator (ccr/bin/emocmrsp) records connectivity and configuration information inclusive of the proxy. This response file can be used in broad deployment across systems and platforms. 10.2.7.0.0 New Features ======================= Support for Shared Oracle Homes ------------------------------Fresh installations of Oracle Configuration Manager are now enabled for shared home support. These installations can be shared transparently by installing the Oracle Configuration Manager binaries on a shared resource such as a network file system. Individual hosts leverage the shared binary tree transparently by creating host specific directories that isolate configuration information. Alternatively, the location of the Oracle Configuration Manager configuration information can be placed in a specific location by defining the environmental variable ORACLE_CONFIG_HOME. Upgrades of Oracle Configuration Manager from releases prior to 10.2.7.0.0 can not support sharing of the Oracle Configuration Manager binaries. Running configuration collections as Root ----------------------------------------Previous versions of Oracle Configuration Manager restricted command execution to the owner of the Oracle Home. The collection of configuration information is now also permitted by the root user. Commands such as those that start the Oracle Configuration Manager and perform software updates are still restricted to the Oracle Home owner. 10.2.6.0.0 New Features =======================

Notification of Oracle Configuration Manager Updates ---------------------------------------------------Oracle Configuration Manager contains the capability to automatically update itself. Customers that disable this capability find that collections cease to be uploaded when a new update is automatically available. With the 10.2.6 release of Oracle Configuration Manager, customers can receive advance notification of a pending update by registering for patch updates to Oracle Configuration Manager patch number 5567658 on My Oracle Support. By downloading the patch update and updating it manually, the software can be validated prior to being required. Updates are made available for automatic installation two weeks after the advance distribution notification is made. Older versions of the collector will not be permitted to upload configuration information until this update is installed. Customers who have automatic updates enabled need not take any additional steps. The software will automatically update itself. Manually Updating Oracle Configuration Manager ---------------------------------------------With the 10.2.5.0.0 release of Oracle Configuration Manager, updates to the collection mechanisms can be manually applied if automatic updates are disabled. The most recent downloadable update is available through the My Oracle Support patch download mechanism. Download the patch numbered 5567658. Application of the update is performed by issuing the command $ORACLE_HOME/ccr/bin/emCCR update_components -distribution=<file> where $ORACLE_HOME is the installation root containing the Oracle Configuration Manager that is to be updated, and <file> is the file specification of the downloaded patch. The update of Oracle Configuration Manager may require reinstrumentation of Oracle Enterprise Manager Grid Repository, Oracle Database, or Oracle E-Business Suite repository for configuration collections. Issue the command $ORACLE_HOME/ccr/bin/emCCR status to determine if there are additional update steps that need to be performed. Diagnostics Upload -----------------The upload of diagnostic information to Oracle for attachment against an open service request is now functional with this release. The upload of diagnostic information requires the user specify the Username and Password of the My Oracle Support account used to create the service request. The Oracle Configuration Manager prompts for this information in a no-echo mode. On Microsoft Windows systems, the prompting for this information will dispatch a new console window. This window can be closed after upload has completed.

Change in behavior ================== Enabling/Disabling collection of IP and MAC addresses: ----------------------------------------------------With the 10.2.5.0.0 release of Oracle Configuration Manager, the user now has the ability to disable the collection of specific configuration items. The only two configuration items that can be disabled are the collection of the host IP address and the Network Interface MAC address. By default, these configuration items are collected. To disable their collection, add a property to the collector.properties file in $ORACLE_HOME/ccr/config. Add the following line to disable the collection of the host IP address: ccr.metric.host.ecm_hw_nic.inet_address=false Add the following line to disable the Network Interface MAC address collection: ccr.metric.host.ecm_hw_nic.mac_address=false The metric(s) are re-enabled by removing the corresponding line from the collector.properties file. NFS Disk information not collected by default --------------------------------------------With the 10.2.5.0.0 release of Oracle Configuration Manager, collections no longer contain information on NFS mounted filesystem information. To enable the collection of the added configuration information, add the following property to the $ORACLE_HOME/ccr/config/collector.properties file. metric.host.ecm_os_filesystem.nfs_enable=true

Generic Known Issues ==================== Installing or reconfiguring the OCM Collector with a JDK > 1.4 results in java.lang.SecurityException exception ---------------------------------------------------------------Configuring or initial setup of Oracle Configuration Manager with a Oracle Configuration Manager Repeater using a JDK that is not 1.4 results in the exception: java.lang.SecurityException: The jar file has unsigned class files. You must use a JDK that is 1.4.* to leverage a Oracle Configuration Manager Repeater.

'peer not authenticated' error encountered creating a OCM response file specifying an OCM Repeater that listens on https ----------------------------------------------------------------------------The creation of a Oracle Configuration Manager response file specifying a OCM Repeater that listens on https returns the error 'peer not authenticated'. The utility proceeds to prompt for a proxy that will also fail. $ORACLE_HOME/ccr/bin/emocmrsp -repeater https://server.x.com:4473 OCM Installation Response Generator 10.3.1.0.0 - Production Copyright (c) 2005, 2009, Oracle and/or its affiliates.All rights reserved. An unrecoverable network configuration error was encountered. peer not authenticated. Unable to establish a network connection to Oracle. If your systems require a proxy server for outbound Internet connections, enter the proxy server details in this format: [<proxy-user>@]<proxy-host>[:<proxy-port>] If you want to remain uninformed of critical security issues in your configuration, enter NONE Proxy specification: The use of http is the only scheme permitted for connections to the repeater. Data sent through a repeater is protected using AES and RSA cipher encryption algorithms to insure data privacy. Installation considered configured after abnormal termination of setupCCR or configCCR commands ---------------------------------------------------------------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.

Relationship between Siebel Server and Database not captured -----------------------------------------------------------The relationship between the deployment of a Siebel Server and dependent database is not collected by this version of the collector.

Java Requirements ----------------Oracle Configuration Manager requires a Java home being present in the $ORACLE_HOME/jdk 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 directory. GNU Free Software Foundation JDK not supported ---------------------------------------------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. Error failing to register during upgrade of Oracle Configuration version from version 10.2.5 to 10.2.6 ----------------------------------------------------------------------------The upgrade of Oracle Configuration Manager (OCM) to version 10.2.6.0.0 results in a transparent re-registration of the OCM software with Oracle. If the registration fails (as a result of a transient network outage), the scheduler is placed in a 'Down for Upgrade' state. This state is reset in approximately 15 minutes after the failure and the scheduler can be restarted when connectivity is re-established. On UNIX platforms, a scheduler restart operation is automatically attempted every 15 minutes until successful. On Microsoft Windows, the scheduler must be manually restarted. The upgrade of the OCM collector from 10.2.5.0.0 to 10.2.6.0.0 can be manually performed or it will automatically be re-attempted during the next regularly scheduled collection. Oracle Inventory Data Unavailable for Pre-9.0 Database Installations ------------------------------------------------------------------------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. Error encountered running installCCRSQL.sh -----------------------------------------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/collectc onfigasmdb.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. Changes to Oracle Home environmental settings not detected during collections -----------------------------------------------------------------------------The installation of Oracle Configuration Manager takes a snapshot of the process environment. These key environmental variables are stored such that scheduled collections behave the same even though they are running as detached processes. If any of the following variables change, update the snapshot file by running the command: $ORACLE_HOME/ccr/bin/emSnapshotEnv. Key environmental variables are: ORACLE_HOME, JAVA_HOME, TZ, TNS_ADMIN, CRS_HOME, CLUSTER_NAME, LD_PRELOAD and ORAINST_LOC. Start Date, Last Collection and Next Collection times inconsistent -----------------------------------------------------------------------------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 timestamps 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. emCCR config fails to start if acceptance of license agreement is removed -----------------------------------------------------------------------------Acceptance of the Oracle Configuration Manager license agreement is recorded in the $ORACLE_HOME/ccr/config/collector.properties file. If the property named ccr.agreement_signer is removed, emCCR config will not start. Simply add a record of the form: 'ccr.agreement_signer=true' to the $ORACLE_HOME/ccr/config/collector.properties file. Under no circumstances should any user changes be made to collector.properties file in the $ORACLE_HOME/ccr/config/default directory. This file is modified

by the upgrade process and any user changes will be lost. Reviewing collected configuration information with Mozilla returns the error Error loading stylesheet: An XSLT stylesheet does not have an XML mimetype: -----------------------------------------------------------------------------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. Windows Specific Known Issues ============================= "%ORACLE_CONFIG_HOME% refers to a non-existent directory" encountered -----------------------------------------------------------------------------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 Windows RAW device unsupported -----------------------------------------------------------------------------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 'Input Error: There is no file extension in "<directory>"' error encountered installing Oracle Configuration Manager -----------------------------------------------------------------------------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 Windows Registry key HKLM/SYSTEM/CurrentControlSet/Control/FileSystem/NtfsDisable8dot3NameCreation is set to 1. 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.

'Java version not able to be identified' error encountered installing or issuing Oracle Configuration Manager commands -----------------------------------------------------------------------------When installing Oracle Configuration Manager, an error indicating that the JAVA version was not able to be identified is returned, however: - JAVA_HOME is defined and the following command returns the JDK version %JAVA_HOME%\bin\java -version OR - 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 HKLM/SYSTEM/CurrentControlSet/Control/FileSystem/NtfsDisable8dot3NameCreation is set to 1. 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. Could not create service <name> : 1072 during software installation ------------------------------------------------------------------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. emCCR update_components takes a long time to deploy software updates -------------------------------------------------------------------The 'emCCR update_components' command allows for the specification of a directory that contains a staged set of JAR files or a full Oracle Configuration Manager distribution. If the location is on a network filesystem, the command takes a long time to complete. The problem is a base JDK bug (http://bugs.sun.com/bugdatabase/view_bug.do?bug_i d=4770745). Place the staged contents or distribution on a local directory before performing the command. Oracle Configuration Manager does not complete auto-upgrade from 10.2.3

Version on Windows 2000 and Windows 2003 server. ----------------------------------------------------------------------The automatic upgrade of the Oracle Configuration Manager from 10.2.3 does not automatically complete the installation of the update and leaves the service stopped. A simple restart of the Oracle Configuration Manager service via the %ORACLE_HOME%\ccr\bin\emCCR start command completes the upgrade. This issue is resolved in the 10.2.4 version of the Oracle Configuration Manager. UNIX Specific Known Issues ========================== Error Initializing JVM when Installing Oracle Configuration Manager -----------------------------------------------------------------------------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_wa it, 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. PERL5LIB not defined encountered during upgrade from 10.2.2 to 10.2.3 -----------------------------------------------------------------------------During the upgrade from 10.2.2 to 10.2.3, the following error message is displayed: PERL5LIB is not defined. Unable to perform the "<command>" operation. Please re-run the command. The upgrade deploys updated scripts that are at the same time being consumed. This interim state finds the PERL5LIB undefined. Re-issue the command. If such a message is mailed by the cron system, you may ignore it. The next invocation of cron job for Oracle Configuration Manager will automatically re-issue the command. Error updating core package from 10.2.2.0.2 to 10.2.3.0.0 on an NFS volume. -----------------------------------------------------------------------------The upgrade from 10.2.2.0.2 to 10.2.3.0.0 fails with an error and the 10.2.2 version is re-installed. Review of the install-core*.log that is identified in the error message indicates a deletion of the lib directory has failed. NFS volumes behave differently when deleting files that are in use than on local volumes. NFS files are not removed but marked as hidden with a filename of the form .nfs<sequence>. Once the file is released, the NFS server removes the hidden file. This problem is corrected in the 10.2.3.0.0 version of the Oracle

Configuration Manager package. To update to the 10.2.3.0.0 release, remove the Oracle Configuration Manager directory via the command: 'rm -rf $ORACLE_HOME/ccr'. Perform a full installation of the 10.2.3.0.0 Oracle Configuration Manager. This issue is resolved in Oracle Configuration Manager versions 10.2.4.0.0 and later. 'command not found' and 'Unable to acquire deployment lock' displayed during upgrade from 10.2.2.0.2 to 10.2.4 of the Oracle Configuration Manager -----------------------------------------------------------------------------Installation of the 10.2.2.0.2 Oracle Configuration Manager automatically performs a download of updates and applies these to the installation. This occurs with the downloadable form of the Oracle Configuration Manager kit from My Oracle Support as well as through installation of the Oracle Enterprise Manager Grid Control 10.2.0.2 patchset. The following messages appear during this installation: ** Installing base package ** Deploying core - Version 10.2.2.0.2 ** Registering installation with CCR server(s) ** ** Getting package updates from ContentServer ** Deploying engines - Version 10.2.2.0.0 Deploying scripts - Version 10.2.2.0.2 Deploying core - Version 10.2.4.0.0 $ORACLE_HOME/ccr/bin/deployPackages: line 583: -1: command not found $ORACLE_HOME/ccr/bin/deployPackages: line 586: Unable to acquire deployment lo ck ... Deploying metricdata - Version 10.2.4.0.0 Deploying scripts - Version 10.2.4.0.0 $ORACLE_HOME/ccr/bin/deployPackages: line 583: -1: command not found $ORACLE_HOME/ccr/bin/deployPackages: line 586: Unable to acquire deployment lo ck ... The messages (line 593... and 'Unable to acquire deployment lock' errors) are benign and do not affect the upgrade. They can be ignored. After the installation you can review the version of all installed components by issuing the command "$ORACLE_HOME/ccr/bin/deployPackages -l". The core, metricdata and scripts packages will indicate a 10.2.4 version. Installation of the Oracle Configuration Manager fails if CRON is disabled -----------------------------------------------------------------------------The Oracle Configuration Manager relies on the cron capabilities of UNIX to schedule the collection of configuration data. If cron is disabled or not configured, the installation of the Oracle Configuration Manager will fail. To install in this environment, set the environmental variable CCR_DISABLE_CRON_ENTRY=true export CCR_DISABLE_CRON_ENTRY and re-start the installation.

Error in processing ECM_OS_FILESYSTEM metric collection error in log file ------------------------------------------------------------------------------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 thru 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 filesyste m is mounted.