RE: SMON - Killed process

I tried a shutdown abort, startup and shutdown immediate. But believe it or not, SMON just got back at it as soon as I did a shutdown immediate ...

Anyway, I was advised by Orcale to put event = "10052 trace name context forever" in the init.ora file. I have no idea what it does, but I enabled us to shut down the database and take a complete backup. After that, we removed the event-line, started the database and did a shutdown immediate again ... SMON kept working at it for a couple of hours, but was finished by the time I got in this morning to make sure everybody could get to work. Just hope it goes well this evening.

> -----Original Message-----
> From: Chuck Hamilton [SMTP:chuck_hamilton_at_yahoo.com]
> Sent: Friday, June 30, 2000 5:03 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: SMON - Killed process
>
> It's rolling back the transactions for the killed sessions. 8 hours seems
> like an awfully long time though. I sometimes wonder if SMON gets lost. In
> that situation I would probably abort the instance followed by a restart
> and see if the rollback completes any faster during automatic recovery. I
> know of several DBAs who make that their standard practice before starting
> a cold backup - abort, restart, shutdown immediate.
Received on Mon Jul 03 2000 - 02:48:39 CDT