Useful Unix command:
fuser -u Unix_filename
It lists the PIDs of any processes which have the physical file open.
Something I see from time to time is file indices getting Out of step or
self-disabling. The most common cause is building the index while the
file is in use.
I don't know whether
Hello all,
I have a client that migrated from True64 to AIX a few weeks ago (I
wasn't involved with the migration). They are currently having a
problem with an index corruption on a static file. Unidata will not
allow me to do a LIST, LIST.INDEX, DELETE.INDEX, or anything else
I've tried
Make sure you're the only one accessing the file. Remove the X_filename
file at the OS level. Copy another X_filename2 to X_filename (if you
don't have a handy one just create an index on a small file. Then your
DELETE.INDEX should work and you can re-create the index.
Hht
Colin Alfke
Calgary
In the past when we had problems like this, we would create a small
index on a file somewhere else. We would then copy the X_file to the
appropriate name and location of the broken one. (There by
substituting it temporarily)
At that point you can do your DELETE.INDEX file ALL
We (S7)
Kevin,
When we completed our migration from True64 to AIX we had the same
problem. I had to delete all of the indexes and then rebuild them.
First check to be sure that the index file is present where the VOC
indicates it should be. If the file is there try deleting it at the
system level
