http://www.pythian.com/news/652/using-dbms_sys_sql-to-execute-statements-as-another-user/ On Fri, Feb 12, 2010 at 8:38 AM, Barun, Vlado <Vlado.Barun@xxxxxxx> wrote: > I have not tried this for creating new jobs, but what about using > dbms_sys_sql? > > > Vlado Barun, M.Sc., OCE, OCP, MCP > Sr. Database Architect/Manager, Database Engineering and Operations > Jewelry Television > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] > On Behalf Of Rich Jesse > Sent: Thursday, February 11, 2010 3:21 PM > To: oracle-l@xxxxxxxxxxxxx > Subject: How to best schedule jobs in another schema? > > Howdy, > > Revisiting my post from 2008: > > > //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 > > > -- > //www.freelists.org/webpage/oracle-l > > > -- > //www.freelists.org/webpage/oracle-l > > > -- Thanks & Regards, Taral Desai