SQL_TRACE Output Location

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Alan Cobban
    #1

    SQL_TRACE Output Location

    Hi,

    I'm currently trying to run a SQL trace for a SQL*PLUS session and run
    the resulting output file through tkprof.

    Using the command -

    ALTER SESSION SET SQL_TRACE = TRUE;

    I get a trace file on the UNIX server in the udump directory. The
    problem is that the permissions on this file are 750 for the oracle
    user (dba group). As I do not have access to the oracle user or a
    user which is part of the dba group I cannot view the file.

    Can these files be sent to another location (such as the client PC's
    C: drive) or to the same location with different permissions without
    changing Oracle's database parameters (such as _TRACE_FILES_PU BLIC or
    USER_DUMP_DEST) ?

    Thanks,

    Alan.
    Tags: None
    • sybrandb@yahoo.com
      #2
      Re: SQL_TRACE Output Location

      alancobban@yaho o.co.uk (Alan Cobban) wrote in message news:<a2b728db. 0312040724.111f 6f8b@posting.go ogle.com>...
      Hi,
      >
      I'm currently trying to run a SQL trace for a SQL*PLUS session and run
      the resulting output file through tkprof.
      >
      Using the command -
      >
      ALTER SESSION SET SQL_TRACE = TRUE;
      >
      I get a trace file on the UNIX server in the udump directory. The
      problem is that the permissions on this file are 750 for the oracle
      user (dba group). As I do not have access to the oracle user or a
      user which is part of the dba group I cannot view the file.
      >
      Can these files be sent to another location (such as the client PC's
      C: drive) or to the same location with different permissions without
      changing Oracle's database parameters (such as _TRACE_FILES_PU BLIC or
      USER_DUMP_DEST) ?
      >
      Thanks,
      >
      Alan.

      Obviously the database server won't have access to your PC. As you
      don't want to change the _trace_files_pu blic parameter, I guess you
      are stuck.

      Sybrand Bakker
      Senior Oracle DBA

        Comment

        • Martin Burbridge
          #3
          Re: SQL_TRACE Output Location

          alancobban@yaho o.co.uk (Alan Cobban) wrote in message news:<a2b728db. 0312040724.111f 6f8b@posting.go ogle.com>...
          Hi,
          >
          I'm currently trying to run a SQL trace for a SQL*PLUS session and run
          the resulting output file through tkprof.
          >
          Using the command -
          >
          ALTER SESSION SET SQL_TRACE = TRUE;
          >
          I get a trace file on the UNIX server in the udump directory. The
          problem is that the permissions on this file are 750 for the oracle
          user (dba group). As I do not have access to the oracle user or a
          user which is part of the dba group I cannot view the file.
          >
          Can these files be sent to another location (such as the client PC's
          C: drive) or to the same location with different permissions without
          changing Oracle's database parameters (such as _TRACE_FILES_PU BLIC or
          USER_DUMP_DEST) ?
          Tom Kyte has a solution on his web site

          The page is not found
          http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:7115831027951



          --
          Martin Burbridge

          pobox 002 email is full of spam and never read

            Comment

            Previous template Next
            Working...