It might be worth checking if the problem reproduces
if you switch from using ANALYZE to using dbms_stats()
(or vice versa if you are doing your analyse with dbms_stats).
--
Jonathan Lewis
http://www.jlcomp.demon.co.uk
Next Seminars
UK Sept
Australia August
Malaysia September
USA x 2 November
http://www.jlcomp.demon.co.uk/seminar.html
Norman Dunbar wrote in message ...
>Hi Richard,
>
>Trouble maker - me ?
>I have a rep for breaking software - when I first joined this company
>they told me 'go play with the software and see if you can find any
>bugs' so I logged over 40 in my first morning. The MD came to see me in
>the afternoon and asked me to keep it up :o)
>
>The only things these tables have in common is :
>
>- the same tablespace
>- they are reasonably biggish (about 40,000 rows)
>- they are analyzed (sic) compute but estimate is the same
>- they have DATEs, VARCHAR2 and NUMBER(m,n). Some have a LONG column but
>not all (yes I know, but we're getting there !)
>- no CLOBS etc
>
>It happens if the table is exported and imported into a new user so I'm
>presuming that there is something about the table structure that is
>causing LMTs grief - I just havent tracked it down yet.
>
Received on Sat Jul 27 2002 - 14:23:43 CDT
