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

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!