Re: Oracle screws up Sun host

andreyNSPAM_at_bookexchange.net (NetComrade) wrote:

>you should be able to connect internal and shutdown abort..

I try to stay by the rules which say not to use shutdown abort unnecessarily. Well, I only know it is necessary when it does not work any more.

>extremely
>rarely do we have to reboot a server (almost never, i don't recall
>such thing happenning for a long time). And the only thing that we
>kill off are some dead connections (e.g. ps -ef|grep LOCAL|grep
><SID>), I don't recall seeing ora background processes sitting around.
>Also, you should be able to kill runaway processes via alter session
>or OS, I never saw oracle background processes to be 'runaway'.

The processes that I had to kill were archiver processes. Now I remember that four days ago the archiver was blocked ("no destination available") because too many redologs were produced as the DB was reorganized and tables were moved. What I did was to delete some of these archived logs, "archive log stop", "archive log all", "archive log start" and everything seemed to go well. It just seemed.

>It's probably best that you resolve those ORA-0600's with oracle
>support.

I used Oracle support once. It was enough. It is a waste of time.

Rick Denoire Received on Mon Apr 21 2003 - 19:16:35 CDT