| Oracle® Enterprise Manager Agent Release Notes for Windows 10g Release 2 (10.2) Part Number B25968-02 |
|
|
View PDF |
| Oracle® Enterprise Manager Agent Release Notes for Windows 10g Release 2 (10.2) Part Number B25968-02 |
|
|
View PDF |
Agent Release Notes for Windows
10g Release 2 (10.2)
B25968-02
February 2006
These Release Notes identify differences between the delivered Oracle Enterprise Manager Management Agent Release 10.2.0.1 product and its documented functionality.
Note:
To check for updates to this document and view other Oracle documentation, see the Documentation section on the Oracle Technology Network (OTN) Web site:This document contains the following sections:
This section addresses installation issues.
When 10.2.0.1 Management Agent and CMSDK's "ifsctl start" are installed on the same machine, you may encounter an exception when you run "ifsctl start" on that machine to start the CMSDK domain controller. This is because the 10.2.0.1 Management Agent install prefixes its directories to the path of the system environment variable.To avoid this exception, manually remove $AGENT_ORACLE_HOME related entries from the system environment variable "PATH", and then run "ifsctl start".
(Bug 4883113)
On Microsoft Windows, the Agent Config Assistant for a 10.2 installation and the Upgrade Assistant for a 10.1 to 10.2 upgrade fail if any directory or subdirectory in the installation path begins with the letter "u".
To avoid this problem, ensure that directories and subdirectories in your installation path begin with letters other than "u".
(Bug 4879597)
When Agent-only installation is performed on the RAC environment by selecting multiple nodes, only Host and cluster targets get discovered on all the nodes. For discovering other targets, you have to maually perform the discovery on all the nodes. To do so, use the following command:
<ORACLE_HOME>/bin/agentca.bat -f -c "node1,node2..."
For example:
<ORACLE_HOME>/bin/agentca.bat -f -c "staio05,staio06"
(Bug 4766358)
In the NT Real Application Clusters (RAC) Agent install scenario, after you reconfigure a secured Management Agent using the "<AGENT_HOME>/bin/agentca -f" script, check its status. Ideally, the Management Agent should have regained its secured status in spite of being reconfigured. However, if the Management Agent is not secured, manually secure it by running this script:
<AGENT_HOME>/bin/emctl secure agent <PASSWORD>
(Bug 4912661)
While cloning 10.2.0.1 Management Agent, if the installation process hangs at the configuration phase, run the agent cloning installation process in "noconfig" mode, and then run the "agentca" script for "config and discovery".
First run the agent cloning installation process in "noconfig" mode from ORACLE_HOME:
<ORACLE_HOME>/oui/bin/setup.exe -clone -forceCLone ORACLE_HOME=<value of oracleHome> ORACLE_HOME_NAME=<oracle_home_name> -noconfig
After the installation, go to <ORACLE_HOME>/bin and run the "agentca" script:
<ORACLE_HOME>/bin/agentca -f
(Bug 4900980)
When database targets are discovered after a Management Agent is installed, their status in the Enterprise Manager Grid Control console appears as "Unavailable". This is because Grid Control is not updated with the password for "dbsnmp", and as a result, it is unable to monitor and manage database targets.
To resolve this issue, configure the database targets. In the Enterprise Manager Grid Control console, click the Database subtab (under Targets tab), select the database target you want to configure, and click Configure. On the Configure Database Instance: Properties page, provide the password.
(Bug 4954787)
On Microsoft Windows 2000, you may not be able to invoke Oracle Universal Installer to install the Management Agent if there are innumerous Java processes running on that machine.
To resolve this issue, run the following command:
setup -J-Dsun.java2d.noddraw=true -Dsun.awt.nopixfmt=true
(Bug 4376855, 5020783)
This section addresses the upgrade issues.
In the NT RAC agent upgrade scenario, even after the Agent-only installer completes the upgrade and shows a success message, the Management Agent may not start on any of the nodes.
In order to complete all configurations and have the Management Agents start on any of the nodes, you have to execute the upgrade utility on every single node in the RAC. The executable is <new_home>/oui/bin/<host_name>.upgrade.bat, where <host_name> is the full-qualified host name.
For example:
<new_home>/oui/bin/chyu-pc.us.oracle.com.upgrade.bat
(Bug 4901299)
After a Management Agent is upgraded, the port configurations are retained, and you should keep using the same ports for all the agent functions. The portlist.ini file may not contain the complete or correct port numbers.
(Bug 4889872)
When the Management Agent is upgraded, a new Oracle Home directory is created for it. Any scripts referenced by OS-based User-Defined Metrics that are located in the 10.1.0.4 Management Agent's Oracle Home directory will not be copied into the newly created Oracle Home directory.
To ensure that OS-based User-Defined Metrics continue to work, the original Oracle Home directory of the 10.1.0.4 Management Agent must not be deleted unless all the User-Defined Metric scripts are copied into a new directory (preferably outside any existing Oracle Home) and the User-Defined Metrics definitions have been updated in the Enterprise Manager Console to reflect the new script locations.
(Bug 4768845)
This section addresses performance issues.
If the process nmupm consumes too much CPU time, verify that the performance counters perfDisk,perfProc, and perfOS are not disabled. For example to check PerfOS service, go to the registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance
Check if there is an entry 'DisablePerformanceCounters' with the value "1". If there is one, change the value of this entry to "0". Similarly check and set the entries for perfDisk and perfProc.
More information on how to set these entries can be found at:
(Bug 4894672)
On Microsoft Windows, when you run out of desktop heap, you may encounter errors such as: "The application failed to intialize properly (0xc00000142)".
Click OK to terminate the application. This sometimes makes the machine unusable.
To circumvent this issue, you need to increase the desktop heap size. To do this, open the registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows
Look at the entry SharedSection. It usually has three values separated by commas. To increase the desktop heap size for non-interactive desktops, the third value needs to be modified. Change its value to "3072", and reboot the machine for the changes to take effect.
More detailed information about this can be found at:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;184802
A related Microsoft KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824422
(Bugs 4867529, 4768354, and 4765172)
This section addresses application server status issues.
Using Enterprise Manager Grid Control 10.1.0.x (10.1.0.4, 10.1.0.5), if you visit the home page of an OC4J, Oracle HTTP Server, or OracleAS Web Cache target that is being monitored by a 10.2 Management Agent, the "Up Since" value in the General Section will always be "Unavailable".
(Bug 4882496)
When a discovery of application server targets is initiated from the Enterprise Manager Grid Control console, an IO exception error is displayed even though the operation is successful. Ignore this message if the application server targets are successfully added to Enterprise Manager Grid Control.
(Bug 4714617)
When a Management Agent is installed on a host that already has application server targets installed on it, an auto discovery is initiated by the Management Agent after its installation and all the application server targets in that environment are listed in the Enterprise Manager Grid Control console.
When you try to remove any of those listed application server targets using the Enterprise Manager Grid Control console, the selected target gets deleted from the console as well as the central agent. However, the centralagent.lst file in IAS_HOME, which contains entries for central agents monitoring this IAS, does not get updated accordingly. As a result, when you perform a rediscovery of this IAS target from the central agent, this discovery does not happen appropriately.
To circumvent this issue, access the centralagent.lst file from IAS_HOME/sysman/emd, and manually delete the entry for the central agent of the IAS target you just removed from the console.
(Bug 4995039)
This section addresses third-party application server monitoring issues.
When you use the Enterprise Manager Grid Control console to stop an IBM WebSphere Application Server Cell instance, the instance stops and remains in "Down" status for a short while but restarts automatically within few minutes and changes its status to "Up" without any manual intervention. As a result, you may also encounter errors when you try to manually restart this instance.
To workaround this issue, use the Administer link provided on the home page to access the IBM WebSphere Administration console, and perform all stop and restart operations from that console.
(Bug 5021239)
This section addresses backup and recovery issues.
On Microsoft Windows, while recovering applicaion server targets, you may see the message "Backup you selected does not exist". This message is valid when backup is not available in the backup directory. However, sometimes this message is displayed even when backup is available on Oracle Management Service.
To fix this issue, apply ARU patch 8108087 to the Management Service, and then recover the application server targets. To obtain the patch, access the Automated Release Updates (ARU) site at http://aru.us.oracle.com, click Patches, and search for patch request number 8108087.
(Bug 4639053)
The output of the offline backup job on Microsoft Windows databases will have extra lines at the end with errors for removing temporary files and directories. These errors have no influence on the job status. They can be ignored.
(Bug 4716400)
This section addresses web cache management issues.
Using Enterprise Manager Grid Control 10.1.0.x (10.1.0.4, 10.1.0.5), if you visit the home page of a 10.1.2 OracleAS Web Cache, there will be two "Administer" links displayed in the Related Links section.
(Bug 4882466)
This section addresses data guard management issues.
When using the Data Guard Verify Configuration function to add standby redo log files to a logical standby, an ORA-16826 warning may be encountered.
To clear the warning, select the logical standby database in the Data Guard overview page, then click Edit. On the General Properties page, click Reset to clear the warning.
(Bug 4652272)
This section addresses Oracle Collaboration Suite (OCS) management issues.
You may encounter an internal server error when you define a generic aggregate service (or system target), and add the OCS sub-component service as one of its members. This is because an OCS sub-component service (e.g. Email User Access Service, Calendar User Access Service) cannot have multiple parent services associated with it.
To fix this issue, apply ARU patch 8107532 to the Management Service, and then configure the OCS services. To obtain the patch, access the Automated Release Updates (ARU) site at http://aru.us.oracle.com, click Patches, and search for patch request number 8107532.
(Bug 4890876)
You may encounter an internal server error when you add a new OCS sub-component service (e.g. Email User Access service, Calendar User Access service, etc) from the Configure Component service page. This may happen if the OCS component service name contains multibyte characters.
To fix this issue, apply ARU patch 8111452 to the Management Service, and then configure the OCS services. To obtain the patch, access the Automated Release Updates (ARU) site at http://aru.us.oracle.com, click Patches, and search for patch request number 8111452.
(Bug 4860550)
You may see error messages while adding OCS component services (e.g. Email Service, Calendar Service, etc). This may happen if the number of discovered agent monitored targets exceeds 100.
To fix this issue, apply ARU patch 8107532 to the Management Service, and then configure the OCS services. To obtain the patch, access the Automated Release Updates (ARU) site at http://aru.us.oracle.com, click Patches, and search for patch request number 8107532.
(Bug 4758081)
On Microsoft Windows, while configuring Real-Time Collaboration Service and Calendar Service, you may see incorrect data displayed on the System/Services Test Properties page. This is because the test properties are not discovered correctly for these services.
To fix this issue, apply ARU patch 8107532 to the Management Service, and then configure the OCS services. To obtain the patch, access the Automated Release Updates (ARU) site at http://aru.us.oracle.com, click Patches, and search for patch request number 8107532.
(Bug 4758013)
This section addresses documentation issues.
The help system does not have information about the new licensing packs and plug-ins.
(Bug 4686894)
After the Oracle Management Service is started or restarted, it may take a long time for the help browser to display the online help system the first time it is invoked. For all subsequent help use, topics display immediately.
To fix this performance problem, apply ARU patch 8083686 to the Management Service. This patch fixes the problem with help browser performance and provides the full set of online help files. To obtain the patch, access the Automated Release Updates (ARU) site at http://aru.us.oracle.com, click Patches, and search for patch request number 8083686.
(Bug 4865772)
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle Enterprise Manager Agent Release Notes for Windows, 10g Release 2 (10.2)
B25968-02
Copyright © 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
