Re: sysdba sysoper not powerful?

I get the same error message that you do if I do not make the connection "as sysdba". Which makes me think you are only missing the correct connection syntax.

The following is a connection without sysdba to generate the error you received, a connection with sysdba and then a shutdown and startup.

SQL> connect sysdbauser/password_at_here
Connected.
SQL> shutdown immediate
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected

SQL> connect sysdbauser/password_at_here as sysdba Connected.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> connect sysdbauser/password_at_here as sysdba Connected to an idle instance.
SQL> startup pfile=c:\oracle\ora81\database\inithere.ora ORACLE instance started.

Frank Hubeny
WExcel, Chicago (http://www.wexcel.com)

Doug Cowles wrote:

> I thought a user with sysdba and sysoper could bring down
> the database.
> I created an ops$oracle account and granted sysdba, sysoper,and dba
> to it.
> From sqlplus - if I shutdown immediate
> I get
> ORA-01093 alter database close only permitted with no sessions
> connected.
> Wheras a regular internal or svrmgrl session just shuts them down.
> Is the sysdba sysoper account supposed to use svrmgrl, not sqlplus ?
> When I try that, I get ORA-01031: insufficient privleges.
>
> What am I missing?
>
> - Dc.
Received on Sun Nov 21 1999 - 15:29:22 CST