Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3
  • All Products

Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Configuration Guide

Configuration Guide

Back Next

C_REPOS_DB_RELEASE Table

C_REPOS_DB_RELEASE Table

The C_REPOS_DB_RELEASE table contains the
Operational Reference Store
 properties.
The following list describes the C_REPOS_DB_RELEASE properties that Enterprise Manager displays for the
Operational Reference Store
 databases, depending on your preferences:
DEBUG_LEVEL
Debug level for the ORS database. The debug level can be one of the following integer values:
100 = error level debugging
200 = warning level debugging
300 = information level debugging
400 = debug level debugging
500 = debugging for all levels
ENVIRONMENT_ID
The environment ID.
DEBUG_FILE_PATH
Path to the location of the ORS database debug log.
DEBUG_FILE_NAME
Name of the ORS database debug log.
DEBUG_IND
Flag that indicates whether debug is enabled or not.
0 = debug is not enabled
1 = debug is enabled
DEBUG_LOG_FILE_SIZE
For
Oracle
 environments. Size of database log file (in MB); default is 5.
DEBUG_LOG_FILE_NUMBER
For
Oracle
 environments. Number of log files used for log rolling; default is 5.
TNSNAME
TNS name of the ORS database.
CONNECTION_PORT
Port on which the ORS database listens.
ORACLE_SID
Oracle database ID.
DATABASE_HOST
Host on which the database is installed.
INTER_SYSTEM_TIME_DELTA_SEC
The number of seconds required to make up the difference between the database server system time and the system time of another machine.
COLUMN_LENGTH_IN_BYTES_IND
For
Oracle
 environments. Flag that the SQLLoader uses to determine if the database it is loading into is a UTF-8 database. A default value of 1 means that the database is UTF-8.
LOAD_TEMPLATE
For
IBM DB2
 environments. The path on the database server for log files that the db2 load command generates when you are in logging mode.
MTIP_REGENERATION_REQUIRED_IND
Flag that indicates that the MTIP views will be regenerated before the match/merge process. The default value of 0 (zero) means that views will not be regenerated.
GLOBAL_NOLOGGING_IND
For
Oracle
 and
IBM DB2
 environments. This is used when tables are created to enable logging for DB recovery. The default of 1 means no logging.
0 COMMENTS
We’d like to hear from you!