Identity Manager 8.1.5 - Data Archiving Administration Guide

Change management Implementing a One Identity Manager History Database

Permissions for the One Identity Manager History Database on a SQL Server One Identity Manager History Database permissions in a managed instance Azure SQL Database Advanced configuration for transferring data Tips for using more than one SQL Server Tips for using integrated Windows authentication Setting up a One Identity Manager Service for the One Identity Manager History Database Setting up an administrative workstation for accessing the One Identity Manager History Database Installing One Identity Manager History Database components Installing a One Identity Manager History Database The update process for releasing a new version

Declaring the database source in the One Identity Manager History Database Archiving procedure setup

Selecting an archiving procedure in the One Identity Manager database Specifying data retention periods Configuring databases for archiving Deleting log entries in the One Identity Manager database without archiving Optimizing performance by deleting log entries

Configuring databases for archiving

One Identity Manager database:

Enable the Common | ProcessState | ExportPolicy configuration parameter in the Designer and enter the value HDB.
Configure the sections for export and define a retention period.
In the Designer, check the value of the Common | ProcessState | PackageSizeHDB configuration parameter. This parameter specifies the maximum number of progress groups that can be transferred to the One Identity Manager History Database. The default value is 10000.

One Identity Manager History Database:

Declare the One Identity Manager database as source database in the One Identity Manager History Database.
Importing is carried out at regular intervals by the One Identity Manager History Database's One Identity Manager Service. Configure and enable the system schedule Import process information directly in the Designer.

Deleting log entries in the One Identity Manager database without archiving

If records from separate sections are kept in the One Identity Manager database for a certain amount of time but are not archived later, you have the following options:

To exclude a certain section from archiving, do not configure it for export, just specify a retention period.
To delete all sections without archiving, specify a retention period. In the Designer, set the Common | ProcessState | ExportPolicy configuration parameter and enter the value NONE.

The records are deleted from the One Identity Manager database by DBQueue Processor when the retention period has ended. In addition, all entries for triggered actions are deleted if they have no corresponding records in those sections.

NOTE: If you do not specify a retention period, the records from that section are deleted from the One Identity Manager database during daily DBQueue Processor maintenance tasks.

Optimizing performance by deleting log entries

If there is a large amount of data, you can specify the number of objects to delete per DBQueue Processor operation and run in order to improve performance. You use configuration parameters to make the choice for each section.

Table 3: Configuration parameters for deleting logged data changes
Configuration parameter	Meaning
Common \| ProcessState \| PropertyLog \| Delete	This configuration parameter allows configuration of deletion behavior for logged data changes.
Common \| ProcessState \| PropertyLog \| Delete \| BulkCount	This configuration parameter contains the number of entries to be deleted in an operation.
Common \| ProcessState \| PropertyLog \| Delete \| TotalCount	This configuration parameter contains the total number of entries to be deleted in any processing run.

Table 4: Configuration parameters for deleting process information
Configuration parameter	Meaning
Common \| ProcessState \| ProgressView \| Delete	This configuration parameter allows configuration of deletion behavior for process information.
Common \| ProcessState \| ProgressView \| Delete \| BulkCount	This configuration parameter contains the number of entries to be deleted in an operation.
Common \| ProcessState \| ProgressView \| Delete \| TotalCount	This configuration parameter contains the total number of entries to be deleted in any processing run.

Table 5: Configuration parameters for deleting process history
Configuration parameter	Meaning
Common \| ProcessState \| JobHistory \| Delete	This configuration parameter allows configuration of deletion behavior for the process history.
Common \| ProcessState \| JobHistory \| Delete \| BulkCount	This configuration parameter contains the number of entries to be deleted in an operation.
Common \| ProcessState \| JobHistory \| Delete \| TotalCount	This configuration parameter contains the total number of entries to be deleted in any processing run.

Table 6: Configuration parameters for deleting process status entries
Configuration parameter	Meaning
Common \| ProcessState \| Delete	This configuration parameter allows configuration of deletion behavior for process status entries.
Common \| ProcessState \| Delete \| BulkCount	This configuration parameter contains the number of entries to be deleted in an operation.
Common \| ProcessState \| Delete \| TotalCount	This configuration parameter contains the total number of entries to be deleted in any processing run.

Identity Manager 8.1.5 - Data Archiving Administration Guide

Configuring databases for archiving

One Identity Manager database:

One Identity Manager History Database:

Related topics

Deleting log entries in the One Identity Manager database without archiving

Related topics

Optimizing performance by deleting log entries

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Identity Manager 8.1.5 - Data Archiving Administration Guide

Configuring databases for archiving

One Identity Manager database:

One Identity Manager History Database:

Related topics

Deleting log entries in the One Identity Manager database without archiving

Related topics

Optimizing performance by deleting log entries