It would make sense, I would expect Oracle to take a shortcut with LOB Indexes, simply hard-coding the fact that access to the LOB should always be via the LOB index. Consequently there would be no point in thinking about them
You could run SQL_TRACE prior to the dbms_stats call, and see if there is a 'bitand(flag,NNNN)' line in the query that identifies indexes that excludes LOB indexes. Jonathan Lewis http://www.jlcomp.demon.co.uk Author of: Practical Oracle 8i: Building Efficient Databases Next Seminar - Australia - July/August http://www.jlcomp.demon.co.uk/seminar.html Host to The Co-Operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html -----Original Message----- To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Date: 23 April 2002 22:52 I've hit bug 1499329 As a workaround, I'm analysing the tables in the staging environment then I'm doing an exchange partition. I can analyse the tables/indexes without problem in the staging environment. My question is when creating a clob, Oracle creates a sys_...$$ indexes. When analysing the schema, those sys_...$$ indexes do not have any statistics. Is that normal ? TIA -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jonathan Lewis INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
