Re: Can't connect to instance

"Life Learner" <PowerE2E_at_yahoo.com> wrote in message news:<GHb7a.342622$sV3.10443026_at_news3.calgary.shaw.ca>...
> "David Fitzjarrell" <oratune_at_msn.com> wrote in message
> news:32d39fb1.0302261347.74f9cd42_at_posting.google.com...
> > "Life Learner" <PowerE2E_at_yahoo.com> wrote in message
> news:<IdW6a.336431$Yo4.12110110_at_news1.calgary.shaw.ca>...
> > > Hi all,
> > >
> > > I already added one user into "dba" group on my Solaris machine, but
> still
> > > couldn't connect to the instance:
> > >
> > > # sqlplus /nolog
> > >
> > > SQL*Plus: Release 8.1.7.0.0 - Production on Wed Feb 26 11:03:57 2003
> > >
> > > (c) Copyright 2000 Oracle Corporation. All rights reserved.
> > >
> > > SQL> connect / as sysdba
> > > ERROR:
> > > ORA-01031: insufficient privileges
> >
> > Is DBA this user's primary group? If not, a 'newgrp DBA' command
> > should fix the problem.
> >
> >
> > David Fitzjarrell
>
> thanks for input. I'd like to clarify my case. I am trying to connect to the
> Oracle instance WITHOUT AUTHENTICATION
> under different unix accounts, which already has been put into "dba" group
> of unix system.
>
> 1. the default user "oracle", its primary group is "dba", works fine.
> 2.other regular users, its secondary group is "dba", works fine.
> 3. the user "root" , its secondary group is "dba", FAILS. But it works after
> "newgrp dba".
>
> is it weird?

Not really. The install guide says "Do not do that." Unix is letting you force the issue by replacing your primary login shell with one that has the dba group. The thing about root is, root can do anything root wants. That is why many experienced admins who wear different hats only give _themselves_ root when they _have_ to. Experience means having many bullet holes in your feet, especially from not following directions like "do not point gun at feet."

It used to be something about locking out users in non-dba groups that run daemons...

jg

--
@home is bogus.
Unix is user-friendly, it is just very picky about its friends.