Create the required TableSpaces in both the Monitor Database (WFMDB) and the EventQueue Database (FMCDB). BI Monitor allows you to control the distribution of the Monitor and the EventQueue Database tables and indices into a number of TableSpaces. The database tables and indices are grouped and categorized so that each category can be assigned to a separate TableSpace.
This number is the maximum number of TableSpaces to which you can assign the database tables and indices. This means you do not have to create all these TableSpaces, but you can create part of them. In this case, during the deployment steps, you can assign more than one group of tables or indices to the same TableSpace.
Please refer to the section named Database Tables and Indexes Allocation with Multiple TableSpaces for details about the distribution of the Monitor and EventQueue database tables and indexes on multiple TableSpaces.
For each created TableSpace, add the TableSpace container and specify its name and directory.
The page size value of the MQ Workflow database table spaces is not affected by the number of business measures in the organization file processes.
In DB2, there is a trade off between low maintenance and high performance regarding the type of the used TableSpaces. System Managed Spaces (SMS) provide low maintenance overheads with low performance, while Database Managed Spaces (DMS) provide high performance but with higher maintenance overheads than SMS TableSpaces.
Splitting a database table and its indices on two different TableSpaces is a feature of DMS TableSpaces only.
For DMS TableSpaces, it is strongly recommended to use the same size for each container of the same tablespace to achive the optimum I/O operation.
Important Note: Please refer to IBM DB2 documentation for details about DMS Maintenance procedure