Skip to Main Content
  • Questions
  • User_dump_dest is inconsistent with the actual trace path

Breadcrumb

May 4th

Question and Answer

Chris Saxon

Thanks for the question.

Asked: November 10, 2018 - 10:36 am UTC

Last updated: November 12, 2018 - 11:02 am UTC

Version: 12c

Viewed 1000+ times

You Asked

If my question is too simple or meaningless, you can ignore it.

Why does my user_dump_dest parameter get a different path than the actual path?

I run this example:

EODA@muphy>select c.value || '/' || d.instance_name || '_ora_' || a.spid || '.trc' trace from V $process a, V $session b, V $parameter c, V $instance D where a.addr=b.paddr and b.audsid=userenv('session id') and c.name='user_dump_dest';


Track file path obtained:
D:\APP\ORCL\PRODUCT\12.1.0\DBHOME_1\RDBMS\TRACE/muphy_ora_3316.trc

Actual path:
D:\app\Orcl\diag\rdbms\muphy\muphy\trace\muphy_ora_3316.trc

and Chris said...

From 11g you should use v$diag_info to find the trace file locations:

select value from v$diag_info
where  name = 'Diag Trace';

VALUE                                                       
/ade/b/2757588126/oracle/log/diag/rdbms/db122/db122/trace 


And if you want to find the file name for your session, you can get it from v$process.tracefile:

select tracefile
from   v$process a, V$session b
where  a.addr     = b.paddr
and    b.audsid   =  sys_context ( 'USERENV', 'SESSIONID' );

TRACEFILE                                                                        
/ade/b/2757588126/oracle/log/diag/rdbms/db122/db122/trace/db122_s000_50940.trc

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

A reader, November 13, 2018 - 2:58 pm UTC

Thank you very much for helping me out. I already understand.

More to Explore

Administration

Need more information on Administration? Check out the Administrators guide for the Oracle Database