m 6.0+)

dba/m Database Manager installation and Operations Manual 522633-004 2-13

• RUN REMGDB $vol ($vol is the volume on which dba/m Database Manager was

installed)

Upgrade dba/m

Upgrading NonStop dba/m Database Manager will only update the server objects and

dba/m database without deleting the current data.

To Upgrade NonStop dba/m Database Manager on server, follow the following steps

• Use IPsetup to install dba/m Database Manager IPM server components to the

installation volume on Himalaya system.

• Logon to the Himalaya system as a super group user.

• Setup IPM Installation environment

c> Change current volume and sub volume to $<vol>.ZDBAM

> VOLUME $<vol>. ZDBAM

d> Load the UPGINSTL macro:

> LOAD/ KEEP 1/UPGINSTL

• Execute the UPGINSTL macro:

UPGRADE

The UPGRADE macro finds out existing installed node name, and dba/m volume name

from $SYSTEM.GENUS.CONFIG . It does the various checks before UPGRADE starts.

If the user ID is not appropriate or does not belong to the super group the installation

exists. An Error message is displayed, instructing the user to log on using correct Super

Group user ID.

Verifies that the Guardian Version is correct and that SQLCI2, TMF, and RSC are

running. If any of these checks fail, then the installation macro displays the appropriate

error message and exits.

Checks for the existence of all dba/m IPM related files, such as program files and IPM

installation macro, in the current sub volume. If the files are not found, the macro will

prompt you to enter the sub volume name where the NonStop dba/m IPM files are stored.

Verifies that the NonStop SQL/MP Version is 350 or later.

• If the above checks pass then macro:

Copies the program files from $<volume>.ZDBAM to the appropriate

subvolume.

SQL Compiles the Object code

Starts the dba/m Database Manager Pathway Environment.