Yes, but you should log a call with the WRC. Either the block type of the data block needs to be changed to say that it contains big string data or the pointer to it needs to be changed to say that it doesn't. Look a the data block with REPAIR to determine whether it has any big strings or not.
"Andrzej Siodlowski" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > I have > Cache for UNIX (Linux/Intel) 4.1.13 (Build 212) Wed Feb 19 2003 07:32:17 > EST. > Whe I checked my database by INTEGRIT, I have some errors: > > **********Global ADMED is Not OK********** > Error of type 7 while processing pointer block 316956 > The error occurred while processing node 27 > which is ^ADMED(53057,2,200308251118,7,7) pointing to the lower level block > 1085499 > The pointer block expected the data block to have > big strings but the data block's type information > says it does not. > ***We will continue checking with the next pointer block at this level. > Data Level: # of blocks=10,359 20MB (73% full) > Big Strings: # of blocks=3,512 7,024kb (53% full) # = 3,392 > Total: # of blocks=14,000 27MB (68% full) > Elapsed Time = 49.4 seconds 11:08:06 > ^G^G > > Global: ADMEDM > Pointer Level: # of blocks=1 2kb (4% full) > Pointer Level: # of blocks=4 8kb (52% full) > Bottom Pointer Level: # of blocks=182 364kb (74% full) > **********Global ADMEDM is Not OK********** > Error of type 6 while processing pointer block 994787 > The error occurred while processing node 85 > which is ^ADMEDM(26576,6,200401121023,1,8) pointing to the lower level > block > 1293992 > The pointer block did not expect the data block to have any > big strings but the data block's type information > says it does. > ***We will continue checking with the next pointer block at this level.Is > there any way to repair this problem ?Best regards,Andy > >
