Installation and Configuration Guide > Part II: Before You Install the Services > Prepare for Application Services and Databases > Model Repository Service

Model Repository Service

The Model Repository Service manages the Model repository. It receives requests from Informatica clients and application services to store or access metadata in the Model repository.

The following table summarizes the dependencies for products, services, and databases that are associated with the Model Repository Service.

Dependency	Summary
Products	The following products use the Model Repository Service: - Big Data Management - Big Data Parsing - Big Data Quality - Big Data Streaming - Enterprise Data Catalog - Enterprise Data Lake
Services	The Model Repository Service properties do require an association with another application service.
Databases	The Model Repository Service uses the following database: - Model repository. Stores metadata created by Informatica clients and application services.
Installer	You can create the Model Repository Service when you run the installer.

Model Repository Database Requirements

Informatica services and clients store data and metadata in the Model repository. Configure a monitoring Model repository to store statistics for ad hoc jobs, applications, logical data objects, SQL data services, web services, and workflows. Before you create the Model Repository Service, set up a database and database user account for the Model repository. It is recommended that you use different database configuration for Model repository and monitoring Model repository.

The Model repository supports the following database types:

•IBM DB2 UDB
•Microsoft SQL Server
•Oracle

Allow 3 GB of disk space for DB2. Allow 200 MB of disk space for all other database types.

When you configure Microsoft SQL Server, you can choose to configure the Microsoft Azure SQL Database as the Model repository.

For more information about configuring the database, see the documentation for your database system.

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.

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.