Exception Management Audit Database Requirements
The exception management audit database is a single repository for data that describes the work that Analyst tool users perform on Human task instances. The Analyst Service identifies the database connection and the schema name. The Data Integration Service writes the audit data to the database.
If the Analyst Service does not identify an exception management audit database, the Data Integration Service writes the audit data to the database that contains the task instance records.
The exception management audit database supports the following database types:
- •IBM DB2 UDB
- •Microsoft SQL Server
- •Microsoft Azure SQL Database
- •Oracle
- •PostgreSQL
Allow 200 MB of disk space for the database.
Note: Ensure that you install the database client on the machine on which you want to run the Content Management Service.
IBM DB2 Database Requirements
Use the following guidelines when you set up the repository on IBM DB2:
- •The database user account must have the CREATETAB, CONNECT, CREATE VIEW, and CREATE FUNCTION privileges.
- •Informatica does not support IBM DB2 table aliases for repository tables. Verify that table aliases have not been created for any tables in the database.
- •Set the tablespace pageSize parameter to 32768 bytes.
- •Set the NPAGES parameter to at least 5000. The NPAGES parameter determines the number of pages in the tablespace.
Microsoft Azure SQL Database Requirements
Use the following guidelines when you set up the repository:
- •Set the allow snapshot isolation and read committed isolation level to ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT to minimize locking contention.
To set the isolation level for the database, run the following commands:
ALTER DATABASE DatabaseName SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE DatabaseName SET READ_COMMITTED_SNAPSHOT ON
To verify that the isolation level for the database is correct, run the following commands:
SELECT snapshot_isolation_state FROM sys.databases WHERE name=[DatabaseName]
SELECT is_read_committed_snapshot_on FROM sys.databases WHERE name = DatabaseName
- •The database user account must have the CONNECT, CREATE TABLE, and CREATE VIEW privileges.
Microsoft SQL Server Database Requirements
Use the following guidelines when you set up the repository on Microsoft SQL Server:
- •The database user account must have the CONNECT, CREATE TABLE, CREATE VIEW, and CREATE FUNCTION privileges.
Oracle Database Requirements
Use the following guidelines when you set up the repository on Oracle:
- • Verify that the database user has the following privileges:
- - ALTER TABLE
- - CREATE SESSION
- - CREATE SEQUENCE
- - CREATE TABLE
- - DROP TABLE
- - UPDATE TABLE
- •Informatica does not support Oracle public synonyms for repository tables. Verify that public synonyms have not been created for any tables in the database.
- •Set the following parameters to the Informatica recommended values:
Parameter | Recommended Value |
|---|
open_cursors | 3000 |
Sessions | 1000 |
Processes | 1000 |
PostgreSQL Requirements
Use the following guidelines when you set up the repository on PostgreSQL:
- •Use a JDBC connection to connect to the PostgreSQL database.
Informatica installs a DataDirect JDBC driver for PostgreSQL that you can use to connect to the database. Find the driver in the clients/DeveloperClient/infacmd installation directory, and copy the driver to the clients/externaljdbcjars directory .
- •Specify the database schema name. Do not leave the schema name blank.
If the database uses the default PostgreSQL schema name of public, you can specify public as the schema name.
- •Verify that the database user has the CONNECT and CREATE TABLE privileges.