10.1. Oracle VDI Installation and Configuration

10.1.1. Installation on Oracle Linux Platforms Fails Due to Missing Packages
10.1.2. Configuration on Oracle Linux Platforms Fails When SELinux is Enabled
10.1.3. Oracle VDI Configuration Is Failing to Import svc_vdadb.xml
10.1.4. Can I Try Out MySQL or Set up an Evaluation Oracle VDI Remote Database?
10.1.5. Adding a Host to an Oracle VDI Center Fails With a Sun Ray Server Software Replication Error
10.1.6. Reconfiguring Oracle VDI Fails With "Error While Configuring Database"
10.1.7. Oracle VDI Configuration Fails to Create Database Tables With Remote Windows Databases That Use UTF-8
10.1.8. Reverting to a Previous Release of Oracle VDI

10.1.1. Installation on Oracle Linux Platforms Fails Due to Missing Packages

When you install Oracle VDI on Oracle Linux platforms, the installation script checks whether the required packages are installed on the system. If any packages are missing, Oracle VDI uses the yum command to download and install them. The installation fails if the missing packages cannot be installed, and a message is displayed that lists the missing packages.

The required packages might not be able to be downloaded because no repositories are configured for yum, or if there are other problems, for example incorrect proxy configuration or network connectivity issues.

To resolve the installation problem, ensure that yum is configured properly and is working. Then install Oracle VDI again.

If you want to install the missing required packages manually, the packages are listed in the log file for the failed installation in /var/log/vda-install.timestamp.log.

10.1.2. Configuration on Oracle Linux Platforms Fails When SELinux is Enabled

On Oracle Linux platforms where SELinux is enabled (SELinux status is Enforcing or Permissive ), Oracle VDI installs correctly but configuration fails. When the configuration fails, you might see messages such as:

  • RDP Broker cannot be enabled

  • Common Agent Container (vda) cannot start

The message also lists a log file for the configuration failure, which might provide more information about the problem.

For Oracle VDI configuration to succeed, SELinux must be disabled. Use either the sestatus or the getenforce command to check the current SELinux status.

To resolve the problem:

  1. Disable SELinux.

    Edit the /etc/selinux/config file and change the SELINUX setting to SELINUX=disabled.

  2. Reboot the host to apply the SELinux configuration change.

    After the reboot, use either the sestatus or the getenforce command to confirm that the configuration change has been applied.

  3. Unconfigure Oracle VDI.

    You must unconfigure before you can configure Oracle VDI again.

    # /opt/SUNWvda/sbin/vda-config -u
  4. Configure Oracle VDI.

    # /opt/SUNWvda/sbin/vda-config

10.1.3. Oracle VDI Configuration Is Failing to Import svc_vdadb.xml

vda-config is failing to import svc_vdadb.xml because TEMP/application/database/vdadb does not get deleted. This is most commonly seen if a terminal is killed during uninstallation or configuration of Oracle VDI (vda-config/install -u), when the uninstallation/unconfiguration is run from the same Sun Ray session.

Workaround after getting the error:

  1. To recover the SVC repository's snapshot, run the following.

    # /lib/svc/bin/restore_repository
    1. When prompted with Enter Response [boot], select manifest_import instead of the default, boot.

    2. Choose the correct snapshot (manifest_import-200904??_??? - the time of backup will be in DDMMYY format).

    3. After the system reboots, check to see that svc:/TEMP/application/database/vdadb:default has been removed.

  2. Run the Oracle VDI configuration as usual.

10.1.4. Can I Try Out MySQL or Set up an Evaluation Oracle VDI Remote Database?

Yes! The MySQL Sandbox is a quick and easy way to setup MySQL or try out Oracle VDI remote database setup.

You can find it here: https://launchpad.net/mysql-sandbox.

To install a simple MySQL server just execute:

mysql-sandbox-path/make_sandbox path-to-your-mysql.tar.gz

On Oracle Solaris platforms, you might have to add /usr/sfw/bin to your path in order to make mysql_sandbox work.

More documentation about MySQL Sandbox can be found at: https://launchpad.net/mysql-sandbox

10.1.5. Adding a Host to an Oracle VDI Center Fails With a Sun Ray Server Software Replication Error

When you add a Host to an Oracle VDI Center, it might fail with the following error message:

Sun Ray Server Software Configuration
   + Configuring Sun Ray Server Software...

Error: There was an error configuring Sun Ray Server Software replication

See the log file '/var/log/vda-config.2012_04_05_16:12:43.log' for additional information.

If the log file shown in the error message contains a Signature mismatch - check configuration message, it is possible that the Sun Ray group signature has been changed using the Sun Ray administration tools. These tools do not update Oracle VDI. See Section 8.11.9, “Synchronizing the Sun Ray Group Signature and Data Store Password” for details of how to synchronize the group signature.

