ILM History

Partitioning the database with ILM is an efficient method to deal with the enormous amount of reporting, statistical and historical data that can be produced by the Automation Engine. After switching out/dropping partitions, you can still access their key data on the ILM History page. If for any reason you have to access old records, you can make a search here to find the partition on which they were stored and restore it.

The ILM History page displays the list of removed partitions.

The History list provides the following information:

Column	Description
Partition No.	Running number of the partition On MS SQL Server, staging tables always have the partition number "0".
Parent	It is possible to partition 5 table areas in the database; the Parent is the schema name (MS SQL Server) or the corresponding main table of the Automation Engine database (Oracle).
Filegroup / Tablespace	Name of the Filegroup (MS SQL Server) or the tablespace (Oracle) where the data is stored.
Start time	Time at which the partition has started to store data.
Endtime	Time at which the partition has finished to store data.
Min. RunID	Smallest RunID available in the partition, that is, the RunID of the first task that has been stored on it.
Max. RunID	Highest RunID available in the partition, that is, the RunID of the last task that has been stored on it.

Searching for Partitions

In large installations you may have many partitions. A search box is available on the toolbar that helps you find specific records:

The search is not context sensitive.

Start typing your text string in the search box. The application starts displaying possible matches as you type.

Exporting the Contents of the History List

This function allows you to export the currently visible data into a .csv file. To use it click at the top right-hand corner of your environment.

Depending on the browser you are using, you will either be prompt to define the location of the file or you will find it at the bottom of your browser.