1.0

Table Of Contents
4. If you use the default SQLFire server conguration, then you must copy user data from the old server
installation directory to the new, shared data directory (/var/opt/vmware/sqlfire). For example, if
you were upgrading from version 1.0.1 you would enter:
prompt# cp -Rp /opt/vfabric/sqlfire/vFabric_SQLFire_101/datadictionary
\
/var/opt/vmware/sqlfire/
prompt# cp -p /opt/vfabric/sqlfire/vFabric_SQLFire_101/vf.sf-license.cfg
\
/var/opt/vmware/sqlfire/
5. If you congured disk persistence or overow for tables and you did not specify an explicit disk store to use,
then you must copy the default disk store from the old SQLFire installation directory to the new directory.
For example:
prompt# cp -p
/opt/vfabric/sqlfire/vFabric_SQLFire_101/BACKUPSQLF-DEFAULT-DISKSTORE*
\
/var/opt/vmware/sqlfire/
6. If you created new disk stores by specifying path relative to the old SQLFire version's working directory,
you must copy those disk stores to the same relative directory in the new SQLFire installation. For example,
if you created a disk store in the previous release using a command similar to:
sqlf> CREATE DISKSTORE store1 'dir1';
then you must copy the dir1 directory to the new SQLFire installation's working directory:
prompt# cp -Rp /opt/vfabric/sqlfire/vFabric_SQLFire_101/dir1 \
/var/opt/vmware/sqlfire/
Note: Disk stores that you created using a path outside of the older SQLFire working directory continue
to work without any changes.
7.
If you modied /etc/sysconfig/sqlfire from the default conguration prior to the upgrade, the
yum upgrade process saved your modications to the le /etc/sysconfig/sqlfire.rpmsave
. If you want to continue using these modications, then you must manually update the new conguration
le (/etc/sysconfig/sqlfire) with the same changes.
8.
If you made license key modications to the old sqlfire.properties le (such as
/opt/vfabric/sqlfire/vFabric_SQLFire_101/sqlfire.properties) prior to the upgrade,
the yum upgrade process saved your modications to the le
/opt/vfabric/sqlfire/vFabric_SQLFire_101/sqlfire.properties.rpmsave. If you
want to continue using these modications, then you must manually update the new conguration le with
the same changes.
Upgrade Issues
Upgraded SQLFire members cannot participate in a distributed system that contains SQLFire members from an
earlier version. Shut down all existing cluster members before restarting the cluster with upgraded SQLFire
members.
Thin clients from earlier versions of SQLFire can operate against the latest version of SQLFire. However, thin
clients using the latest SQLFire JDBC drivers are not compatible with older versions of SQLFire.
Refer to the Release Notes to learn about changes that were introduced in the latest update.
vFabric SQLFire User's Guide24
Getting Started with vFabric SQLFire