How to best schedule jobs in another schema?

From: Rich Jesse <rjoralist_at_society.servebeer.com>
Date: Thu, 11 Feb 2010 14:20:57 -0600 (CST)
Message-ID: <a2d8edfd2730c81de1b811521b74ef73.squirrel_at_society.servebeer.com>



Howdy,

Revisiting my post from 2008:

http://www.freelists.org/post/oracle-l/Scheduler-jobs-run-as-creator-instead-of-owner

...I found a vague inference to a Scheduler job running as *creator* instead of *owner*:

http://download.oracle.com/docs/cd/B14117_01/server.101/b10739/scheduse.htm

Confusing and inconsistent with other Oracle security IMHO, but that's the way it works.

So how should one schedule jobs to run in another schema? The schemas I'm trying to run jobs in cannot be logged into for security purposes (have an invalid password). The only thing I can come up with is to write a DBMS_SCHEDULER wrapper package to be created in each schema, but this is a maintenance nightmare. Either that, or use a generic "execute immediate" proc in each schema, but the security implications of that should be obvious.

Anyone using DBMS_SCHEDULER to run jobs in another schema? How do you use it?

Thanks,
Rich

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Feb 11 2010 - 14:20:57 CST

Original text of this message