|
---------- > From: Dave Parmer <dparmer@interaccess.com> > To: BPCS-L@midrange.com > Subject: Re: 6.02 and Oracle > Date: June 18, 1998 11:45 PM > > The Oracle manual says that this happens when a user presses cntrl-c. <snip> > If you have ruled this out then it is possible that something in BPCS is > causing this though I doubt it unless it happens every time (it sounds like > an intermittent problem from your post). In the case of MRP, we run it in batch at 1:30 am. In the case of the other programs that run interactively, we have monitored it like crazy and the job is not killed at the Client or UNIX level. > > These types of problems are very hard to pin down since they do not happen > every time. It usually ends up being an Oracle or UNIX system setting > (believe it or not). Definately hard to pin down, since our application is on an HP and our database is on a DEC. This has only started to happen recently - we have been testing for over a year, and live for a few months now. The best thing to do is call the Helpline in Chicago > armed with as many bpcslog examples as you can get. They are going to > assume someone is using the kill command. If you know this is not the case > then be persistent and have them log on to your system and monitor it when > MRP is running. They might be able to see an Oracle or UNIX resource > problem. Both SSA offices in Chicago and Toronto have been notified of the problem. Still awaiting their response :-) -Christine +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.