| Oracle® Virtual Assembly Builder Release Notes 11g Release 1.1 (11.1.1) Part Number E22515-02 |
|
| View PDF |
| Oracle® Virtual Assembly Builder Release Notes 11g Release 1.1 (11.1.1) Part Number E22515-02 |
|
| View PDF |
Release Notes
11g Release 1.1 (11.1.1)
E22515-02
April 2011
These release notes describe issues associated with Oracle Virtual Assembly Builder. They include the following topics:
This section describes specific issues for components that Oracle Virtual Assembly Builder can introspect. The list of issues for each component presents the most severe or frequently encountered issues first, followed by lower priority issues.
This section describes the following topics:
This section describes issues for OracleVM. It includes these items:
Section 1.1.2, "Limit Virtual Machine Names to 100 Characters or Less"
Section 1.1.3, "Limit Virtual Machine Passwords to 50 Characters or Less"
Intermittent errors have been reported when using OracleVM. If you receive an error that includes oracle.ovs.biz, check the OracleVM logs to ensure you understand the root cause of the problem. In some cases, simply reaccomplishing the task will solve the problem, but consulting the logs is the best approach.
Oracle Virtual Machine limits virtual machine names to 100 characters or less. If your names are too long, you will receive the error: oracle.ovs.biz.exception.invalidNameException: OVM-4008
Oracle Virtual Assembly Builder Deployer determines virtual machine names based on the following format:
deploymentId_subassemblyName_applianceName_instanceName0
In order to have virtual machine name length in the defined 100 character limit, the assembly name (and all subassembly names) and appliance names combined must be short enough that, when combined, are less than 100 characters.
Oracle Virtual Machine limits virtual machine passwords to 50 characters or less; your virtual machine password must be less than 50 characters long. If your password is too long, you will receive the error: Oracle.ovs.biz.exception.OVSException: OVM-5101 The template{0} cannot be found
This section describes issues for Oracle WebLogic Server. It includes these items:
Section 1.2.2, "Deployment Failure Caused by Setting plan-dir and plan-path"
Section 1.2.3, "Application Deployment Plan Causes Deployment Failure"
Section 1.2.4, "Deployment Failure Due to Missing .JAR in Base Image"
Section 1.2.5, "Oracle WebLogic Server and Oracle JRockit Virtual Edition Must Be Compatible"
Section 1.2.6, "Applications with JDBC Remap May Need to be Manually Restarted"
Section 1.2.7, "High Availability Patch for Oracle Virtual Machine, Release 2.2"
Section 1.2.8, "No SSL Support When Deploying to WebLogic Server on JRockit Virtual Edition"
Section 1.2.9, "Applications Accessing Web Services Not Updated at Deployment"
Section 1.2.10, "Limitation with Oracle WLS Domains Upgraded from 10.3.1"
Section 1.2.11, "Templates Created on Individual Servers Cannot Be Deployed"
Section 1.2.12, "Admin URL Required to be Specified When Managed Server is No Longer Running"
You can create a WebLogic Server service (such as a JMS server definition or a data source definition) with a name that contains a forward slash ( '/' ). Services with forward slashes in their names will cause WebLogic Server deployments to fail. To work around this, ensure that your WebLogic Server services do not have the '/' character in their names.
A valid configuration in config.xml for an application deployment plan can have both a <plan-dir> and a <plan-path> specified where the <plan-path> value is absolute, and the <plan-dir> value should be ignored.
Oracle WebLogic Server introspection fails if this is how the application deployment plan location is configured. To work around this issue, remove or comment out the <plan-dir> element from config.xml.
An application that has an application deployment plan configured will cause deployment of the WebLogic Server server that the application targets to fail.
To work around this issue, remove any instance of the appdeployplan.py file (found in the shared area of the catalog) before template creation. After deployment, the application deployment plan must be manually copied to the location configured in config.xml, and the application that references the plan must be started manually.
Deployment of an Oracle WebLogic Server application fails due to a missing jar. The error occurs if the following conditions are present for the application:
Part of the Oracle WebLogic Server domain
Packed during introspection as part of the domain_template.jar
Resides on an Oracle WebLogic Server assembly on Oracle JRockit Virtual Edition
This problem does not occur on the Oracle Enterprise Linux deployment because the needed library is captured as part of the reference system (the Oracle Middleware Home contains the library).
This failure does not cause the overall deployment to fail; only the Oracle WebLogic Server deployment of the applications requiring the missing libraries are affected.
To avoid this problem, use Oracle WebLogic Server JRockit Virtual Edition tools to copy over the needed libraries onto the Oracle JRockit Virtual Edition image:
Shut down the virtual machines after Oracle Virtual Assembly Builder deployment succeeds.
Use Oracle WebLogic Server JRockit Virtual Edition tools to copy the missing libraries onto the image.
Power the image back on
If you want to deploy Oracle WebLogic Server on Oracle JRockit Virtual Edition, ensure that the reference system you introspect is compatible with the Oracle JRockit Virtual Edition base image used during template creation. If you do not, the deployment will fail.
Check the certification matrix for specifics:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
An error has been reported in which an application using JDBC data source mapping configured at the application scope fails to start. The failure occurs only for deployments on Oracle WebLogic Server AdminServer, and only immediately after the AdminServer itself is deployed.
To correct this problem, manually start the AdminServer.
This issue impacts only users who have High Availability enabled for their appliance virtual machines; for users who do not have High Availability-enabled appliance virtual machines, there is no issue and no action is required.
Oracle Corporation recommends that you use Oracle Virtual Assembly Builder or Oracle WebLogic Server Node Manager to stop High Availability appliances (that is, appliances within assemblies configured as High-Availability virtual machines) running on Oracle WebLogic Server on JRockit Virtual Edition. If you want to stop these appliances using other consoles or operations, then you must install a patch that fixes a problem that erroneously restarts the appliances.
The High Availability (HA) enhancement is delivered through an updated Oracle VM agent and Xen packages which can be applied to Oracle VM Server 2.2. The new packages are available for download from Oracle's ULN (Unbreakable Linux Network at http://linux.oracle.com <http://linux.oracle.com%22>
When you navigate to that location, choose the ovm22_i386_latest channel. See the FAQ (https://linux.oracle.com/uln_faq.html<https://linux.oracle.com/uln_faq.html%22>) for detailed instructions.
After you update your Oracle VM Server 2.2 (there is no need for update if you have a new install of Oracle VM Server 2.2.1), ensure you have the required packages or later versions:
ovs-agent-2.3-38
xen-3.4.0-0.1.10
xen-64-3.4.0-0.1.10
xen-debugger-3.4.0-0.1.10
xen-tools-3.4.0-0.1.10
Because the base image for WebLogic Server on JRockit Virtual Edition does not include a demo trust store, Oracle Virtual Assembly Builder does not support SSL when deploying to WebLogic Server on JRockit Virtual Edition. This means that you cannot introspect and then deploy to WebLogic Server on JRockit Virtual Edition those domains that have the domain-wide admin port enabled.
There may also be issues with enabling SSL ports for WebLogic Server on JRockit Virtual Edition. You must configure SSL, post-deployment, for WebLogic Server on JRockit Virtual Edition.
An application that accesses a Web service that is also hosted on the Oracle WebLogic Server reference system will not be updated to point to the new web service location upon deployment. You must update the application to access the web service WSDL on the new Oracle VM host, and then redeploy the application through Oracle WebLogic Server administration tools, such as Admin Console or wlst, to the Oracle VM Oracle WebLogic Server environment.
Oracle Virtual Assembly Builder uses a pack/unpack utility when moving Oracle WebLogic Server domains. An issue with the utility causes the unpack operation to fail when using the utility to move a domain that was originally a 10.3.1 domain, but which was upgraded to 10.3.2 during installation of 10.3.2.
If you create a template on an individual server in Oracle WebLogic Server, the command line and graphical user interface operations will not indicate an error. However, such templates cannot be deployed because they lack certain deployment artifacts (the domain template jar in content, and data at the assembly level).
This issue applies to an uncommon scenario in which Oracle Virtual Assembly Builder has deployed and started the required instances in the assembly, including the Oracle WebLogic Server Managed Servers, and later the Managed Server (but not the Guest OS) has either crashed or been explicitly shutdown through an external tool.
If you want to perform manual starts from the context of the Guest-OS, you must manually modify the StartManagedServer.sh script to provide the correct Admin Server URL (Admin Server hostname). This is required because the default admin URL has the wrong value (the machine name of the Admin Server is not known at the time of template creation).
You can still start or stop the server through the node manager in Admin Console.
This section describes issues for Oracle Web Cache. It includes these items:
Section 1.3.1, "Oracle Web Cache Administration Port Not a Privileged Port"
Section 1.3.3, "Update Virtual Host Map Properties When Making Port Changes"
Oracle Virtual Assembly Builder does not support an Oracle Web Cache appliance to be deployed with its administration port being a privileged port (a port number less than 1024).
Oracle Virtual Assembly Builder does not automatically update the webcache.xml file for each instance, after you perform scaling. Even when the scaling operation completes without errors, you must still update the webcache.xml file for each instance, so that the instance recognizes all the members in the cluster.
In Oracle Web Cache, there is not necessarily a correlation between the ports in the virtual host map (VHM) elements and those in the listen elements of the Oracle Web Cache configuration. Whenever you make a port change, you must update your VHM ports by manually updating the properties associated with the VHMs.
This section describes issues for Oracle Database. It includes these items:
Section 1.4.2, "Use default name LISTENER on Reference Systems"
Section 1.4.4, "Upgraded 10g Oracle Homes Cannot be Introspected"
If the database vault has been configured in your reference system's database home, you may experience failures during some Oracle Virtual Assembly Builder operations.
In order to avoid any problems, complete these steps:
Before introspection, execute the following command on your system to temporarily disable Database Vault in the database home:
$ make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk dv_off ioracle
Re-start the database on your reference system and then shut it down.
After packaging, execute the following command on your reference system to re-enable Database Vault in the database home:
$ make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk dv_on ioracle
Re-start the database on your reference system.
After deployment, execute the following command on the new virtual machine to enable Database Vault in the database home:
$ make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk dv_on ioracle
Re-start the database on the new virtual machine.
During Oracle Virtual Assembly Builder operations, the listener on newly-created virtual machines starts using the default name LISTENER. If you used a different name for the listener on your reference system, you will receive an error. To avoid this error, ensure that you use the default name (LISTENER).
If you must use a different listener name, start your listener manually with the correct name:
$ORACLE_HOME/bin/lsnrctl start <listener name>
Note:
To view the correct listener name, see: $ORACLE_HOME/network/admin/listener.ora.The database introspector expects the listeners (the listener.ora configuration) to be configured as follows:
(ADDRESS = (PROTOCOL = TCP)(HOST = example.cm)(PORT = 5521))
Note:
The protocol, host, and port are all required, and must appear in the order above.You cannot introspect a single-instance database Oracle Home if that Oracle Home has been upgraded from Release 10g.
This section describes issues for operations for Oracle Virtual Assembly Builder studio, such as introspection, packaging, and deployment. It includes these items:
Section 2.1, "Oracle Virtual Assembly Builder Introspection Issues"
Section 2.2, "Oracle Virtual Assembly Builder Packaging Issues"
Section 2.3, "Oracle Virtual Assembly Builder Deployment Issues"
This section describes issues observed during introspection. It includes these items:
Section 2.1.1, "Remote Introspection Must Be Run as Specific Users"
Section 2.1.2, "Unable to Create Secure Connections for Multiple OVMs in a Single Session"
Section 2.1.3, "Do Not Try to Import and Register a Template at the Same Time"
The remoteUser specified for remote WLS introspection must be either the owner of the WLS process that is running on the reference system, or must be a user that has permission to read files that the owner of the WLS process creates.
You can create secure connections to multiple OVMs using Oracle Virtual Assembly Builder Studio. However, you cannot create secure connections to multiple OVMs during a single Studio session. In order to create multiple secure connections, you must create a secure connection, then exit Oracle Virtual Assembly Builder Studio. Restart Studio and create the next secure OVM connection. You must repeat this process for each desired secure OVM connection.
Do not attempt to import and register a template at the same time. Doing so will cause the registration to fail and may cause unforeseen side-effects.
This section describes issues observed during packaging operations. It includes these items:
Section 2.2.1, "Troubleshooting Template Registration Errors"
Section 2.2.2, "Packages and Templates Cannot be Shared on Registered Appliances"
If you receive an error while registering a template (such as ImportError, or any error including oracle.ovs.biz.exception.OVSException) in the Oracle Virtual Assembly Builder log file, be sure to check the Oracle VM logs for the root cause, as it may not be expressed in the Oracle Virtual Assembly Builder logs.
Multiple appliances can share packages and templates. Modifying a package on one appliance modifies the package on the other appliances in the relationship. However, after you register an appliance, that sharing no longer takes place. This is expected behavior, but users should be aware of it.
When packaging a local reference system that was installed using a different OS userid than the one used for the Oracle Virtual Assembly Builder installation, packaging will fail with file permission errors. There are two workarounds for this issue. Use either:
Run Oracle Virtual Assembly Builder as root. When you do this, all generated artifacts in catalog (such as metadata, packages, and others) are owned by the root user and all subsequent operations must also be executed as root user.
Run local packaging through remote ssh. Treat the local reference system as remote and perform remote packaging, using an ssh user that has read permission of the reference system installation.
An intermittent problem has been reported in which the status of a template is not immediately updated after the status has changed. If you encounter this issue, stop and restart Oracle Assembly Builder Studio.
This section describes issues observed during deployment. It includes these items:
Section 2.3.3, "NFS Mounting Not Supported in Reference Systems"
Section 2.3.4, "Firewall Implications for Template Registration"
Section 2.3.5, "Recovering from Unexpected Errors During Deployment"
Scale operations are affected by failed deployments.
Scale down operations only remove properly (successfully) deployed instances. In the case of failed deployments, those instances are not removed during scale down. This occurs because failed instances are left for you to troubleshoot. If you want to remove instances that failed to deploy, you must undeploy them, fix the plan, and then redeploy.
In the case of Scale up operations, it is prohibited if a failed instance(s) exists in the assembly. As above, you must undeploy, fix the problem, and then redeploy.
Deployment attempts will fail if IP addresses specified in the deployment plan are unresolved on the Oracle Virtual Assembly machine (the machine on which Deployer is running). To avoid this issue, ensure that IP addresses are resolvable.
Oracle Virtual Assembly Builder does not support NFS mounting in the reference system, since these NFS mounts will not be created by Assembly Builder in the deployment environment. In some cases, deployment will fail if the reference system has an NFS mount.
A number of third-party tools require mounting file systems as part of their configuration. This can require specific workarounds. For example, when using the Websphere MessageQueue external JMS server, you may encounter the following issues:
The configuration for the JMS Server requires access to a class provided by Websphere. In some environments, those classes (also known as jars) are added to the PRE_CLASSPATH environment variable prior to starting Oracle WebLogic Server. Ensure that the configuration for your environment does not require modification for Oracle WebLogic Server to be able to see these jar files automatically on startup.
The Oracle WebLogic Server configuration for the JMS server requires a JNDI connection URL as follows, 'file://<path to mq config>'. This file resides on the external Websphere server, and must be mounted locally so it can be used.
To allow template registration, the Oracle VM host must be able to download the template through HTTP from the Assembly Builder host. If you are using a firewall (for example, iptables on Linux) then you must properly configure that firewall to allow the communication. By default Oracle Virtual Assembly Builder specifies its HTTP port to be "0" which causes the system to issue one (so there is no default port).
You can specify the port by setting the "ovmPort" property in deployer.properties.
A simpler solution is to turn off the firewall. For iptables, use the following command: /etc/init.d/iptables stop
To configure your firewall, refer to the documentation for your firewall.
Whenever an unexpected error occurs during deployment, you typically want to examine what went wrong and perform necessary cleanup before recovering from the error. For these reasons, Oracle Virtual Assembly Builder provides neither an automatic recovery mechanism, nor a tool to recover from a failure.
To perform recovery of the Deployer:
Examine the resource pools in the corresponding Oracle Virtual Machine managers configured in the resource-pools.xml file relevant to the crashed AB_INSTANCE and perform cleanup. This includes cleaning up (stopping and destroying) all instances initiated by Oracle Virtual Assembly Builder.
Delete the .hastore file.
This returns the Deployer to a clean state.
This section describes other issues observed while performing operations in Oracle Virtual Assembly Builder. It includes these items:
When following the procedure to create resource pools using the graphical interface of Oracle Virtual Assembly Builder Studio set to the Japanese locale, the Add DNS button does not function. To work around this problem, set the locale to English:
Exit Oracle Virtual Assembly Builder
Execute the commands:
export LC_ALL= c ./abstudio.sh
Create resource pool connection in the English locale.
When large top-level items are deleted through Oracle Virtual Assembly Builder Studio, the interface may appear to have locked-up, when in fact it is running normally. This is normal behavior, allow the application to finish its task.
Ensure your virtual machines have at least 500MB of available swap space (on each machine).
Messages displayed during top-level delete of items are displayed in English only.
This section includes corrections to published documentation.
The text in Section 2.1.1 of Oracle Virtual Assembly Builder User's Guide lists an incorrect command for launching Oracle Virtual Assembly Builder Studio. This is the correct command:
$AB_INSTANCE/bin/abstudio.sh
The text in the third paragraph of Section 2.3.1.2.1 of Oracle Virtual Assembly Builder User's Guide should read:
The "config" action is executed only once at initial deployment after the VM has fully started. The "start" action is executed after a "config" action, and at any other time when the deployed VM is started (initiated either from Oracle Virtual Assembly Builder or from outside). The "stop" action is executed when the deployed VM is stopped (initiated either from Oracle Virtual Assembly Builder or from outside).
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. 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
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.
Oracle Virtual Assembly Builder, 11g Release 1.1 (11.1.1) Release Notes
E22515-02
Copyright © 2011 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 software or related documentation 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 USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software 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.
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|