Sun Java System Application Server Enterprise Edition 8.2 Release Notes

Special Deployment and Upgrade Information

This section lists additional information about HADB deployment and upgrading.


Online Upgrade from 4.4.1 to 4.4.2

It is not possible to upgrade from 4.2 or 4.3 to 4.4 online. However, 4.4 supports online upgrade for the future versions. To upgrade from 4.4.1 to 4.4.2, perform the following steps:

  1. Install 4.4.2 on all HADB hosts (On another path than that of 4.4.1 – for instance /opt/SUNWhadb/4.4.2-6).

  2. Install the new version on the hadbm client hosts.

  3. Stop all management agents running on the HADB hosts.

  4. Start the management agent processes using the new version's software, but with the old configuration files. In the remaining steps, please use the hadbm command found in the new version's bin directory.

  5. Register the package in the management domain (default package name here becomes V4.4, so another package name may be required to avoid conflicts with existing packages having the same name):

    hadbm registerpackage --packagepath=/opt/SUNWhadb/4.4.2-6 V4.4.2
  6. Restart the database with the new version (the following command does a rolling restart of the nodes):

    hadbm set packagename=V4.4.2 database_name
  7. Check that the database status is “running” (using the command hadbm status) and that it functions normally, serving the client transactions.

  8. If everything works, the old installation can be removed later.

    Before unregistering the old package, remove all references to the old package from the ma repository. Otherwise, hadbm unregisterpackage will fail with “package in use.” A dummy reconfiguration operation, for instance, hadbm set connectiontrace=<same_as_previous_value> will remove all references to the old package. Now, unregister the old package:

    hadbm unregisterpackage [--hosts=<host_list>] <old_package_name>

    Remove the old installation from the file system, as described in the HADB installation instructions.