Match Analysis Tool for MDM Introduction › howto › 6 › Documents › MAT_Help...Introduction The main objective of the Match Analysis Tool (MAT) is to help MDM Administrators

© 2014 Informatica Corporation Page 1 of 15

Match Analysis Tool for MDM

Introduction The main objective of the Match Analysis Tool (MAT) is to help MDM Administrators or users in:

Self-assisting the tokenization related issues Reducing the manual effort in checking the configurations manually Analyzing the current match configurations in the hub and suggesting the users with the

“Findings” in the environment, and its corresponding “Recommendations”

Finding and directing to the right KB Articles, related to each of the parameters involved in the tokenization process

Providing an over-all analysis of all the tokenization and match parameters across various areas such as environment variables, database specific parameters, property files, and population files along with a tokenization health check of the environment

MDM Support Login Launch the MDM support URL with Hub admin user’s credentials from MDM Hub Console -> Help -> MDM Support Tools menu. Note: For Weblogic, provide additional credentials of Weblogic administration user and password.

Choose ORS Will display list of ORS(s) registered with MDM installation.

Select the ORS (where you need to run a “Tokenization Health Check”) from the "Choose ORS" dropdown.

After selecting the ORS, the tool will display the list of Base Objects fetched from the selected ORS. Select a Base Object from this BO List.

Enabling Include BO Metrics checkbox, will collect additional parameters, specific to the selected Base Object such as – Dirty Indicator count, Hub State Indicator count, Null Fuzzy Key count, Number of tokens, Consolidation Indicator count, Exclude From Match column count(if enabled), etc. There will be a table constructed as a summary of these parameters, at the bottom of the page. Enable this parameter only if you want to do an analysis based on the data available in the BO.


Note: Enabling this parameter, would run several performance sensitive queries in the ORS schema. Use this option with caution.

Select a Base Object and click on ‘Retrieve’ button, to run a health check on the Tokenization parameters upon this Base object.

“Reset” button is used to reset the ORS Name and Base Object Name, so that users can change the ORS and the Base Object name, to run the health check on another Base Object.

“Export” button helps to export the health check results, to a CSV file, so that this can be shared with support team, to analyze the tokenization health check and help in advanced issues related to tokenization.

Server(s)

Displayed when the user clicks on “Retrieve” button. Provides tabular view to display all the online cleanse server count and the online match

server count. It also displays the URL of the online match servers available, as match server plays a key role

in Tokenization job

Note: The above tabular view displays the URL of the online Match servers only, as tokenization job runs on the Match servers. Following screenshot explains that there are two online match servers along with URLs and three online cleanse servers, displayed as below:

Health Check Results – Hub Server

This is a grid that contains six columns as follows:

o Module - Type of module, to which the parameter belongs to, such as All, Database or Environment Variable

o Type – Type of message such as ALL, ERROR, WARNING or INFO o Parameter

The tokenization parameter name that is validated by the tool. The number of parameters can vary, depending upon the check box property –

“Include BO Metrics” in the “Choose ORS” section. If the above check box is not checked, then the following parameters are

displayed:

Exact Match Flag

NLS Character Set


NLS Length Semantics

SIP_POP Column

Check Missing Children

Java Version If “Include BO Metrics” in the “Choose ORS Section” is enabled, the following

parameters are validated and displayed, additionally:

Tokens in the <BO>_STRP Table Dirty indicator count for the records which has DIRTY_IND = 1 in the

Base Object

Hub State Indicator count(based on Match Pending indicator) for the records which has DIRTY_IND = 1 in the Base Object

Consolidation Indicator count for the on-hold(Consolidation Indicator = 9) records, which has DIRTY_IND = 1 in the Base Object

Exclude from Match Flag and the count of records with Exclude from Match enabled

o Findings

The column that fetches the tokenization configurations from the MDM Hub corresponding to the selected Base object.

o Recommendations The suggestions / recommendations provided by the support, if the parameter

validated is not an “INFO” o KB Link

The required KB Article links that will help users to resolve the issue, related to each of the parameter.

This will open up the “My Support” portal and asks for login credentials, based on which it opens up the specified KB Articles automatically.

