Formating output of a query for tracing

Question

Hi,
This is for 10.2.0.4 on IBM AIX 6.1
I need to generate traces for some sessions by setting the event 10046. I want to generate an SQL script for doing this which will be as follows.
SQL> oradebug setorapid 20
SQL> oradebug unlimit
SQL> oradebug Event 10046 trace name context forever, level 12
SQL> oradebug setorapid 100
SQL> oradebug unlimit
SQL> oradebug Event 10046 trace name context forever, level 12
SQL> oradebug setorapid 210
SQL> oradebug unlimit
SQL> oradebug Event 10046 trace name context forever, level 12 In this example, you see only three sessions but actually i have a lot of session and that is why i need to have a script.
I have following query which i can use to get the PID of a session which i would be tracing.
select a.pid
from v$process a, v$session b
where a.addr=b.paddr and a.username is not null ;Can anyone help to tell me how to generate a script for doing this. I tried to do following but formatting is not correct. I want above three trace commands in a sequence for every PID in my script.
select
'oradebug setorapid '||b.pid||'                                   '||
'oradebug unlimit                                                 '||
'oradebug Event 10046 trace name context forever, level 12        '||
'oradebug tracefile_name                                          '
from v$session a, v$process b where a.username is not null and a.paddr=b.addr order by b.spid;Salman

Answer 1

Hi, Salman,
You're writing one line of output per file.
If you want to write 4 lines per file, add newline characters (CHR(10) on my system; may be different on yours) between the lines, like this:
select    'oradebug setorapid ' || p.pid                     || CHR (10) ||
       'oradebug unlimit'                              || CHR (10) ||
       'oradebug Event 10046 trace name context forever, level 12'     || CHR (10) ||
       'oradebug tracefile_name                                          '
from        v$session      s,
       v$process      p
where        s.username      is not null
and        s.paddr     = p.addr
order by  p.spid;Why use meaningless table aliases like a and b?
Why not use something that reminds you which table is which, and helps prevent mistakes; something like p for v$process and s for v$session?