If I am moving from a standalone Windows environment to a distributed environment on UNIX, what do I need to do to ensure I don't lose any of my data? Does the data need to be converted in a sequential order or can I convert data directly from 422 to 424?
Moving Environments: From Windows standalone to UNIX distributed
The documents attached describe the detailed steps of the migration from
4.2.2 to 4.2.4 FP1 Hot Fix. Please note that you are also going to be moving from a standalone environment on Windows to a distributed environment on UNIX; there is uniqueness. In this case, go through the upgrade on Windows first and convert all your models to 4.2.4. After you have done this you can then install 4.2.4 FP1 Hot Fix
on the distributed environment. So, just follow the steps of the migration on a standalone environment for now. Later, you will perform installation and deployment on a distributed environment.
docs attached: Workbench 424fp1installfinal.doc
There is no point, in my opinion, to move from 4.2.2 to 4.2.3, since you can move directly from 4.2.2 to 4.2.4 Fix Pack 1 HotFix (instructions are in the document that I had sent you yesterday.
For more information on end of service days, please visit the following
The migration instructions I read looked like
you have to convert the 4.2.2 models to 4.2.3 and then again to 4.2.4.
However, you don't need to install 4.2.3.
The powerful migration feature, which is available on 4.2.4 fix pack 1
hot fix, migrates the database for you from 4.2.2. to 4.2.4 in two
1. The install server utility which is run against the database moves
the schema from 4.2.2 to 4.2.3
2. Then, when you deploy 4.2.4, from within the web application, you
migrate the database from 4.2.3 to 4.2.4
Again, you will not need to install nor deploy 4.2.3 for this procedure.