Reprinted: http://informatica.iblog.com/post/3070/70389
All metadata information of Informatica is stored in the metadata database in the form of database tables. Of course, Infa's own tools provide a lot of user-friendly functions, so that we can easily operate during development, but people's needs are always changing. If you need to easily get the information you need, we need to He has a deep understanding of the metadata database.
All metadata information of Informatica is stored in the metadata database in the form of database tables. Of course, Infa's own tools provide a lot of user-friendly functions, so that we can easily operate during development, but people's needs are always changing. If you need to easily get the information you need, we need to He has a deep understanding of the metadata database.
Informatica provides us with all the information through tables and views. Here, we will introduce most common and very useful tables and views through a series of posts. Based on these things, we can find out the data we need according to different needs, and we can also develop some auxiliary Infa applications.
/
OPB_ATTR :
INFORMATICA (Designer, Workflow, etc.) The names, current values, and
Brief description of the attribute item
For example: ATTR_NAME: Tracing Level
ATTR_VALUE: 2
ATTR_COMMENT: Amount of detail in the session log
Purpose: You can quickly check the purpose and description of some attribute items encountered during design or setting through this table
OPB_ATTR_CATEGORY:
Classification and description of each attribute of INFORMATICA
例如： CATEGORY_NAME: Files and Directories
DESCRIPTION: Attributes related to file names and directory locations
Purpose: View several categories and descriptions of the attribute items mentioned in the table above
OPB_CFG_ATTR:
The configuration data of Session Configuration under each Folder in the WORKFLOW MANAGER, each configuration corresponds to a group of data with the same Config_Id in the table, a group of configuration data totals 23
For example: ATTR_ID: 221
ATTR_VALUE: $PMBadFileDir
Purpose: View all the configuration items and values of Session Configuration, and easily compare the configuration similarities and differences between different Folders
OPB_CNX:
The definition of source and target database connections in WORKFLOW MANAGER, including Relational Connection, Queue Connection, Loader Connection, etc.
For example: OBJECT_NAME: Orace_Source
USER_NAME: oral
USER_PASSWORD: `?53S{$+*$*[X]
CONNECT_STRING: Oratest
Purpose: View all connections and their configuration data configured in WorkFlow Manager
OPB_CNX_ATTR:
Some related attribute values of all database connections recorded in the above table, one attribute value is one piece of data. For example, for the connection of the Relational Connection class, there are three additional attributes, and the corresponding table has three records, respectively recording the attribute values of its Rollback Segment, Environment SQL, and Enable Parallel Mode, corresponding to ATTR_ID 10, 11, 12
For example: OBJECT_ID: 22
ATTR_ID: 10
ATTR_VALUE: 1 (representing Enable Parallel Mode is selected)
VERSION_NUMBER: 1
Purpose: To view the related attribute values of all configured connections, and some environment SQL and rollback segment settings, to facilitate unified viewing and comparison
OPB_DBD:
Attributes and locations of all imported sources in INFORMATICA DESIGNER
For example: DBSID: 37
DBDNAM: DSS_VIEW
ROOTID: 37
Purpose: View the attributes of all sources in association
OPB_DBDS:
The source cited in INFORMATICA MAPPING, that is, the correspondence between Mapping and the source in the above table
For example: MAPPING_ID: 3
DBD_ID: 4
VERSION_NUMBER: 1
Purpose: Check which Mapping has referenced a defined source, as its source or give the Mapping name, according to the OPB_MAPPING table association, you can see which sources the Mapping refers to
OPB_EXPRESSION:
All defined expressions in INFORMATICA DESIGNER
For example: WIDGET_ID: 1003
EXPRESSION: DECODE(IIF(TYPE_PLAN != '05',1,0),1,QTY_GROSS,0)
Purpose: By associating with the OPB_WIDGET table, view the expression definitions in all Expression conversion modules in the entire metabase
OPB_EXTN_ATTR:
In the Mapping page of Edit Tasks in WORKFLOW MANAGER, when Targets is selected, the setting value of its related properties. One record for each attribute value.
For example: ATTR_ID: 2
ATTR_VALUE: ora_test1.bad
Purpose: directly view the data loading settings of all session related target tables through association
OPB_FILE_DESC:
The definition of import rules for all text files in INFORMATICA, such as separators, etc.
For example: STR_DELIMITER: 11,
FLD_DELIMITER: 9,44,0
CODE_PAGE: 936
Purpose: View the rule definitions of different texts in the system
Informatica's metadata includes all the data we encountered during development and configuration. Of course, in theory, we can change the settings by directly modifying database values, but listing the purpose of these tables is just to give you a convenient way to view information Method, even if you are familiar with the metadata database, it is strongly recommended not to directly modify the value of the metadata table, but to make changes through the Informatica tool.
OPB_GROUPS:
Definition of all groups in INFORMATICA
For example: GROUP_ID: 2
GROUP_NAME: Administrators
Purpose: View all groups set in the current system
OPB_MAPPING:
The storage of all Mappings in INFORMATICA, and stores some of the Mapping attributes such as the last storage time, description, etc.
For example: MAPPING_NAME: m_PM_COUNT_BILL
MAPPING_ID: 1521
LAST_SAVED: 03/27/2006 20:00:24
Purpose: The purpose of this table is very large. You can query the data in this table to get all the data that has been modified after a certain time.
With Mapping, all Mappings that are invalid, the greater role of this table is to associate with other tables, and get
More Mapping related information
OPB_MAP_PARMVAR:
The definition of all the parameters of Mapping in INFORMATICA, and related information such as initial values
For example: MAPPING_ID: 1538
PV_NAME: $$DP_ENABLE_RAND_SAMPLING
PV_DEFAULT: 0
Purpose: View all parameter information set by the system, and the association with OPB_MAPPING can be based on the given
Mapping name to view all parameter information set under the Mapping
OPB_METAEXT_VAL:
IINFORMATICA metadata extension information, which records all metadata related information extended in the design
The following is the metadata extension of a Session
For example: METAEXT_NAME: COMMENT
OBJECT_TYPE: 68 (Session)
PM_VALUE: The Link's Main Table,Design by Jack
Purpose: View all extended metadata information in the design, and view the metadata extension information of the specified object through association
Information, to help focus on viewing and understanding some information in the design process
OPB_OBJECT_TYPE:
Definition table of all objects in INFORMATICA design
For example: OBJECT_TYPE_ID: 1
OBJECT_TYPE_NAME: Source Definition
Purpose: You can view all the objects defined by INFOMATICA, and can be used as the associated dimension table of other tables to view all relevant information of an object
OPB_PARTITION_DEF:
All PARTITION definitions in SESSION
For example: SESSION_ID: 2578
PARTITION_NAME: Partition #1
Purpose: Through association, according to the name of the Session, find out all the Partition settings contained in the Session
OPB_REPOSIT:
INFORMATICA REP server configuration related information
For example: DATAVERSION: 5002
PEPOSIT_NAME: hnsever
Purpose: View INFORMATICA REP server configuration information
OPB_REPOSIT_INFO:
INFORMATICA REP database connection configuration information
For example: REPOSITORY_NAME: TEST-REP
DB_USER: infa_user
DB_NATIVE_CONNECT: infa_conn
HOSTNAME: hnsever
PORTNUM: 5001
Purpose: View the configuration information of INFORMATICA REP server database connection
OPB_SCHEDULER:
All SCHEDULER setting information table in WORKFLOW
For example: SCHEDULER_ID: 81
SCHEDULER_NAME: Scheduler_DAY_10
START_TIME: 3/13/2005/00/20
Purpose: This table records all SCHEDULER information, as well as its various attribute settings, so as to facilitate the overall consideration of the scheduling cooperation between each SCHEDULER
OPB_SERVER_INFO:
INFORMATICA SEVER server configuration information
For example: SERVER_NAME: INFA_SEVER
TIMEOUT: 300
HOSTNAME: hnsever
PORT_NO: 4001
IP_ADDRESS: 196.125.13.1
Purpose: View INFORMATICA SEVER server configuration information
OPB_SESSION:
All Sessions in WORKFLOW record the correspondence between Session and Mapping and Session related one
Some basic attributes
For example: SESSION_ID: 11
MAPPING_ID: 3
Purpose: View the correspondence between Session and Mapping, and get the correspondence between Session name and Mapping name through association
OPB_SESSION_CONFIG:
Record the Config configuration information of all Sessions in WORKFLOW
例如： CONFIG_NAME: default_session_config
COMMENTS: Default session configuration object
Purpose: View all configured Session Config information in the current system
OPB_SESS_FILE_REF:
Definition of the correlation between all Flat File and Session in the INFORMATICA extraction process
For example: SESSION_ID: 682
FILE_ID: 66
Purpose: View the relevant situation of the Flat File source in the entire system
OPB_SESS_FILE_VALS:
Details of all Flat File files in the system, including file name, path, etc.
For example: SESSION_ID: 1560
FILE_NAME: PTM_LU_CHILD.txt
DIR_NAME: $PMSourceFileDirPTM
Purpose: Through association, you can view the Flat file name and path related to Session, and view all related Flat files and statistics of the system
OPB_SESS_TASK_LOG:
This is the information record of INFORMATICA for all logs of Session running, and records the error situation of Session.
For example: INSTANCE_ID: 6
MAPPING_NAME: m_ASSET_SUB_ACCOUNT
LOG_FILE: C:Program Files......s_ASSET_SUB_ACCOUNT.log
FIRST_ERROR_MSG: No errors encountered.
Purpose: This is one of the final tables for checking the running status of the Session. It is the easiest way to get whether the Session is running normally and the first error brief information when it was wrong, and the location of the log file.
OPB_SRC:
All sources defined in INFORMATICA DESIGNER
For example: SRC_ID: 12
SUBJ_ID: 27
FILE_NAME: AM_EQP_ASSESS
SOURCE_NAME: AM_EQP_ASSESS
Purpose: Through the association of Subj_Id, you can find out all the sources defined in each Folder
OPB_SRC_FLD:
Definition of all fields of the source table in INFORMATICA
For example: FLDID: 82
SRC_ID: 12
SRC_NAME: FLAG_ID
Purpose: Associate the above table to get all the fields of the source table, their definitions and related attribute values
OPB_SRV_LOC_VARS:
In INFORMATICA system server configuration, all system variables and the current values of variables
For example: VAR_ID: 13
VAR_NAME: $PMRootDir
VAR_VALUE: D:Program FilesInformatica PowerCenter 7.1.1Server
Purpose: View all system variables of the current server and their current values
OPB_SUBJECT:
All theme definitions in INFORMATICA, that is, definitions and related attributes of all Folders
For example: SUBJ_NAME: OAM
SUBJ_ID: 2
GROUP_ID: 3
Purpose: Folder ID is the foreign key of many other tables, as the association of other tables, you can view all relevant object information under the Folder
OPB_SWIDGET_INST:
Record all objects and their related attributes referenced by Mapping used in a Session, that is, down to one record for each conversion module
For example: SESSION_ID: 11
MAPPING_ID: 3
INSTANCE_NAME: LKP_OTHER_CHECK11
PARTITION_TYPE: 1
Purpose: View all objects referenced by each Session and their current attribute values
OPB_SWIDGINST_LOG:
After INFORMATICA is running, the running logs of related source and target objects in all running Sessions, that is, the running time, the number of successfully extracted data, etc.
For example: TASK_INSTANCE_ID: 92
PARTITION_ID: 1
PARTITION_NAME: Partition #1
WIDGET_NAME: SQ_SHIFT_CODE
APPLIED_ROWS: 723
START_TIME: 2004-11-4 8:48:12
END_TIME: 2004-11-4 8:48:31
Purpose: This is the most detailed log record of the operation of each object after INFORMATICA is running. It has important reference value for checking the correctness of the data and tuning the performance.
OPB_SWIDG_GROUP:
The definition table of all Groups on the Union_Transformation module in INFORMATICA DESIGNER
For example: SESSION_ID: 1410
GROUP_NAME: PM_GROUP1
Purpose: This table separately records all the groups set on the Union_Transformation module, and can find out all the Union Group definitions on a Session through association
OPB_TABLE_GROUP:
The definition table of all Groups on the Router Transformation module in INFORMATICA DESIGNER.
For example: OBJECT_ID: 3409
ATTR_VALUE: FROM_ID = 'xx'
Purpose: This table separately records all the Groups set on the Router Transformation module and the grouping conditions of the Group. All the grouping settings and grouping conditions of Route r in a Mapping can be found through correlation
OPB_TARG:
Definition of all target tables in INFORMATICA DESIGNER
OPB_TABLE_GROUP:
The definition table of all Groups on the Router Transformation module in INFORMATICA DESIGNER.
For example: OBJECT_ID: 3409
ATTR_VALUE: FROM_ID = 'xx'
Purpose: This table separately records all the Groups set on the Router Transformation module and the grouping conditions of the Group. All the grouping settings and grouping conditions of Route r in a Mapping can be found through correlation
OPB_TARG:
Definition of all target tables in INFORMATICA DESIGNER
For example: TARGET_ID: 3
SUBJ_ID: 2
TARGET_NAME: HAM_DEPT
Purpose: This table stores all target table definitions, and all target table definitions under a folder can be found through association
OPB_TARGINDEX:
Index can be defined for the target table in INFORMATICA. The table stores all the definitions of the target table Index
For example: TARGET_ID: 1626
INDEXNAME: IDX_AUDIT
Purpose: find out all Index definitions carried out in INFORMATICA and related target table information
OPB_TARGINDEXFLD:
All related fields defined by Index on the target table in INFORMATICA
For example: INDEXID: 6
FLDNAME: AREC_BILL_ID
Purpose: to correlate and find out the tables and fields defined by Index in INFORMATICA
OPB_TARG_FLD:
Field information of all target tables in INFORMATICA
For example: TARGET_ID: 131
TARGET_NAME: CHECK_PROPERTY
Purpose: View all field information of the target table, or give the field name, find the field in those target tables
OPB_TASK:
Records of all tasks in WORKFLOW, including Session, Worklet, WorkFlow, etc.
For example: TASK_ID: 1717
TASK_NAME: s_OAM_LOG_ARR
Purpose: This table is the main table of Workflow's Task records. Through association, you can find out all Workflow, Worklet, Task, etc. contained in a folder, and find out all Tasks under a Workflow
OPB_TASK_ATTR:
This table records all attribute values of Task, one record for each attribute
For example: ATTR_ID: 2
ATTR_VALUE: s_AM_ASSET_TYPE.log
Purpose: View the attribute settings of related tasks, find all tasks with the same attribute settings in the system
OPB_TASK_INST:
Task instance table, similar to OPB_TASK table information, but this table mainly highlights the relationship between Workflow and Task, and OPB_TASK table is the base table of Task
For example: WORKFLOW_ID: 9
INSTANCE_NAME: s_USED_KIND
Purpose: Find all Task information under a Workflow
OPB_TASK_INST_RUN:
This table records the log information of each task run, including the current start time, service name, etc.
For example: INSTANCE_NAME: s_ASSET_ACCOUNT
START_TIME: 2004-11-3 15:20:01
END_TIME: 2004-11-3 15:20:08
SERVER_NAME: ETL-SVR
Purpose: This table records the log information of each task running. The information about time plays an extremely important role in performance tuning. You can also observe the same task, run effects over a period of time, evaluate the running status of the server, etc.
OPB_TASK_VAL_LIST:
This table records the attribute values in some Tasks, such as the Command value in Command Task
For example: TASK_ID: 2990
PM_VALUE: DEL “D:FILE_LIST.TXT”
VAL_NAME: DELETE
Purpose: You can view the task attribute values set in the current system, and you can also view the command values of all Commands
OPB_USERS:
This table records all users set in Rep Manager and their related attributes
For example: USER_ID: 5
USER_NAME: DEMO
USER_PASSWD: hG63"4.`
USER_PRIVILEGES1: 79
Purpose: to view all users and related attributes defined by INFORMATICA in the system
OPB_USER_GROUPS:
This table records the relationship between users and groups in Rep Manager
For example: USER_ID: 2
GROUP_ID: 3
Purpose: View which users exist in a group, or associate which group each user belongs to