| Hi Jerry,
> o Is this problem reproducible?
I think not, because installing the AIRCO DEMO AM on the microvax was
succesfull.
But installing this on the VS4000-60 is got the error, when I did after this
a man/tool the AIRCO entitie was there??
I did a man/tool delete class AIRCO and after that I did again a install.
Now the install was succesfull.
So I have no really a problem, but maybe I encountered a bug somewhere.
> o Also, please send me all DAP command files that the AIRCO DEMO
> loads into the dictionary.
The dap command files you can find at:
HLRG02::MCC_AIRCO_AM_MGMT_IF.COM
HLRG02::MCC_AIRCO_AM_SRVC_IF.COM
Thanks for your reply.
/-/ Henk.
|
| Henk:
This was a tough problem to solve. I ended up finding and fixing two
problems:
o First, I was able to reproduce the symptom you described on any
dictionary (big or small), by executing two REBUILD commands in
succession.
This problem was easy to fix (initialization problem) and the fix
has been put into the V1.3 FT Update kit (class t1.3.1).
o However, I was not convinced that this was the same reason why
you experienced the problem with the AIRCO DEMO installation.
So, I tried to reproduce the problem on many different dictionaries
of many different sizes. I was unsuccessful and was beginning to
give up when a co-worker gave me a 67MB ULTRIX dictionary (70 MIBS
loaded) that exhibited this same problem!
This dictionary turned out to be corrupt. A couple of records had
child pointers for records that weren't in the dictionary. This
caused some data loss in the CTM build algorithm that caused the
error message that you saw.
I have changed the CTM build algorithm to ignore these corrupt
records and to continue to build the CTM file. These changes are
also included in the V1.3 FT Update kit (class t1.3.1).
I am not sure why your dictionary got corrupted. One way that this
can happen is if a LOAD, UPDATE, DELETE, AUGMENT or MERGE operation
was interrupted during processing. In fact, the building of the 67MB
dictionary I used was indeed interrupted during a MERGE operation.
Unfortunately there is no easy way to confirm the integrity of your
dictionary. However, the fixes that I've made in the FT Update kit
should alleviate the effects of any small corruption in your
dictionary. That's all I can do for now...
- Jerry
|