Product Documentation
Abstract
IBM Relationship Resolution and Identity Insight provides periodic fixes for releases 4.1.0, 4.2.0 and 8.0 respectively.
The following is a complete listing of fixes for Versions 4.1.0 & 4.2.0 and 8.0.0 with the most recent fix at the top.
Content
Identity Insight Version 8.0.0
Hot Fix 5 (V 8.0.0.140) |
Hot Fix 4 (V 8.0.0.135) |
Fix Pack 2 (V 8.0.0.130) |
Hot Fix 3 (V 8.0.0.109) |
Hot Fix 2 (V 8.0.0.95) |
Hot Fix 1 (V 8.0.0.90) |
Fix Pack 1 (V 8.0.0.88) |
Upgrade Paths:
8.0 GA --> FP 2 (v8.0.0.130) --> HF 4 (v8.0.0.135) --> HF 5 (v8.0.0.140)
8.0 GA --> FP 1 (v8.0.0.88) --> FP 2 (v8.0.0.130) --> HF 4 (v8.0.0.135) --> HF 5 (v8.0.0.140)
8.0 GA --> FP 1 (v8.0.0.88) --> HF 1/2/3 --> FP 2 (v8.0.0.130) --> HF 4 (v8.0.0.135) --> HF 5 (v8.0.0.140)
---------------------------------------------------------------------------------------------------------------------------------------------
Relationship Resolution Version 4.2.0
Hot Fix 2 Roll-up (V4.2.0.532) |
Hot Fix 2 (V 4.2.0.527) |
Fix Pack 2 (V 4.2.0.512) | |
Fix Pack 1 (V 4.2.0.491) | |
Hot Fix 1 (V 4.2.0.489) |
Relationship Resolution Version 4.1.0
Hot Fix 3 (V 4.1.0.105) | |
Hot Fix 2 (V 4.1.0.96) | |
Hot Fix 1 (V 4.1.0.86) |
---------------------------------------------------------------------------------------------------------------------------------------------
Fix release date: 28 Oct 2011 Last modified: 28 Oct 2011 Status: Available (Critical) Download information |
Fixes | Description |
Pipeline maintenance items: | |
1 | Enable limits to detail logging to improve efficiency and performance. This change means that only the most related and best details are logged. For example, the scores that hit the rule are logged, but not all names. |
2 | Unique constraint violation error during load causing pipeline to fail. |
3 | Fixed UMF_MERGE message FROM/TO DSRC_ACCT_ID ordering issue. |
4 | Unresolve - re-resolve loops occur on large entities when a disclosed relation is added (or via an X-message against the entity). Unresolve continues as a CPU-intensive process and needless database updates are triggered. |
5 | DB2 Database transport lock handling improvement. |
6 | Long running transactions occurred due to unresolve/re-resolve looping. In ambiguously-merged accounts, the unresolve process was non-deterministic in the order it would attempt to re-assemble the examined entity. |
Visualizer maintenance items: | |
1 | Visualizer issue with displaying a long list of numbers in the Find By Attribute Screen. |
2 | "Role Alert Rule" drop down too small; cannot see entire name of alert role on "Role Alert Status Report" page. |
Miscellaneous maintenance items: | |
1 | Alteration to Index - add ENTITY_ID to DSRC_ACCT.IX_FORCED_RESOLVE_ID. This improves linking when doing merges. |
Fix release date: 20 May 2011 Last modified: 20 May 2011 Status: Available (Critical) Download information |
Fixes | Description |
Pipeline maintenance items: | |
1 | Infinite deadlock retries |
2 | Pipeline crash on delete |
3 | CircaDOB params cross link w/ DOB |
4 | Pipelines need a delay if no data in transport table |
5 | Ignoring COMPANY culture resulting in name parsed |
6 | QSMNA exception for COMPANY names w/ "AND", "&" |
7 | Pipeline crashes on shutdown CEP-enabled |
Visualizer maintenance items: | |
1 | 2 digit year, plus timestamp, is being displayed in From and Thru dates on Visualizer Entity Resume report |
Miscellaneous maintenance items: | |
1 | Webservices stating record processed when it failed |
2 | SOA_ADDR_MATCHED_DURING_ER view not returning EXACT ADDRESS |
Fix release date: 14 Mar 2011 Last modified: 14 Mar 2011 Status: Available (Critical) Download information |
Fixes | Description |
Pipeline maintenance items: | |
1 | Unresolve and related issues Improvements have been made to the memory-usage and CPU-usage characteristics for Entity-resolution processing. |
2 | Legacy IW*WEBSERVER (srd.wsdl) Some EQ searches that exceeded the max record count on returns resulted in the pipeline returning a properly formatted XML message but the XSLT in the Web services corrupted it. |
3 | Insertion of SQL Comments into all SQL-calls (with enable/disable switch) This enhancement is required to support large-scale parallelization of pipeline-inserts in PPP / threaded environments and to stop latch-contention on DB2. By adding unique identifier information to the 'header' of each SQL query, the database-engine can allocate separate space and latches for each instance of a given SQL query per pipeline thread and pipeline rather than sharing the same SQL-query-string across pipelines and threads. This increases memory-usage on the database-tier (depending on number of pipelines and number of threads per pipeline), but reduces latch-contention. This feature is disabled by default. To enable it, set the following value in the [SQL] section of the pipeline.ini file: INSERT_COMMENTS=Y. |
4 | Infinite deadlock retries In HTTP mode, the pipeline should not retry transactions (bidirectional messages), but should return errors to the client so the client can retry. |
5 | GNR Name Hasher did not handle UTF-8 characters correctly Client responses are now correctly encoded in UTF-8 when appropriate. |
6 | Resolved deadlocks and the error limit count Resolved deadlocks are no longer counted in the error limit. |
7 | SOA process() function with data with an ampersand ('&') problem You can now call the SOA process() function with data that has an ampersand ('&') in it. This applies to all SOA functions and for other characters. |
8 | UNUM_MATCH_PERCENTAGE - new pipeline.ini parameter The Unique Number Matching percentage parameter can be set from 1 to 100. The higher the number, the more precisely an incoming Unique-number has to match in order to generate a Unique-Number-Match. To implement: In the [MM] section of your pipeline.ini file(s), add the following entry (case-sensitive) UNUM_MATCH_PERCENTAGE=xx. The default is 75 if not specified. |
9 | Incorrect attribute denials The system no longer denies when there is a common attribute. The system does not run the whole unresolve analysis project if the new conflicting attributes are found with a denial, but no penalty score (a penalty score of 0.) |
10 | Additional resolved issues and reported problems
|
Visualizer maintenance items: | |
1 | Missing alert on Upgrade from 8.0 to FP1 The Visualizer will now successfully obtain Match Merge rule information from a new IIv8.0 database column if it is populated, or fallback to the previous method if it is not populated. |
2 | Additional resolved issues and reported problems
|
Miscellaneous maintenance items: | |
1 | Documentation corrections Various topics throughout the content have been corrected or improved. |
2 | Updated CEP Rule-Builder deployment and instructions When the fix pack 2 installer is run on the Application Server, a new zip file is provided as part of the IBM Identity Insight installation on the Application Server (<RR_INSTALL>/cep/CEP_3.0.1.1.03-J2SE.zip). This zip file contains updated files that enable you to obtain an ArrayList containing the values of the "externalId" attributes of the events which participated in the situation, for the IOutputSituation function. This new function is available when creating CEP Rules using the Client-side Eclipse-based CEP Rule-Builder (previously provided in IIv8.0 in the <RR_INSTALL>/cep/CEP_3.0.1.01.zip file). Once the fix pack 2 Installer has been run on the Application Server, you must perform the following Manual steps to install these updated files into yourr Eclipse (CEP Rule-builder) framework: 1.Copy the new CEP zip file down to the client machine where the CEP Rule-Builder is being run. 2.Expand the zip file. 3.Copy the files to the following directory on the client <CEP_DEPLOY_DIRECTORY>\CEP_3.0.1.1.00\eclipse\plugins\com.ibm.amit.commonlib_3.0.1.1. |
3 | MQ 6.0.1.1 on HP (11i v3) Use MQ 6.0.1.1 on HP (11i v3) rather than MQ 6.0.1.0. |
Fix release date: 26 Oct 2010 Last modified: 26 Oct 2010 Status: Available (Critical) Download information |
Fixes | Description |
1 | The pipeline is shutting down, if the pipeline sends a foreign address to QSAVI server with only the US/CAN DBs installed. |
2 | UMF_MERGE failing with a "Requested search config for an invalid entity type" message |
3 | UMF_MERGE fails when entities were previously force merged |
4 | Large memory usage by pipeline processes & Unresolve performance improvements |
5 | Legacy webservices (srd.wsdl) - Error message returned is corrupted |
Fix release date: 5 Aug 2010 Last modified: 5 Aug 2010 Status: Available (Critical) Download information |
Fixes | Description |
1 | Performance Issue with HTTP transport corrected. |
2 | The pipeline no longer performs ER when a duplicate record is loaded into the system. |
3 | If DSRC_CODE or REL_DSR_ID is used it gets the DSRC_CODE of the RELATED_ENTITY correctly but fails to do conflict detection properly |
4 | Entity resume is not using best_address in the resume header section |
5 | Feature Enhancement: UNUM threshold: A UNUM confirmation can happen even though the UNUMs are not identical. |
6 | Name sifter: Sifter over-agressively categorizes names as Organizational. |
7 | Group1 international startup validation times out. |
8 | Can't call the SOA process() function with data with & |
9 | Disclosed Relation role alert graph doesn't display properly if description left blank |
Fix release date: 23 Apr 2010 Last modified: 23 Apr 2010 Status: Available (Critical) Download information |
Fixes | Description |
1 | Performance Issue with HTTP transport corrected. |
2 | The pipeline no longer performs ER when a duplicate record is loaded into the system. |
Fix release date: 30 March 2010 Last modified: 30 March 2010 Status: Available (Critical) Download information |
Fixes | Description |
Pipeline Items | |
1 | UMF Builder DATE and DATETIME problem UMF Builder Keywords DATE and DATETIME functionality was transposed. UMF_OUTPUT_RULE table has been corrected. If you have custom output messages, verify that your results have not been affected. |
2 | ADDR preparsed and unparsed error Sending both a preparsed street address and unparsed street address (populating ADDR1 and Street Num in the XML) caused the ADDR Hash to Double Up. The system now takes the preparsed street name. |
3 | Degrees of separation discrepancies The strength of an alert running with a threshold of more than three degrees of separation was affected by a longer and stronger path. Data source name (DSN) enabled caused discrepancies in the SEP_CONFLICT table. |
4 | Pipeline not failing with critical G1 errors at startup Pipeline did not fail startup on critical G1 errors. G1 errors are now properly checked at startup and the pipeline is shut down if there are critical errors. |
5 | UMF_MERGE conflict detection UMF_MERGE did not perform conflict detection for a merged entity. |
6 | Pipeline crashing with deadlocks Pipeline crashed after deadlock when disclosed relations are embedded in a message like UMF_ENTITY. Pipeline now rolls back and attempts to retry. |
7 | Auditing Find_by users There was no way to "audit" a particular user executing the "Find by Attribute" query from Visualizer. The Find by Attribute search can now log a tag that can be used to set up an audit. Contact IBM Support or your IBM Services representative for more information. |
8 | Alert rule detail lost when using Complex Event Processing CEP engine provides alert rules detail that was lost and not displayable in Visualizer. Fix pack adds a mechanism to get that detail. When available you can double-click the event alert screen to get detail. (See APAR # PJ36708) |
9 | GEM error pipeline shutdown related to Complex Event Processing GEM Error caused pipeline to shutdown when no event was sent to CEP. Error is now detected and pipeline is not shut down. |
10 | DQM rule 660 errors with Latin1 characters DQM rule 660 sent incorrect information about length of messages in its requests when the message body contained Latin1 characters. Characters versus bytes length calculation issue corrected |
11 | Event Alert Detail report problem Unable to open Event Alert Detail reports when the event is not associated with a name. |
12 | Pipeline fails with unhandled Server error ORA-947 Load failed with ORA-947 error and is a bulk inserts issue. The pipeline fails with a "CRIT - Unhandled Server error ORA-947 not enough values" message. This error was specific to implementations using an Oracle database and occurred when not enough columns were present in the insert data. |
13 | Pipeline does not work with MQ client Pipeline now utilizes IBM WebSphere MQ Client libraries if IBM WebSphere MQ Server libraries are not present. |
14 | CEP - Array of Arrays CEP rule-output now generates array-of-arrays output that can be parsed by the pipeline. |
15 | Attributes with Match Level other than 1 can trigger Unresolve Attributes with a match level of 0, 2, or 3 triggered an unresolve cycle. This action is now correctly limited to attributes with a match level of 1. |
Visualizer Items | |
1 | Alert count for "Name and Unique Number" resolution rule discrepancy Discrepancies occurred in the alert count for the "Name and Unique Number" resolution rule when using IBM DB2 version 8. |
2 | Visualizer - Attribute Alert Generator does not work when case# or comment has a ' Case# or Comment may now contain single-quote-marks. |
3 | Generation of conflicts during Unresolve/Reresolve In some situations, unresolve/reresolve failed to generate a new alert. |
4 | "Find by Entity" window/interface inconsistency "Find by entity" window issues. Fixed minor usability issue related to screen content being in sync. |
5 | "Find by" default problem "Find by" window went back to default rather than "remembering" the last type selected/used. The Search window now correctly brings up the "Find by" type last used. |
6 | Maximum number of days limited by 2-digit field Search default cap was limited to 99 and should be larger. Maximum number of days that you can set in the default history window in the Visualizer has been expanded from a two-character field to a three-character field. The maximum is now 999. |
7 | Event details not showing number of decimal places consistently Event details did not consistently show same number of decimal places. Event alert detail now displaying two decimal places consistently. |
8 | Data Source Name alert display problem Problem with viewing DSN alerts detail in the Visualizer. Data is stored in U.S. notation (for example, 52.7). Data from countries that use a comma instead of a decimal point caused problems when trying to display DSN alerts. Local data that uses a comma instead of a decimal point will now display correctly. |
9 | Graphing problems with "Show Related Entities" Graph drew improperly when using "Show Related Entities" if characteristics were part of the Event Report details. |
10 | Alert Summary window update issue In the Alert Summary, the combo box "Display alerts by type" did not get updated with the appropriate alert type or would get out of sync. The display now correctly shows all alert types. |
11 | Entity Resume display problems Relationships on Resume did not display if there was no name for the related entity. Enables linkage to entities without a name. |
12 | French addresses with added dash issue Visualizer was adding a dash that created display problems. This has been corrected. |
13 | Update view button consistency In the Visualizer the Update View button is not disabled when the Entity Events tab is first displayed (by clicking the Show Events button on the Entity Resume tab). |
Miscellaneous Items | |
1 | Additional Complex Event Management information Additional information about how to integrate and use the Complex Event Management component is included in this fix pack update. |
Fix release date: 22 January 2010 Last modified: 22 January 2010 Status: Available (Critical) Download information |
Fixes | Description |
1 | Pipeline Core dump due to large UMF_OUTPUT_MESSAGE |
2 | Pipeline will repeatedly report a deadlock condition with retries until it shuts down even though their database records no such issue. |
3 | Performance Issue - Webservices |
4 | gnrNameHasher Variant-limiting enhancement. This enhancement provides additional tuning parameters to the gnrNameHasher feature. |
5 | Event Processing enhancement - Display only the events that participated in the event alert. |
6 | Unnecessary internal copying of message caused pipeline to crash. |
7 | Pipeline repeatedly reports a deadlock condition with retries until it shuts down |
8 | In Visualizer, the Event Details list displays all the events for the entity. This list is not filtered to display only the events that participated in the event alert |
9 | We do not have a way to "audit" the particular user executing the Find by Attribute query from visualizer. |
10 | Performance Enhancements. |
11 | NameHasher limiting fix. |
Fix release date: 30 Jul 2009 Last modified: 30 Jul 2009 Status: Available (Critical) Download information |
Fixes | Description |
1 | Pipeline exits with database deadlock error. This was due to related error handling from the DB. |
2 | Circa-DOB fixes |
3 | pipeline issue: getRoleAlerts / Latin1 character |
4 | "Error using summary by user id on the SEP conflict table CWUAA0003E". Error occurred when trying to do a 'show all alerts'. |
5 | New entity incorrectly shows no alerts history. |
6 | XML '&' SOAP - Returned booleans are incorrect. Case, EntityResolver.wsdl - include installed hostname. |
7 | Visualizer crashes due to referential integrity caused by force-deleting an account or attribute used in an alert. |
8 | CEP does not return situations on deferred alerts. |
9 | DQM Sequence# fix - Default assigned sequence #s overwrite customer space. |
10 | CEP-Datestamp (Month vs Minute) |
11 | SOA: getRoleAlertsByEntity call returning incorrect values. |
12 | Visualizer links in attributes show error in opening HTTPS link. |
13 | Entity ID cannot be copied/pasted from either the entity resume or entity graph. |
14 | Source Create Date Change - added date flexibility for dsrc date display. |
15 | Circa DOB thresholding should be inclusive of both ends. |
16 | Enhancement - Customize Name Attribute Scoring Plug-in implementation. |
17 | G1UNC data-repeat returns incorrect address. |
Fix release date: 29 Jan 2009 Last modified: 29 Jan 2009 Status: Available (Critical) Download information |
Fixes | Description |
1 | Pipeline fails because clause is too large. |
2 | Name scoring is done differently in the candidate building than in scoring section of the code. |
3 | Pipeline pulls in all data attached to a disclosed relationship account. |
4 | Scoring issue with Individual Culture Entities vs. Companies. |
5 | Need a way to sequence output messages from entity resolution. |
6 | Role Alert Detail report is missing details. |
7 | Entity Relationship graph for an entity involved in an Event Alert properties pane shows duplicate information. |
10 | Missing XML files. |
11 | Issue with Disclosed Relations after 4.1 upgrade. |
12 | Console entity-type value-checking. |
13 | Console - field height. |
14 | Console - Attribute Denial text change. |
15 | SUIT - Index file. |
16 | Duplicate disclosed relations with different descriptions. |
17 | Visualizer file-load has missing Name record and Alert. |
18 | Empty NAME_GEN tags not handled properly in GNRNameHasher. |
19 | Number matching produces unexpected relationships when hash_length is changed. |
20 | "Passive Load - Num_DENIAL does not work correctly with Name Manager turned on. |
21 | APAR PJ33242 GNR scoring issue fix. |
22 | Confirm weight is not logged for attribute denial. |
23 | Accented characters (French language) are displayed as question marks in the console. |
24 | Child resolution data is missing from the master document. |
25 | Pipeline does not publish deleted relationships. |
26 | Child ER Session does not publish UMF_MATCH. |
27 | (APAR PJ34650) Relationships exist in EAS but not in EDW. UMF_ENTITY. Docs put through with a DSRC_ACTION of 'X' generate unexpected output messages and SEP_RELATION score changes. |
28 | (APAR PJ34650) New Name Key solution. |
29 | (APAR PJ34739) Performance issues for NC2 vs NM. |
30 | (APAR PJ34725) Number uniqueness did not take into account NUM_LOCATION when stored in the entity structure. This is a problem when NUM_LOCATION confirmation is used. The entity structure only keeps the first number of matching type and hash, so when the same number from different accounts with a differing or missing NUM_LOCATION is used, inconsistent NUM_LOCATION confirmations result. In cases where this makes the difference between a 100 Like score and a lower score, this can cause un-resolve re-resolve loops. |
31 | (APAR PJ34723) When using LAS only, the 'determine resolvability' function still decides which name comparator to use from the system_param table. In this case no name comparator should be used at all. This causes resolution rules to ignore LAS name scores when satisfying match merge rules and log 0,0,0 for LAS. |
32 | (APAR PJ34725) Pipeline gets fatal error loading a record. |
33 | IBM Relationship Resolution V4.2 Visualizer - Role Alert/Entity Graph - 'Hide Attribute' option is not available in Linux. |
34 | Users need to be able to reload CEP rules while the system is running. A reload button has been added. |
35 | Characteristic data in the Find By Attribute search-results list is displayed incorrectly when the gnrNameHasher feature is enabled. |
36 | Cannot delete disclose relationship from Visualizer. |
37 | A query in Pipeline Code is incorrect. |
38 | Function 610 does not allow a single value. |
39 | Pipeline should validate that DQM parameter indexes are sequential on startup. |
40 | Validate MM configuration ID at startup. |
41 | AP_RULE table is different between 4.2.1 Install and upgrade from 4.2.0. |
42 | Errors with Console number-types, range checking, and validations. |
43 | Errors in Visualizer - Hide Search entities. |
44 | The pipeline mistakenly increments the number of location neutrals when other data (NAME, ADDRESS, etc.) is ingested and combined with other Event Reporting criteria. |
45 | Missing entries in SEP_CONFLICT for DR. |
46 | Cannot load a UMF file with blank lines through the Visualizer. |
Fix release date: 18 April 2008 Last modified: 14 April 2008 Status: Available (Critical) Download information |
Fixes | Description |
1 | The Selective/Passive Load function now permits only expected data to load. |
2 | Close Number Threshold Behavior fixed. |
3 | Address parser now transliterates when Group1 is disabled. |
4 | Web Services: WS_DETAIL & WS_ALERT format codes now function correctly. |
Fix release date: 18 April 2008 Last modified: 14 April 2008 Status: Available (Critical) Download information |
Fixes | Description |
1 | Console clone of mm_config not doing the new LAS tables. |
2 | Conflicts with 0 scores should not be created |
3 | WSUTIL error on <UMF_QUERY> tag |
4 | Missing description data on Confirms & Denials console screen |
5 | Passive load to not load when num location does not match |
6 | Deleted Sep_roles and DSRC_ACCT records should not be used to create alerts and should not be added to er_entity_state table |
Fix release date: 04 December 2006 Last modified: 06 December 2006 Status: Available (Critical) Download information |
Fixes | Description |
1 | Degree of Separation, when enabled, sometimes inserts multiple rows in the SEP_CONFLICT_REL table with the same degree for the same conflict |
2 | In the Console, users could only choose the data source class by its description instead of its ID |
3 | Pipelines that accept data from MQSeries queues hung on bad XML messages |
4 | The ACCT_LOADED field in the DSRC_ACCT tables is not properly updated when using the Passive Load feature |
5 | DQM Rule 131 incorrectly truncated the entire string instead of the specified portion |
6 | UMR_ALERT documents that were published when using Degrees of Separation may have contained an incorrect value for the DEGREE element |
7 | The DB2 implementation of the database transport for a pipeline had locking issues that might affect performance |
8 | When using Degrees of Separation, the MATCH_ID column in the SEP_CONFLICT_REL table might not be properly updated |
9 | Close matches found by the system were not drawn properly in the graphs in the Visualizer |
10 | The Console did not allow valid values to be entered for the Confirm Weight of a number |
Fix release date: 29 September 2006 Last modified: 29 September 2006 Status: Superseded Download information |
Fixes | Description |
1 | The First Name field is no longer required on the Add Entity and New Search screens |
2 | The count of relationships in the Search Results screen now displays correctly |
3 | The Likeness Score field was added to the Search Result screens |
4 | Persistent searches are displayed in the Inbox based on the case number and the status |
5 | DB2 performance issues with Visualizer graphs and the entity resume have been resolved |
6 | The count of relationships for conflicts in the Conflict List screen now displays correctly |
7 | In the Italian language file, the translation for 'State' was changed to "Provincia" |
8 | The count of relationships and the likeness score in the Search lists now show "0" instead of null when there are zero relationships |
9 | The count of relationships on the immediate Search Results screen now displays correctly |
10 | Performance of functions dealing with names of related-entities has been increased |
Fix release date: 09 August 2006 Last modified: 15 August 2006 Status: Superseded |
Fixes | Description |
1 | Matching details on the Conflict screen were not correct in some cases |
2 | Matching details on the Search Results screen were not correct in some case |
3 | Clicking on relationships on the Entity Resume did not highlight the correct set of related data items in some cases |
4 | The SEP_RELATIONS and SEP_CONFLICT_REL tables were using outdated entity resolution IDs |
5 | Name matches were logged in ER_DETAIL when the rule used does not require name matches |
6 | Name confirmation occurs but is not logged when Name Manager is disabled or not required (a 0 value is in the rule) |
7 | The SEP_RELATIONS table is not always updated during an incomplete resolution recovery |
8 | Passive load returns XML without an ENTITY_ID causing a Visualizer error |
Change history
· Last modified: 28 July 2009
· 15 April 2008: Created Fix List Page.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27008307