Re: shutdown

you have to use

SVRMGRL> shutdown abort

to have oracle disregard the TCP connection from your dead pc which oracle thinks is still alive because solaris will keep probing that
TCP connection for 2 hrs ( by default )
thinking that it is still alive

# ndd -get /dev/tcp tcp_keepalive_interval

this defaults to 7200000 msecs == 2 hours

setting it to 240000 == 4 minutes

# ndd -set /dev/tcp tcp_keepalive_interval 240000

so if you parse a

SVRMGRL> shutdown immediate

you will have to wait for 4 minutes and
then solaris will force down your dead PC connection TCP socket and then oracle will see this and let your shutdown immediate do its thing correctly. This is because Oracle 7.3 SQL*Net looks to Solaris for socket status

but later version of oracle got saavy to this ( like versions 8 and 8i and up ) so that regardless of what solaris says oracle knows how to handle this all by itself

( i forget what the parameter actually is though )

some wizrd DBA lsnrctl person will know ...

regards
chris

Audun wrote:
>
> I've got that problem too when I try to shut down a db on a SUN box (OEM
> 7.3.4.0.1) after restarting my own PC. I's no problem as long as I don't
> restart the PC.
>
> linemodus:
> User=oracle, Group=dba ->svrmgrl ->connect internal ->shutdown
> immediate...
>
> The env (SID, ORACLE_HOME ++) are OK.
>
> Do anyone have an idea?
>
> Audun Hansen
>
> "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
> news:tffl5ielenc455_at_beta-news.demon.nl...
> >
> > "Félix" <fgaitero_at_e-netfinger.com> wrote in message
> > news:9d8ibm$g9q$1_at_talia.mad.ttd.net...
> > > I cannot shutdown my database as connect to system/manager. I can only
> > > shutdown as internal. When I attemp a shutdown as system/manager I get
 the
> > > error message:
> > > ORA-01031: insufficient privileges.
> > >
> > >
> >
> > That would be the normal behavior. Any account which doesn't have at least
> > SYSOPER privilege can't shut the database.
> >
> > Regards,
> >
> > Sybrand Bakker, Oracle DBA
> >
> >
> >

--