Configuration During Implementation

As part of initial provisioning, default partitions are created for the following:

• Customer Care and Billing & Oracle Utilities Application Framework Objects: 48 months

• Meter Data Management Objects: 13 months, with exception of Initial Measurement Data, which is 3 months

Work and Asset Management and Operational Device Management do not yet support ILM (W1 prefixed tables are not partitioned).

Adjustments to the default partitioning can be made, ideally during implementation (before go-live). Changes after go-live can cause lengthy update periods (downtime), as data may have to be shifted between partitions.

Note: Based on these recommendations, PMax partitions should be empty. If this is the case the partition split will occur quickly. If there is data in the PMax partition because new partitions weren't created during implementation, when data is moved to one new partition, the split will occur quickly, but it will take time to build the index for the new partition, depending on how much data is moved. If a subset of records are moved out of the PMax partition, and some remain, the split could take hours, depending on how much data is present.

New historical partitions are created (as needed) by the "Add Partition" batch process (K1-ILMAD) based on retention period settings. Irrespective of creating partitions for current, future, or previous months, the K1-ILMAD batch process always creates the new partition in Advance Compression. Historical partitions created by K1-ILMAD can be changed to HCC by running the compression batch job.

Loading and/or processing of the data from HCC is slower than Advance compression (only applicable to non-Measurement tables) between 2% to 5%, however after go-live, compression jobs will run effectively.

As part of the implementation, customers are required to configure retention periods in two ILM-related Master Configurations and scheduler batch streams to enable ILM batches run monthly.

ILM-related Master Configurations include the following:

• ILM Configuration

• ILM Configuration - MDM Sub-retention

ILM Configuration

The ILM Configuration master configuration contains a Default Retention Period parameter as a global default value that will be used if not overridden at the maintenance object level. This configuration also includes ILM Eligibility Algorithms along with associated Crawler Batch controls for each maintenance object.

A Retention Days parameter can be set on individual ILM managed maintenance Objects, which override the Default Retention Period.

Oracle recommends setting the ILM Master Configuration Default Retention Period to 1461 days (or a value override by implementations), then setting the Retention Period for Meter Data Management maintenance objects to 400 days (just over 13 months).

For more details on Meter Data Management-specific guidelines, please refer to Partioning and Data Removal in the Oracle Utilities Meter Solution Administrative User guide

ILM Configuration - MDM Sub-Retention

The ILM Configuration - MDM Sub-retention master configuration is provided for specific configuration related to three high-volume Meter Data Management objects: Initial Measurement Data, Activity, and Device Event. This master configuration support defining sub-retention periods in days for each object and further by 'type' to allow for early archive eligibility of non-critical data (by creating sub-partitions).

The ILM Configuration - MDM Sub Retention master configuration will actually set the ILM Retention Period in Days Maintenance Object Option for the three maintenance objects supported: Initial Measurement Data, Activity, and Device Event.

This optional feature allows you to differentiate retention of initial measurements by Interval vs. Scalar as well as by unit of measure (UOM) code, Device Events by Event Category, and Activities by Activity Type. For instance, you could choose to specify a sub-retention value of 90 days for Device Event Types that are not critical, and drop those subsets of records early - while the critical events could be kept for the full retention period of 13 months.

Initially installed partition defaults for sub-partitions are as follows:

• Initial Measurement Data: 30, 60, 90 days

• Activity / Device Event: 30, 60, 90, 400 days.

This is the default setup, but these sub-partitions will be dropped if not used.