10.1.6. Reconfiguring Oracle VDI Fails With "Error While Configuring Database"

When you reconfigure Oracle VDI on a host, the configuration can fail with an Error While Configuring Database message and a reference to a log file for additional information.

On an Oracle VDI master database host, the log file typically contains the following:

MySQL Database Server Configuration
+ Initializing database...
...
/opt/SUNWvda/mysql/bin/mysqld: File './mysql-bin.index' not found (Errcode: 13)
110630 23:59:59 [ERROR] Aborting

110630 23:59:59 [Note] /opt/SUNWvda/mysql/bin/mysqld: Shutdown complete
...
Error: Error while configuring database.     

On other Oracle VDI hosts, the log file typically contains the following:

MySQL Database Slave Configuration
...
+ Initializing database...
110630 23:59:59 [ERROR] Fatal error: Can't change to run as user 'vdadb' ;  
Please check that the user exists!
110630 23:59:59 [ERROR] Aborting
110630 23:59:59 [Note] /opt/SUNWvda/mysql/bin/mysqld: Shutdown complete
...
Error: Error while configuring database.   

The problem is caused by the presence of a /var/opt/SUNWvda/mysql directory, which has data from a previous Oracle VDI configuration.

To resolve this problem:

  1. Log in as root on the Oracle VDI host.

  2. Unconfigure Oracle VDI on the host.

    # /opt/SUNWvda/sbin/vda-config -u
  3. Remove the directory /var/opt/SUNWvda/mysql.

  4. Configure Oracle VDI on the host.

    # /opt/SUNWvda/sbin/vda-config

10.1.7. Oracle VDI Configuration Fails to Create Database Tables With Remote Windows Databases That Use UTF-8

On Windows platforms, MySQL limits key sizes to 767 bytes. Due to this limit, the Oracle VDI configuration process fails when using a remote MySQL database on Windows platforms that have UTF-8 enabled.

There are two possible workarounds for this issue.

  1. Modify the /etc/opt/SUNWvda/vda-schema-create.sql file on your primary Oracle VDI host and configure Oracle VDI software again.

    Change the line:

    UNIQUE INDEX distinguished_name (`distinguished_name` ASC, `ud_id` ASC) ,

    to:

    UNIQUE INDEX distinguished_name (`distinguished_name`(250) ASC, `ud_id` ASC) ,

    This workaround might cause problems assigning users to pools or desktops if the distinguished name (DN) of the user is longer than 250 characters.

  2. Change the character set of the MySQL database to latin1 and configure Oracle VDI again.

    This workaround causes problems logging in users who have UTF-8 characters in their user name.

10.1.8. Reverting to a Previous Release of Oracle VDI

If a failure occurs during or just after you update an Oracle VDI Center to the latest release and you are unable to recover, it is best to revert to the previous version of Oracle VDI by restoring all the hosts in the Oracle VDI Center from your own backups.

If you do not have backups of your hosts, it is possible to revert to the previous version of Oracle VDI manually by reconfiguring the hosts and restoring the Oracle VDI database.

Steps

  1. Ensure the database backup is copied to a separate host.

    Unless you specified a file and location when you created the database backup, the backup job creates a zip file, /var/tmp/vdi-backup-timestamp.zip.

    If you cannot locate the backup zip file, a copy is included with the preserved configuration on each host in the Oracle VDI Center. The preserved configuration is stored in another zip file, /var/opt/SUNWvda/preserve/vda-preserve.zip. Unzip this file and copy the db-backup.zip file.

    If you do not have a backup of the database, you cannot revert to the previous version. Do no attempt to create a backup now.

  2. Ensure the preserved configuration zip file for each host is copied to a separate host.

    The preserved configuration zip file is /var/opt/SUNWvda/preserve/vda-preserve.zip.

  3. If you need to reinstall the previous version of Oracle VDI on a host, download the Oracle VDI software archive to a temporary location on the host.

  4. Revert Oracle VDI to the previous version on each host in the Oracle VDI Center.

    Once you begin this step, do not use Oracle VDI Manager or the vda command until the revert process has been finished on all hosts in the Oracle VDI Center.

    Start with the primary host in the Oracle VDI Center. Once you have reverted the primary, you can revert the secondaries. Only revert one secondary host at a time.

    The steps required to revert a host depend on the stage you reached when you updated the host to the latest version. Select one of the following and perform the required steps to revert the host:

  5. Restore the Oracle VDI database from the backup.

    See Section 8.7.2, “Restoring the Oracle VDI Database” for details.

