7.7.1 Using the Data Retention Manager

The Data Retention Manager typically runs as part of automated processing that a job scheduling tool such as Maestro or Unicenter AutoSys controls. However, you can run Data Retention Manager manually on a daily, weekly, or monthly basis to manage database tables.

The following sections describe how to configure and execute the utility and maintain database partitions and indexes.

Configuring the Data Retention Manager

To configure the Data Retention Manager, follow these steps:
  1. Navigate to the <OFSAAI Installed Directory>/database/db_tools/mantas_cfg/ install.cfg file. This file contains common configuration information that Data Retention Manager and other utilities require for processing
  2. Use the sample install.cfg file to do a configuration.

    Note:

    The configuration parameters in the install.cfg are only used if command line parameters are not provided. It is strongly recommended that you provide command line parameters instead of using the install.cfg parameters.

The Data Retention Manager automatically performs system checks for any activity that may result in an error , such as insufficient space in the tablespace. If it discovers any such activity, it logs a Warning message that identifies the potential problem. If Data Retention Manager fails to run successfully, you can configure the utility so that the ingestion process for the following day still proceeds.

The following sample section from the install.cfg file provides other configuration information specific to this utility, including required and optional parameters.
######### DATA RETENTION MANAGER CONFIGURATION
##################
# Set the Data Retention Manager input variables
here.
##
drm_operation=P
drm_partition_type=A
drm_owner=${schema.mantas.owner}
drm_object_name=A
drm_weekly_proc_fl=Y

This example shows default values that the system uses only when calling the utility with no command line parameters.

Table 7-17 Data Retention Manager Processing Parameters

Parameter Description
drm_operation

Operation type:

  • P-Partition
  • AM-Add Monthly Partition
  • DM-Drop Monthly Partition
  • RI- Rebuild Indexes
  • RV- Recompile Views
  • T-Truncate Current Partition
drm_partition_type

Partition type:

  • D-Daily
  • W-Weekly
  • M- Monthly
  • X-Mixed-Date
  • A-All Partitions (Daily, Weekly, Monthly)
drm_owner Owner of the object (Atomic schema owner).
drm_object_name

Object name.

If performing an operation on all objects, the object name is A.
drm_weekly_proc_fl Flag that determines whether partitioning occurs weekly (Y and N).

Note:

The system processes Daily partitioned tables (drm_partition_type=D) and Mixed-date partitioned tables (drm_partition_type=X) simultaneously. Therefore, you need only specify D or X to process these tables.
An example for the Mixed-date partition, for the present date 20050711, is:
P20050711 (Current Day)
P20050708 (Previous Day and End of week #1)
P20050701 (End of previous week #2)
P20050630 (End of previous Month #1)
P20050624 (End of previous week #3)
P20050617 (End of previous week #4)
P20050531 (End of previous Month #2)