This chapter decribes the installation and configuration issues encountered for Oracle Configuration Manager (OCM) for the following platforms:
This section describes the installation and configuration issues encountered that are specific to the Windows platform:
RAC Installs: OCM Does Not Pick Up Oracle Home Name for Its Service Names
OCM Upgrade to 10.3.5 Fails When Using the -distribution Option
getHttpClientClasspath Variable Undefined Error After Upgrade to OCM 12.1
When there is an Oracle Configuration Manager upgrade failure on the Windows environment, the log file is named update2.log.
For some Real Application Cluster (RAC) 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)
-distribution OptionWhen 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)
Error: "%ORACLE_CONFIG_HOME% refers to a non-existent directory"
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.
Error: 'Input Error: There is no file extension in "<directory>"'
When installing Oracle Configuration Manager (OCM), 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.
Installing Oracle Configuration Manager (OCM) on a Windows NFS shared drive fails with an error.
OCM must be installed on a local, non-removable, writeable drive. Unless the drive type is set to fixed, OCM may not be supported. The drive type should be set to fixed before the OCM Collector can be configured.
For instructions for setting the drive type property, see:
https://msdn.microsoft.com/en-us/library/ys4ctaz0%28v=vs.84%29.aspx
(Bug 20234326)
After applying the patch to upgrade to OCM 12.1, OCM does not start manually. Running the emccr start command generates an error.
Workaround: Start the service manually from services.msc. Look for Oracle<oracle_home><oracle_config_home>ConfigurationManger service and start it manually.
(Bug 18107265)
Error: Variable is undefined: 'getHttpClientClasspath'
The OCM version present in the home might be much higher as compared to the version present being shipped as part of patch. If OCM is installed and configured already, it should not be over-written with another fresh kit during upgrade of the product.
Workaround: Copy the ccr\inventory\*.jar files to the ccr\inventory\pending directory and override when asked for conflict. Once copied, run the ccr\bin\deployPackages command.
(Bug 18004161)
This section describes the installation and configuration issues encountered for Linux, Solaris, and Unix platforms:
OCM Fails During Installation of Oracle Database Release 11.2 on Linux x86-64
Error Initializing JVM When Installing Oracle Configuration Manager
Installation of the Oracle Configuration Manager fails, with the following error in $ORACLE_HOME/ccr/hosts/<hostname>/log/install-core-*.log, indicating a relink issue. The log file contains records such as:
skipping incompatible /usr/lib64/gcc/x86_64-suse-linux/4.3/libgcc.a when searching for -lgcc /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: cannot find -lgcc collect2: ld returned 1 exit status
The problem occurs on a 64-bit Linux system where the 32-bit libraries are not installed. Install the native Linux x86_bit kit located on the My Oracle Support site (http://support.oracle.com).
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 following sections apply for all platforms:
To enable debug logging by the collector, add the following property to the collector.properties file.
log4j.rootCategory=DEBUG, Rolling
If the $ORACLE_CONFIG_HOME variable was defined for the deployment of the collector, the location of the collector.properties file is the $ORACLE_CONFIG_HOME/ccr/config directory.
Otherwise, add the property to the <INSTALLED_PRODUCT_ROOT>/ccr/hosts/<hostname>/config/collector.properties file.
Note that debug logging of the collector consumes space. Once you have completed the debugging task, remove the added entry from the collector.properties file to resume the previous behavior.
To have Perl scripts generate debugging output when the collection is run, set EMAGENT_PERL_TRACE_LEVEL=1 and run emSnapshotEnv.
To see all the steps performed throughout the execution of the setupCCR, configCCR, and deriveCCR commands, set the CCR_DEBUG environment variable to 1. We suggest that the output be redirected to a file. This enables you to send the file to Oracle Support if needed.
This section describes some of the errors you may encounter while you work with Oracle Configuration Manager and provides possible solutions to these errors:
Insufficient Privileges While Running installCCRSQL collectconfig
Incorrectly Configured Hostnames are Displayed in My Oracle Support
Oracle Home Environmental Changes not Detected During Collection
When you run the installCCRSQL.sh script, it creates the ORACLE_OCM user and sets up a job to collect database configuration information. The ORACLE_OCM user requires EXECUTE privileges on UTL_FILE and DBMS_SCHEDULER for database versions 10g or higher, and on the DBMS_JOB for pre-10g databases. If these privileges are granted to PUBLIC, the ORACLE_OCM user inherits these privileges, otherwise these privileges are explicitly granted when the installCCRSQL.sh script is executed. If the inherited privileges are revoked, the following errors indicating the lack of privileges will be logged in the alert_log:
ORA-12012: error on auto execute of job 52 ORA-04068: existing state of packages has been discarded ORA-04063: package body "ORACLE_OCM.<package name>" has errors ORA-06508: PL/SQL: could not find program unit being called
To resolve these errors, you must grant the missing EXECUTE privilege to the ORACLE_OCM user.
For database versions 10g and higher, grant EXECUTE privileges on the UTL_FILE and DBMS_SCHEDULER packages to the ORACLE_OCM user by entering the following SQL*PLUS commands:
SQL> grant execute on UTL_FILE to oracle_ocm; SQL> grant execute on DBMS_SCHEDULER to oracle_ocm; SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile; SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
For pre-10g databases, grant EXECUTE privileges on the DBMS_JOB package to the ORACLE_OCM user by entering the following SQL*PLUS commands:
SQL> grant execute on UTL_FILE to oracle_ocm; SQL> grant execute on DBMS_JOB to oracle_ocm; SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile; SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
To ensure that hostnames are displayed with their fully qualified names on My Oracle Support, the /etc/hosts file must contain an entry that includes both the hostname and the domain in the following format:
<IP-Address> <Full-HostName> <Short-HostName>
For example:
10.10.10.10 myhost.mydomain myhost
If the /etc/hosts file has not been correctly configured, only the short name is displayed on My Oracle Support.
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, ORACLE_CONFIG_HOME, IAS_CONFIG_HOME, ORACLE_INSTANCE, JAVA_HOME, TZ, TNS_ADMIN, CRS_HOME, CLUSTER_NAME, LD_PRELOAD, ORAINST_LOC, BEA_HOME, and WL_HOME.
The following sections describe the known issues with OCM:
Exadata Target Associations Not Displaying Properly in My Oracle Support
Cloning an OCM Installation Setup in Compatibility Mode Fails
OCM Collector Installed in Siebel Server and Gateway Directory Trees
Stale Associations for Virtual Machines Reflected in My Oracle Support UI
Termination of setupCCR/configCCR Commands Returns Configuration Message
Start Date, Last Collection and Next Collection Times Inconsistent
Error When Reviewing Collected Configuration Information with Mozilla
Could not create service <name> : 1072 during software installationMetric Collection Error in Log File
OCM Fails When Patching Oracle Identity Management and Oracle Web Tier
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 host.example.com_2:oracle_dbmachine:split_no:2"
(Bug 14697857)
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
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.
Note:
For virtual machine collections, it takes 24 hours to reflect the state change.setupCCR/configCCR Commands Returns Configuration MessageAn 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.
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.
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.
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)
Error: Java version not able to be identified
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.
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 running the ls command 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.
If a user home directory does not have write permissions, then OCM returns the following error:
chmodFile.sh returned:1
Workaround:
Set the CCR_USER_HOME environment property variable to a directory where user of OCM has write permissions
Run the following command to allow the OCM collector to capture the new property:
ccr/bin/emSnapshotEnv
Once you complete the steps above, you should no longer see the error.
(Bug 17895226)
If you are upgrading Oracle Identity Management or Oracle Web Tier to 11g Release 1 (11.1.1.9.0) from any release prior to and not including 11g Release 1 (11.1.1.6.0), and you did not previously configure Oracle Configuration Manager (OCM), then OCM will fail if you decide to configure it in 11g Release 1 (11.1.1.9.0).
Workaround:
To work around this issue, follow the steps below prior to running the 11g Release 1 (11.1.1.9.0) configuration wizard:
Navigate to the ORACLE_HOME/ccr/bin directory.
Run the following commands:
setupCCR configCCR emCCR collect emCCR status
If you choose to skip the OCM configuration when you initially run the 11g Release 1 (11.1.1.9.0) configuration wizard, but then choose to configure it later, then follow the steps below:
Navigate to the ORACLE_HOME/ccr/bin directory.
Set the ORACLE_CONFIG_HOME environment variable to your instance home directory.
Run the following commands:
setupCCR configCCR emCCR collect emCCR status
(Bug 16450488)