Overview

This document discusses strategies and specific procedures to accomplish a successful upgrade of the dlxs database. If you are using DLXS version 9, you will want to upgrade to version 2 of the metadata database. If you are using DLXS version 10, you will want to upgrade to version version 3 of the metadata database. The procedure you follow to upgrade the database depends on what version of the database you are starting with. If you have version 1 of the database and you want to upgrade to version 4, you will first have to run the script $DLXSROOT/bin/db/upgrade_1_2 to get to version 2, $DLXSROOT/bin/db/upgrade_2_3 to get to version 3, and finally $DLXSROOT/bin/db/upgrade_3_4 to get to version 4.

It is important to keep in mind that each version of the database is meant to be run with a specific version of DLXS. For example, version 2 of the database works with version 9 of DLXS, but will not work with other versions of DLXS. So, if you need to have two or more versions of DLXS running, you will need to setup a database with the appropriate version for each of your DLXS installations. If this is of interest to you, contact DLXS Help for guidance in doing this.

Below is a series of steps to follow when upgrading your database. In order to update to version 2 of the database, you must have a version 1 of the database. If you do not have a version 1 of the database, start at Step 1. If you have a version 1 of the database and want to update to version 2, go to Step 3. If you have a version 2 of the database and want to update to version 3, go to Step 4.

Step 1. To upgrade to Version 1 of the database

To upgrade to version 1 of the database, you need run $DLXRROOT/bin/db/dconv. This script will copy all the data in the colldb and groups files used by image, bib, and text class into a CSV database. The CSV database created will be in $DLXSROOT/misc/db directory.

Step 2. CVS vs MySQL

Now that you have copied all your data from the colldb and groups file into a CSV database, you can have the middleware access this metadata database. But if you have a MySQL installation at your site, you may wish to move the CSV installation to a MySQL database. To do this you can run the script $DLXSROOT/bin/db/dbmove –s CSV –t MySQL (the s stands for source, and the t for target). Before you do this you will need to create a database by the name of dlxs, and two users for this database with specific privileges, These users are dlxs, and dlxsadm. Refer to the section of the DLXS documentation on database users to get more information about setting up the privileges for these users.

If at any time you wish to move back to a CSV database, you can run the command $DLXSROOT/bin/db/dbmove -r all –s MySQL –t CSV. Just make sure that the $DLXSROOT/misc/db directory is empty and that the script has permissions to write to it. This database move script will not move the entire MySQL database to CSV, since the MySQL database may contain an enormous amount of data which could be potentially hazardous to place on a disk. To learn more about the dbmove command read the doucumentation section about the dbmove script.

Step 3. To upgrade to version 2 of the database from version 1

If you need to upgrade version 1 of the database to version 2, you will need to use the script $DLXSROOT/bin/db/upgrade_1_2. $DLXSROOT/bin/db/upgrade_1_2 can be run against either a MySQL database or a CSV database.

To upgrade a MySQL database enter $DLXSROOT/bin/db/upgrade_1_2 –d MySQL. Notice that the upgrade will try to backup the MySQL database into the directory $DLXSROOT/misc/MySQL_DB_Backup before performing the upgrade. This is done just in case something goes wrong, you’ll have a backup of the database. From the backup, you should be able to use the MySQL mysqlimport script to recover your database if you need to.

To upgrade a CSV database enter $DLXSROOT/bin/db/upgrade_1_2 –d CSV. Notice that the upgrade will try to backup the CSV database into the directory $DLXSROOT/misc/CSV_DB_Backup before performing the upgrade. This is done just in case something goes wrong, you’ll have a backup of the database.

Once the upgrade is completed you should have a version 2 of the metadata database that is compatible with version 9 of the DLXS.

The following is a list of changes that the upgrade script makes:

The sessions table is redefined to contain id varchar(32) default null, a_session long blob, and a key by the name of sessions_index composed of id is created.

Step 4. To upgrade to version 3 of the database from version 2

If you need to upgrade version 2 of the database to version 3, you will need to use the script $DLXSROOT/bin/db/upgrade_2_3. $DLXSROOT/bin/db/upgrade_2_3 can be run against either a MySQL database or a CSV database.

To upgrade a MySQL database enter $DLXSROOT/bin/db/upgrade_2_3 –d MySQL. Notice that the upgrade will try to backup the MySQL database into the directory $DLXSROOT/misc/MySQL_DB_Backup before performing the upgrade. This is done just in case something goes wrong, you’ll have a backup of the database. From the backup, you should be able to use the MySQL mysqlimport script to recover your database if you need to.

To upgrade a CSV database enter $DLXSROOT/bin/db/upgrade_2_3 –d CSV. Notice that the upgrade will try to backup the CSV database into the directory $DLXSROOT/misc/CSV_DB_Backup before performing the upgrade. This is done just in case something goes wrong, you’ll have a backup of the database.

Once the upgrade is completed you should have a version 3 of the metadata database that is compatible with version 10 of the DLXS.

The following is a list of changes that the upgrade script makes:

A new table is added:PageviewFig. This table consist of idno varchar(32) with default value of '', seq int (11) with default value of 0, image varchar(32) with default value of '', and a key by the name of idno composed of idno and seq is created. The sessions table is redefined to contain id varchar(32) default null, a_session long blob, and a key by the name of sessions_index composed of id is created.

Step 5. To upgrade to version 4 of the database from version 3

If you need to upgrade version 3 of the database to version 4, you will need to use the script $DLXSROOT/bin/db/upgrade_3_4. $DLXSROOT/bin/db/upgrade_3_4 can be run against either a MySQL database or a CSV database.

To upgrade a MySQL database enter $DLXSROOT/bin/db/upgrade_3_4 –d MySQL. Notice that the upgrade will try to backup the MySQL database into the directory $DLXSROOT/misc/MySQL_DB_Backup before performing the upgrade. This is done just in case something goes wrong, you’ll have a backup of the database. From the backup, you should be able to use the MySQL mysqlimport script to recover your database if you need to.

To upgrade a CSV database enter $DLXSROOT/bin/db/upgrade_3_4 –d CSV. Notice that the upgrade will try to backup the CSV database into the directory $DLXSROOT/misc/CSV_DB_Backup before performing the upgrade. This is done just in case something goes wrong, you’ll have a backup of the database.

Once the upgrade is completed you should have a version 4 of the metadata database that is compatible with version 11 of the DLXS.

The following is a list of changes that the upgrade script makes:

The tables: BookBagItems, idresolver, FindaidClass, and FindaidClassGroup were added. Below is a list of the fields in these tables: