Você está na página 1de 4

good-link:http://www.scribd.com/doc/37238250/Siperian-XU-Administrator-s-Guide-S P1#outer_page_349 tokenization\ fuzzy dirty_indicator control tables repos repar --match tables used????

from ambrish how to deploy build?import export of files in hub how addressdoctor iconfigured? Hoe SIF works? =============================================== select * from c_repar_match_col_src select * from c_repar_match_path_component select * from c_repar_match_path_comp_filter select * from c_repar_match_rule select * from c_repar_match_rule_component select * from c_repar_match_set ================================================ Hi All, Now in IMDMDEV1 there are 10.6% unique QLIMS pkey_src_object are matching with C TMS, and there are 4533 unique QLIMS pkey_src_object which are matching with CTM S in OLD MDM study Site locator but not matching CTMS in IMDMDEV1 Research Facil ity. Will do some more detail analysis regarding why this 4533 QLIMS records are matching with in CTMS in study site locator but not in imdmdev1 RF. 1. 33178/ 312651 = 10.6% unique QLIMS PKEY_SRC_OBJECT are matching with CTM S in imdmdev1 Select distinct pkey_SRC_object from cmx_ors.c_b_party_xref where rowid_system = 'QLIMS' and rowid_object in (select rowid_object from cmx_ors.c_b_party_xref wh ere rowid_system = 'CTMS') 2. For those QLIMS data which are not matching with CTMS in RF, compared wi th study site locator, 4533 unique qlims pkey_src_object are matching CTMS, abou t 1.5% of total QLIMS in RF. 4533/312651 = 1.5% select distinct PKEY_SRC_OBJECT from ( select distinct A.ROWID_OBJECT, A.PARTY_SUB_TP, A.FULL_NM, A.PARTY_TP, B.ROWID_SYSTEM, B.PKEY_SRC_OBJECT, B.FULL_NM s_full_nm, C.PKEY_SRC_OBJECT addr_xref_PKEY_SRC_OBJECT, C.ADDR_LINE_1,C.ADDR_LINE_2, C.ADDR_LINE_3, C.CITY, C.CNTRY_CD, C .CNTY, C.STATE_PRVNC_CD, C.PSTL_CD, C.PSTL_CD_EXTNSN, C.VLD_ADDR_IND, D.PARTY_ID_FK, D.ADDR_ID_FK, D.S_PARTY_ID_FK, D.S_ADDR_ID_FK, E.PARTY_ID_FK phn_xref_party_id_fk, E.COMM_TP_CD phn_tp, E.COMM_V AL phn_comm_val, E.Q_PHONE_MATCH_TXT, E.Q_SYS_OF_REC_IND phn_rec_ind, E.Q_PRIM_F LG prim_phn_flg, F.PARTY_ID_FK email_party_id_fk, F.COMM_TP_CD email_tp, F.COMM_V AL email_comm_val, F.Q_SYS_OF_REC_IND email_rec_ind, F.Q_PRIM_FLG prim_email_flg

from (select * from cmx_ors.c_b_party where PARTY_TP = 'HCO') A, (select * from cmx_ors.c_b_party_xref where party_tp = 'HCO') B, cmx_ors.c_b_addr_xref C, cmx_ors.c_b_party_addr_xref D, cmx_ors.c_b_party_phn_xref E, cmx_ors.c_b_party_eltrnc_addr_xref F, (select * from mdm_pub.v_study_site_src_sys_locator@mdmprd where MD M_SRC_SYS_DESC = 'QLIMS' and MDM_entity_cluster_id in (select MDM_entity_cluster_id from mdm_pu b.v_study_site_src_sys_locator@mdmprd where MDM_SRC_SYS_DESC = 'CTMS' )) G where A.ROWID_OBJECT = B.ROWID_OBJECT and

B.PKEY_SRC_OBJECT = D.S_PARTY_ID_FK(+) and D.S_ADDR_ID_FK= C.PKEY_SRC_OBJECT(+) and B.ROWID_XREF = E.PARTY_ID_FK(+) and B.ROWID_XREF = F.PARTY_ID_FK(+) and A.hub_state_ind = 1 and D.HUB_STATE_IND = 1 -- 479490 All records and B.rowid_system = 'QLIMS' -- 247809 records and B.ROWID_OBJECT not in (select rowid_object from cmx_ors.c_b_party_xref w here rowid_system = 'CTMS') -- 185559 records and substr(b.pkey_src_object,5) = G.INV_KEY -- 8326 records ) -- 4533 records ========================================================================== match table select * from c_b_party_strp order by ROWID_OBJECT C_baseObjectName_MTCH =============================================================================== select distinct ms.rowid_match_set, ms.MATCH_SET_NAME, ms.ruleset_filter_sql, --mr.ROWID_MATCH_RULE, mr.rule_no, mr.match_purpose_str, mr.match_level_str, mr.AUTOMERGE_IND, mr.RULE_ENABLED_IND, mr.EXACT_RULE_IND, mr.RULE_ACCEPT_LIMIT_ADJUSTMENT, mc.match_column_name, mc.SEQ, mc.MATCH_KEY_IND, mc.MATCH_KEY_WIDTH_STR, mc.FUZZY_IND, mrc.NULL_MATCH_IND, mrc.SEGMENT_MATCH_IND, mrc.SEGMENT_MATCH_VALUE, mrc.MATCH_WEIGHT_ADJUSTMENT from cmx_ors.C_REPAR_MATCH_SET ms, cmx_ors.C_REPAR_MATCH_RULE mr, cmx_ors.C_REPAR_MATCH_RULE_COMPONENT mrc, cmx_ors.C_REPAR_MATCH_COLUMN mc where mr.ROWID_MATCH_RULE = mrc.ROWID_MATCH_RULE and mrc.rowid_match_column = mc.rowid_match_column

and ms.rowid_match_set = mr.rowid_match_set --and ms.rowid_match_set = 'SVR1.3HDT' and mc.ACTION_TYPE_STR = 'insert' order by ms.MATCH_SET_NAME, mr.rule_no, mc.seq ================================================================================ RUNBOOK STEPS: Prior to the initial load: Open the MDM Hub as admin. Navigate to Utilities -> Batch Group Acquire a write lock Expand the Stage and Load groups from each source Select the Force Update checkbox for the Load steps for the following tables: o Party (except LOVs) Do this for all four sources Completed. NEW Step: From MDM hub console as admin, choose cmx_ors schema, go to utilities, batch vie wer then click Group by and select by table . Execute Party Phone -> Synchronize -> Synchronize Meta Data for Party Phone, Pending for clarification. May not be applicable will know after step 3 Initial Load: Step1: MDM_2_1/iMDM_Load/Load Source Data Completed Step2: MDM_2_1/iMDM_Adhoc_Job_Prompt: mdm_job_name: BATCH_GROUP: Stage and Load flow for LOVs This step is not recomme nded to run AB. So initiated from mdm hub. Failed due to ORA-25153 (INC0452330 resolved) Completed Step3: MDM_2_1/iMDM_Load/Stage and Load/Stage and Load flow from QLIMS source Failed Completed Step4: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge on US Addresses Completed Step5: MDM_2_1/ iMDM_Load/Merge and Match/Match and Merge on Non-US Addresses Completed Step6: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge Investigator Complete d Step7: MDM_2_1/iMDM_Load/Merge and Match/ Match and Merge - HCO Complete d Step8: MDM_2_1/iMDM_Load/Stage and Load/Stage and Load flow from ECG source Completed Step9: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge on US Addresses Completed Step10: MDM_2_1/iMDM_Load/Investigator/Merge and Match/Match and Merge on Non-U S Addresses Completed Step11: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge Investigator Complete d Step12: MDM_2_1/iMDM_Load/Merge and Match/ Match and Merge HCO Completed Step13: MDM_2_1/iMDM_Load/Stage and Load/Stage and Load flow from CTMS source Completed Step14: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge on US Addresses Completed Step15: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge on Non-US Addresses Completed Step16: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge Investigator Complete d Step17: MDM_2_1/iMDM_Load/Merge and Match/ Match and Merge HCO Completed

Step18: MDM_2_1/iMDM_Load/Stage and Load/Stage and Load flow from INNTRAX sourc e Completed Step 19: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge on US Addresses Completed Step 20: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge on Non-US Addresses Completed Step 21: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge Investigator Complete d Step 22: MDM_2_1/iMDM_Load/Merge and Match/ Match and Merge HCO Complete d Step 23: MDM_2_1/iMDM_Load/CTMS Integration Completed Step 24: MDM_2_1/iMDM_Load/Publishing Layer Completed imdm_pub.imdm_publish.delta_load Completed with errors (Stuart sent an email to Vince) wf_LOAD_PUB_INVSTGTR_DATA - Succeeded Redo of Step3: MDM_2_1/iMDM_Load/Stage and Load/Stage and Load flow from QLIMS source Completed Redo of Step6: MDM_2_1/iMDM_Load/Merge and Match/Match and Merge Investigator Completed ================================================================================ ===

Você também pode gostar