Re: Concurrent Request Schedule
- From: Subodh Deshpande <subodh_deshpande@xxxxxxxxx>
- To: ora-apps-dba@xxxxxxxxxxxxx
- Date: Mon, 23 Feb 2009 02:22:47 -0800 (PST)
it makes me a sense to what Edward is saying, have not understood what possible
problems you are looking with request set.
finally the script has to handel these things..
________________________________
From: Brian Matrose <BMatrose@xxxxxxxxx>
To: ora-apps-dba@xxxxxxxxxxxxx
Sent: Saturday, 21 February, 2009 0:20:09
Subject: RE: Concurrent Request Schedule
This would be easy to do if it was a single concurrent request but its much
more difficult with a request set.
Brian Matrose
Information Technology Specialist 4
FIT Group
15 Computer Drive West
Albany, New York 12205
518-437-3532
________________________________
From: ora-apps-dba-bounce@xxxxxxxxxxxxx
[mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of Chuck Edwards
Sent: Friday, February 20, 2009 1:46 PM
To: ora-apps-dba@xxxxxxxxxxxxx
Subject: Re: Concurrent Request Schedule
It might be a good idea to leverage the script that places the file on the
server to kick off the concurrent request set. After all, that script knows
when the file is ready, so just have it kick off the concurrent program using
CONCSUB as soon as it places the file. That way no one has to launch anything
manually, and the file is processed as quickly as possible.
Chuck Edwards
Blue Gecko, Inc
http://www.bluegecko.net/oracle-apps-dba
On Feb 20, 2009, at 10:31 AM, Brian Matrose wrote:
I have a question on concurrent requests.
Here is the scenario.
1. Everyday we receive a file from an outside company. We have a script that
runs in the morning that grabs the file and places it on our Oracle Financials
server for processing.
2. The financials users have a concurrent request set, that they want to
schedule everyday to process the file.
If we can guarantee that the file is available at the same time every morning
we have no problems.
Ex. We receive the file at 6:00 AM and transfer it to the Oracle Financials
server and the Financials User schedules to run their concurrent request set
each morning at 6:30.
Our problem occurs if for some reason we don’t receive the file until 6:45 AM
or even later. We have suggested that the user schedule the request for every
hour so that if we host the file late, the next running of the concurrent
request would process it. Their issue is that they don’t want numerous
concurrent requests filling up their view request screens because it would be
too confusing. So my question is, is their any way to schedule a request set to
run only until it completes successfully and than stop running until the next
day.
Thanks
Brian Matrose
Information Technology Specialist 4
FIT Group
15 Computer Drive West
Albany, New York 12205
518-437-3532
________________________________
________________________________
This e-mail transmission contains confidential information that is the property
of the sender. If you are not the intended recipient, you are notified that any
retention, disclosure, reproduction or distribution of the contents of this
e-mail transmission, or the taking of any action in reliance thereon or
pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that
this e-mail is free of viruses, interception or interference. NYSIF disclaims
liability for any unauthorized opinion, representation, statement, offer or
contract made by the sender on behalf of NYSIF. NYSIF's delegation of
authorities, setting out who may make representations or contract on behalf of
NYSIF, is available by contacting NYSIF at mailadm@xxxxxxxxxx Jurisdiction for
all actions arising out of dealings with NYSIF shall lie only in a court of
competent jurisdiction of the State of New York.
_____________________________
________________________________
This e-mail transmission contains confidential information that is the property
of the sender. If you are not the intended recipient, you are notified that any
retention, disclosure, reproduction or distribution of the contents of this
e-mail transmission, or the taking of any action in reliance thereon or
pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that
this e-mail is free of viruses, interception or interference. NYSIF disclaims
liability for any unauthorized opinion, representation, statement, offer or
contract made by the sender on behalf of NYSIF. NYSIF's delegation of
authorities, setting out who may make representations or contract on behalf of
NYSIF, is available by contacting NYSIF at mailadm@xxxxxxxxxx Jurisdiction for
all actions arising out of dealings with NYSIF shall lie only in a court of
competent jurisdiction of the State of New York.
Other related posts: