Migrate the galaxy database

Migrating the galaxy database leaves your object configurations intact. Although the object code changes when the underlying object type is updated, for example, if the $UserDefinedObject is enhanced to support a newly-introduced feature, these updates do not change any object configuration you made in the previous version.

When you migrate the database:

• The IDE you use to migrate the database must be the current version.

• The GR node must already be upgraded to the current version.

Make sure that all connections to the Galaxy database are closed before migrating the database.

After you migrate the Galaxy, deployed objects on a non-upgraded node are marked with pending software upgrade status.

To migrate the galaxy:

1. Start the IDE.

2. Connect to the galaxy. You are prompted to migrate it.

3. Follow the prompts to complete the migration.

Migration errors

Migration of a very large galaxy may fail, with various (and sometimes misleading) warnings and errors displayed in the Logger. This is due to the Galaxy database transaction log expanding beyond its maximum allocated size.

Note: These errors do not affect object configuration.

Before making the changes described here, use the Event Viewer to check if the transaction log is full. If you confirm that the transaction log has exceeded its maximum file size restriction, remove the restriction as follows:

4. In SQL Server Management Studio, right click the Galaxy database, then select Properties on the shortcut menu.

5. In the Database Properties dialog, select the Files page.

6. Locate Log ... in the File Type column.

7. Click the ellipsis (...) button in the Autogrowth column on the same line.

8. In the Change Autogrowth for Base_Application_Server_log dialog, select the Unrestricted File Growth radio button under the Maximum File Size parameter, then click OK.

9. After the galaxy migration is finished, repeat steps 1 through 5 to reinstate the file size limit on the transaction log.