Recently I discovered that the 'statdump' utility can generate data 
files which contain inconsistencies, and which cannot be subsequently 
imported by 'optimizedb -i' without being edited.
CA Technical Support told me that this was a known problem,that an SIR
was in the pipeline,and that the recommended workaround was to edit 
the statdump file manually.

However,I found that :-
    a) the problem occurs when iirelation.reltups is too low,
       because this results in a statdump file with a repetition 
       factor higher than the rowcount.This can sometimes be avoided by
       modifying the table in question.    
    b) Running on a VAX, I was able to write some DCL to detect and
       correct the error which now runs as a batch job after the
       statdump and therefore always produces valid statdump data files.

I would be happy to provide details to anyone interested.

-- 
e-mail from barry williams at:
              Dillons the Bookstore, 82 Gower Street, London, WC1E 6EQ 
England
              tel: +44 (0)171 636 1577  fax: +44 (0)171 580 7680
Please report any problems to: postmaster@dillons.co.uk

Ingres Q & A

To William's Home Page

© William Yuan 2000

Email William