Hi folks,
7.3.4 on Solaris
checking whether a certain job is running.
submitted by this procedure.
job doesn't run as the owner of the procedure. The job deletes rows from a
table, and simply noone has direct delete privileges.
deliberately removed the current job, and I ran the procedure using my own
account. The results were unexpected:
where all set to my account
disappeared at all. It was not broken, it simply vanished.
a similar procedure is run at database start, but then I still need to do
this 'on behalf of', otherwise I will end up having a script with hard-coded
username password combo's.
ideas/trics.
version?
DBA
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Tue Apr 20 1999 - 10:01:51 CDT
