Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Disconecting from Oracle without killing Oracle SPs

Disconecting from Oracle without killing Oracle SPs

From: Default User <user_at_jsc.nasa.gov>
Date: Mon, 28 Dec 1998 13:41:23 -0600
Message-ID: <3687DEE3.A1DC1788@jsc.nasa.gov>


Looking for ideas. What I want to do is kick off Stored procedures, then disconnect.
Should be simple except Oracle kills the process. Is there a way to tell Oracle to
keep the process running even after disconnection?

    I've been trying to develop a means for a currently running application to batch SP's
against already created and populated tables. Problem is that as soon as the ODBC
connection is broken all SP's spawned by that connection are killed.

    Platform is
Client VB using ODBC (Oracle73 Ver 2.5) on Win 95 machines Server Oracle 7.3 on Solaris box.

Current product connects to Oracle runs the SPs and then processes the data
when it returns. This can take several hours on some of the longer queries. Instead
client wants the ability to run proccess and turn off the machine. Then process
the results the next day or lator that day or whenever it is done.

This would be simple if breaking the ODBC connection didn't kill the SP. We
tried running the SP from a CGI script instead of directly sending it to SQL but
this is untolerably slow since it has to be run as a back ground proccess and Unix
assigns it a very low priority. Next try was Nohup but Nohup and SQLPlus are
not being agreeable.

Any ideas?

Thanks
Dan
daniel.p.smith1_at_jsc.nasa.gov
dan.p.smith_at_usa.net Received on Mon Dec 28 1998 - 13:41:23 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US