Connector Framework Release Notes
10g Release 2 (10.2.0.2)
B31145-01
September 2006
These release notes describe:
How to access the documentation
Key features of the Connector Framework
Prerequisites before using the Connector Framework
How to install the Connector Framework
Configuring and using the Connector Framework
Known issues for this release
You can access the documentation for the Connector Framework from the Oracle Technology Network (OTN). You can find data sheets, the certification matrix, and other documentation in the OTN under Enterprise Manager and in Metalink.
The Connector Framework provides clients with the following capabilities:
Query Enterprise Manager data through a unified web services interface.
Request Enterprise Manager to create a Real Application Clusters (RAC) database through a web services interface.
Request Enterprise Manager to add nodes to existing RAC databases through a web services interface.
Request Enterprise Manager to delete nodes from existing RAC databases through a web services interface.
The Connector Framework has the following system requirements:
Oracle Enterprise Manager Management Server version 10.2.0.2
Oracle Enterprise Manager Management Agent version 10.2.0.2
Oracle Database version 10.2.0.2
For the Connector Framework to function properly, you need to set up emcli. For a procedure on how to do this, see the Oracle Enterprise Manager Connector Framework Integration Guide (B31191-01).
For security purposes, the OMS should be set up using HTTPS.
The Connector Framework is installed to the OMS home. The $ORACLE_HOME in the procedure below refers to the OMS home. To download and install the Connector Framework, do the following:
Download the Connector Framework installable files from OTN by clicking Downloads, then Enterprise Manager.
Stop OMS by running:
$ORACLE_HOME/opmn/bin/opmnctl stopall
Start the Oracle Universal Installer (OUI) by running the following command:
For Linux or Unix:
$ORACLE_HOME/oui/bin/runInstaller
For Windows:
$ORACLE_HOME\oui\bin\setup
When prompted by OUI, locate products.xml in the installation source directory:
connectors/framework/10.2.0.2/1.0/source/Disk1/stage
Follow the instructions in the OUI screens.
Access the Enterprise Manager web console from one of the following URLs:
http://server:port/em/connector/ManagementService
https://server:port/em/connector/ManagementService
The Connector Framework is installed to the OMS home. The $ORACLE_HOME in the procedure below refers to the OMS home. To uninstall the Connector Framework, do the following:
Stop OMS by running:
$ORACLE_HOME/opmn/bin/opmnctl stopall
Start the Oracle Universal Installer (OUI) by running the following command:
For Linux or Unix:
$ORACLE_HOME/oui/bin/runInstaller
For Windows:
$ORACLE_HOME\oui\bin\setup
Click Deinstall Products..., open the list under OMS home, then open the list under the connector to be uninstalled.
Select the connector to be uninstalled and Connector Framework 1.0.0.0.0 under it, then click the Remove… button.
Click Yes for confirmation, then exit OUI.
Manually delete the following section from $ORACLE_HOME/j2ee/OC4J_EM/applications/em/em/WEB-INF/web.xml:
Example 1 Code for Management Service Interface for Connector Framework
<description>Management Service Interface for Connector Framework</description>
<servlet>
<servlet-name>ManagementService</servlet-name>
<servlet-class>oracle.j2ee.ws.StatelessJavaRpcWebService</servlet-class>
<init-param>
<param-name>class-name</param-name>
<param-value>oracle.sysman.connector.base.mgmtsvc.
ManagementServiceImpl</param-value>
</init-param>
<init-param>
<param-name>interface-name</param-name>
<param-value>oracle.sysman.connector.base.mgmtsvc.
IManagementService</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>ManagementService</servlet-name>
<url-pattern>/connector/ManagementService</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>35</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
Start OMS by running:
$ORACLE_HOME/opmn/bin/opmnctl startall
To understand how to configure and use Connector Framework release 10.2.0.2, refer to the Oracle Enterprise Manager Connector Framework Integration Guide (B31191-01). The Enterprise Manager documentation library for this release is located at the following URL:
http://download-west.oracle.com/docs/cd/B16240_01/doc/nav/portal_booklist.htm
The following universal limitations and known issues apply to this release of the Connector Framework.
Only CFS and ASM storage types are currently supported.
Only one disk group is currently permitted. Consequently, you need to disable flash_recovery when manually installing RAC.
The Connector Framework only supports English in the Enterprise Manager credential user name, CRS/RAC AggregateTarget name, and node target name.
The system integrated with Enterprise Manager through the Connector Framework should create the RAC database through the software library image before it can add a node to the RAC.
Enterprise Manager does not currently provide context-sensitive help for the Connector Framework. This feature will be supported in the future.
The OS credential for all the hosts in the cluster must be the same.
After deleting a node, the deleted node must be added back first before adding any other node.
The first node in the RAC (the one specified in the Create RAC job) cannot be deleted through the connector.
For the Linux platform:
The user running jobs on the target machine must be in the oinstall group.
With CFS storage, the rac_database aggregate target name must be in uppercase.
For the Windows platform:
The rac_database aggregate target name and the database instance name must be in uppercase.
The oms_delete_all_targets property must be set to true for Delete Node jobs.
The following known issues have available patches.
When you create a RAC database or add a new node, you cannot automatically set the monitoring credential for the Agent.
Install the following OMS patch:
MetaLink 5186115: p5186115_10202_GENERIC.zip
(Bug 5186115)
You cannot create a RAC if the public interfaces are on a private network.
For the Linux platform, install the following database patch:
MetaLink 5256865: p5256865_10202_LINUX.zip
For the Windows platform, install the following database patch:
MetaLink 5383042: p5383042_10202_WINNT.zip
There are three issues for patch MetaLink 5256865. Follow the steps below as a workaround:
Before applying the patch, comment out the following line in file 5256865/custom/scripts/postrootpatch.sh:
$CHMOD u-w $CH/lib/* (line 237)
Before applying the patch, add the two entries cv/remenv/exectask and cv/remenv/exectask.sh to both of the following files:
5256865/custom/scripts/postpatch.sh (line 29)
5256865/custom/scripts/prepatch.sh (line 86)
After applying the patch, edit file $DB_HOME/bin/cluvfy to set ORA_CRS_HOME to the correct CRS_HOME.
(Bug 4437727)
Install the following Agent patch:
MetaLink 5218082: p5218082_10202_GENERIC.zip
The Agent patch should be applied to the target computers to run the RAC provisioning jobs.
(Bug 5218082)
Install the following OMS patch:
MetaLink 5467873: p5467873_10202_GENERIC.zip
Install the following Agent patch:
MetaLink 5533210: p5533210_10202_GENERIC.zip
The Agent patch should be applied to both the Enterprise Manager server and the target computers to run the RAC provisioning jobs.
(Bug 5467873)
The following sections document known issues pertaining to RAC.
The workaround is to use an uppercase database instance name.
(Bug 5439927)
Example 2 Workaround in the Request Model for 5439927
<AggregateTarget>
<Name>RAC1</Name>
<Type>rac_database</Type>
<Target>
<Name>RAC1_RAC11</Name>
<Type>oracle_database</Type>
…
</Target>
<Property>
<Name>gdbName</Name>
<Value>RAC1</Value>
</Property>
<Property>
<Name>sid</Name>
<Value>RAC1</Value>
</Property>
…
</AggregateTarget>
The workaround is to set the oms_delete_all_targets property to be true in the rac_database aggregate target. Otherwise, restart the target and manually delete DB HOME.
(Bug 5513165)
After you remove a node from an existing RAC, the host target still remains in the cluster target. You must manually remove the host target from this cluster target before you reuse this host.
The workaround is to set the oms_delete_all_targets property to be true in the rac_database aggregate target. Otherwise, you will need to manually delete the host from the cluster through Enterprise Manager as follows:
From Enterprise Manager, select the Targets tab, then the All Targets tab.
Select the Cluster target from the Search drop-down list, then click Go.
Select the target, then click Configure. The Configure Target page appears.
Remove the membership of the node you removed from the RAC, then click Update.
(Bug 5166979)
The following sections document known issues pertaining to DBCA.
The workaround is to change the database instance to lowercase for DBCA. The Connector Framework automatically takes care of this.
(Bug 5451904)
Workaround for the Linux platform:
Use uppercase letters for the rac_database aggregate target name when the storage is CFS.
Workaround for the Windows platform:
Use uppercase letters for the rac_database aggregate target name whether or not the storage is CFS. The Connector Framework changes the gdb name to uppercase for DBCA in case you forget to do so.
(Bug 5359240)
Example 5 Workaround in the Request Model for 5359240
<AggregateTarget> <Name>RAC1</Name> <Type>rac_database</Type> <Target> <Name>RAC1_RAC11</Name> <Type>oracle_database</Type> … </Target> <Property> <Name>gdbName</Name> <Value>RAC1</Value> </Property> <Property> <Name>sid</Name> <Value>RAC1</Value> </Property> … </AggregateTarget>
The workaround is to use orapwd to generate the password file for the database instance and ASM instance if the storage type is ASM. The Connector Framework automatically takes care of this.
(Bug 5451945)
The following sections document issues unrelated to RAC or DBCA.
The workaround is to pass in %perlbin% as an argument. The Connector Framework automatically takes care of this.
(Bug 5099754)
The workaround is to use different CVU commands for the Linux platform. The Connector Framework automatically takes care of this.
The Windows platform does not require a workaround, because the exit code of CVU would be zero even when the command fails (bug 5467164).
(Bug 5513197)
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.
Connector Framework Release Notes, Release 2 (10.2.0.2)
B31145-01
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 USA, Inc., 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.