Re: SET PDQPRIORITY error

In article <6fo8mf$cfc@sjx-ixn1.ix.netcom.com>, Ray Garrison <apsnet@ix.netcom.com> writes >I recently installed 7.23.UC1 on an HP9000 V-class box running >HP/UX 11.0. > >When I issue the SET PDQPRIORITY command, with either a numeric >or symbolic option (SET PDQPRIORITY HIGH or SET PDQPRIORITY 100) >using low, medium, high, or numberic values from 1 to 100 I get > >unknown error message 874 > >Checking this error text I am told that this is an internal >optimizer problem and to call technical support. I called >tech support, and as usual they haven't got the faintest idea >what could be wrong; suggested run update statistics. I don't >see how update statistics could be affecting pdqpriority, but >I went ahead and updated stats on all critical columns/tables >anyway - made no difference. > Update stats sets up the values that the optimizer uses to decide how to perform the query. Possibly something within the system tables had become corrupt. Update stats would have fixed this. e.g. np_used (number of pages used) being < 0. Next run oncheck -cr oncheck -ce oncheck -cc <database name> oncheck -cID <database name> These check nothing is corrupt. >Any ideas? This is a serious problem - am getting performance >on the V system (4 CPU 2 GIG RAM) only slightly better than we >had on the D system (2 CPU 1 GIG RAM) it replaced. > >Thanx > >Ray Garrison -- David Williams Maintainer of the Informix FAQ Primary site (Beta Version) http://www.smooth1.demon.co.uk Official site http://www.iiug.org/techinfo/faq/faq_top.html I see you standin', Standin' on your own, It's such a lonely place for you, For you to be If you need a shoulder, Or if you need a friend, I'll be here standing, Until the bitter end... So don't chastise me Or think I, I mean you harm... All I ever wanted Was for you To know that I care