To increase application response time, you want to divide the transactions in a high-volume general ledger application module so that the application queries specific segments. You decide to create segments based on calendar year so that users can easily query the module by year. In the Enterprise Data Manager you create a time dimension that you configure as a date range. Then you create a general ledger segmentation group that contains related general ledger tables. In the Data Archive user interface you create a data classification and configure the time dimension to create segments for all general ledger transactions by year, from 2010 through the current year.

When you run the segmentation policy, the ILM Engine divides each table across the general ledger segmentation group based on the dimension you defined. The smart partitioning process creates a segment that contains a tablespace for each year of general ledger transactions. The smart partitioning process also creates a default segment for new transactions and transactions that do not meet business rule requirements for the other segments. As users enter new transactions in the general ledger, the application inserts the transactions in the default segment where they remain until you move them to another segment or create a new default segment.