I wish it would! But I think this part is correct. Of course, I've
been staring at it long enough to be well into stupid mistake
devel users dba
-rwsr-s--x 1 oracle devel 53734878 Sep 21 12:48 /home/oracle/
#define SS_DBA_GRP "devel"
#define SS_OPER_GRP "devel"
Have I missed something obvious here? I know "devel" is a weird
choice of group name but I didn't do the install and as far as I can
see it should work.
On Dec 6, 2006, at 3:08 PM, Mladen Gogala wrote:
> Your group is "oinstall" and your "dba" group is not active.
> "newgrp dba" should do the trick.
> -----Original Message-----
> From: oracle-l-bounce@(protected)
> Sent: Wednesday, December 06, 2006 5:14 PM
> To: Oracle-L Freelists
> Subject: can't connect '/ as sysdba'
> I'm still googling for answers but it's looking like I won't
> finding one, so time to ask here.
> I am working as a consultant with a 22.214.171.124 installation. I
> present when it was installed and didn't see anything out of
> ordinary happen. It seems to function normally with one
> exception -
> no matter what I do, I get an ORA-01031
> error when I try to connect with '/ as sysdba', which
> dbstart and dbshut from working. I have worked with other
> installations and have never had this problem before.
> Most of the suggestions boil down to making sure that group
> assignments are correct and that TWO_TASK is not set, and
> followed up on both of those. The group that owns all of
> the files
> in $ORACLE_HOME is the same one that's set in config.c and
> is the
> oracle user's primary group. I am only expecting this to
> work as the
> oracle user.
> What else could be wrong?