Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Identity Resolution 10.2 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Defining a System
  4. Flattening IDTs
  5. Link Tables
  6. Loading a System
  7. Static Clustering
  8. Simple Search
  9. Search Performance
  10. Miscellaneous Issues
  11. Limitations
  12. Error Messages

Design Guide

Design Guide

Back Next

Search Statistics

Search Statistics

If no records are found, either no candidates were found or scoring rejected all candidates. To determine which, stop the servers, delete all log files, and restart. Run a relate with
-vs
 (statistics) and an input file with just one record. Stop the servers to flush the logs. Check the Server log file for the following: 

apic>				 Hstogram: 							FS FindSet - unique     recs countnt
apic> 				Histogram-FS: 											1   			2
apic> 				Histogram-FS: 											2				183
apic> 				Histogram-FS:............3 				57
apic> 				Histogram-FS: 											4				42
apic> 				Histogram-FS: 											5				16
apic> 				Histogram-FS: 											6				13
apic> 				Histogram-FS:............8 				17
apic> 				Histogram-FS: 											11			   24
This histogram shows the number of searches that found n candidates (n is the left hand column, number of searches on the right).
If you see the log as follows: 
apic>          Histogram-FS:                0           1
then it means there are no candidates found. The possible causes are:
  • Key-Logic for IDX does not match key-logic for search (different fields/algorithms perhaps?)
If it actually found some candidates, check for: 

apic>						 Matches-Total:....................KSL 		1265
apic> 						 Matches-Accepted: 			 				       KSL   	915
apic>						 Matches-Rejected: 							         KSL 	   28
apic> 						 Matches-Undecided: 						        KSL 		 	32
This provides information on what happened during scoring. If all candidates were rejected, some possible causes are:
  • score threshold too high
  • bad method options
Try setting the score limit very low so that everything is accepted. Then use relate’s
-u
 and
-l
 switches to set upper (or lower) score limits until you figure out what the real limit should be.
0 COMMENTS
We’d like to hear from you!