Two possible scenarios here:
- A bug (surely not!)
- Incorrect configuration
I don't have 8.1.7 any more to play with, so I can't reproduce the scenario,
but this should definitely work as documented. Sure as heck does in 9i
where INTERNAL is no more.
--
HTH. Additions and corrections welcome.
Pete
Author of "Oracle8i: Architecture and Administration Exam Cram"
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!"
Bruce Pihlamae, long-term Oracle DBA
"Joachim Rupik" <JRupik_at_awrsp.gov.pl> wrote in message
news:3C6133A5.C9724C52_at_awrsp.gov.pl...
> Hello,
>
> I have one question:
>
> I can connect to oracle using new syntax (method) " connect / as sysdba"
and it
> should be equivalent to "connect internal" (de-supported beginning from
9i).
> But below is output that shows that it does not work the same way. Why?
>
> Thank you in advance,
> Joachim Rupik
> jrupik_at_awrsp.gov.pl
>
> $ sqlplus /nolog
>
> SQL*Plus: Release 8.1.7.0.0 - Production on Tue Jan 8 08: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
>
>
Received on Wed Feb 06 2002 - 10:00:18 CST
