AIX clustered server: Assign custom DB2 for z/OS table spaces

The repository of WebSphere Portal consists of many tables and indices that are created 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 you begin:

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

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

• For details on creating table spaces refer to the documentation for the database.

• When using IBM DB2 Universal Database™ for z/OSas 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

AIX clustered server: Install DB2 for z/OS
AIX clustered server: Use JCL templates to set up DB2 for z/OS
AIX clustered server: Create DB2 for z/OS users
AIX clustered server: Create remote DB2 for z/OS databases
AIX clustered server: Grant privileges to DB2 for z/OS database administration users

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. Determine the names of custom table spaces.

2. Open the mapping file WP_PROFILE /PortalServer/config/tablespaces/dbdomain.space_mapping.properties 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

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

4. Save and close dbdomain.space_mapping.properties.

5. From a command prompt, specify the option -DuseCustomTablespaceMapping=true when starting the database transfer.
   For example,
   Windows™: ConfigEngine.bat database-transfer -DuseCustomTablespaceMapping=true

   UNIX™: ./ConfigEngine.sh database-transfer -DuseCustomTablespaceMapping=true

   i: ConfigEngine.sh database-transfer -DuseCustomTablespaceMapping=true

Parent

AIX clustered server: Set up a remote DB2 for z/OS

Previous

AIX clustered server: Create the Java Content Repository database

Next topic

AIX clustered server: Configure WebSphere Portal to use DB2 for z/OS January 5, 2012

  2011/12/15 documentation refresh 2011/12/15 documentation refresh

+

Search Tips   |   Advanced Search