Design Guide

10.5 HotFix 2
- 10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Auditing

The auditing of the Persistent-IDs can be enabled at multiple levels. These levels include tracking of changes to a cluster, cluster members and preferred records. A further fine grained level auditing can be performed by auditing the IDT records to main previous versions.

The auditing of a cluster involves logging of all changes done to a cluster. This level of auditing limits to tracking the changes to a cluster level.

The auditing of member records on a cluster involves logging the changes to the member records of a cluster. This level of auditing tracks individual members of a cluster based on the operations done on the cluster.

The auditing of preferred records on a cluster involves logging of the maintenance operations of the cluster and its impact on the preferred record. This level of auditing track the changes done in respect to selection or changes done to the preferred record for a specific cluster

For example: When two clusters (say 1 and 2) merge, the cluster level audit would record details to indicate cluster 1 merged into cluster 2. The record level audit would record details of each of the records of cluster 1 that moved to cluster 2. In case the merge resulted in a change in the preferred record the change would be captured by the preferred record audit.

The

IDT

option

Audit-PID

enables the auditing of Persistent-IDs maintenance operations (add, delete) by logging all changes to a database table named

<decorated IDT name>_MH

. The layout of the Audit Table is described in the IDT-Definition section of this manual. This option is now obsoleta.

The Persistent ID options

Audit-Cluster

Audit-Record

can be used to enable the auditing of Persistent-IDs for cluster and member records respectively.

To enable auditing of preferred records (

Audit-Preferred

) and auditing of member records (

Audit-Record

) on a cluster, it is mandatory to enable the cluster level auditing (

Audit-Cluster

The audit records are stored in an SQL-accessible table named

IDT_Name_CA

IDT_Name_RA

and

IDT_Name_PA

where

IDT_Name

is the fully qualified name (database table name) of the IDT being clustered.

Audit table layout

The Cluster audit table contains the following columns:

RECID

is reserved for internal use.

IDS_TS

contains the timestamp in format YYYYMMDDHHMISS

IDS_CL_ID

contains the

ClusterId

(defined by Persistent-ID-Prefix).

IDS_CL_NUM

contains the

ClusterNumber

IDS_CL_NUM_TO

contains the

ClusterNumber

of the destination cluster during merge or split operations

IDS_OPERATION

contains the operation performed. It contains the following values: 1 = add, 2 = delete, 3 = link, 4 = unlink, 5 = update, 6 = update of PREFERRED, 7 = update of COMMENT, 8 = update of STATUS, 9 = add due to update, and 10 = delete due to update.

IDS_MODIFIER

is reserved for future use

IDS_FLAG

contains flags used to indicate the state of the cluster. It is a bit-field containing the following values: 0x0001 = created by automated process, 0x0002 = Manually modified, 0x0004 = new cluster, and 0x0004 = undecided.

IDS_IDT_RECID

contains the

RecID

of the corresponding IDT row.

IDS_IDT_RECID_TO

contains the

RecID

of the matched IDT row.

IDS_SCORE

is the score achieved by the record when it joined the cluster. The first member always has a score of 0. Note that scores are not recalculated when additional members join the cluster, so the scores do not reflect the state of a cluster at a specific point in time.

IDS_COMMENT

contains the comments

The member record audit table contains the following columns:

RECID

is reserved for internal use.

IDS_TS

contains the timestamp in format YYYYMMDDHHMISS

IDS_CL_ID

contains the

ClusterId

(defined by

Persistent-ID-Prefix

IDS_CL_NUM

contains the

ClusterNumber

IDS_CL_NUM_TO

contains the

ClusterNumber

of the destination cluster during merge or split operations.

IDS_OPERATION

contains the operation performed. It contains the following values: 1 = add, 2 = delete, 3 = move, and 4 = update.

IDS_MODIFIER

is reserved for future use

IDS_FLAG

IDS_IDT_RECID

contains the

RecID

of the corresponding IDT row.

IDS_CLACT_RECID

contains the

RecID

of the related cluster audit record.

Source Primary Key 1

...

Source Primary Key n

A maximum of 36 primary keys is permitted. See the

Persistent-ID

section for details.

The preferred record audit table contains the following columns:

RECID

is reserved for internal use.

IDS_TS

contains the timestamp in format YYYYMMDDHHMISS

IDS_CL_ID

contains the

ClusterId

(defined by

Persistent-ID-Prefix

IDS_CL_NUM

contains the

ClusterNumber

IDS_OPERATION

contains the operation performed. It contains the following values: 5 = generate, 6 = regenerate, 7 = select, 8 = deselect, 9 = delete, and 10 = modify. The values 7, 8, and 10 are applicable only for the Member-is-Preferred option.

IDS_MODIFIER

is reserved for future use.

IDS_FLAG

IDS_IDT_RECID

contains the

RecID

of the corresponding IDT row.

IDS_CLACT_RECID

contains the

RecID

of the related cluster audit record.

Source Primary Key 1

...

Source Primary Key n

A maximum of 36 primary keys is permitted. Refer to the

Persistent-ID

section for details.

Persistent-ID (Dynamic Clustering)

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Design Guide

Design Guide

Auditing

Auditing

Audit table layout