Optimizedb problems ...

[Colin Hay]

I build stats on system catalogs using

optimizedb -zs25 -zk -zc -u'$ingres' <dbname>

today I got the error

E_OP0393 consistency check
The sensistivity of a histogram was out of range 0.0 <= value <= 1.0

Half the tables are left optimizedb and half not

If I do a help table on those that are optimized I get the same error

statdump -zdl -u'$ingres' <dbname>

does not remove the stats but neither does it return an error ...

Removing the stats by hand using the -r flag for each table does work.

How can I get around this guys ???

Ingres 2.0 on Solaris

[Gale, Peter NESL-IT]

Try not using sampling (-zs25). It is not going to save much time on the
system catalogs any way.

Peter Gale
+44 (0)191 210 2658
peter...@npowernorthern.com

[Leandro Pinto Fava]

Hi Colin,

I found this error before, but using optimizedb -zc -zk dbname on Ingres 2.5/0011 int_w32 with nopatch on w2k.
I raised an issue to CA support and this error was reported to me as a bug in older versions of ingres (#92234).
There is a workaround for this bug setting vch_compression in CBF and unload and reload the database.
What patch has you applied on your ingres installation?

HTH.
Regards,

Leandro Fava
DBA
Universidade de Santa Cruz do Sul-UNISC
www.unisc.br
Fone: +55 51 3717 7424

[Leandro Pinto Fava]

Opps, sorry.

... setting vch_compression to off ...