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 Oracle VM. It includes these items:
Intermittent errors have been reported when using Oracle VM. If you receive an error that includes oracle.ovs.biz, check the Oracle VM logs to ensure you understand the root cause of the problem. In some cases, simply reattempting 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
Oracle VM supports handling an appliance with up to 26 virtual disks. If you attempt to perform operations to create a larger number of virtual disks, you will experience a failure and an error message indicating that a 'disk image declared in the OVF does not exist in the OVA.'
Although you must supply a VNC password when creating templates, and can override this password in a deployment plan, neither of these values will actually take effect. You must access virtual machine VNC consoles through the Oracle VM Manager console, using the appropriate credentials as defined by Oracle VM Manager.
This section describes issues for Oracle WebLogic Server. It includes these items:
Forward Slashes in Server Service Names Cause Oracle WebLogic Server Deployment Failures
Applications with JDBC Remap May Need to be Manually Restarted
Applications Accessing Web Services Not Updated at Deployment
Admin URL Required to be Specified When Managed Server is No Longer Running
WLS Plug-in Does Not Support Changing Ownership of File Sets
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.
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.
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.
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.
The Oracle WebLogic Server plug-in does not support changing the ownership of file sets. The default 'oracle' user must be used or unexpected results, including possible deployment failure, could result.
You observe an error where servers in an Oracle WebLogic Server cluster cannot start through Node Manager. This error can occur if you have relocated your Node Manager home, which is not supported. Specifically, the node manager configuration at introspection time only occurs when the nodemanager.properties file resides in the <weblogic_home>/common/nodemanager directory.
This section describes issues for Oracle Web Cache. It includes these items:
If Oracle WebCache has been registered with Enterprise Manager and is introspected, the resulting Enterprise Manager registration output cannot be connected to the Oracle WebLogic Server Admin server input due to a protocol mismatch.
The workaround is to manually edit the appliance.xml file for Oracle Web Cache. Under $AB_INSTANCE/catalog/metadata find the appliance.xml file for the Oracle Web Cache component. Edit it and search for the 'EMRegistration' output. Change the protocol from 'HTTP' to 'http'. You should now be able to connect the output to the Oracle WebLogic Server Admin server input.
Oracle Virtual Assembly Builder does not support the deployment of an Oracle Web Cache appliance with a privileged port (a port number less than 1024) as its administration port.
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:
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 capturing the file sets, 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.
This section describes issues for Oracle Forms and Oracle Reports. It includes these items:
After deploying an assembly, in Oracle HTTP Server, Oracle Forms and/or Oracle Reports deployed virtual machines, change the ownership of the following files to the "root" user:
$ORACLE_HOME/bin/nmo
$ORACLE_HOME/bin/nmb
$ORACLE_HOME/bin/nmhs
Alternatively, you can run $ORACLE_HOME/bin/root.sh as the root user which sets the right ownership on these files.
Not having the ownership set to "root" for these files impacts the Oracle EM Agent's ability to collect performance metrics.