Re: dostats questions

From: Roland Wintgen <rw@evg.de> > >could someone please give me a hint about the following: >I have created a table called asciitab (char char(1), ascii smallint) and >two unique indexes on column (char) and (ascii). Additionatly a unique >constraint for (char, ascii) and a referential constraint on (ascii, char) >(I know that this is some sort of overkill) >When running dostats it gives the following output: > >UPDATE STATISTICS MEDIUM FOR TABLE asciitab DISTRIBUTIONS ONLY; >UPDATE STATISTICS HIGH FOR TABLE asciitab (ascii); >UPDATE STATISTICS HIGH FOR TABLE asciitab ( char ) DISTRIBUTIONS ONLY; >UPDATE STATISTICS LOW FOR TABLE asciitab (ascii, char); >UPDATE STATISTICS LOW FOR TABLE asciitab (char); >UPDATE STATISTICS LOW FOR TABLE asciitab (char, ascii);> >The question is, why do the two UPDATE STATISTICS HIGH differ? Which one >is the correct one? When dropping the indexes, it seems to work well. Because Art is smart enough to know that all the other stuff that USH does was done the first time and he only needs to create the distributions the second time around? They're both correct. They work on different indexes. >Another thing I noticed when I was running the SQL-Statements that were >generated by dostats, was that sometimes when watching with onstat -g sql >an ISAM error -111 showed up. The SQL Error said 0. >I regularly run oncheck -cDI and nothing seems broken. So what about >the error codes. Is that something I should worry about? No. >This phenomen does show up on IDS 7.23UC6 on AT&T Unix as on IDS 7.30UC10-1 >on Linux. > >Thanks for any comments. Tempting... ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com