Search

Configuration Guide

Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Audit Log Table

Audit Log Table

The audit log information is stored in the audit log table named C_REPOS_AUDIT.

The following table shows the schema for the audit log table, C_REPOS_AUDIT:

Name	Oracle Data Type	IBM DB2 Data Type	Microsoft SQL Server Data Type	Description
ROWID_AUDIT	CHAR(14)	CHARACTER(14)	NCHAR (14)	Unique ID for this record. Primary key.
CREATE_DATE	TIMESTAMP	TIMESTAMP	DATATIME2	Record creation date. Defaults to the system date.
CREATOR	VARCHAR2(50)	VARCHAR (50)	NVARCHAR (50)	User associated with the audit event.
LAST_UPDATE_DATE	TIMESTAMP	TIMESTAMP	DATETIME2	Same as CREATE_DATE.
UPDATED_BY	VARCHAR2(50)	VARCHAR (50)	NVARCHAR (50)	Same as CREATOR.
COMPONENT	VARCHAR2(50)	VARCHAR(50)	NVARCHAR (50)	Component involved: SIF.sif.api
ACTION	VARCHAR2(50)	VARCHAR(50)	NVARCHAR (50)	One of the following: SIF request name message queue name
STATUS	VARCHAR2(50)	VARCHAR(50)	NVARCHAR (50)	One of the following values: debug info warn error fatal
ROWID_OBJECT	CHAR(14)	CHARACTER(14)	NCHAR (14)	The rowid_object, if known.
DATA_XML	CLOB	CLOB	NVARCHAR (max)	XML associated with the auditable event: request, response, or JMS message. Populated only if the Include XML option is enabled (checked). Passwords are never stored in the audit log. If a password exists in the XML stream (whether encrypted or not), Informatica MDM Hub replaces the password with the text “******”.
CONTEXT_XML	CLOB	CLOB	NVARCHAR (max)	XML that might contain contextual information, such as configuration data, the URL that was invoked, trace for the execution of a match rule, and so on. If an error occurs, the request XML is always put in this column to ensure its capture in case auditing was not enabled for the SIF request that was invoked. Populated only if the Include XML option is enabled (checked).
ROWID_AUDIT_PREVIOUS	CHAR(14)	CHARACTER(14)	NCHAR (14)	Reference to the ROWID_AUDIT of the related previous entry. For example, links a response entry to its corresponding request entry.
INTERACTION_ID	NUMBER(19)	BIGINT(8)	NUMERIC (19,0)	Interaction ID. May be NULL since INTERACTION_ID is optional.
USERNAME	VARCHAR2(50)	VARCHAR(50)	NVARCHAR (50)	User that invoked the SIF request. Null for message queues.
FROM_SYSTEM	VARCHAR2(50)	VARCHAR(50)	NVARCHAR (50)	Source system for a SIF request, or Admin for message queues.
TO_SYSTEM	VARCHAR2(50)	VARCHAR(50)	NVARCHAR (50)	System to which the audited event is related. For example, API Requests to Hub set this to “Admin” and the responses are the system or null if not known (and vice-versa for Responses).
TABLE_NAME	VARCHAR2(100)	VARCHAR(100)	NVARCHAR (100)	Table in the Hub Store that is associated with this audited event.
CONTEXT	VARCHAR2(255)	VARCHAR(255)	NVARCHAR (255)	Metadata. For example, pkeySource This is null for audits from Hub, but may have values for audits done through the SIF API.

Using the Audit Log

Watch

Comments

0 COMMENTS

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