Plsql_trace_events

Hi,
under sys I've runned the script tracetab.sql, which has creted the two tables : PLSQL_TRACE_EVENTS and PLSQL_TRACE_RUNS.
after that i grant the necessary privileges (under sys):
GRANT DELETE, INSERT, SELECT ON SYS.PLSQL_TRACE_EVENTS TO HR;
GRANT DELETE, INSERT, SELECT ON SYS.PLSQL_TRACE_RUNS TO HR;So, now i connect with HR to the same database and run the following:
select * from PLSQL_TRACE_EVENTSwich give me:
ORA-00942: table or view does not exist
and
select * from PLSQL_TRACE_RUNSwhich give me:
ORA-00942: table or view does not exist
while if i run the trace with the pl/sql developer, it works right, can some one tell me why?
thanks
Francesco

Hi,
i've run the script to create the table from sys account because in the script file there was written tu run it from sys account.
I do not know if i can run it from hr account and it works, right.
the script is tracetab.sql and it should be under ORACLE_HOME/rdbms/admin.
why yuo suggest to run the script from hr account?
thanks
Francesco

Similar Messages

DBMS_PROFILER tables empty

Hi,
I ran the following code to profile my code:
<h6>
DECLARE
l_result BINARY_INTEGER;
retcode number;
errbuf varchar2(500);
BEGIN
l_result := DBMS_PROFILER.start_profiler(run_comment => 'xxotc_cust_class_stage_t: ' || SYSDATE);
my_pkg.main ( errbuf
,retcode
,'/usr/tmp'
,'small_file.txt'
l_result := DBMS_PROFILER.stop_profiler;
END;
</h6>
After the program completes, when I query the profiler tables plsql_profiler_runs and plsql_profiler_units I do not find any data.
Is there anything wrong that I am doing?
Thanks.

I am not sure what all tables, sequences are required, but here is what I found on my system:
SELECT owner, object_name, object_type, status
FROM dba_objects
WHERE object_name LIKE 'PLSQL%'
ORDER BY 1, 3
Row#     OWNER     OBJECT_NAME     OBJECT_TYPE     STATUS
1     APPS     PLSQL_PROFILER_UNITS     SYNONYM     VALID
2     APPS     PLSQL_PROFILER_RUNS     SYNONYM     VALID
3     APPS     PLSQL_PROFILER_RUNNUMBER     SYNONYM     VALID
4     APPS     PLSQL_PROFILER_DATA     SYNONYM     VALID
5     SYS     PLSQL_PROFILER_RUNNUMBER     SEQUENCE     VALID
6     SYS     PLSQL_TRACE_RUNNUMBER     SEQUENCE     VALID
7     SYS     PLSQL_TRACE_RUNS     TABLE     VALID
8     SYS     PLSQL_PROFILER_UNITS     TABLE     VALID
9     SYS     PLSQL_PROFILER_RUNS     TABLE     VALID
10     SYS     PLSQL_PROFILER_DATA     TABLE     VALID
11     SYS     PLSQL_TRACE_EVENTS     TABLE     VALID

How to debug hanging DML job

How I have these dml jobs that hangs I have use
ALTER SESSION set events '10046 trace name context forever,level 12';
but it looks like o trace is being generated as it is still running and on v$session it says one is waiting on configuraton and one is waiting on concurrency ?
How do I debug this kind of hanging situation?

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - ProductionIt is weired that one of the session is waiting on a TM lock on PLSQL_TRACE_EVENTS and PLSQL_TRACE_RUNS
and the event is log file switch completion
ANd it is actually hanging at inserting into these two tables.
Would it be just an oracle_bug ?
I am thinking killing the sessions and running it without pl/sql trace and see what happens ?

Docs of Trace Tables of DBMS_TRACE

Dear all,
where can find documentation about tables of DBMS_TRACE collected data? TRACETAB.SQL contains the script that creates the tables like sys.plsql_trace_runs and sys.plsql_trace_events, but some of the columns are cryptic. For example event_kind is numbers, which I cannot decode their meanings. Could anybody point me out to a reference of it?
Best regards,
Val

The DBMS_TRACE package spec describes the event types, e.g.
plsql_trace_start        constant integer := 38; -- Start tracing
plsql_trace_stop         constant integer := 39; -- Finish tracing
plsql_trace_set_flags    constant integer := 40; -- Change trace options
plsql_trace_pause        constant integer := 41; -- Tracing paused
plsql_trace_resume       constant integer := 42; -- Tracing resumed
plsql_trace_enter_vm     constant integer := 43; -- New PL/SQL VM entered                                           /* Entering the VM */
plsql_trace_exit_vm      constant integer := 44; -- PL/SQL VM exited*
plsql_trace_begin_call   constant integer := 45; -- Calling normal routine
plsql_trace_elab_spec    constant integer := 46; -- Calling package spec                                     /* Calling package spec*/
plsql_trace_elab_body    constant integer := 47; -- Calling package body
plsql_trace_icd          constant integer := 48; -- Call to internal PL/SQL routine
plsql_trace_rpc          constant integer := 49; -- Remote procedure call
plsql_trace_end_call     constant integer := 50; -- Returning from a call
plsql_trace_new_line     constant integer := 51; -- Line number changed
plsql_trace_excp_raised constant integer := 52; -- Exception raised
plsql_trace_excp_handled constant integer := 53; -- Exception handler
plsql_trace_sql          constant integer := 54; -- SQL statement
plsql_trace_bind         constant integer := 55; -- Bind parameters
plsql_trace_user         constant integer := 56; -- User requested record
plsql_trace_nodebug      constant integer := 57; -- Some events skipped
                                                   -- because module compiled
                                                   -- NODEBUG
plsql_trace_excp_unhandled constant integer := 58; -- Exception unhandled at
                                                   -- top level

Plsql_trace_events

Similar Messages

Maybe you are looking for