Thanks. I wasn't sure if a shared mount was possible on the db server. I
will see if I can figure that out.
On Wed, Jun 24, 2020 at 4:53 PM Tharmarajah, Sam <
sambavan.tharmarajah@xxxxxxxx> wrote:
We have somewhat same requirement. The way we have handled it was to have
a shared mount between the dB and the batch server. Have directory object
in the dB pointed to the share. On the batch server, the remote services
puts the file under appropriate folders , an a cron job that will awake up
and run the sql or plank on the dB.when then does the rest of the process.
On the batch server where the sql gets executed, we have setup wallet and
tightly limit ace
ss to the OS user and heavily audit.
Sent from my iPhone
On Jun 24, 2020, at 3:15 PM, Ethan Post <post.ethan@xxxxxxxxx> wrote:
CAUTION: This email originated from outside of the University of
Saskatchewan. Do not click links or open attachments unless you recognize
the sender and know the content is safe. If in doubt, please forward
suspicious emails to phishing@xxxxxxxx
I was hopeful I could use DBMS_SCHEDULER for this. Not sure, credentials
are the main issue I think.
I could write scripts I want to run to a table and have an external server
checking for new records and running the .sql from another host.
Not sure if a shared file system is possible. I write an entry to a log on
a shared file system and another server is monitoring same file system and
runs script when commanded.
How would you accomplish this task?
Ultimately I love .sql scripts for some things and don't want to port them
to PL/SQL. I need to be able to run, get output and save, email...this
needs to happen in response to some event within the database.
Thanks!
Ethan