This grid will display the health check results from the hub perspective, with the ERRORs

displayed first, followed by the WARNINGs, and followed by the INFORMATION.

This will help users to concentrate on the ERRORs first followed by the WARNINGs related to the Tokenization parameters.

The “?”(Question mark) displayed next to each of the parameters, will provide a “Help Text” of each of the parameters displayed, upon hovering on it. For example, when you consider “NLS LENGTH SEMANTICS” parameter, the following would be the “Help Text”, which would help the users to understand the usage of that parameter:


Grid Options 1) There is a flexibility to re-size each of the above columns in the grid to see the entire message

for each of the parameters. 2) You can also filter the parameters, based on the value contained in each of the column. For

example, you can filter the “ERROR”s alone in the “Health Check Results - Hub Server” grid, to filter out only ERROR messages as below:

3) For the columns, “Module” and “Type”, users can filter based on the available drop down 4) For the columns “Parameter”, “Findings”, “Recommendations”, “KB Link”, users can enter the

value, which the system will automatically filter, based on the value given. Please find the example below, where we filter the “Dirty Indicator” parameter, by typing it as below:

5) There are other features like – “Group By Types” and “Ungroup Types”, wherein the users can easily group the parameters as INFO, ERROR and WARNING. This acts like a toggle button.


6) If you have enabled the check-box – “Include BO Metrics” while retrieving, the following information would be displayed at the bottom of the page:

7) The above image is a summary of BO Metrics, which would give a brief overview of the BO Status.

8) Out of the above parameters, “Excluded from Match” would be displayed, only if the selected Base object contains “EXCLUDE_FROM_MATCH” column.

9) When the Base object selected, contains the SIP_POP Column enabled, then the following information would be displayed under “BO Metrics” section:

a. No.of.Records with SIP_POP Column as NULL b. No.of.Records with SIP_POP Column as an Invalid Population File c. No.of.Records with SIP_POP Column as Population File that is Disabled

Refer to Appendix A for the expected hub related parameters that are validated and the

corresponding “Findings” and “Recommendations”

Health Check Results – Match Server This grid is dynamically generated, based on the registered online “Match Servers” to the MDM

Hub.

For example, if you have registered two online Match servers, then there would be two grids generated each with a heading in the following format:

o Health Check Results – Match Server N (http://<host_name>:<port_no>/cleanse), where N is the count of the registered online Match server, and <host_name> and <port_no> are the match server’s host name and port number.

Each of this grid also contains six columns, similar to the hub server grid including Module, Type, Parameter, Findings, Recommendations and KB link


Grid Options 1) Module column will have the options for All, Environment Variable, File Property and Files 2) Other options such as Group/Ungroup, filter etc. work similar to the Hub Server grid 3) The toggle button – “Show Population Files”, displayed under the footer of each match server,

displays the Population file names and their corresponding file sizes, in each of the match servers.

a. For example – Clicking on the “Show Population Files” button in one of the match server grid, will display the following information:

4) The above information would be useful to compare the population name and sizes of each

population file across all the match servers attached to the MDM hub. 5) Once the “Show Population Files” button is clicked, it changes to ”Hide Population Files” as

above, to help users to hide the population files, if not needed.

Refer to Appendix B for the expected cleanse related parameters that are validated and the corresponding “Findings” and “Recommendations”


Appendix – A

Hub Parameters – Validation Rules

Sl.No Parameter Rule for reference Findings Recommen dations

Type

1 Exact Match Flag

C_REPOS_TABLE.EXACT_MATCH_ OBJ_IND = 0

Fuzzy Match Base Object N/A INFO

2 Exact Match Flag

C_REPOS_TABLE.EXACT_MATCH_ OBJ_IND = 1

Exact Match Base Object N/A INFO

3 Exclude From Match flag

Exclude from Match flag not enabled N/A INFO


Count of BaseObject Records.exclude_from_match=1

Exclude from Match flag enabled for the BaseObject. %,d records (flagged as 1) to be excluded for tokenization

Review the records with exclude_fr om_match =1 status to confirm

WARNING


Count of BaseObject Records.exclude_from_match=1

