"The nice thing about OMNIDEX is you can just re-execute your install job,
which will tidy things up a bit, then reindex."
Yes, if you have a small number of records. We have one dataset, the indexing of which, took seven
hours on a 997-1200. It now takes about a quarter of the time on an N-Class, but not so little that
I would call it 'nice' -- no reflection on the Omnidex product, just a comment about the quantity of
our data.
As for restoring or moving around partial data bases, we do this routinely. One just has to figure
out what all of the parts are, and that does include Omnidex.
--
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax: 617-509-1955
pager: 781-226-2431
Carol Darnell
<caroldarnell@HOT To: [log in to unmask]
MAIL.COM> cc:
Sent by: HP-3000 Subject: Re: [HP3000-L] image database omnidex error msg
Systems
Discussion
<[log in to unmask]
TC.EDU>
11/07/2003 11:21
AM
Please respond to
Carol Darnell
First.... do NOT play restore games with the IMAGE root file! Oh my....
the things i've seen when folks were creative with that kind of thing.
I'd also be curious about your restore process - I've seen people restore
the IMAGE database, especially using the replace option, but forgot to
specify in the restore the corresponding OMNIDEX files! Or, similarly,
folks purging the database for a non-replace restore, but forgetting to
purge the OMNIDEX files, which then didn't get replaced.
The nice thing about OMNIDEX is you can just re-execute your install job,
which will tidy things up a bit, then reindex.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
