DB2 Server for VM: System Administration

Moving a VM Application Server from One User ID to Another

If you are moving a database from one VM user ID to another VM user ID, you need to do the following:

Update the VM directory entries for the new user ID. Use the same statements as they were used in the origin user ID. See VM Directory Control Statements for some example entries of the VM directory control statements.
```
+---------------------------VMSES/E Consideration----------------------------+
```
If the database you are moving is the original database machine (SQLMACH), which VMSES/E recognizes, you must update the installation user ID's VM directory to link to the new production and service minidisks.
```
+------------------------End of VMSES/E Consideration------------------------+
```
Copy all the files from the original service and production minidisks to the new service and production minidisks.
Copy the PROFILE EXEC from the original database user ID's A-disk to the new user ID's A-disk.
In the new user ID, access the production minidisk as file mode Q in write mode.

XEDIT the file ARISPIDC MACRO Q. Change the original database user ID to the new user ID. For example:

Before:

Line 1:  PRODUCTION:  SQLMACH  195
Line 2:  SERVICE:     SQLMACH  193

·
·
·

After:

Line 1:  PRODUCTION:  NEWMACH  195
Line 2:  SERVICE:     NEWMACH  193

·
·
·

XEDIT the file resid SQLDBN Q. Change the original database user ID to the new user ID. For example:
Before:
```
DBMACHID=SQLMACH,DCSSID=dcssid,DBNAME=dbname
```
After:
```
DBMACHID=NEWMACH,DCSSID=dcssid,DBNAME=dbname
```

XEDIT the file resid SQLFDEF Q. Change all the occurrences of the original database user ID to the new user ID. For example:

Before:

/*** FOLLOWING LINES FOR BDISK ***/
If var1='DEF' Then CP LINK SQLMACH 200 200 W

·
·
·

/*** FOLLOWING LINES FOR LOGDSK1 ***/
If var1='DEF' Then CP LINK SQLMACH 201 201 W

·
·
·

/*** FOLLOWING LINES FOR LOGDSK2 ***/
If var1='DEF' Then CP LINK SQLMACH 202 202 W

·
·
·

/*** FOLLOWING LINES FOR DDSK1 ***/
If var1='DEF' Then CP LINK SQLMACH 203 203 W

·
·
·

/*** FOLLOWING LINES FOR DDSK2 ***/
If var1='DEF' Then CP LINK SQLMACH 204 204 W

·
·
·

/*** FOLLOWING LINES FOR DDSK20 ***/
If var1='DEF' Then CP LINK SQLMACH 216 216 W

·
·
·

After:

/*** FOLLOWING LINES FOR BDISK ***/
If var1='DEF' Then CP LINK NEWMACH 200 200 W

·
·
·

/*** FOLLOWING LINES FOR LOGDSK1 ***/
If var1='DEF' Then CP LINK NEWMACH 201 201 W

·
·
·

/*** FOLLOWING LINES FOR LOGDSK2 ***/
If var1='DEF' Then CP LINK NEWMACH 202 202 W

·
·
·

/*** FOLLOWING LINES FOR DDSK1 ***/
If var1='DEF' Then CP LINK NEWMACH 203 203 W

·
·
·

/*** FOLLOWING LINES FOR DDSK2 ***/
If var1='DEF' Then CP LINK NEWMACH 204 204 W

·
·
·

/*** FOLLOWING LINES FOR DDSK20 ***/
If var1='DEF' Then CP LINK NEWMACH 216 216 W

·
·
·

If the database server name is going to be different, follow the steps described in Changing the Server Name and Resource Identifier to change the server name and the resource ID.
Copy the database minidisks (Directory, log disks and dbextents) to the new userid. For details on moving the database minidisks, refer to the following sections in Chapter 9, Making Backups and Recovering from Failures:
VMSES/E considerations: To apply service to the new user ID, you must create a PPF (Product Parameter File) override to the 5697F42S $PPF file. The PPF override must reflect the new database user ID and service and production minidisk address or SFS directory names. The $PPF file resides on the VMSES/E Software Inventory disk (MAINT 51D). Therefore, when servicing DB2 Server for VM, the files are copied to the correct database user ID. Refer to the VM/ESA: VMSES/E Introduction and Reference for more information on creating a PPF override.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]