On our ArcSDE 10 SP5 (on Solaris T-4, Oracle 11.2.0.3), when I try to kill a 3-tier connection through "sdemon -o kill -t all -p <password> -N" - doesn't matter if I use "all" or individual pid, I'm getting "Underlying DBMS error, Unable to kill servers" error. I believe that SDE has all the required privileges. After our DBA added SDE to the DBA role, now I'm getting "Invalid DBA password, Unable to kill server" error. The odd thing is we also have a user schema geodatabase in this Oracle instance, and I'm able to kill 3-tier connection in this user schema geodatabase. There is also no problem to "kill" direct connect in both the SDE and user schema geodatabases. So, the only problem is to "kill" 3-tier connections in SDE geodatabase. Does anyone have seen this before? I suspect the problem is related to some settings, but why the user schema doesn't have this issue? I don't see any difference in the sdeconfig of these two geodatabases either. I also was not able to find concrete SDE log errors nor Oracle trace errors. The most information I got was from 10.1 Desktop "Geodatabase Administration" tool with "Underlying DBMS error (No Data Found)." Is there a document detailing what exact steps "sdemon -o kill" is doing, so I can walk through each step manually?
Thanks!