Trace Output

[jlcox]

I had a very long-running job that generated quite a bit of trace output. When I bring up the trace tab, PL/SQL Developer stops responding for a very long time then finally returns with an out-of-memory error message. Clicking the delete button on the trace tab generates several Oracle errors about tables not existing.

How can I delete the trace output?

 

[Marco Kalter]

delete sys.plsql_trace_events e
    where e.runid in (select r.runid from sys.plsql_trace_runs r where r.run_owner = user);
  delete sys.plsql_trace_runs r where r.run_owner = user;
  commit;

This will delete all trace runs of the currently connected user!

 

[jlcox]

Still not sure what's causing the errors. Clicking on the "delete" button on the trace tab generates these errors in a dialog box:

ORA-06550: line 4, column 14:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 4, column 3:
PL/SQL: SQL Statement ignored
ORA-06550: line 5, column 14:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 5, column 3:
PL/SQL: SQL Statement ignored

I've tried this on several different systems (development, test, production) and always get this message. I've run the profload.sql, proftab.sql, and tracetab.sql scripts as SYS.

 

[Marco Kalter]

Do you have any privileges on these tables?