You can capture an errorstack trace for the session when this occurs, via something similar to: alter session set events '1031 trace name errorstack level 3'; This *should* show you exactly what object it was attempting to access. I'd suggest implementing it via a logon trigger, so that you can target the affected sessions as specifically as possible. You probably want to set * tracefile_identifier* to something easily identified as well. On Tue, Nov 6, 2012 at 8:20 AM, Michael Dinh <mdinh235@xxxxxxxxx> wrote: > Hello, > I have been experiencing ORA-01031 insufficient privileges from application > using Weblogic (WLS) connected as the schema owner. > > Database is 11.2.0.3 the SQL itself does not fail when execute from > SQL*Plus and only fails when execute from the application using WLS. > > Restarting the database resolved the issue one time but it's reoccurring. > Any help to identify the issue is greatly appreciated and I will be > creating SR as well. > -- //www.freelists.org/webpage/oracle-l