IBM FileNet P8, Version 5.2.1            

Separating isolated regions into a custom table space

To organize isolated regions in table spaces, you must first define the separate table spaces in the database, specify the table spaces for the region in the administration console, and move the existing isolated region data into those table spaces.

Procedure

  1. Before you run rdbConvertReg, ensure that the table space in use is not shared, by selecting the isolated region in the administration console:
    Option Description
    For a workflow system:
    1. In the domain navigation tree, click the object store.
    2. In the object store navigation tree, select the Administrative > Workflow System folder.
    3. Click the Isolated Regions tab.
    4. Click the isolated region to open it.
    5. Click the Table Spaces tab to view the table spaces that are in use. If the table space in use is shared, do not use it. Instead, create a new table space.
    For a legacy workflow system:
    1. In the domain navigation tree, click the Legacy Workflow Systems folder.
    2. Select the workflow system in the tree.
    3. Click the Legacy Isolated Regions tab.
    4. Click the isolated region to open it.
    5. Click the Table Spaces tab
    In the lower part of the page, there is a section for Custom Table Space Associations.

    If the Restrict the isolated region to only these custom table spaces is checked, the table spaces are already restricted.

  2. Use vwtool to run the rdbConvertReg command to verify that all of the RDB objects for the region are in the correct table spaces. Use the l option, which will list all the tables and their locations.
  3. Use the database tools to create one or more new table spaces for the existing region, according to your database. Grant table space privileges to the workflow system runtime user (such as, f_sw). For example, for Region 100, create reg100data.
  4. If Case Analyzer is configured for the workflow system, use the Take Offline action in Case Analyzer Process Task Manager to take the Case Analyzer store offline.
  5. In the administration console, specify one or more custom table spaces for the region. See Step 1, the step about Custom Table Space Associations. After you specify the new region information, ensure that you apply your changes. When the changes are applied, verify that the table space information is correct for the existing region. The table spaces listed should include the original table spaces along with the new table spaces.
  6. In the Actions menu in the General tab for the isolated region, click Lock Isolated Region to lock the isolated region.
  7. Purge as many log entries as possible before you run rdbConvertReg so that when you move existing data, you do not have to move all of the records. For more information, see Purge data from the event log tab.
  8. In vwtool, use the rdbConvertReg command to display a list of the current table and index names, the current locations, and the location where the data will be moved.
  9. Lock the region. For the remaining steps in this procedure, the region should remain locked and unavailable for use until verification passes. Use the rdbConvertReg command to lock the region. At the prompt, enter the c (convert) option. For a hardcopy, choose Yes to save a file of the manifest. At the prompt, choose Yes to confirm that you want to convert the region. The region data will not be converted until you move all of the data into the correct table spaces.
  10. Use the database tools to move the data to the new table spaces, as specified in the manifest.
  11. After you complete moving the data, run vwtool and enter rdbConvertReg with the c option again. The command verifies that the workflow system region tables and indexes were moved from the current database table spaces to the new region-defined table spaces.
  12. Unlock the region.
  13. Use the Bring Online action in the Case Analyzer Process Task Manager to bring the Case Analyzer store online.
  14. In the Custom Table Space Associations section, of the isolated region page, select the Restrict the isolated region to only these custom table spaces check box.
  15. Optional: After the conversion process, existing database views are still usable. Because the tables are moved to another location in the database, the database views are not affected. To re-create the database views, complete the following steps:
    1. In vwtool, set the correct region, and then use the createDBViews command to re-create the database views.
    2. Select either the v or s options. The v option automatically creates the views and the s option creates a script that you can run manually from the RDBMS database.


Last updated: March 2016
iso_region_sep_proced.htm

© Copyright IBM Corporation 2016.