DSM/Tape Catalog User's Guide

Database Design of DSM/TC
DSM/Tape Catalog User’s Guide — 520233-008
9 - 3
Moving the Volume and File Catalogs to Another
Volume
Moving the Volume and File Catalogs to Another Volume
Occasionally you need to move the volume catalog and file catalog to another volume
without losing data on registered tapes. MEDIACOM does not provide a command
interface to do this.
To relocate a DSM/TC catalog subvolume from one physical location to another within
the same system:
1. Locate the DSM/TC map table:
SQLCI GET CATALOG OF SYSTEM;
The DSM/TC map table is usually in the SQL/MP system catalog subvolume.
If the map table is not there, it is in the SQL/MP catalog subvolume that
MEDIADBM is registered in. To locate the catalog subvolume:
SQLCI FILEINFO $SYSTEM.SYSnn.MEDIADBM, DETAIL;
When you find the map table in this subvolume, note its location. This example
procedure assumes the name $SYSTEM.SQL.
2. Get the owner and security of the existing catalog:
MEDIACOM INFO VOLCAT|FILECAT *
This example assumes user 255, 255, with security NUNU.
3. Logon as the user identified in step 2.
4. Create the new SQL/MP catalog:
SQLCI CREATE CATALOG $VOL2.DSMCAT2 SECURE “NUNU”;
This catalog is the repository for the moved DSM/TC t
ables, indexes, and views.
5. Stop all tape activities:
a. Stop mounting tapes or running jobs that require tapes.
b. Stop all existing processes running from the MEDDEM object file:
>STATUS *,PROG $SYSTEM.SYSnn.MEDDEM,STOP
c. Stop all existing processes running from the MEDIADBM object file:
>STATUS *,PROG $SYSTEM.SYSnn.MEDIADBM,STOP
d. Optionally, temporarily rename the MEDIADBM object to prevent new
inst
ances from being processed.
6. Verify that the catalog subvolume is not in use:
FUP LISTOPENS $VOL1.DSMCAT.*
If any SQL objects are open, resolve the situation. Usually this entails stopping the
processes that have the objects open.