Rapidly growing volumes of data make it more difficult than ever for today’s business to remain agile and responsive to competitive demands. To enhance performance of applications while trying to maintain massive amounts of data, DB2 introduced the Partitioned Tablespace.  While this tablespace provides parallel access to applications as well as many other benefits, it comes with a cost.  Administering partitioned tablespaces is a real struggle for DB2 DBAs.

• Deciding new limitkeys is difficult and time consuming as data grows
• Imbalanced partitions after application activity can cause degradation in application performance
• Individual partitions approaching DB2 limits cause surprise outages to the business
• No safe and easy way to convert Simple and Segmented Table spaces to Partitioned Tablespaces

The DB2 Solutions force the DBA to turn over full control of their partitions to the DB2 Reorg. The Reorg can automatically "smooth" partitions. However, this process is slow and inflexible. DBAs have no way to know what the object will look like after the rebalance and no way to control which keys of the clustering index should be used for the rebalance. Alternatively, the DBA may manually update the limitkeys followed by a Reorg. This process is extremely dangerous and offers no help in the formation of the limitkeys (often the hardest part) or a look ahead to see if the desired outcome will be met. The DB2 options force the DBA to turn over control and hope for no surprises.

CDB’s Partition Management Solution offers everything from complete single step rebalance to full limitkey overrides to powerful “What-If” processing.  A DBA may simply run the product over and over to determine which limitkeys or combination of columns produce the actual desired results before running the full re-partition, all while leaving the object 100% available to applications.  The CDB Partition Management Solution helps you remain flexible and in control no matter how much data you manage.

Key Benefits

• Powerful “What-If” processing while leaving the object 100% available to applications
• Ability to change the number of KEYCOLS used in the repartition
• Determines the new limitkeys automatically or the DBA can feed in new limitkeys or any combination of both methods
• Flexible and Intelligent Automation to meet any repartitioning requirements of a DB2 shop
• Split or add partitions
• Convert Simple or Segmented Tablespaces to Partitioned Tablespaces.