rjamya [mailto:rjamya@xxxxxxxxx] wrote: > is there a privilege issue here? Was thinking along those lines but do not see how. All the objects (tables and PL/SQL units) belong to the same schema. The DBMS_JOB is scheduled in that schema. The data is subject to FGAC though, but the schema is excempt from it (access policy). I have the PL/SQL stack logged at the time of the error (have a custom rolled applog API that logs errors and PL/SQL stacks) - this shows nothing unusual. The anon block (from DBMS_JOB) calling the main procedure and it failing. Anyway, have a hack in place to work around this (specified proc has now been disabled as the data it creates is currently not used by the web reporting front-end). Job runs fine without it. Oh well, if you run into a wall, spray grafitti on it. ;-) -- Billy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail and its contents are subject to the Telkom SA Limited e-mail legal notice available at http://www.telkom.co.za/TelkomEMailLegalNotice.PDF ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- //www.freelists.org/webpage/oracle-l