HP Integrity NonStop H-Series - Manual (Page 156)

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.
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 there is no activity (requests) taking place in NonStop Software Essentials.
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.
Updating DSM/SCM Databases
You might need to perform these activities periodically to ensure the target database is updated
and synchronized with the host database. Keeping the databases updated and synchronized is
crucial for effectively managing your system configuration.
1. Update a target database with the information regarding all TSVs. See “Verifying the Target
System Database through ZPHITI” (page 156) .
2. Create an independent snapshot. See “Creating an Independent Snapshot of the Target
System” (page 157) .
Verifying the Target System Database through ZPHITI
Verify the target database after volume or subvolume operations are performed outside of
DSM/SCM, such as:
• Deleting a SYSnn
• Moving, copying, or renaming TSVs
• Moving, modifying, or adding files to subvolumes on the target system
• Adding, deleting or renaming a volume
Verifying the database ensures that the target database contains correct TSV information by:
• Verifying the location of TSVs and files on the target system
• Updating the target database with the correct locations and names of the TSVs if any TSVs
have been moved, copied, or deleted
• Determining whether files have been deleted (It does not check whether a file has been moved)
To verify a target system database:
156 Managing the NonStop Software Management Environment