Model Repository Database Requirements
Before you create a repository, you need a database to store repository tables. Use the database client to create the database. After you create a database, you can use the Administrator tool to create a Model Repository Service.
Each Model repository must meet the following requirements:
- •Each Model repository must have its own schema. Two Model repositories or the Model repository and the domain configuration database cannot share the same schema.
- •Each Model repository must have a unique database name.
In addition, each Model repository must meet database-specific requirements.
Note: The Model Repository Service uses the DataDirect drivers included with the Informatica installation. Informatica does not support the use of any other database driver.
Mappings will fail with the following error if the database schema for the Model Repository Service database is not DB2:
[ICMD_10033] Command
[runmapping] failed with error [ [JSF_0045] The requested interface [com.informatica.ds.ms.common.MappingService]
is not available.]
To use Microsoft SQL Server as a Model Repository Service database, configure DB2 as the database schema and specify a tablespace.
IBM DB2 Database Requirements
Use the following guidelines when you set up the repository on IBM DB2:
- •Specify the tablespace name when you use IBM DB2 as the Model Repository database.
- •If the repository is in an IBM DB2 database, verify that IBM DB2 Version 10.5 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.
IBM DB2 Version 9.1
If the Model repository is in an IBM DB2 9.1 database, run the DB2 reorgchk command to optimize database operations. The reorgchk command generates the database statistics used by the DB2 optimizer in queries and updates.
Use the following command:
REORGCHK UPDATE STATISTICS on SCHEMA <SchemaName>
Run the command on the database after you create the repository content.
Microsoft SQL Server Database Requirements
Use the following guidelines when you set up the repository:
- •Specify the database schema name when you use Microsoft SQL Server as the Model Repository database.
- • 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: