You can customize your library server database by setting custom table, index, and large object (LOB) table spaces for item type root and child components, indexes, and LOB attributes. Using custom table spaces can increase the efficiency of database management and can increase database performance.
In Content Manager EE, you can use the system administration client to set custom table spaces for new item type root and child components and indexes, including the table, index, and LOB attributes. You can also set custom table spaces for new child components of item types that existed in previous versions of Content Manager EE.
For a Content Manager EE system that uses the Oracle database, you can modify the table spaces, with some limitations on the modifications that you can perform.
The following tables show how you can use custom table spaces for item type root and child components, indexes, and LOB attributes:
For a DB2 Universal Database database, you can set table, index, and LOB custom table spaces for new root and child components, but after the table spaces are set, you cannot modify them. You cannot set table spaces for root and child components that existed in versions of Content Manager EE earlier than Version 8.4.2 through the system administration client.
For this object | Can you set default table spaces? | Can you modify the default table space? |
---|---|---|
Existing root component (Version 8.4.1 and earlier) | No | No |
Existing child component in an existing root component | No | No |
New child component in an existing root component | Yes, for the child component table, index, and LOB | No |
New root component | Yes, for the root component table, index, and LOB | No |
New child component in a new root component | Yes, for the child component table, index, and LOB | No |
For an Oracle database, you can set table, index, and LOB custom table spaces for new root and child components and you can set the index and LOB table spaces for existing root and child components (root and child components that existed in versions of Content Manager EE earlier than Version 8.4.2). You can also modify the default index and LOB table space for a root or child component for any new indexes or LOB attributes that are added after the default is originally set. After modifying the default value of index or LOB table space, note that the new table spaces will only affect new LOB attributes and user defined indexes rather than the ones already created.
For this object | Can you set default table spaces? | Can you modify the default table space? |
---|---|---|
Existing root component (Version 8.4.1 and earlier) | Yes, for the root component index and LOB | Yes, index and LOB only |
Existing child component in an existing root component | Yes, for the child component index and LOB | Yes, index and LOB only |
New child component in an existing root component | Yes, for the child component table, index, and LOB | Yes, index and LOB only |
New root component | Yes, for the root component table, index, and LOB | Yes, index and LOB only |
New child component in a new root component | Yes, for the child component table, index, and LOB | Yes, index and LOB only |
In order to fully utilize this feature, map out your table spaces before creating item types in Content Manager EE. Consider how your data is structured, how many item types and components you might create, and what types of activities are going to occur on the item types and components. The use of custom table spaces for item types can improve database performance and management in some environments. Examples:
Using a single table space for all item type components, indexes, and LOB attributes can cause performance problems for large-scale Content Manager EE systems, and some individual item types can themselves be large. Therefore, putting each component in its own table space can result in improved database performance. In addition, if multiple custom table spaces are used, then the database administrator can monitor, back up, and restore table spaces based on the individual requirements of the item types and components. Finally, some item types are more active than others (for example, an item type for all scanned documents), and customizing a table space for the item type would enable the database administrator to span the table space across physical devices to improve performance of the Content Manager EE system.
See your database manual for best practices on creating table spaces.
The following system and components table are predefined by Content Manager EE during configuration. Only an experienced database administrator should change their physical properties.
Bufferpool | Table space | Description |
---|---|---|
icmlsmainbp32 | icmlfq32 | Holds all the large, persistent, "frequently used" tables (notably, all the item type tables). When a new item type is defined, the system administration client defines the new tables in this table space. If you customize the DDL, then define this table space across multiple containers for performance and scalability. |
icmlnf32 | Holds the large but less-frequently used tables, such as event logs, versions, and replicas. If you don't use any of these features, then this table space does not need much space. | |
icmlsvolatilebp4 | icmvfq04 | Holds the "volatile" tables, those whose size is usually small but which can vary widely, and for which both updates and deletes are very common. For example, the tables associated with document routing "in progress" items and checked out items. Putting this on a separate physical disk will help performance. |
icmlsfreqbp4 | icmsfq04 | Holds all the small "frequently used" but seldom updated tables (such as system information, user definitions, and ACLs), that do not take up much space but that are always needed in memory for good performance. |
cmbmain4 | cmbinv04 | Holds the federated inventory tables. |
Starting in Version 8.5, the Content Manager EE configuration now creates automatic storage tablespaces for the library server database and resource manager database instead of DMS (Database Managed Space) or SMS (System Managed Space).