10.1. Installation and Configuration

10.1.1. Oracle VDI Configuration Is Failing to Import svc_vdadb.xml
10.1.2. Can I Try Out MySQL or Set up an Evaluation Oracle VDI Remote Database?
10.1.3. Do I Need to Configure Sun Ray Software Separately?
10.1.4. Reconfiguring Oracle VDI Fails With "Error While Configuring Database"
10.1.5. Oracle VDI Configuration Fails to Create Database Tables With Remote Windows Databases That Use UTF-8

10.1.1. 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.2. 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 <absolute-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.3. Do I Need to Configure Sun Ray Software Separately?

A separate installation of Sun Ray Software is not necessary because Sun Ray Software is installed and automatically set up as part of the Oracle VDI installation and configuration.

10.1.4. 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 primary 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 an Oracle VDI secondary host, 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.5. 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.