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

Home -> Community -> Usenet -> c.d.o.server -> Re: shutdown immeditae waiting, grep ora, got process

Re: shutdown immeditae waiting, grep ora, got process

From: Howard J. Rogers <hjr_at_dizwell.com>
Date: Sun, 19 Oct 2003 08:53:47 +1000
Message-ID: <3f91c508$0$21652$afc38c87@news.optusnet.com.au>


joe bayer wrote:

> Howard,
> How do you kill "intelligent agent"?
> ps -eaf|grep intellignet or ps -eaf|grep agent
> did not return anything.


Oh God, don't start killing things at the O/S level. That's why I said 'shutdown the intelligent agent', not kill it. I meant exactly what Sybrand has listed as the commands. Before 9i, it was lsnrctl dbsnmp_stop. In 9i, it's agentctl stop.

Regards
HJR

> 
> Thanks
> 
> 
> "Howard J. Rogers" <hjr_at_dizwell.com> wrote in message
> news:3f90f533$0$24515$afc38c87_at_news.optusnet.com.au...

>> yls177 wrote:
>>
>> > hi, below are my steps
>> >
>> > 1) shutdown immediate;
>> > 2) but oracle still hanging, as in can do a ps -ef | grep ora and
>> > still the set of family oracle processes are alive
>> > 3) so i do a select * from v$instance;
>> > 4) and when it says that " oracle not available"
>> > 5) then i safely do a shutdown abort
>> > 6) finally, the family set of oracle processes are gone.
>> >
>> > but is it absolutely safe to do this?
>> >
>> > please confirm
>>
>> It's never *absolutely* safe to do a shutdown abort. There is a
>> miniscule, but real, risk that you lose your current redo log seconds
>> after doing the shutdown abort. *All* shutdown aborts require instance
>> recovery on subsequent startup. All instance recoveries require the
>> contents of the current redo log to be available. Therefore, after a
>> shutdown abort, if
> you

>> lost your current redo log, you would not be able to do instance recovery
>> and you would be faced at best with the prospect of performing an
>> incomplete media recovery... meaning transactions would be lost.
>>
>> A lot of people do shutdown abort - startup -shutdown immediate to get
>> around this problem.
>>
>> Me? I would shutdown the intelligent agent, and then do a shutdown
>> immediate. The agent has a session on the database, and it's one that
> seems

>> not to respond very well to the shutdown immediate command. So kill the
>> agent first, and you tend to find immediate shutdowns become a lot
>> faster.
>>
>> Regards
>> HJR
>> --
>> --------------------------------------------
>> See my brand new website, soon to be full of
>> new articles: www.dizwell.com.
>> Nothing much there yet, but give it time!!
>> --------------------------------------------
>>
-- 
--------------------------------------------
See my brand new website, soon to be full of 
new articles: www.dizwell.com.
Nothing much there yet, but give it time!!
--------------------------------------------
Received on Sat Oct 18 2003 - 17:53:47 CDT

Original text of this message

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