OSI/MHS Configuration and Management Manual

Installing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual424827-003
4-26
Upgrading in Two Stages
Setting the Database Conversion Options on the Installation Menu.
To place the Route Database Conversion and MS Database Conversion options on the
installation menu interactively, run the installation procedure as described under
Installing OSI/MHS for the First Time on page 4-11. Answer yes to the question:
The following warning appears. Press RETURN to continue.
Answer yes to the following question:
Answer yes to the following question:
The installation procedure sets the following steps as defaults:
Copying the OSI/MHS ISV to the OSI/MHS subvolume.
Securing new executable object files.
Converting the route database.
SQL compiling the MS initialization program.
SQL compiling the MS program.
Converting the MS database.
These steps are required for a D22 or D41 upgrade that includes MS groups.
At this point, the installation menu appears. Follow the instructions in “Installing
OSI/MHS for the First Time” to complete the installation.
Upgrading in Two Stages
A two-stage installation is appropriate when you have many MS groups or many MS
APPLs within each group. First, you run the installation procedure to upgrade all of
your OSI/MHS subsystem except the MS groups. When the first run of the installation
procedure is complete, you then run it a second time. During this second run,
Are MS groups to be installed? [y]
Warning: MS databases for OSI/MHS D22 version are
incompatible with D20 or D21 versions, which
must be converted. This is achieved by
executing the MS Database Conversion step.
Migration from C31 to D22 conversion is NOT supported
Migration from D20 to D22 conversion is required.
Migration from D21 to D22 conversion is required.
MS Database Conversion step will not purge
existing files unless directed to.
Is NonStop SQL installed? [y]
Is this an upgrade to D22 version from either D20 or D21 version? [n]