Moving a dsm/scm database (zphihmi or zphtmi) – HP Integrity NonStop H-Series User Manual
Page 310
Managing DSM/SCM
DSM/SCM User’s Guide — 529846-014
17 - 17
Moving a DSM/SCM Database (ZPHIHMI or
ZPHTMI)
3. To cancel the check-out of the Configuration Manager profile, from the
Configuration Manager Profile Check-Out screen, press F4.
To cancel the check-out of a target system profile, a software input, or a
configuration revision, on the appropriate Check-Out screen, enter any character in
the Selection field of each item to cancel the check-out; then press F4.
Moving a DSM/SCM Database (ZPHIHMI or ZPHTMI)
You can move the DSM/SCM database from one volume to another on the same
system using the ZPHIHMI or ZPHITMI.
DSM/SCM databases must be on volumes with names of no more than seven
characters ($six-characters) because DSM/SCM supports multiple RVUs.
To move a host or target database:
1. Make sure the Planner Interface is not running.
2. Stop all servers through PATHCOM and all processes running from PHIHDBMG
(PHITDBMG for a target database).
3. On the Maintenance Interface main menu, enter 6 (Database Relocation) in the
Selection Number field, and press F1. DSM/SCM displays the Database
Relocation screen.
4. On the Database Relocation screen:
a. Enter the name of the volume where the database currently resides.
b. Enter the name of the new volume for the database.
c.
Press F1.
DSM/SCM moves the database and recompiles the programs with embedded SQL
statements it uses. The recompile can be time consuming. The Maintenance
Interface waits for the compile to finish. You cannot perform other DSM/SCM
activities during the compile.
Results of the database relocation are written to the file DBRELOUT in the
ZDSMSCM subvolume.
5. After relocating the database, run STOPSCM and STARTSCM to update the
DSM/SCM PATHMON servers with the location of the database.
Note. To update the location of the DSM/SCM SQL catalog, the user performing the relocate
must have permission to access the SQL system catalog.
To improve system performance, keep the databases and archive on different volumes.