Exclude from Match flag enabled for the BaseObject. No record (flagged as 1) to be excluded for tokenization

N/A INFO

6 Dirty Indicator

Count of BaseObject Records.dirty_ind=1

%,d records (flagged with dirty indicator as 1) to be tokenized

Execute "Tokenizati on" job to tokenize records

WARNING

7 Dirty Indicator

Count of BaseObject Records.dirty_ind=0

No records (flagged as dirty indicator as 1) available to be tokenized

N/A INFO

8 Tokens in <BO>_STRP table

Count of <BO>_STRP records %s table is empty. No tokens available

%s = <BO>_STRP table

Execute "Tokenizati on" job to tokenize records

WARNING

9 Tokens in <BO>_STRP table

Count of <BO>_STRP records %,d tokens available in %s table

%,d=Count %s=<BO>_STRP table

You may re-execute tokenizatio n job if additonal tokens to be created

INFO

10 Hub State Indicator

C_REPOS_TABLE.match_pending_i nd=1 and BaseObject Records.hub_state_ind not in (0,1) and dirty indicator as 1

Match Pending records flag is enabled on the Base Object. %,d soft deleted records (hub state indicator as -1) not be tokenized

To tokenize such records, either update match pending indicator flag or hub state indicator flag

WARNING

Sl.No Parameter Rule for reference Findings Recommen

dations Type


C_REPOS_TABLE.match_pending_i nd=1 and "No" BaseObject Records.hub_state_ind not in (0,1) and dirty indicator as 1

Match Pending records flag is enabled on the Base Object. No soft deleted records (hub state indicator as -1) will be tokenized

N/A INFO


C_REPOS_TABLE.match_pending_i nd=0 and BaseObject Records.hub_state_ind in (0,1) and dirty indicator as 1

Match Pending records flag is disabled on the Base Object. %,d pending/soft deleted records (hub state indicator as 0 or -1) not to be tokenized

To tokenize such records, either update match pending indicator flag or hub state indicator flag

WARNING


C_REPOS_TABLE.match_pending_i nd=0 and "No" BaseObject Records.hub_state_ind in (0,1) and dirty indicator as 1

Match Pending records flag is disabled on the Base Object. No pending/soft deleted records (hub state indicator as 0 or -1) will be tokenized

N/A INFO

14 Consolidation Indicator

Count of BaseObject Records.Consolidation Ind = 9 and Dirty Ind = 1

%,d records (flagged with consolidation indicator as 9) are marked on-hold and will not be tokenized

To tokenize such records, update the consolidati on indicator

WARNING

15 Consolidation Indicator

Count of BaseObject Records.Consolidation Ind = 9 and Dirty Ind = 1

No records (flagged with consolidation indicator as 9) are marked on-hold

N/A INFO

16 NLS Length Semantics

NLS_LENGTH_SEMANTICS = CHAR and C_REPOS_DB_RELEASE.column_le ngth_in_bytes_ind = 0

NLS_LENGTH_SEMANTICS is CHAR and COLUMN_LENGTH_IN_BYTES is 0

N/A INFO


NLS_LENGTH_SEMANTICS = CHAR and C_REPOS_DB_RELEASE.column_le ngth_in_bytes_ind <> 0

NLS_LENGTH_SEMANTICS is CHAR, but COLUMN_LENGTH_IN_BYTES is not marked as 0 (zero)

Set COLUMN_L ENGTH_IN_ BYTES to 0 if NLS_LENGT H_SEMANT ICS is CHAR

WARNING


NLS_LENGTH_SEMANTICS = BYTE and C_REPOS_DB_RELEASE.column_le ngth_in_bytes_ind = 1

NLS_LENGTH_SEMANTICS is BYTE and COLUMN_LENGTH_IN_BYTES is 1

N/A INFO


NLS_LENGTH_SEMANTICS = BYTE and C_REPOS_DB_RELEASE.column_le ngth_in_bytes_ind <> 1

NLS_LENGTH_SEMANTICS is BYTE but COLUMN_LENGTH_IN_BYTES is not marked as 1

Set COLUMN_L ENGTH_IN_ BYTES to 1 if NLS_LENGT H_SEMANT

