Re: connect as versus internal

From: Nitin Goyal <nitingoyal_at_hotmail.com>
Date: 7 Feb 2002 23:06:02 -0800
Message-ID: <32343515.0202072306.7bd2c821@posting.google.com>

Hi,

It seems its a much simpler issue rather than password file and additional syntax checking:

See the snippet below - this was run when there was no Oracle instance running:

[oracle_at_linux oracle]$ sqlplus /nolog

SQL*Plus: Release 8.1.7.0.0 - Production on Fri Feb 8 12:23:46 2002

(c) Copyright 2000 Oracle Corporation. All rights reserved.

SQL> shutdown abort;
ORA-01031: insufficient privileges

SQL>
SQL>
SQL> connect internal;

Connected to an idle instance.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> It is clear from Joachim Rupik's post that

$ 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
<<<<<<--- Here you were not able to connect in the first place.

SQL> shutdown abort
ORA-01031: insufficient privileges <<<<<<-- As not connected, this error raised
SQL>
SQL> connect internal
Connected to an idle instance.

The only point of inetrest being that we get the message "ORACLE instance shut down" even when there is no instance running. Maybe Oracle is too sure of completing this successfully so that it doesnt even bother to check whether there is an instance even in the first place. Received on Fri Feb 08 2002 - 01:06:02 CST