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 3.3.2.5, “Prerequisite Packages”.

The following error is displayed during installation of the database if the prerequisite bc package is not installed:

Step 1 of 9 : Database ...
Installing Database ...
Retrieving Oracle Database 11g XE ...
Installing Oracle Database 11g XE ...
Configuring Oracle Database 11g XE ...
Failed to configure Oracle Database 11g XE
            
[...]

Starting Oracle Net Listener...Done
Configuring database...
Database Configuration failed.  Look into /u01/app/oracle/product/11.2.0/xe/config/log for details

Workaround: Install the bc package. For information on how to install bc, see Section 3.3.2.5, “Prerequisite Packages”.

The Oracle VM Manager installer may fail to install Oracle XE and displays the message:

Failed: The database instance is not available.

You can check the log file at /tmp/ovmm-installer.selfextract_id/install-date.log for more detailed information.

Workaround: There are two workarounds to this issue.

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/install-date.log for more detailed information.

Workaround: Possible workarounds for this issue are:

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 schema OVS;
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

The Oracle VM Manager installation may fail to start the Oracle XE listener. The Oracle XE listener may fail to start because the host name in the listener.ora file is not mapped to an IP address.

Workaround: Add the IP address and host name to the /etc/hosts file. See Section 3.3.2.2, “Network” to configure the host name. Alternatively, you can specify the IP address in the listener.ora file. The listener.ora file is located in the directory:

/usr/lib/oracle/xe/app/oracle/product/11.2.0/server/network/admin

Manually start the Oracle XE listener with the command:

# /usr/lib/oracle/xe/app/oracle/product/11.2.0/server/bin/lsnrctl start

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/install-date.log for more detailed information.

Workaround: Set the character set to en_US.UTF-8:

If the oracle user account is created using NIS-based authentication (Network Information Services), the 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 ...

Workaround: Create a non-NIS-based oracle user account on the host computer and rerun the installer.