Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Release Notes

- Previous: Pre-upgrade Tasks/Data Migration
- Next: Testing the Upgrade

## Upgrade Procedure

To upgrade from HADB version 4.4.x to version 4.4.2-7, perform the following steps:

1. Perform the pre-upgrade tasks mentioned above as necessary.

2. Install HADB version 4.4.2-7 on all HADB hosts (on another path than that of version 4.4.x, for instance on `/opt/SUNWhadb/4.4.2-7`).

3. Install the HADB 4.4.2-7 version on the `hadbm` client hosts, if they are different than that of the HADB hosts.

4. Stop all management agents running on all HADB hosts.

5. 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.

6. Register the package in the management domain (default package name 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-7 V4.4.2-7

7. Run the `hadbm listpackages` command and check that the new package is registered in the domain.

8. Restart the database with the new `hadbm` version 4.4.2-7. If it is necessary to move the devices and history files, run online upgrade combined with setting new paths for devices and history files in one single operation:

       hadbm set packagename=V4.4.2-7,devicepath=new_devpath,
       historypath=new_histpath

   Otherwise, if the devices and history files are already outside of the installation directory, run the following command, which only does a rolling restart of the nodes:

       hadbm set packagename=V4.4.2-7 database name

9. Check that the database status is “running” (using the `hadbm status` command) and that it functions normally, serving the client transactions.

10. If everything is working, 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 pacakge name

11. Remove the old installation from the file system.

- Previous: Pre-upgrade Tasks/Data Migration
- Next: Testing the Upgrade

- © 2010, Oracle Corporation and/or its affiliates