Xref: alice comp.databases.oracle.server:39537 Path: alice!news-feed.fnsi.net!newsfeed.ecrc.net!newsfeed.nacamar.de!dispose.news.demon.net!demon!news.demon.co.uk!demon!camk.demon.co.uk!Andy.Hardy From: Andy Hardy Newsgroups: comp.databases.oracle.server Subject: Re: How to properly manage listener on a DBMS_PIPE Date: Tue, 2 Feb 1999 09:56:18 +0000 Organization: ALSTOM Automation Distribution: world Message-ID: References: <78sa0b$hgg$1@mosquito.HL.Siemens.DE> X-Trace: news.demon.co.uk 917950469 nnrp-09:29592 NO-IDENT camk.demon.co.uk:194.222.188.130 X-Complaints-To: abuse@demon.net MIME-Version: 1.0 X-Newsreader: Turnpike Version 3.04 Lines: 31 In article <78sa0b$hgg$1@mosquito.HL.Siemens.DE>, Rainer Leidner writes >I use DBMS_PIPE to send messages to an external listener/daemon. >I experience occasional problems to start the listener or to keep it >running. > >What is a good method to make sure that the listener is always up and >running? > >This is in Oracle 7.3.4 on Solaris 2.5.1. > >Tnx > >Rainer > > Not quite sure what you mean about getting a listener/daemon to keep running - never suffered myself! We tend to set up a job to run any 'forever' pipe listener procedures - they never exit and start up again whenever the database is restarted. Andy P.S Don't forget that the 'forever' jobs will each require a job queue... -- Andy Hardy Senior IT Systems Engineer, ALSTOM Automation Tel: +44 1908 696200 Fax: +44 1908 696225 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Opinions are mine and do not necessarily reflect those of ALSTOM Automation