Path: news.easynews.com!easynews!news-out.cwix.com!newsfeed.cwix.com!solaris.cc.vt.edu!news.vt.edu!msunews!not-for-mail From: "Chris Weiss" Newsgroups: comp.databases.oracle.server Subject: Re: Crashes when desc user_segments Date: Sat, 2 Feb 2002 22:34:15 -0500 Organization: www.hpdbe.com Lines: 46 Message-ID: References: NNTP-Posting-Host: 198.109.162.195 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Xref: easynews comp.databases.oracle.server:133705 X-Received-Date: Sat, 02 Feb 2002 20:34:09 MST (news.easynews.com) Typically, when one or more of your system views is causing either a core, hang, or a killed session, then your system tablespace and/or data dictionary is corrupt Check your alert log and dump areas for core dumps and ORA-600 type errors. I would recommend that you export your data, kill the database, and import to a fresh database with the previous database and data files completely removed and replaced. You might also run diagnostics on your disks. You may have a bad disk. I have had your exact problem happen on a small Linux box when I tried a gigantic update query on a small single disk database. Oracle hung and the data dictionary was corrupted. I was able to recover by following the procedures I described above. If you have a full cold back up, you can restore and that should cure the problem as well. However, knowing how far to go back and when the corruption occurred might create issues. I am assuming since this is not a production database, the data probably is not critical, so trashing and rebuilding is your best option. Good Luck! -- ~~~~~~~~~~~~~~~~ Chris Weiss www.hpdbe.com High Performance Database Engineering ~~~~~~~~~~~~~~~~ "J Alex" wrote in message news:kCH68.502978$oj3.96490553@typhoon.tampabay.rr.com... > My sql*plus crashes when I am in as a dba user (well, any user) and try to > desc user_segments. I can select from it fine, but doing a describe on > user_segments closes the SQL*Plus window. This is true whether on the server > or a client. > It's 8.1.7.0.0 on NT. I haven't found other views/tables that causes this > (but I haven't tried them all). > Describing sys.dba_segments is fine. > The database is new and not in production yet. My main concern is whether > this is a symptom of a bigger issue that hasn't shown up yet. > >