Maintenance

Cube

Purpose

Invalidate N1 AA Analyzer cube data cache

Menu

Administration ⇒ Analyzer ⇒ Maintenance

Use case

Exceptional circumstances

You can use the Invalidate button to clear the N1 AA Analyzer cube data cache in memory. This cache is built up during execution of N1 AA Analyzer analyses and significantly increases analysis performance. It is valid only while no change happens to the underlying N1 AA Analyzer data and repository data in the database. Generally, the N1 AA Analyzer does all the cache management itself, so there is no need to invalidate it manually. Only use this function in case you had changed the N1 AA database manually and want to get rid of the memory-mirrored old cache data.

Reorganizations

Purpose

Manually archive or unarchive historical N1 AA Analyzer data

Menu

Administration ⇒ Analyzer ⇒ Maintenance

Use case

Weekly or monthly business. Only needed if no reorganization is already scheduled as job in the background.

By entering a start and end timestamp and pressing the Archive or Unarchive button, a reorganization is executed through a newly created ArchiveUnarchiveJob job. In general, keeping the N1 AA Analyzer database small, offers maximum analysis performance. However, besides all regularly scheduled reorganization runs you can move data into an archive table (technically between database tables ResourceConsumption and ResourceConsumptionArchive) without limitation. Additionally, to keep the database clean, you can export or import the archive and vacuum the database using PostgreSQL database tools. Note that while an ArchiveUnarchiveJob is running, both the Archive and Unarchive buttons are disabled.

Imports

Purpose

Manually import N1 AA Analyzer data

Menu

Administration ⇒ Analyzer ⇒ Maintenance

Use case

Daily business. Only needed if no import is already scheduled as job in the background.

By clicking the Execute button, an N1 AA Analyzer data import is started. The data, that had been previously written locally by the performance collectors, is imported into the N1 AA database. If a regular data import is not scheduled by a persistent AnalyseDataImportJob job, a new transient job is created and executed automatically. For more information, see Scheduler. Otherwise, the persistent job is used for this execution. The advantage of this behavior is that all log lines of this manual data import job are appended to the jobs normal log along with the scheduled job lines and saved to the database. Note that while an AnalyseDataImportJob job is running, the Execute button appears disabled.