Convert existing region to recovery enabled

If you have existing isolated regions that were initialized but not enabled for region recovery, you can still enable them. You must first define the desired separate tablespaces in the database, specify the tablespaces for the region in Process Task Manager, and move the existing isolated region data into those tablespaces.

Use the rdbConvertReg command in vwtool to convert an existing region so that it can be enabled for region recovery. rdbConvertReg first verifies that all the RDB Objects for that region are in the correct tablespaces, and then separates region data located in Process Engine (PE) system tables into separate region level tables.

IBM recommends purging as many log entries as possible before running so that when moving existing data, you do not have to move all the records.For more information, see To purge events as part of the PA backup procedure.

Convert existing isolated regions

  1. Before running rdbConvertReg, ensure that the tablespace in use is not shared. In Process Task Manager, click the isolated region. If the tablespace in use is shared, do not use it. Instead, create a new tablespace.
  2. Use the database tools to create one or more tablespaces for the region, according to your database. For example, for Region 100, create reg100data.
  3. In Process Task Manager, specify the custom tablespace(s) for the region. See Regions General tab for more information. If Process Analyzer (PA) is configured for PE, stop PA in Process Task Manager.
  4. In Process Task Manager, lock the region.

    The region should remain locked and unavailable for use until after Step 7.

  5. In vwtool, use the rdbConvertReg command to display a list of the current table/index names, the current locations and the location where the data will be moved.

    At the prompt, enter the c (convert) option. For a hardcopy, choose Yes to save a file of the manifest.

    At the prompt, to confirm that you want to convert the region, choose Yes. (NOTE  The region data will not be converted until you move all the data into the correct tablespaces.)

  6. Use the database tools to move the data to the new tablespace(s) as specified in the manifest.
  7. After the data move is complete, run vwtool and enter rdbConvertReg with the c option again. The command now verifies that the PE region tables and indexes were moved from the current database tablespaces to the new region-defined tablespaces.

    Once the verification passes, rdbConvertReg processes the PE system tables as necessary to enable the region for recovery. See the example below.

  8. Unlock the region and restart PA.
  9. Select Enable for Region Recovery.

NOTES 

Running the region conversion utility

Usage:

Vwtool –Y <Admin user name>+<Admin password>
vwtool: rdbConvertReg
Choice? ('c', 'l', 'e',, CR=exit): c
hardcopy?(y/n) cr=y
output file: <filename> Suggest manifestR22

 

Manifest example

NOTE  The following example uses Microsoft SQL Server, and the term "filegroup" (From DB Filegroup, To DB Filegroup). For Oracle or DB2, these are called tablespaces.

<vwtool:22>rdbConvertReg

Create :

c - Verify that all PE region database objects are in the correct rdb location
    Convert the region to be ready to set backup enabled.
    Message will be displayed if all PE database objects are
    not in the correct location in the database.

NOTE: region must be locked in order to complete this step.

l - Just list current DB locations.

e - Exit.

Choice? ('c', 'l', 'e', CR=exit): c

Do you want a hard copy? y/n: (CR=y)

Verify and convert for region 22
Please confirm that you want to convert region 22: y/n (CR=n)y
PE Reg 22 MSSQL 2005 Database Filegroups

Use the following list to move PE region 22 tables and indexes,
from current DB tablespace to new region defined tablespace.
Use database tools to move tables and indexes
to new DB filegroups(s)

 

Table/Index name From DB Filegroup To New DB Filegroup

VWQueue22_100

vwdata_fg

--> vwdataR22
VWqwobnum22_100

vwdata_fg

--> vwdataR22

VWquniqid22_100

vwdata_fg

--> vwdataR22

VWqsort22_100 vwdata_fg

--> vwdataR22

     

VWQueue22_101

vwdata_fg

--> vwdataR22
VWqwobnum22_101

vwdata_fg

--> vwdataR22

VWquniqid22_101

vwdata_fg

--> vwdataR22

VWqsort22_101 vwdata_fg

--> vwdataR22

VW_IND2 vwdata_fg --> vwdataR22
     

