Re: connect as versus internal

It seems that the "as sysdba" syntax invokes some additional checking on password files and permissions. I had this same thing happen, but after recreating the password file ($ORACLE_HOME/dbs/orapw) and setting remote_login_password=exclusive everything seems to work OK.

(8.1.7.2 on Solaris 2.7)

-Peter

Joachim Rupik wrote:
>
> 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 Thu Feb 07 2002 - 10:18:51 CST