Re: Why is it so difficult to shutdown Oracle?

From: Chuck Hamilton <chuckh_at_ix.netcom.com>
Date: 1996/01/26
Message-ID: <4eb453$2aq_at_cloner3.netcom.com>#1/1


smushran_at_us.oracle.com (Sunil Mushran) wrote:

>lunch_at_ix.netcom.com(Arthur Chung ) wrote:

>> We are running Oracle 7.1.6 on Sun Sparc1000 with various front-ends
>> (Gupta/Business Objects) and I'm very puzzled with the shutdown
>> mechanism of Oracle.
 

>> Our DBA consultant(who does get fat check) tells us that,
>> 'shutdown normal or immediate' only kills the processes
>> locally connected.
>> But since most of our users are accessing Oracle through the PC
>> front-end progs. we have mostly 'non-local' connections.
 

>> And since these 'non-local' connection won't die out when we use
>> 'shutdown normal or immediate', dba created a sql script that
>> generates the session-id of all the connection
>> by querying v$session table.
>>
>> And then, we are using those session-id to disconnect each session
>> that are connected from PC. (ie, alter system kill session '11,555')
>> Sounds complicated?... I think so.
 

>> Is this the right way to do shutdown in client-server environment?
>> Is there a better way to shutdown the Oracle while many sessions are
>> opened from PC?
 

>> Many thanks in advance.
>> -Arthur
 

>Strange.... At least on Desktop Servers (NetWare et al), SHUTDOWN
>IMMEDIATE kills all the shadow processes (i.e. both local and remote
>connections).
 

>sm

It does the same on UNIX too. The user isn't immediately notified of the shutdown, but the next time he tries to access the database he will be.

--
Chuck Hamilton
chuckh_at_ix.netcom.com

Never share a foxhole with anyone braver than yourself!
Received on Fri Jan 26 1996 - 00:00:00 CET

Original text of this message