HP3000-L Archives

June 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stigers, Greg ~ AND" <[log in to unmask]>
Reply To:
Stigers, Greg ~ AND
Date:
Thu, 11 Jun 1998 19:59:10 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
Yet Another Naive/Newbie Question, for those who understand Oracle and
POSIX better than I do. While I was out of the office, we had some
network problems which seemed to have hosed the Oracle listener. Our
DBA, who does not have SM authority, contacted an admin at the data
center. After some research, the data center admin killed the Oracle
listener, then the DBA brought it back up, and all was status quo.

My primary question is, could the DBA have determined the process id and
killed the listener himself, or is there a way to kill the listener
other than by process id? I see that the listener is in the SERVICES.NET
file, but not in INETDCNF. Also, the listener runs as a system process,
not under an id, as those wrapped by the inetd. But I am not quite sure
what sense to make out of this (explanations welcome). Now, this is a
long shot, but if the DBA cannot get the process id, is there any way
for the process to run under the Oracle id instead of as a system
process, or is the latter a requirement?

ATOM RSS1 RSS2