Re: connect / as sysdba not equivalent to connect internal

It's a SQL*Plus bug 9and I note you haven't patched to 8.1.7.3 where I believe the bug was sorted). An artifact of the merge of server manager and sql*plus functionality which meant that sqlplus would occasionally reject connection requests it was supposed to accept (such as the one you describe).

Internal and "/ as sysdba" *are* functionaly identical: both get you connected as SYS as a privileged user. It's just taken SQL Plus a bit of time to catch on to the new thinking!

In 9i, for example, it's not a problem.

Regards
HJR "Marcel Kraupp" <marcel.kraupp_at_gmx.ch> wrote in message news:332bb004.0205130819.350f59a0_at_posting.google.com...
> Hello
>
> I was (mis-)led(?) to believe that
> connect / as sysdba
> is equivalent to
> connect internal
> on 8i.
>
> However, I found out that they're not. If someone could point
> me to the differences I'd be very thankful.
>
> Here's what happened.
>
> I wanted to bounce my database. I connected / as sysdba and did a
> shutdown immediate. However, that shutdown took very long, so I
> decided to do a 'shutdown abort'. This is what happened
>
> $ sqlplus /nolog
>
> SQL*Plus: Release 8.1.7.0.0 - Production on Mon Mai 13 17:40:20 2002
>
> (c) Copyright 2000 Oracle Corporation. All rights reserved.
>
> SQL> connect / as sysdba
> ERROR:
> ORA-01089: immediate shutdown in progress - no operations are permitted
>
> SQL> shutdown abort
> ORA-01031: insufficient privileges
> SQL>
> SQL> connect internal
> Connected to an idle instance.
> SQL> shutdown abort
> ORACLE instance shut down.
> SQL> exit
> Disconnected
>
>
> The point is: "connect internal" is supposed to be deprecated and replaced
> by a / as sysdba, but internal seems to be more powerful as I can complete
> with it an action that I couldn't have otherwise (or had no clue how)
>
> So, if someone knows an answer to this, please let me know
>
> MK
Received on Tue May 14 2002 - 03:43:39 CDT