HP3000-L Archives

October 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Fatula <[log in to unmask]>
Reply To:
Steve Fatula <[log in to unmask]>
Date:
Mon, 12 Oct 1998 01:15:54 -0500
Content-Type:
multipart/mixed
Parts/Attachments:
text/plain (1194 bytes) , vcard.vcf (444 bytes)
It would likely help if you would provide the install job, so we can see what
Omnidex commands are being used. Also, a FO SETS from query or some similar
definition. It can depend on the type of field the date is stored in for
example.

Jennifer Downs wrote:
>
> Hi!
>
> I'm running Omnidex 3.04 indexing a date field on a dataset with 100,000+
> records. TPI is set on. Every night, this date field is updated on
> approximately 300 records with a canned program. The problem is that the
> field isn't indexing properly, so if I do a serial search on that field, I
> get 300 records...if I do an Omnidex search, I get between 10-20 records.
> There is no discernable pattern to the 10-20 that index properly. It looks
> pretty random. Talking to a programmer friend, it was suggested that this
> might be a Btree problem (I don't know what that means, but it sounds
> pretty cool. <s>). Tech support for the canned ap is baffled. Any thoughts
> or suggestions on how to solve the problem? Right now I'm reindexing every
> night, which is not a good long term solution since it chops an hour out of
> the available night processing time.
>
> Thanks in advance!
> Jennifer
>
> IS Flunky
> Morse Distribution
> Bellingham, WA



ATOM RSS1 RSS2