ERROR



dations Type

ICS is BYTE 20 NLS Length

Semantics NLS_LENGTH_SEMANTICS not in (BYTE, CHAR)

NLS_LENGTH_SEMANTICS is neither BYTE not CHAR

Set NLS_LENGT H_SEMANT ICS to either CHAR or BYTE

ERROR

21 NLS Character Set

NLS_CHARECTERSET in UTF-8, UTF- 16

NLS_CHARACTERSET is %s

%s=UTF-8 or UTF-16

N/A INFO

22 NLS Character Set

NLS_CHARECTERSET not in UTF-8, UTF-16

NLS_CHARACTERSET is neither UTF-8 nor UTF-16

Set NLS_CHAR ACTERSET to either UTF-8 or UTF-16

INFO

23 SIP_POP Column

SIP_POP column not included N/A INFO

24 SIP_POP Column

SIP_POP column included SIP_POP column value in BaseObject must match a valid population file name from C_REPOS_S SA_POPUL ATION table

INFO

25 Fuzzy Match Key

No fuzzy match key column is defined in the base object

Define a fuzzy match key column to participate in the tokenizatio n

ERROR

26 Fuzzy Match Key

Physical columns not configured for fuzzy match key

Configure one or more physical columns

ERROR



dations Type

for the fuzzy match key

27 Records with NULL Fuzzy Key Columns

Fuzzy match key column(s) : %s [%s] No NULL values on any of the fuzzy match key columns

%s - comma separated key columns %s - fuzzy match key table

N/A INFO

28 Records with NULL Fuzzy Key Columns

Fuzzy match key column(s) : %s [%s] %,d records have NULL values on fuzzy match key columns

%s - comma separated key columns %s - fuzzy match key table

NULL values on fuzzy match key columns will generate NULL tokens. Try to keep NOT NULL values on such columns

ERROR

29 Check Missing Children

No match path defined Match paths not defined N/A INFO


No match path defined with check missing children as No

No match paths defined with Check Missing Children flag as No

N/A INFO


Match path defined with check missing children as No

Match paths (%s) defined in base object have Check Missing Children flag as No

If this flag is No, parents records will not be tokenized when any child/grand child record is missing. And it can affect the search results as well. Set it based on the business requiremen ts

WARNING

32 Java Version Java_Version Java Version: %s N/A INFO


Appendix – B Cleanse Parameters – Validation Rules


dations Type

1 SSAPR variable

SSAPR environment variable is NULL

SSAPR environment variable is NULL Set SSAPR environme nt variable as <INFA_HO ME>\\hub\ \cleanse\\r esources

ERROR

2 SSAPR variable

SSAPR environment variable is not NULL

SSAPR variable is %s

%s - SSAPR variable value

N/A INFO

3 Match folder Match folder exists under SSAPR location

SSAPR match folder location (%s) validated

%s - <SSAPR>/match

N/A INFO

4 Match folder Match folder does not exist under SSAPR location

SSAPR match folder location (%s) does not exist

%s - <SSAPR>/match

Match folder is expected to be present underneath the SSAPR location

ERROR

5 SSAPR Path SSAPR environment variable not contains the pattern \\cleanse\\resources

SSAPR variable (%s) is not pointing to <INFA_HOME>\\hub\\cleanse\\resource s folder

Set SSAPR environme nt variable as <INFA_HO ME>\\hub\ \cleanse\\r esources

ERROR

6 SSAPR Path SSAPR environment variable contains the pattern \\cleanse\\resources

SSAPR variable (%s) is pointing to <INFA_HOME>\\hub\\cleanse\\resource s folder

N/A INFO

7 SSAPR Path SSAPR environment variable contains the pattern \\cleanse\\resources

SSAPR variable location (%s) does not exist

SSAPR variable folder is expected to be present

ERROR


8 Population

Files C_REPOS_SSA_POPULATION.POPU LATION_NAME with ENABLED_IND = 1

No population is enabled in the database Enable at least one population file in C_REPOS_S SA_POPUL ATION table for Fuzzy enabled base object.

ERROR

9 Population Files

Population files are not there in the server

No population files are available in the cleanse server