Existing Oracle VDI Configuration Preserved But Latest Release Not Installed

  1. Log in as root on the host.

  2. Move the /var/opt/SUNWvda/preserve directory to a safe location.

    If you backed up the vda-preserve.zip file to a separate host when you started the update, you can delete the /var/opt/SUNWvda/preserve directory.

  3. Stop the Oracle VDI database service.

    Perform this step only if you are using the Oracle VDI embedded MySQL database.

    Oracle Solaris Platforms

    1. Stop the Oracle VDI database service.

      # svcadm disable vdadb
    2. Check that the database service is stopped.

      # svcs svc:/application/database/vdadb:default

    Oracle Linux Platforms

    1. Stop the Oracle VDI database service.

      # /opt/SUNWvda/lib/vda-db-service stop
    2. Check that the database service is stopped.

      # /opt/SUNWvda/lib/vda-db-service status
  4. Unconfigure Oracle VDI.

    # /opt/SUNWvda/sbin/vda-config -u

    It may take longer than normal to unconfigure the host.

  5. Delete the /var/opt/SUNWvda/cluster.map file.

  6. Configure Oracle VDI.

    # /opt/SUNWvda/sbin/vda-config

    When you configure a host, ensure you do not change the topology of the Oracle VDI Center. The primary and secondary hosts must retain their original roles.

  7. Restart the Oracle VDI service.

    Run the following command as root:

    # /opt/SUNWvda/sbin/vda-service restart

Latest Oracle VDI Release Installed But Not Configured

  1. Log in as root on the host.

  2. Move the /var/opt/SUNWvda/preserve directory to a safe location.

    If you backed up the vda-preserve.zip file to a separate host when you started the update, you can delete the /var/opt/SUNWvda/preserve directory.

  3. Uninstall the latest release of Oracle VDI.

    # /opt/SUNWvda/sbin/vda-install -u
  4. Reboot the host.

  5. If required, downgrade the operating system to the version of the operating system that is supported in the previous release of Oracle VDI.

  6. Install the previous release of Oracle VDI.

    Unzip the Oracle VDI software archive for the previous release and change working directory to the extracted directory.

    # ./vda-install

    At the end of the installation, you are prompted to configure Oracle VDI. Do not configure at this stage. Type n and press the Return key.

  7. Delete the Oracle VDI Center configuration files.

    If the following files exist, delete them:

    • /var/opt/SUNWvda/cluster.map

    • /etc/opt/SUNWvda/.truststore

    • /etc/opt/SUNWvda/.keystore

  8. Delete the vda instance from Cacao.

    To check if the vda instance still exists, run the following command.

    # cacaoadm list-instances

    On Oracle Linux platforms, the cacaoadm command is in /opt/sun/cacao2/bin.

    If the vda instance is listed, run the following commands:

    # cacaoadm stop -f -i vda
    # cacaoadm delete-instance -i vda
  9. Configure Oracle VDI.

    # /opt/SUNWvda/sbin/vda-config

    When you configure a host, ensure you do not change the topology of the Oracle VDI Center. The primary and secondary hosts must retain their original roles.

  10. Restart the Oracle VDI service.

    Run the following command as root:

    # /opt/SUNWvda/sbin/vda-service restart

Latest Oracle VDI Release Installed and Configured

  1. Log in as root on the host.

  2. Move the /var/opt/SUNWvda/preserve directory to a safe location.

    If you backed up the vda-preserve.zip file to a separate host when you started the update, you can delete the /var/opt/SUNWvda/preserve directory.

  3. Unconfigure and uninstall the latest release of Oracle VDI.

    # /opt/SUNWvda/sbin/vda-install -u

    When prompted, type Y to unconfigure the host.

  4. Reboot the host.

  5. If required, downgrade the operating system to the version of the operating system that is supported in the previous release of Oracle VDI.

  6. Install the previous release of Oracle VDI.

    Unzip the Oracle VDI software archive for the previous release and change working directory to the extracted directory.

    # ./vda-install

    At the end of the installation, you are prompted to configure Oracle VDI. Do not configure at this stage. Type n and press the Return key.

  7. Delete the Oracle VDI Center configuration files.

    If the following files exist, delete them:

    • /var/opt/SUNWvda/cluster.map

    • /etc/opt/SUNWvda/.truststore

    • /etc/opt/SUNWvda/.keystore

  8. Check if the vda instance still exists in Cacao.

    # cacaoadm list-instances

    On Oracle Linux platforms, the cacaoadm command is in /opt/sun/cacao2/bin.

    If the vda instance is listed, run the following commands:

    # cacaoadm stop -f -i vda
    # cacaoadm delete-instance -i vda
  9. Configure Oracle VDI.

    # /opt/SUNWvda/sbin/vda-config

    When you configure a host, ensure you do not change the topology of the Oracle VDI Center. The primary and secondary hosts must retain their original roles.

  10. Restart the Oracle VDI service.

    Run the following command as root:

    # /opt/SUNWvda/sbin/vda-service restart