Or you could just grant the underlying privileges... The only thing I've run into so far that really *does* require a DBA account (and maybe other people have run into others) are jobs which require the truncation of tables from a schema which does not own those tables... seems you just can't grant that right. Well, maybe you can now, that *was* years ago... Still... HTH, Bambi. ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of SHEEHAN, JEREMY Sent: Friday, November 14, 2008 10:06 AM To: John.Fedock@xxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx Subject: RE: running UTLRP.sql Why not just create a job that runs this periodically? You can run it every 3 hours and have it run by a generic sysdba account. Jeremy From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Fedock, John (KAM.RIC) Sent: Friday, November 14, 2008 11:01 AM To: oracle-l@xxxxxxxxxxxxx Subject: running UTLRP.sql For 10.2.0.3, HP-UX, the header in the script clearly states you must be a user with SYSBDA privs to run. The doco states that a SYSDBA user can also: * Perform STARTUP and SHUTDOWN operations * ALTER DATABASE: open, mount, back up, or change character set * CREATE DATABASE * DROP DATABASE * CREATE SPFILE * ALTER DATABASE ARCHIVELOG * ALTER DATABASE RECOVER * Includes the RESTRICTED SESSION privilege After code changes, we run utlrp.sql to recompile invalidated objects. We would like some users to run this, but not any with a SYSDBA privs. Any ideas? Maybe a Unix script that they can execute that will run and do this? Just looking for fresh ideas. TIA, John Fedock "K" Line America, ISD Department