Standalone server: Assign custom table spaces

The repository of WebSphere Portal consists of many tables and indicecreated in default table spaces. When using an existing set of table spaces for the objects of the repository, specify this when executing the database transfer to the target database system.

Before beginning:

• The custom table spaces must exist prior to the execution of database transfer.

• To see which table spaces can be customized in each domain, reference...
  WP_PROFILE/PortalServer/config/tablespaces/dbdomain.space_mapping.properties

• When using IBM DB2 Universal Database™ for z/OS as a data store, WebSphere Portal requires that its indexes are not padded. Therefore, set the DSNZPARM parameters to RETVLCFK=NO or PADIX=NO, or both.

Prerequisites

Standalone server: Install DB2 for z/OS

Standalone server: Create users on DB2 for z/OS

Standalone server: Create remote databases

If custom table spaces are assigned, each must be assigned explicitly. The default table spaces can be used to contain database objects; however the name of the default table space must be specified in the corresponding mapping files. This applies to all database domains that are transferred in a single database transfer.

Configure custom table space assignments

1. Determine the names of the custom table spaces.

2. Open the mapping file...
   WP_PROFILE/PortalServer/config/tablespaces/dbdomain.space_mapping.properties

   /ul> that specifies the table space and index space property pairs for each database table:

   • dbdomain.table_name.tablespace
   • dbdomain.table_name.index_name.indexspace

   For the file name and each table space and index space property pair, dbdomain can be any one of the following values:

   • release
   • community
   • customization
   • jcr
   • feedback
   • likeminds

   For jcr, edit mapping file:

   WP_PROFILE/PortalServer/jcr/config/jcr.space_mapping.properties

   ...which contains additional table space and index space property pairs for each jcr.table_name.tablespace database table.

   • Assign a table space to each .tablespace entry in the mapping file. Assignments to .indexspace entries are ignored. The table space name must be qualified by the database name and prepended by the keyword IN and a space.

     For example:

     community.COMP_INST.tablespace=IN COMM8KSPACE
     
     Repeat this step for each domain that we are transferring.

   • Save and close dbdomain.space_mapping.properties

   • From a command prompt, specify the option...
     -DuseCustomTablespaceMapping=true

     ...when starting the database transfer.

     For example,

     ./ConfigEngine.sh database-transfer -DuseCustomTablespaceMapping=true

Parent: Standalone server: Prepare DB2 for z/OS
Previous: Standalone server: Create remote databases
Next: Standalone server: Configure Portal to use DB2 for z/OS