Import the population files to <SSAPR>\m atch folder for all enabled population s

ERROR

10 Population Files

No population file is enabled in the database

Enable at least one population file in C_REPOS_S SA_POPUL ATION table

ERROR

11 Population Files

All population files are valid and enabled. Population files - %s

%s - List of valid population files

N/A INFO

12 Population Files

Enabled population files - %s Disabled population files - %s

Enable the required population files in C_REPOS_S SA_POPUL ATION table

WARNING

13 Population Files

No population file exists in the cleanse server location (%s) which are enabled in the database

%s - <SSAPR>/match


ERROR

14 Population Files

Configured population files - %s Missing population files - %s

N/A WARNING


15 Base Object's

Population File(s)

No population is enabled in the database

Enable the BaseObject configured population files in C_REPOS_S SA_POPUL ATION table

ERROR

16 Base Object's Population File(s)

Population file selected in the BaseObject is not enabled in the database

Enable the BaseObject configured population files in C_REPOS_S SA_POPUL ATION table

ERROR


No population file exists in the cleanse server location (%s) which are referenced in the BaseObject

%s - <SSAPR>/match

Import the population files to <SSAPR>\m atch folder for all BaseObject referenced population s

ERROR


Population file that is referenced in the BaseObject, does not exists in the cleanse server location (%s)

%s - <SSAPR>/match


ERROR


Population Files enabled - %s

%s - List of populations configured in the BaseObject

N/A INFO


Configured population files - %s Missing population files - %s

N/A WARNING

21 Java Version Java_Version Java Version: %s N/A INFO

22 Properties file cmxcleanse.properties available cmxcleanse.properties available in %s

%s - file location

N/A INFO


23 Server

Encoding flag cmx.server.match.exact_match_fu zzy_bo_api is not present

cmx.server.match.server_encoding is not present in the cmxcleanse.properties

Server Encoding is required to be present in the server, to differentiat e unicode and non- Unicaode data

WARNING

24 Server Encoding flag

cmx.server.match.exact_match_fu zzy_bo_api is blank

Server Encoding flag is blank Set Server Encoding flag in cmxcleanse .properties with 0 or 1

ERROR


cmx.server.match.exact_match_fu zzy_bo_api is 0 or 1

Server Encoding flag - %s

%s - 0 or 1

N/A INFO


cmx.server.match.exact_match_fu zzy_bo_api is neither 0 or nor 1

Server Encoding flag (%s) is invalid

%s - 0 or 1

Set Server Encoding flag in cmxcleanse .properties with 0 or 1

ERROR

27 Exact Match Fuzzy BO API flag

cmx.server.match.exact_match_fu zzy_bo_api is not present

cmx.server.match.exact_match_fuzzy_b o_api is not present in the cmxcleanse.properties

If you are using IDD Extended search or SearchMat ch SIF calls with combinatio n of exact and fuzzy columns then this flag is required to be 1

WARNING


cmx.server.match.exact_match_fu zzy_bo_api is blank

Exact Match Fuzzy BO API flag is blank Set Exact Match Fuzzy BO API flag in cmxcleanse .properties with 0 or 1

ERROR


cmx.server.match.exact_match_fu zzy_bo_api is 0 or 1

Exact Match Fuzzy BO API flag - %s

%s - 0 or 1

N/A INFO


30 Exact Match

Fuzzy BO API flag

cmx.server.match.exact_match_fu zzy_bo_api is neither 0 or nor 1

Exact Match Fuzzy BO API flag (%s) is invalid

%s - 0 or 1

Set Exact Match Fuzzy BO API flag in cmxcleanse .properties with 0 or 1

ERROR

31 LD_LIBRARY_ PATH variable

LD_LIBRARY_PATH environment variable is NULL

LD_LIBRARY_PATH environment variable is NULL

Set LD_LIBRAR Y_PATH environme nt variable as <INFA_HO ME>\\hub\ \cleanse\\li b

ERROR

32 LD_LIBRARY_ PATH variable

LD_LIBRARY_PATH environment variable is not NULL

LD_LIBRARY_PATH variable is %s

%s - LD_LIBRARY_PATH variable value

N/A INFO
