Domain Configuration Repository Database Requirements
Informatica components store metadata in relational database repositories. The domain stores configuration and user information in a domain configuration repository.
You must set up a database and user account for the domain configuration repository before you run the installation. The database must be accessible to all gateway nodes in the Informatica domain.
When you install Informatica, you provide the database and user account information for the domain configuration repository. The Informatica installer uses JDBC to communicate with the domain configuration repository.
The domain configuration repository supports the following database types:
- •IBM DB2 UDB
- •Microsoft SQL Server
- •Oracle
- •Sybase ASE
Allow 200 MB of disk space for the database.
IBM DB2 Database Requirements
Use the following guidelines when you set up the repository on IBM DB2:
- •If the repository is in an IBM DB2 9.7 database, verify that IBM DB2 Version 9.7 Fix Pack 7 or a later fix pack is installed.
- •On the IBM DB2 instance where you create the database, set the following parameters to ON:
- - DB2_SKIPINSERTED
- - DB2_EVALUNCOMMITTED
- - DB2_SKIPDELETED
- - AUTO_RUNSTATS
- •On the database, set the configuration parameters.
The following table lists the configuration parameters that you must set:
Parameter | Value |
|---|
logfilsiz | 8000 |
maxlocks | 98 |
locklist | 50000 |
auto_stmt_stats | ON |
- •Set the tablespace pageSize parameter to 32768 bytes.
In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not specify a tablespace, the default tablespace must meet the pageSize requirements.
In a multi-partition database, specify a tablespace that meets the pageSize requirements. Define the tablespace in the catalog partition of the database.
- •Set the NPAGES parameter to at least 5000. The NPAGES parameter determines the number of pages in the tablespace.
- •Verify that the database user has CREATETAB, CONNECT, and BINDADD 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.
- •In the DataDirect Connect for JDBC utility, update the DynamicSections parameter to 3000.
The default value for DynamicSections is too low for the Informatica repositories. Informatica requires a larger DB2 package than the default. When you set up the DB2 database for the domain configuration repository or a Model repository, you must set the DynamicSections parameter to at least 3000. If the DynamicSections parameter is set to a lower number, you can encounter problems when you install or run Informatica services.
For more information about updating the DynamicSections parameter, see
Updating the DynamicSections Parameter of a DB2 Database.
Microsoft SQL Server Database Requirements
Use the following guidelines when you set up the repository on Microsoft SQL Server:
- • 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.
Oracle Database Requirements
Use the following guidelines when you set up the repository on Oracle:
- •Set the open_cursors parameter to 4000 or higher.
- •Set the permissions on the view $parameter for the database user.
- •Set the privileges for the database user to run show parameter open_cursors in the Oracle database.
When you run the pre-installation (i10Pi) system check tool, i10Pi runs the command against the database to identify the OPEN_CURSORS parameter with the domain database user credentials.
You can run the following query to determine the open cursors setting for the domain database user account:
SELECT VALUE OPEN_CURSORS FROM V$PARAMETER WHERE UPPER(NAME)=UPPER('OPEN_CURSORS')
- • Verify that the database user has the following privileges:
- - CREATE SEQUENCE
- - CREATE SESSION
- - CREATE SYNONYM
- - CREATE TABLE
- - CREATE VIEW
- •Informatica does not support Oracle public synonyms for repository tables. Verify that public synonyms have not been created for any tables in the database.
Sybase Database Requirements
Use the following guidelines when you set up the repository on Sybase ASE:
- •Set the database server page size to 16K or higher. You must set the page size to 16K as this is a one-time configuration and cannot be changed afterwards.
- • Set the database locking configuration to use row-level locking.
The following table describes the database locking configuration that you must set:
Database Configuration | Sybase System Procedure | Value |
|---|
Lock scheme | sp_configure "lock scheme" | 0, datarows |
- •Set the Sybase database option "ddl in tran" to TRUE.
- •Set "allow nulls by default" to TRUE.
- •Turn ON the Sybase database option select into/bulkcopy/pllsort.
- •Enable the "select" privilege for the sysobjects system table.
- • Create the following login script to disable the default VARCHAR truncation:
create procedure dbo.sp_string_rtrunc_proc as set string_rtruncation on
sp_modifylogin "user_name", "login script", sp_string_rtrunc_proc
The login script is executed every time the user logs into the Sybase instance. The stored procedure sets the parameter at the session level. The sp_modifylogin system procedure updates "user_name" with the stored procedure as its "login script". The user must have permission to invoke the stored procedure.