Tech Tip: ehealth upgrade path

Document created by Yulun.Zhang Employee on Sep 3, 2014Last modified by SamCreek on Dec 17, 2016
Version 3Show Document
  • View in full screen mode

You can only do an in place update to release 6.3.2.0X from a CA eHealth installation that is at release 6.3.1.06 or higher. Any update from ehealth 6.3.1.05 or lower to 6.3.2.0X requires that you either upgrade in place to ehealth 6.3.1.06 first, or do a two machine migration from ehealth 6.3.1.05 or lower to 6.3.2.0X. The two machine migration is used in the situations where a new OS is required  for carrying out the upgrade to meet support requirements, such as upgrading ehealth 6.3.0.06 on win2003 to 6.3.2.05 running on win2008. Two machine migration consists of the following three steps

 

1. Install ehealth on the target machine
2. Do an ascii database save on the source machine
3. Transfer the ascii database from source to target machine and load it into the newly installed ehealth

 

The minimum ehealth version you can do the asc db save from and load it directly to 6.3.2.0X is 6.2.2.0X. That means that you can load asc db save derived from 6.2.2.0X, 6.3.0.0x and 6.3.1.0x to 6.3.2.0X.

Attachments

    Outcomes