The strange thing is that it worked before on a different systems.
BTW this is oracle 10.2.0.2.0
Any more ideas ...
I run it from the script
This is the way I get sid&serial num
select a.username,a.sid ,a.serial#
into :v_username,:v_sid,:v_serial_num
from v/$session a, v/$sqlarea b, v/$process c
where a.sql_address=b.address
and c.ADDR=a.PADDR
and c.SPID='$PID';
The strange thing is that it worked before on a different systems.
BTW this is oracle 10.2.0.2.0
Any more ideas ...
I run it from the script
This is the way I get sid&serial num
select a.username,a.sid ,a.serial#
into :v_username,:v_sid,:v_serial_num
from v/$session a, v/$sqlarea b, v/$process c
where a.sql_address=b.address
and c.ADDR=a.PADDR
and c.SPID='$PID';
Have you check connection type of session whether it is SHARED or DEDICATED in v$session.
I am definetly missing something
I have just run the same on the system it worked before and got the same result
1. login as sysem in db and run sql - select count(*) from dba_objects a, dba_objects b; just to run for a while
2. login as sysdba from different session
3. Get SID and SERIAL#
4. EXECUTE SYS.dbms_system.set_sql_trace_in_session (14, 470, TRUE);
PL/SQL procedure successfully completed.
5. Checked udump dir .. -nothing there
I wouldnt grant execution privilege on a system package such as this one to a user
Hi what i meant is not to grant execution privilege to user,is to grant execute to dbms_system to user,but by mistake i wrote like that,i corrected that.
Bookmarks