VWQueue22_102

vwdata_fg

--> vwdataR22
VWqwobnum22_102

vwdata_fg

--> vwdataR22

VWquniqid22_102

vwdata_fg

--> vwdataR22

VWqsort22_102 vwdata_fg

--> vwdataR22

     

VWQueue22_103

vwdata_fg

--> vwdataR22
VWqwobnum22_103

vwdata_fg

--> vwdataR22

VWquniqid22_103

vwdata_fg

--> vwdataR22

VWqsort22_103 vwdata_fg

--> vwdataR22

     

VWQueue22_104

vwdata_fg

--> vwdataR22
VWqwobnum22_104

vwdata_fg

--> vwdataR22

VWquniqid22_104

vwdata_fg

--> vwdataR22

VWqsort22_104 vwdata_fg

--> vwdataR22

     

VWQueue22_105

vwdata_fg

--> vwdataR22
VWqwobnum22_105

vwdata_fg

--> vwdataR22

VWquniqid22_105

vwdata_fg

--> vwdataR22

VWqsort22_105 vwdata_fg

--> vwdataR22

VW_IND3 vwdata_fg --> vwdataR22
     

VWQueue22_106

vwdata_fg

--> vwdataR22
VWqwobnum22_106

vwdata_fg

--> vwdataR22

VWquniqid22_106

vwdata_fg

--> vwdataR22

VWqsort22_106 vwdata_fg

--> vwdataR22

VW_IND4 vwdata_fg --> vwdataR22
     

VWRoster22_114

vwdata_fg

--> vwdataR22
VWrwobnum22_114

vwdata_fg

--> vwdataR22

VWrwobtag22_114

vwdata_fg

--> vwdataR22

VW_IND5 vwdata_fg --> vwdataR22
     
VWLog22_115

vwdata_fg

--> vwdataR22
VWLogTime22_115

vwdata_fg

--> vwdataR22

VWEventTime22_115

vwdata_fg

--> vwdataR22

VWLogEvtWPId22_115 vwdata_fg

--> vwdataR22

VWLogSequence22_115

vwdata_fg

--> vwdataR22

VW_IND6 vwdata_fg

--> vwdataR22

Region 22 location verification complete, verification shows more tables to move.

Copy the tables as listed and rerun this option.
<vwtool:22>

Verification example

Sample output after moving the data to the new tables and running rdbConvertReg the second time. With the data in the appropriate tablespaces, verification is successful and the remaining data for Region 22 is split out of the PE system tables and copied to the new tablespace.

<vwtool:1>reg 22
Current region is: 1
New region is: 22
<vwtool:22>rdbConvertReg

Create :

c - Verify that all PE region database objects are in the correct rdb location
    Convert the region to be ready to set backup enabled.
    Message will be displayed if all PE database objects are
    not in the correct location in the database.

NOTE: region must be locked in order to complete this step.

l - Just list current DB locations.

e - Exit.

Choice? ('c', 'l', 'e', CR=exit): c

Do you want a hard copy? y/n: (CR=y)

Verify and convert for region 22
Please confirm that you want to convert region 22: y/n (CR=n)y

PE Reg 22 MSSQL 2005 Database Filegroups.

Use the following list to move PE region 22 tables and indexes,
from current DB tablespace to new region defined tablespace.
Use database tools to move tables and indexes
to new DB filegroups(s)

Table/Index name From DB Filegroup To New DB Filegroup

Region 22 location verification complete, verification PASSED

Created table VWWobTimeOut22.

Created table VWNotify22.

Created table VWPAEventState22.

Created table VWPending22.

Created table VWIsolReg22.

Copied data for table VWIsolReg22.

Copied data for table VWWobTimeOut22.

Copied data for table VWNotify22.

Copied data for table VWPAEventState22.

Copied data for table VWPending22

Deleted data in VWPending.

Deleted data for table VWWobTimeOut.

Deleted data for table VWNotify.

Deleted data for table VWPAEventState.

Region is setup for region backup enable for region # 22
Unlock region and continue with backup enable procedure.
<vwtool:22>