Prev: constraint disable (no)validate
Next: DBMS_AQ
From: Danos on 8 Feb 2005 05:50
Hi,

recently upgraded from Oracle 8.1.7 to 9.2 on Solaris 9 and I'm having
some problems. One of our applications won't start if I start Oracle
as an oracle dba (gid is dba). There seems to be some issue there

If I start Oracle is a member of the dba group but has a different
active group the application will start but I get errors when trying
to stop the database as a dba. I start sqlplus with the /nolog switch
and connect as sysdba (sys). First of all sqlplus tells me I'm
connected to and idle instance and then...


shutdown immediate

gives me the following errors:
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-27140: attach to post/wait facility failed

If I try to force a startup it gives me the following error:
ORA-01031: insufficient privileges


It's the same way if I do it the other way around... that is if i
start oracle with a user that has gid=dba and try to shut it down with
a user that is just a member of the dba group i get the same errors.

Anyone have any ideas?
From: Steve H on 8 Feb 2005 06:40
Could you connect via SQL*Net as a user with 'sysoper' privilege
(you'll need a password file and 'grant sysoper to <user>') ?


Also, for your example, check that the 'sticky' bit is set on the user
and group execution bit for the required oracle binaries so that all
processes that run oracle use the same memory

e.g. one of them is this:

-rwsr-s--- 1 oracle dba 69198144 Nov 22 13:12 oracle

From: hpuxrac on 8 Feb 2005 08:11
Go into the oracle home bin directory and do an ll ... look at the info
for the oracle executable ( what user and group it belongs to and the
permissions ). Post your results if you need more help otherwise you
can probably figure it out.

 | 
Pages: 1
Prev: constraint disable (no)validate
Next: DBMS_AQ