Hi Susan,
I have seen something like this once.
A file had been copied between accounts, I think at UNIX level, and it
still contained an index pointing to the old account. The result was
very confusing until some searching questions were asked.
This forms the basis of a fantastic "tale of woe" that I picked up from a
very large UV user in the UK and tell on all relevant training courses that
we deliver.
One of their developers wanted to do some testing so he copied the relevant
data file and indices to a different location (actually, a different machine
if I remember rightly). He then proceeded to do his testing, unaware that he
was actually modifying the indices of the live system. I never heard what
the impact was on the company's business.
The issue here is that, although the indices normally sit alongside the data
file, UV allows you to create these elsewhere for load balancing, etc. It is
therefore necessary for the index pathname to be stored in the data file
header. Copying the data file will not update the indices and the copied
data file will continue to use the indices of the original file. In the case
of my tale of woe above, this went round the network and found the original
file!
UV provides a command, SET.INDEX, that allows you to examine, modify or
remove the index pointer. It is absolutely essential that this is used after
copying/moving a file that has indices.
Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
+44-(0)1604-709200
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
