Re: !!!!!!!This is very serious onconfig standardization . help needed!!!!!!

Also I notice that looking at:- Partition profiles partnum lkrqs isrd iswrt bfrd seqsc 1048898 174539 141611 0 301654 5 1048960 2047306 696268 0 3539620 20 1048961 401218 249464 0 531017 5 1048970 103783 9855 0 130098 3 1048974 107744 42900 0 212488 0 1048987 154563 127243 0 315280 1 1049070 439633 219830 0 549563 2 1049113 883354 331274 0 772944 1 1049122 886340 332942 0 775690 10 1049149 110930 51476 0 202927 20 1049152 202810 155561 0 330382 5 2097167 1368323 73501 0 355777 365 2097220 3040668 152152 55 829937 23 2097227 137496 70953 11 166952 6 2097249 2552795 718433 12 1331176 1 (This is just part of the partition profile) Run select tabname,partnum from systables where tabid >99; against each database. Check the partnums against the partition profile above. For each table you are getting a large amount of reads and lock requests (any >10,000 reads needs looking at, >100,000 reads definetely need looking at). The right indexes are not being used! This is because Either - OPTCOMPIND is set to 2 not 0 in ONCONFIG - Update statistics has not been run - Go to www.iiug.org Software and get utils_ak2 Compile dostats.ec and use it - The right indexes are missing - examine your sql and create the missing indexes then run dostats! David. Either since OPTCOMPIND =2 instead of