Assigning custom 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.
- For details on creating table spaces refer to the documentation for the database.
Prerequisites
- Installing Oracle RAC
- Create users
- Creating databases
- Modifying database properties
- Set up 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.
To configure custom table space assignments:
- Determine the names of custom table spaces.
- Open the mapping file profile_root /PortalServer/config/tablespaces that specifies 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
- Assign a table space to each entry in the mapping file. The table space name must be prepended by the keyword TABLESPACE and a space.
For example: community.COMP_INST.tablespace=TABLESPACE COMM8KSPACE Repeat this step for each domain that you are transferring.
- Save and close space_mapping.properties.
- From a command prompt, specify the option -DuseCustomTablespaceMapping=true when starting the database transfer.
Parent topic:
Configure WebSphere Portal to use Oracle RAC
Previous topic:
Set up databases
Next topic:
Set up Oracle RAC