Re: Insufficient Privileges with '/ as sysdba'

Make sure that the dba group is created and that you log into your OS as a user that belongs to the dba group.

Or, you may have specified remote_login_passwordfile=EXCLUSIVE in your init.ora 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. When you login as sysdba you should use the password that you set in your password file.  

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 Sat Sep 18 2004 - 20:05:04 CDT