Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Has anybody encountered problems with HISTGRM$ ?

Re: Has anybody encountered problems with HISTGRM$ ?

From: Gene Gurevich <g_u_r_e_v_i_c_h_at_yahoo.com>
Date: Mon, 17 Dec 2001 06:06:47 -0800
Message-ID: <F001.003DDBD5.20011217053522@fatcity.com>

Stephane,

I was reading a forum on Oracle Metalink, which may be related to your issue. The Forum's subject is "What is SYS.OBJ#_INTCOL#"? There is a reference to " analyze tables for all indexed columns" witt size 1 instead of default 75. Take a look may be it will be helpful for you

I was wondering what did you mean by "looped on hist_head#"? Did you just remove rows from it? Could you elaborate, please?

Thanks

Gene
--- Stephane Faroult <sfaroult_at_oriolecorp.com> wrote:
> The DBA of one of my customers tried to run one week
> ago dbms_stats() to analyse all indexed columns. The
> result was that all queries ended with ORA-00600. As
> trace files were indicating queries on HISTGRM$ I
> immediately directed him to the CBO (he had not
> instantly linked the cause to the effect). His
> workaround was to switch to RBO, with of course
> side-effects. When I came to the site, I reached for
> my axe and cleaned up everything using questionable
> means, especially against a production database
> (junior DBAs, please skip the next paragraph.
> Socrates was sentenced to death for corrupting the
> youth and I'd rather avoid the same fate).
> I first looped on hist_head$ to remove all related
> rows in histgrm$. Before that any query on
> DBA_COL_HISTOGRAMS ended in ORA-600. After the loop,
> to my surprise there still were rows in histgrm$. I
> deleted them, and still had ORA-600 when querying
> DBA_COL_HISTOGRAMS. They did not disappeared before
> I truncated cluster C_OBJ#_INTCOL# (or something
> like this - the cluster which holds HISTGRM$).
> There is no obvious sign of data block corruption;
> it looks more like a logical corruption. I run the
> same dbms_stats() command on a copy of the database
> without any problem, and I don't know where the
> blame should go.
> Has anybody encountered anything even remotely
> similar? In that case, it is Oracle 8.1.7.2 on
> Tru64.
>
> TIA,
>
> Stephane Faroult




Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Gene Gurevich
  INET: g_u_r_e_v_i_c_h_at_yahoo.com

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: ListGuru_at_fatcity.com (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).
Received on Mon Dec 17 2001 - 08:06:47 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US