Upgrading from Previous Versions

4

Upgrade Overview

Upgrading Oracle to 6.1.11+

Upgrade from 6.1.6 to 6.1.7+

Upgrade from 6.0.4 to 6.1.2+

Upgrade from 5.3.8 to 6.0.2+

 

 

 

Upgrade Overview

Upgrading is a process for migrating data, converting database content to be compatible with updated software. Please review release notes for your new version before assuming migration is necessary or possible. Not all upgrades require migration tasks, and migration is not possible to all versions.

New software is not always capable of using data from older versions. Some data may be lost to the application or cause system errors if not properly upgraded. This migration process is designed to extract legacy data while the old software is operational and then transform this data to be compatible with the new software. You may follow the steps outlined here to preserve existing data when upgrading. Since migration is performed against the database, you only need to do this once for the entire system.

[spacer]

When upgrading, you must upgrade all the clients and additional (application and mediation) serv­ers since they all need to run the same version of code.

Restart / Resync Between Version Upgrades

After each migration stage, start the application server and redcell client, and resync discovered devices. This is especially true for upgrading in stages (5.3.8 to 6.0.4 to 6.1.2).