Change management in a One Identity Manager History Database
Data can be transferred directly from the One Identity Manager database into a One Identity Manager History Database. This is the default procedure for data archiving.
To use this procedure, make the following configuration settings in the 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.
-
Ensure that the Transport to history database schedule is enabled.
The schedule ensures the transfer of data from the One Identity Manager database to the One Identity Manager History Database. The schedule is run by default every 6 hours. In the Designer, adjust the interval as required.
Related topics
Deleting log entries 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.
Related topics
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 4: Configuration parameters for deleting logged data changes
|
Common | ProcessState | PropertyLog | Delete |
Allows configuration of deletion behavior for logged data changes. |
|
Common | ProcessState | PropertyLog | Delete | BulkCount |
Number of entries to be deleted in any operation. The default value is 200. |
|
Common | ProcessState | PropertyLog | Delete | TotalCount |
Total number of entries to be deleted in any processing run. The default value is 10000. |
Table 5: Configuration parameters for deleting process information
|
Common | ProcessState | ProgressView | Delete |
Allows configuration of deletion behavior for process information. |
|
Common | ProcessState | ProgressView | Delete | BulkCount |
Number of entries to be deleted in any operation. The default value is 200. |
|
Common | ProcessState | ProgressView | Delete | TotalCount |
Total number of entries to be deleted in any processing run. The default value is 10000. |
Table 6: Configuration parameters for deleting process history
|
Common | ProcessState | JobHistory | Delete |
Allows configuration of deletion behavior for the process history. |
|
Common | ProcessState | JobHistory | Delete | BulkCount |
Number of entries to be deleted in any operation. The default value is 200. |
|
Common | ProcessState | JobHistory | Delete | TotalCount |
Total number of entries to be deleted in any processing run. The default value is 10000. |
Table 7: Configuration parameters for deleting process status entries
|
Common | ProcessState | Delete |
Allows configuration of deletion behavior for process status entries. |
|
Common | ProcessState | Delete | BulkCount |
Number of entries to be deleted in any operation. The default value is 500. |
|
Common | ProcessState | Delete | TotalCount |
Total number of entries to be deleted in any processing run. The default value is 10000. |
Mapping data in the One Identity Manager History Database
For more detailed information about tracking and logging changes in One Identity Manager, see the One Identity Manager Configuration Guide.
Transferring changes from the One Identity Manager database to the History Database maps the information as follows.
|
Grouping of process triggers |
DialogProcess.GenProcIDGroup |
RawProcessGroup -> ProcessGroup |
|
Process triggers (actions) that trigger a change to the system |
DialogProcess |
RawProcess -> ProcessInfo
where ProcessInfo.UID_ProcessInfo = DialogProcess.GenProcID |
|
Process tracking - process |
DialogProcessChain |
RawProcessChain -> ProcessChain |
|
Process tracking - process step |
DialogProcessStep |
RawProcessStep -> ProcessStep |
|
Records of data changes - operations |
DialogWatchOperation |
RawWatchOperation -> WatchOperation |
|
Records of data changes - modified columns |
DialogWatchProperty |
RawWatchProperty -> WatchProperty |
|
Process history records - processes |
JobHistory |
RawJobHistory -> HistoryChain
where HistoryChain UID_HistoryChain = JobHistory.UID_Tree |
|
Process history records - process steps |
JobHistory |
RawJobHistory -> HistoryJob |
|
Process substitution of GenProcID if processes collide |
DialogProcessSubstitute |
RawProcessSubstitute -> ProcessSubstitute |
