Windows clustered server: Assign custom DB2 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
- The page size of table spaces used by WebSphere Portal must be 8192 bytes.
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
- Determine the names of the custom table spaces.
- 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 entry in the mapping file. The table space name must be 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