This variable includes the settings for ILMStands for Information Lifecycle Management, which refers to a wide-ranging set of strategies for administering storage systems on computing devices. functionality.
Key |
Value |
Restart required |
---|---|---|
ACT_CONTAINER |
Number of the active container Allowed values: "1" - "999" |
No |
ACT_PARTITION |
Current partition number The Automation Engine counts the partitions used for installing ILM and increases this value by "1" with each partition change. |
No |
ACTIVE |
ILM status Allowed values: "Y" and "N" "Y" - ILM is active, i.e. new partitions are created and switch-outs (only MS SQL Server) are performed. |
No |
CALENDAR |
Calendar that includes the days on which the partition should be changed. Format: Calendar object/calendar keyword The partition is changed at 00:00 on the days specified in the calendar keyword. The TimeZone of system client 0000 serves as the time basis. |
No |
EXECUTE_ON_FAILURE |
Object that should be activated if an error occurs. The following script variables can be read from the read buffer:
The object is searched for and activated in all clients except for system client 0000. No activation is allowed in this client. |
No |
EXECUTE_ON_SUCCESS |
Object that should be activated if an ILM action was successful The following script variables can be read from the read buffer:
The object is searched for and activated in all clients except for system client 0000. No activation is allowed in this client. |
No |
LOGIN |
Name of a Login object that includes the database user to be used for executing ILM actions. In the Login object, select the host type "DB". The Login object must be stored in system client 0000. The database user specified in the Login object must have permission to read the following system tables:
|
No |
ONLINE_PARTITIONS |
Number of online partitions. Allowed values: "1" - "999" |
No |
RETRY_MAX_COUNT |
Maximum number of attempts to change the partition until ILM is automatically deactivated. Allowed values: "1" - "3200" |
No |
RETRY_TIME |
Time (in minutes) to wait between attempts to change the partition (RETRY_MAX_COUNT). Allowed values: "1" - "3200" |
No |
SCHEMA_OWNER |
Name of the user who created the AE database. This parameter is required for Oracle databases only. Note that this parameter is case-sensitive. The Automation Engine assumes that there is no further AE installationation within the Oracle instance and that all tables within this instance are unique if no user is indicated. |
No |
STATISTIC_TIME |
Time delay in minutes for the statistical update after the partition has been changed (only Oracle). Allowed values: "0" - "1400" Value "0" has the effect that no statistical update is made. |
No |
TIMEOUT |
Maximum time in seconds that the Automation Engine is stopped before the partition is changed. Allowed values: "60" - "32000" 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 key TIMEOUT is decisive for the maximum waiting time. No new partition can be created if this period of time is exceeded. |
No |
This variable is supplied in system client 0000. Its settings apply to the whole AE system and can only be modified in client 0000.
It contains the settings for partitioning with ILM.
See also:
Overview of all variables in Table Form
Variable
Partitioning with ILM