Metadata Manager Repository Database Requirements
Metadata Manager repository contains the Metadata Manager warehouse and models. The Metadata Manager warehouse is a centralized metadata warehouse that stores the metadata from metadata sources.
Specify the repository details when you create a Metadata Manager Service.
The Metadata Manager repository supports the following database types:
- •IBM DB2 UDB
- •Microsoft SQL Server
- •Oracle
Allow 1 GB of disk space for the database.
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:
- •The database user account that creates the repository must have privileges to perform the following operations:
- - ALTER TABLE
- - CREATE FUNCTION
- - CREATE INDEX
- - CREATE PROCEDURE
- - CREATE TABLE
- - CREATE VIEW
- - DROP PROCEDURE
- - DROP TABLE
- - INSERT INTO
- •The database user that creates the repository must be able to create tablespaces with page sizes of 32 KB.
- • Set up system temporary tablespaces larger than the default page size of 4 KB and update the heap sizes.
Queries running against tables in tablespaces defined with a page size larger than 4 KB require system temporary tablespaces with a page size larger than 4 KB. If there are no system temporary table spaces defined with a larger page size, the queries can fail. The server displays the following error:
SQL 1585N A system temporary table space with sufficient page size does not exist. SQLSTATE=54048
Create system temporary tablespaces with page sizes of 8 KB, 16 KB, and 32 KB. Run the following SQL statements on each database to configure the system temporary tablespaces and update the heap sizes:
CREATE Bufferpool RBF IMMEDIATE SIZE 1000 PAGESIZE 32 K EXTENDED STORAGE ;
CREATE Bufferpool STBF IMMEDIATE SIZE 2000 PAGESIZE 32 K EXTENDED STORAGE ;
CREATE REGULAR TABLESPACE REGTS32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('C:\DB2\NODE0000\reg32' ) EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL RBF;
CREATE SYSTEM TEMPORARY TABLESPACE TEMP32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('C:\DB2\NODE0000\temp32' ) EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.33 BUFFERPOOL STBF;
GRANT USE OF TABLESPACE REGTS32 TO USER <USERNAME>;
UPDATE DB CFG FOR <DB NAME> USING APP_CTL_HEAP_SZ 16384
UPDATE DB CFG FOR <DB NAME> USING APPLHEAPSZ 16384
UPDATE DBM CFG USING QUERY_HEAP_SZ 8000
UPDATE DB CFG FOR <DB NAME> USING LOGPRIMARY 100
UPDATE DB CFG FOR <DB NAME> USING LOGFILSIZ 2000
UPDATE DB CFG FOR <DB NAME> USING LOCKLIST 1000
UPDATE DB CFG FOR <DB NAME> USING DBHEAP 2400
"FORCE APPLICATIONS ALL"
DB2STOP
DB2START
- • Set the locking parameters to avoid deadlocks when you load metadata into a Metadata Manager repository on IBM DB2.
The following table lists the locking parameters you can configure:
Parameter Name | Value | IBM DB2 Description |
|---|
LOCKLIST | 8192 | Max storage for lock list (4KB) |
MAXLOCKS | 10 | Percent of lock lists per application |
LOCKTIMEOUT | 300 | Lock timeout (sec) |
DLCHKTIME | 10000 | Interval for checking deadlock (ms) |
Also, for IBM DB2 9.7 and earlier, set the DB2_RR_TO_RS parameter to YES to change the read policy from Repeatable Read to Read Stability.
- •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.
Note: If you use IBM DB2 as a metadata source, the source database has the same configuration requirements.
Microsoft SQL Server Database Requirements
Use the following guidelines when you set up the repository on Microsoft SQL Server:
- •The database user account that creates the repository must have privileges to perform the following operations:
- - ALTER TABLE
- - CREATE CLUSTERED INDEX
- - CREATE INDEX
- - CREATE PROCEDURE
- - CREATE TABLE
- - CREATE VIEW
- - DROP PROCEDURE
- - DROP TABLE
- - INSERT INTO
- •If the repository must store metadata in a multibyte language, set the database collation to that multibyte language when you install Microsoft SQL Server. For example, if the repository must store metadata in Japanese, set the database collation to a Japanese collation when you install Microsoft SQL Server. This is a one-time configuration and cannot be changed.
Oracle Database Requirements
Use the following guidelines when you set up the repository on Oracle:
- •The database user account that creates the repository must have privileges to perform the following operations:
- - ALTER TABLE
- - CREATE CLUSTER
- - CREATE INDEX
- - CREATE OR REPLACE FORCE VIEW
- - CREATE OR REPLACE PROCEDURE
- - CREATE OR REPLACE VIEW
- - CREATE TABLE
- - DROP TABLE
- - INSERT INTO TABLE
- •Set the following parameters for the tablespace on Oracle:
- <Temporary tablespace>
- Resize to at least 2 GB.
- CURSOR_SHARING
- Set to FORCE.
- MEMORY_TARGET
- Set to at least 4 GB.
- Run SELECT * FROM v$memory_target_advice ORDER BY memory_size; to determine the optimal MEMORY_SIZE.
- MEMORY_MAX_TARGET
- Set to greater than the MEMORY_TARGET size.
- If MEMORY_MAX_TARGET is not specified, MEMORY_MAX_TARGET defaults to the MEMORY_TARGET setting.
- OPEN_CURSORS
- Set to 3000 shared.
- Monitor and tune open cursors. Query v$sesstat to determine the number of currently-opened cursors. If the sessions are running close to the limit, increase the value of OPEN_CURSORS.
- UNDO_MANAGEMENT
- Set to AUTO.
- •If the repository must store metadata in a multibyte language, set the NLS_LENGTH_SEMANTICS parameter to CHAR on the database instance. Default is BYTE.
- •Informatica does not support Oracle public synonyms for repository tables. Verify that public synonyms have not been created for any tables in the database.