Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

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!