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.5 HotFix 2
  • 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

Tracing a Search

Tracing a Search

The Search Server can create a detailed trace file showing:
  • the search record (in IDT format)
  • all candidate records selected using the defined Search-Logic
  • the results of matching the search record with each candidate record

API

This can be enabled from an API program by specifying
LOGTEST=
 in the
options
 parameter of the
ids_system_open call
:
LOGTEST="<full_path_of_log_file>"

relate

The batch search utility relate will create a trace file when the
--3
 switch in used to nominate the name of the trace file. For example,
%SSABIN%\relate --3%SSAWORKDIR%\mysearch.trc

Java Search Client

The Java Search Client can create a trace file. This is enabled / disabled with the menu item
Options
Create Trace File
which toggles tracing on and off.
The default trace filename is
%SSAWORKDIR%\SystemName.trc
A different filename may be specified with
Options
Set Trace Filename
 .
The trace file is written with buffered I/O. It is not completely flushed to disk until the user closes the current search. The Search Client will do this automatically when
  • tracing is turned off, or
  • you switch to a different Search, or
  • the application is closed.

Sample Output

An annotated trace output file is provided to demonstrate how to interpret the information found in the trace. The file is located in the Server’s bin directory and is named
%SSABIN%\srchtrc.txt
0 COMMENTS
We’d like to hear from you!