Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices
The section contains information on known issues you may encounter when installing Oracle VM Manager, and explains how to resolve them. You can find additional information on the following Oracle Support Web sites:
Oracle MetaLink:
Oracle Technology Network virtualization forum: https://forums.oracle.com/forums/forum.jspa?forumID=823
If you contact Oracle Support for assistance with an Oracle VM Manager installation, please include the installation logs. See Section 4.4.5, “Installation Logs” for information on log file names and locations.
The Oracle VM Manager installer performs a standard install of the MySQL RDBMS RPM or PKG. Database files are located at /u01/app/oracle/mysql/data. A standard init script is created at: /etc/init.d/ovmm_mysql. This script can be used to start, stop, restart and obtain the status of the MySQL server:
# /etc/init.d/ovmm_mysql restart
Configuration for the OVMM MySQL instance is contained in /u01/app/oracle/mysql/data/my.cnf. Editing this file may break your Oracle VM Manager installation. Do not edit it without instruction from a support representative.
MySQL events are logged in a log file located at /u01/app/oracle/mysql/data/mysqld.err
The following error is displayed during installation if the prerequisite libaio package is not installed:
libaio is not installed...
Workaround: Install the libaio package. For information on how to install libaio, see Section 4.3.2.5, “Prerequisite Packages”.
The Oracle VM Manager installer may fail to install MySQL and displays the message:
Failed: The database instance is not available.
You can check the log file at /tmp/ovmm-installer.selfextract_id/ovm-manager-3-install-date.log for more detailed information.
Workaround: There are two workarounds to this issue.
Make sure that MySQL is not installed, or has installed correctly. Use the following command to check the status:
$ /etc/init.d/ovmm_mysql status
If MySQL is running, run the Oracle VM Manager installation script to uninstall it, and reinstall Oracle VM Manager.
Make sure the computer's host name matches the host name in the /etc/hosts file. See Section 4.3.2.2, “Network” to configure the host name.
You may encounter the following message:
Creating the Oracle VM Manager database schema ... Failed.
You can check the log file at /tmp/ovmm-installer.selfextract_id/ovm-manager-3-install-date.log for more detailed information.
Workaround: Possible workarounds for this issue are:
Make sure that MySQL has installed correctly. Use the following command to check the status:
$ /etc/init.d/ovmm_mysql status
If MySQL is running, run the Oracle VM Manager installation script to uninstall it, and reinstall Oracle VM Manager.
If you are installing into an existing Oracle database, make sure that you have entered the correct password for the SYS account.
Reinstall Oracle VM Manager.
If the installer fails after creating the Oracle Database OVS schema, but before the end of the installation process is complete, you may end up with a schema that cannot be overwritten when you attempt to perform the install again. To resolve this issue, you should drop the OVS schema, then continue with the reinstall again when you have resolved the install problem.
To drop the OVS schema, log into the Oracle Database as the sys or system user and perform the following steps:
$ sqlplus system/password
SQL> drop user OVS cascade;
SQL> drop profile OVMM_PROFILE cascade;
SQL> exit;The schema name used in this example uses the default schema name, OVS. If you used a custom schema name during the installation, you should replace OVS with the name of your schema. The name of your schema is located in the Oracle VM Manager configuration file located at:
/u01/app/oracle/ovm-manager-3/.config
If you are performing a Simple install using a MySQL database, uninstall and reinstall Oracle VM Manager.
If the operating system is a non-English character set or language, the Oracle VM Manager installer may display the following error:
Update default password failed.
Oracle VM Manager only supports the English language and character set.
You can check the log file at /tmp/ovmm-installer.selfextract_id/ovm-manager-3-install-date.log for more detailed information.
Workaround: Set the character set to en_US.UTF-8:
Run the following command to check if the value of LANG is
en_US.UTF-8:
# env|grep LANG
If the character set is not en_US.UTF-8,
change it to en_US.UTF-8:
# export LC_CTYPE="en_US.UTF-8"
Reinstall Oracle VM Manager.
If the oracle user account is created using NIS-based authentication (Network Information Services), the Oracle VM Manager installation fails during the prerequisite check, and the following error is displayed:
Verifying installation prerequisites ... hardnofiles should be set to 8192 but was 0 Configuration verification failed ...
Or the installation may pass prerequisite check, but may fail later during the installation of the Application Development Framework:
Retrieving Oracle Application Development Framework (ADF) ... Unzipping Oracle ADF ... Installing Oracle ADF ... Installing Oracle ADF Patch...
To workaround this issue, disable ypbind service and create a
non-NIS-based oracle user account using
createOracle.sh on the host computer and
rerun the installer:
# /sbin/service ypbind stop # service ypbind status ypbind is stopped # ./createOracle.sh # ./runInstaller.sh
Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices