Re: Insufficient Privileges with '/ as sysdba'

I'm just stating what I have experienced in my environment at work (which is Windows). Thanks for sharing your experiences with us, too.

Adam

"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:<414ce348$0$20129$afc38c87_at_news.optusnet.com.au>...
> adamenos wrote:
>
> > Make sure that the dba group is created and that you log into your OS
> > as a user that belongs to the dba group.
>
> It's not the dba group. It's whatever group was declared to have
> administrative privileges at the time the installation took place. That is
> *usually* the dba group, but it could be all sorts of other things as well.
>
> > Or, you may have specified remote_login_passwordfile=EXCLUSIVE in your
> > init.ora
>
> That makes zero difference, actually. That the init.ora says to use a
> password file would not stop a preliminary check of the O/S groups and
> memberships.
>
> The parameter says "I have this sort of password file" not "Please don't do
> O/S authentication".
>
> > and you now have a corrupt password file. If you have a
> > corrupt password file then you need to shutdown the database, rebuild
> > the password file and then restart your database.
>
> Re-creating a password file does not require the database to be shut down,
> for the very simple (and obvious) reason that if it did, how would you
> connect to the database in order to issue the shutdown command?!
>
> Just delete it, and use orapwd to re-create it. No shutdown necessary.
>
> All of which is besides the point anyway, because the guy is using O/S
> authentication, not password file authentication.
>
> > When you login as
> > sysdba you should use the password that you set in your password file.
>
> Well, yes... except that as he has demonstrated, he has no problem
> connecting with a password (indicating that the password file is fine), but
> that the problem is with his O/S authentication mechanism.
>
>
>
> >
> >
> >
> > Daniel Morgan <damorgan_at_x.washington.edu> wrote in message
> > news:<1095458613.69943_at_yasure>...
> >> Buck Turgidson wrote:
> >>
> >> > In 9i, I used to be able to use '/ as sysdba' on the command line to
> >> > startup a database. Now in 10g I have to use 'sys/passwd as sysdba'.
> >> >
> >> > Did something like os authentication change in 10g? I am using linux.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > buck_at_turf:~> sqlplus '/ as sysdba'
> >> >
> >> > SQL*Plus: Release 10.1.0.2.0 - Production on Thu Sep 16 09:06:09 2004
> >> >
> >> > Copyright (c) 1982, 2004, Oracle. All rights reserved.
> >> >
> >> > ERROR:
> >> > ORA-01031: insufficient privileges
> >> >
> >> >
> >> > Enter user-name:
> >> > buck_at_turf:~> w
> >> > buck_at_turf:~> sqlplus 'sys/passwd as sysdba'
> >> >
> >> > SQL*Plus: Release 10.1.0.2.0 - Production on Thu Sep 16 09:06:30 2004
> >> >
> >> > Copyright (c) 1982, 2004, Oracle. All rights reserved.
> >> >
> >> > Connected to an idle instance.
> >> >
> >> > SQL> startup
> >> > ORACLE instance started.
> >> >
> >> > Total System Global Area 138412032 bytes
> >> > Fixed Size 777796 bytes
> >> > ...
> >>
> >> 10g is identical to 9i. The problem here is that the operating system
> >> account you are using is not a member of the DBA group.
Received on Tue Sep 21 2004 - 00:31:05 CDT