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:
To recover the SVC repository's snapshot, run the following.
# /lib/svc/bin/restore_repository
When prompted with Enter Response
[boot]
, select
manifest_import
instead of the
default, boot
.
Choose the correct snapshot
(manifest_import-200904??_???
- the
time of backup will be in DDMMYY format).
After the system reboots, check to see that
svc:/TEMP/application/database/vdadb:default
has been removed.
Run the Oracle VDI configuration as usual.
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.
Download and extract it to a temporary folder.
Download the MySQL release of your choice from http://dev.mysql.com/downloads.
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
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.
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:
Log in as root on the Oracle VDI host.
Unconfigure Oracle VDI on the host.
# /opt/SUNWvda/sbin/vda-config -u
Remove the directory
/var/opt/SUNWvda/mysql
.
Configure Oracle VDI on the host.
# /opt/SUNWvda/sbin/vda-config
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.
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.
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.