Assign custom table spaces

 

+

Search Tips   |   Advanced Search

 

The repository of WebSphere Portal consists of many tables and indices that are created in default table spaces. You can set custom table spaces for portal tables and indices.

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

The five JCR table spaces...

...cannot be customized.

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.

To configure custom table space assignments:

  1. Install DB2

  2. Create users

  3. Create remote databases

  4. Determine the names of custom table spaces.

  5. For each mapping file in...

      profile_root/PortalServer/config/tablespaces

    ..edit each in turn...

    ...and specify the table space and index space property pairs for each database table...

      database_domain.table_name.tablespace
      database_domain.table_name.index_name.indexspace

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

    • release
    • community
    • customization
    • feedback
    • likeminds

  6. 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 you are transferring.

  7. Save and close space_mapping.properties.

  8. From a command prompt, when starting the database transfer, specify the option...

      -DuseCustomTablespaceMapping=true


Parent topic:

Configure WebSphere Portal to use DB2


Previous topic:

Creating remote databases


Next topic:

Modifying database properties