OSI/MHS Configuration and Management Manual

Installing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual424827-003
4-30
Returning to a Previous RVU
After the MS SQL databases are converted, the following message appears.
Returning to a Previous RVU
The message store databases for OSI/MHS RVUs D22 and D41 are not compatible
with previous versions. If the databases cannot successfully be converted to the D22
or D41 format, you cannot restart the MS groups. If you must revert back to the
previous version of OSI/MHS, you must use backups or online dumps to restore all
databases back to their original state.
Summary
To install OSI/MHS, you run the installation procedure. This procedure creates an
installation file that contains keywords and installation steps. You edit this file so that it
reflects your subsystem and indicates which installation steps you require.
You then continue the installation procedure, following the prompts that appear on your
screen.
If you are upgrading from an earlier OSI/MHS RVU and you have a large number of
MS groups or MS APPL users, you may want to run installation in two stages. A two-
stage installation allows you to use part of your OSI/MHS subsystem while the
installation procedure converts the MS database to the D22 or D41 format.
End: Conversion of MS Database(s) complete(s)
Note. The MS database conversion creates a set of temporary work files in the MS SDL
database.
There is one temporary file for each file that is being converted (AUT, GEN, BCR, RRT, IPM).
Each file name is preceded with an x (xAUT, xGEN, and so on). If any of the files exist before
the conversion, you are given the choice of purging the files and continuing the installation, or
stopping the installation.
The temporary work files are deleted after installation completes successfully.