Re: utlestat Crashing 8.0.5 Server on Solaris 2.6

ORA-600 are normally Oracle problems that are not frequent and have not been given another error number. It would be best to get on to Oracle Support with the details of the other reference numbers given with the ORA-600. When we have had this in the past it has turned out to be a one off and not worth worrying about as it did not reoccur or it was block level corruption and a rather serioud problem deep in the structure of a tablespace datafile.

Good hunting

--
Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich England)

                        <KevinALewis_at_HotMail.com>

The views expressed herein by the author of this document are not necessarily those of BOCM PAULS Ltd. Rich Goldkamp <RJGoldka_at_dcss.com> wrote in message news:7hci7r$ioa$1_at_nnrp1.deja.com...
>
>
> When running utlestat against an 8.0.5 instance on Solaris 2.6, the
> instance crashed with an ugly ORA-600 error while executing the
> statement
>
> drop table stats$dates;
>
> After restarting the instance, everything was fine (the stats$dates
> table had been dropped), but I'd rather not pay such a high price to
> gather statistics.
>
> I've modified both utlbstat and utlestat by commenting out the "connect
> internal" -- instead I log into server manager as a user with the DBA
> role, but a default tablespace other than SYSTEM. I've also modified
> the scripts to dynamically turn on and off TIMED_STATISTICS at the
> appropriate places. These changes have never caused me grief before,
> but this was the first time I've done it on a Solaris Oracle
> implementation. Also, this database serves as a backend for OAS.
>
> Any and all ideas appreciated!
>
> Thanks,
> Rich
> --
> Rich Goldkamp, Consultant, OCP RJGoldka_at_dcss.com
> Digital Consulting & Software Services (504) 523-5005 x2736
>
>
> --== Sent via Deja.com http://www.deja.com/ ==--
> ---Share what you know. Learn what you don't.---
Received on Thu May 13 1999 - 03:37:08 CDT