UC_ILM_SETTINGS - Settings for Partitioning with ILM

This Variable (VARA) object defines the settings to work with the ILM functionality. It is supplied with system client 0000 and its settings apply to the whole Automation Engine system. For more information, see ILM - Information Lifecycle Management.

ACT_CONTAINER

• Description: Number of active containers

  For more information, see UC_ILM_CONTAINER_* - Automation Engine Database Partitions.

• Allowed values: 1 - 999

• Restart required: No

ACT_PARTITION

• Description: Current partition number

  The Automation Engine counts the partitions used for installing ILM and increases this value by 1 with each partition change.

• Restart required: No

ACTIVE

• Description: ILM status

• Allowed values: Y and N

• Restart required: No

CALENDAR

• Description: Calendar that includes the days on which the partition should be changed

• Format: Calendar object/calendar event

  The partition is changed at 00:00 on the days specified in the calendar event. The TimeZone of system client 0000 serves as the time basis.

• Restart required: No

EXECUTE_ON_FAILURE

• Description: Objects to be activated if an error occurs

  Note: The object is searched for and activated in all clients except for system client 0000. No activation is allowed in this client.

  The following script variables can be read from the read buffer:

  • ILM_ACTION#

    Action in which an error occurred. It can contain the following values:

    • ADD_PARTITION: partition change

    • CHECK: check for data records of active tasks in the partition

    • DROP: (Oracle) deletion of a partition

    • SWITCH_OUT: (MS SQL Server) switch-out of the oldest partition

  • ILM_PARTITION_NAME#

    Nam of the affected partition

  • ILM_ERROR_MSGNR#

    Error number of the Automation Engine

  • ILM_ERROR_MSG_INSERT#

    Variable part of the message text

  • ILM_DB_ERROR_MSG#

    Error message of the database

  • CONSISTENCY

    Consistency check of IPH table

• Restart required: No

EXECUTE_ON_SUCCESS

• Description: Object to be activated if an ILM action is successful

  Note: The object is searched for and activated in all clients except for system client 0000. No activation is allowed in this client.

  The following script variables can be read from the read buffer:

  • ILM_ACTION#

    Action in which an error occurred. It can contain the following values:

    • ADD_PARTITION: partition change

    • CHECK: check for data records of active tasks in the partition

    • DROP: (Oracle) deletion of a partition

    • SWITCH_OUT: (MS SQL Server) switch-out of the oldest partition

  • ILM_PARTITION_NAME#

    Nam of the affected partition

• Restart required: No

LOGIN

• Description: Name of a Login object including the database user to be used for executing ILM actions, see Login (LOGIN)

  The Login object must be stored in system client 0000 and must have the host type DB.

  The database user specified in the Login object must have permission to read the following system tables:

  • ALL_TAB_PARTITIONS

  • ALL_CONSTRAINTS

  • ALL_PART_INDEXES

  • ALL_INDEXES

• Restart required: No

ONLINE_PARTITIONS

• Description: Number of online partitions

• Allowed values: 1 - 999

• Restart required: No

PARTITION_SIZE_MULTIPLICATOR

• Description: Calculates if a turnaround should start

  The usage of the last partition is multiplied by this factor. If the product of the multiplication does not fit in the leftover range, a turnaround is started.

• Allowed values: 1 - 100

• Default value: 3

• Restart required: No

RETRY_MAX_COUNT

• Description: Maximum number of attempts to change the partition until ILM is automatically deactivated

• Allowed values: 1 - 3200

• Default value: 3

• Restart required: No

RETRY_TIME

• Description: Time in minutes to wait between attempts to change the partition RETRY_MAX_COUNT

• Allowed values: 1 - 3200

• Default value: 3

• Restart required: No

SCHEMA_OWNER

Important! This key applies only to Oracle databases.

• Description: Name of the user who created the AE database

  If no user is indicated, the system assumes that there is no further AE installation within the Oracle instance and that all tables within this instance are unique.

• Restart required: No

STATISTIC_TIME

Important! This key applies only to Oracle databases.

• Description: Time delay in minutes for the statistical update after the partition has been changed

• Allowed values: 0 - 1400

  Setting the value to 0 means that no statistical update is made.

• Default value: 15

• Restart required: No

TIMEOUT

• Description: Maximum time in seconds that the Automation Engine is stopped before the partition is changed

  When it is time to change the partition, processing in the AE system comes to a halt and waits until all work processes have ended their ongoing database transactions. The TIMEOUT key is decisive for the maximum waiting time. No new partition can be created if this period of time is exceeded.

• Allowed values: 60 - 32000

• Default value: 3600

• Restart required: No

See also:

• List of VARA Objects for System and Client Values
• User-Defined VARA Objects
• ILM - Information Lifecycle Management