Naming trace file

I have generated many trace files for analysis using tkprof. However, I have a difficulty in locating the exact trace file (.trc) from 100s of trace files. Naming my trace file will save time. Is there a way to name the trace file when I start tracing? (i.e. when I set sql_trace to true).
thanks
Srinidhi Rao

You can use tracefile_identifier feature:
ALTER SESSION SET TRACEFILE_IDENTIFIER = 'traceid';When this parameter value is set, the trace file name has the following format:
sid_ora_pid_traceid.trc
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

Similar Messages

  • Trace File / EJB / dbms_java.grant_permission

    I am trying to deploy a simple Hello World EJB onto Oracle 8.1.7 using Jdeveloper 3.2.
    I get the following error when deploying :
    Loading EJB Jar file and Comm Stubs Jar file...
    error: loadJava has failed to load some classes; Please check trace file!
    *** Errors occurred while deploying the EJB to 8i JVM ***
    *** Deployment completed ***
    My trace file has the following in it :
    *** 2001-05-03 17:33:29.531
    *** SESSION ID:(14.2397) 2001-05-03 17:33:29.531
    Error while creating class oracle/aurora/jndi/sess_iiop/ActivationException
    ORA-29545: badly formed class: User has attempted to load a class (oracle.aurora.jndi.sess_iiop.ActivationException) into a restricted package. Permission can be granted using dbms_java.grant_permission(<user>, LoadClassInPackage...
    could not find oracle/aurora/jndi/sess_iiop/ActivationException in WILLOW2K
    could not find oracle/aurora/jndi/sess_iiop/ActivationException in WILLOW2K
    ORA-29534: referenced object WILLOW2K.javax/naming/InitialContext could not be resolved
    ORA-29545: badly formed class: at offset 128 of packagessb.ssbClient2.main expecting a class-javax.naming.NamingException but encountered a class-oracle.aurora.jndi.sess_iiop.ActivationException.
    ORA-29545: badly formed class: at offset 4 of javax.naming.spi.NamingManager.createObjectFromFactories expecting a class-javax.naming.Context but encountered a class-javax.naming.Context.
    at offset 4 of javax.naming.spi.NamingManager.getStateToBind expecting a class-javax.naming.Context but encountered a class-javax.naming.Context.
    at offset 38 of javax.naming.spi.NamingManager.getStateToBind expecting a class-javax.naming.Context but encountered a class-javax.naming.Context.
    at offset 38 of javax.naming.spi.NamingManager.getStateToBind expecting a class-javax.naming.Name but encountered a class-javax.naming.Name.
    at offset 37 of javax.naming.spi.NamingManager.getURLObject expecting a class-javax.naming.Context but encountered a class-javax.naming.Context.
    ORA-29534: referenced object WILLOW2K.javax/naming/spi/NamingManager could not be resolved
    ORA-29534: referenced object WILLOW2K.javax/naming/spi/NamingManager could not be resolved
    Error while resolving class oracle/aurora/jndi/sess_iiop/ActivationException
    ORA-04043: object /889d46b7_ActivationException does not exist
    I think the error stems from the line :
    (oracle.aurora.jndi.sess_iiop.ActivationException) into a restricted package. Permission can be granted using dbms_java.grant_permission(<user>, LoadClassInPackage...
    Doe anyone know how I can grant the user permission to the above library. How exactly is it done using Oracle 8.1.7 ?
    null

    did you read the install notes (install.htm) or release notes(readme.htm) files for known issues ?
    see the release notes for the following :
    Problems Deploying Business Components for Java Libraries in Different Schema (1095107)
    Attempting to deploy a Business Components for Java library in a different schema from the JDeveloper IDE generates the following error:
    Generating Jar File...done
    Loading EJB Jar file and Comm Stubs Jar file...
    error: loadJava has failed to load some classes; Please check trace file!
    *** Errors occurred while deploying the EJB to 8i JVM ***

  • Java Plug-In Trace File names

    According to this URL, http://java.sun.com/javase/6/docs/technotes/guides/deployment/deployment-guide/tracing_logging.html , the plug-in trace file should be named as indicated:
    The names of the trace and log files are
    plugin<modified version number>.trace
    plugin<modified version number>.log
    where the <modified version number> includes the major, minor and patch version numbers; e.g., plugin142_06.trace or plugin150.log
    But this is not what we're seeing. We see the trace and log files, but here are their names:
    plugin28434.trace
    plugin28435.log
    We are using JRE 1.6.10 on Windows.
    We also have the following questions:
    1. Is there any way to set the maximum file size for a trace file?
    2. Is there a way to set how many backups of the trace file are used?
    3. Is there a way to set the rolling behavior of the trace files? Right now, old trace files are re-written completely at random.

    Any one has found any solutions ?

  • Trace file with different name is alert log file.

    I am strange today
    i found a trace file generated in alert log file with name
    /bdump/stlbas_cjq0_1880.trc:
    but when i am trying to find out in bdump folder i cannot found
    any file with this named. instead i found /bdump/stlbas_cjq0_1853.trc
    is there any possibility of being this scenario ?
    database version:- 10.2.0.4
    Os:- sun solaries spark 64 bits
    Regards
    Halim

    The trace file has been removed/deleted from an OS user. I think you should verify that with OS logs.
    Thanks

  • Naming R3d Files in Premier + Timeline Settings for 4K plus archival HD and SD footage

    We recently made the switch over to Premier and are beginning post on our first 4k 16x9 project.  Very exciting to be editing with the raw r3d files, our one concern is that naming the files (it is a feature doc with a lot of footage) in premier will break the link to the orginal file once we export via xml to resolve for the online as well as to go back to color correct in Red CineX.  Is this correct or comepletely misguided.  My gut says that naming the files in premier is just adding to the metadata associated with the clip and the export should be fine.  Can you please set me straight?
    We are also going to be adding archival footage from 1080 to SD with varied frame rates.  The bulk of the footage is shot at 4k 16x9 at 23.98.  What would you recommend our timeline setting be set at? Ultimately we will be exporting at 1080, but ideally want to keep the timeline as high res as possible for future export at higher resolutions.
    Thank you for your help and guidance!
    Best,
    Travis Rummel
    felt soul media

    I'm afraid there probably isn't a good way to scale SD to 4K...
    unless it originated on film and you can go back to transfer.
    Magic Bullet Instant HD works pretty well upscaling SD to HD.
    when you say renamiong can "sometimes make tracing the original media file on disk more difficult"
    I am referring to file management on disk as it relates to the Project.
    For example if you load all of your media and change the file names,
    then discover that there is something quirky with a particular file... it will
    make it more difficult to trace on disk for evaluation.
    It will not affect the media reference in .xml export at all.

  • Name of WP trace file

    Hi all,
    In my system I can see that my WP trace files are named like dev_w + number, but I have found function module GWY_READ_WP_FILE which is using hardcoded value dev_wp + number. My question is, is it an error in this FM or have these files in past different name?
    Best regards
    Marcin Cholewczuk

    Hi Alexander,
    Thanks for answer, but it's still strange because I saw that at least one SAP report for monitoring was using this FM. It's a shame that I don't have access to SAP marketplace anymore :/
    Best regards
    Marcin Cholewczuk

  • [10g - XE] Why is my disk full of trace files?

    Just in case there's another silly person like me out there who encounters this problem...
    I have XE 10g installed on my local machine (Windows XP), as my own personal test environment.
    My computer was acting really weird yesterday, then today I got an error while using Excel that my disk was full.... and after some investigating, I discovered that I have 39 GB (gasp!) of trace files! These are all located in the directory C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\trace
    ...and some of them are quite large (obviously, since I have 39 GB of them...); one of them by itself is 2 GB.
    Almost all of the files are named like: sqlnet_trace.txt_3132_1.trc And, for example, I already have 5 trace files from today, totaling 15 MB.
    I vaguely recalled setting my trace level to 16 or SUPPORT a LONG time ago, and funny thing, I couldn't remember changing it back to OFF.
    So, if you've been silly like me, check your sqlnet.ora file, and set TRACE_LEVEL_CLIENT=OFF

    Thanks for the tip. I checked listener.ora, and it doesn't appear that any trace files are enabled there. I don't know what Net manager is.
    At least in this case, the server/database is just my personal PC, so the only person it impacted was me. It took 7 months for the trace files to grow to that size with just me using the database, so I can only imagine what it would do to a database in an actual environment.

  • Indentifying trace file name?

    I'm looking for a way to "know" the trace file name of a session being traced from within PL/SQL.
    For instance, if I turn trace on during the execution of a PL/SQL block using DBMS_MONITOR, is there a way to KNOW the name of the trace file that gets generated.
    Doug

    While the SQL statement mentioned here works in a lot of cases, it is "concocted" at best.
    I have been told that HPUX and Solaris versions of Oracle have different naming standards for trace files that don't conform strictly to the format that the SQL statement uses.
    If at all possible I want to KNOW the name of the file, not assume it.
    My initial thought was that there might be a "DBMS*" package that might provide such information, but I have not found anything yet.
    Anyone know of something that might provide this?
    Doug

  • Generating Trace file for ODI Sessions

    ODI Gurus
    am new to ODI, for one of our integration project am using ODI for transforming data from Source to Target Instance.
    Oracle Database is installed on both Source and Target instances. Is there a way to generate Database Trace files for ODI sessions triggered.
    If yes can you provide the steps to enable/disable database trace for ODI sessions.
    Regards
    Uma Shankar

    Hi Uma Shankar,
    My assumptions:
    1.) You want to selectively enable Oracle tracing when only the ODI scenarios are executed and not otherwise.
    If that is the case then you will have to add some external steps comprising of OS commands and variables that will control if those steps are to be executed or not. These steps will invoke the OS commands to start Oracle tracing.
    2.) You know the steps to create a package and know how to use Interfaces and other ODI utilities in the flow of the package.
    3.) You know how to create and execute scenarios
    Steps to Selectively enable tracing.
    1.) Add a variable named V_START_TRACE to the package. This variable will be passed a value from scenario which will determine if you want to enable to trace or not. This variable type is EVALUATE and can have 2 values - TRUE or FALSE. You will have to check for the condition and depending on the condition you will take a path forward.
    2.) Add 2 OS commands to the package - OS_START_TRACE and OS_END_TRACE
    3.) Create 2 shell scripts (or bat files) - odi_start_trace.sh and odi_end_trace.sh with the following commands:
    odi_start_trace.sh :-
    sqlplus session - ALTER SYSTEM SET trace_enabled = TRUE;
    odi_end_trace.sh :-
    sqlplus session - ALTER SYSTEM SET trace_enabled = FALSE;
    You need to invoke SQLPLUS sessions from the above shell scripts to enable/disable the oracle level tracing.
    4.) Add the above shell scripts to the OS commands created in Step 2.
    5.) Join the steps in the following order in the package :
    V_START_TRACE (OK) ->OS_START_TRACE (OK) -> <<+Your Actual Integration Code+>>(OK) -> OS_END_TRACE
    V_START_TRACE (KO) -> <<+Your Actual Integration Code+>>(OK)
    The above KO variable statement doesnt start the trace if the evaluated value doesnt = TRUE. So this will let you do a selective trace.
    6.) Create the scenario from the package and execute the scenario by passing it a value "TRUE" for variable V_START_TRACE.
    Check the startscen.sh syntax, something like:
    *>startscen.sh ... "GLOBAL.V_START_TRACE=TRUE"*
    The above is a general solution for enabling trace for any RDBMS
    If you need any more information, feel free to ping back.

  • How to know date and time information from Trace File defaultTrace.X.trc?

    Hi, all.
      i'm using EP 6.0 SP9 patch 1.
      As you know, default trace is written in the <SID>\JC00\j2ee\cluster\server0\log\defaultTrace.X.trc.
      By using the default trace formatter, it shows like the following sample messages.
    #1.5#0011110E7B2000590000000100000A100003EC71562E6EBC#1104396451585#com.sap.jms.server.ServerClientAdapter##com.sap.jms.server.ServerClientAdapter#Guest#18####716257115a3f11d9b73b0011110e7b20#SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#/Applications/JMS#Plain###JMS internal error at ServerClientAdapter! JMS Service is not started!#
      My questions are
      1. how do we retrieve the date and time information from the above message? It seems that this message has date and time info because LogViewer shows the date and time based on the above message.
      2. how do we change the above date format to easier one
    like "YYYY:MM:DD:hh:mm:ss"? i know that it can be configured from the Visual Admin --> Services --> Log Configurator but i don't know the exact place for the trace file.
      Thanks.

    Hi Sejoon,
    I use the standalone Logviewer to read the log files. Works great.
    "If you have an SAP Web Application Server Java 6.20 or below you may also get a standalone_logviewer.zip file at the SAP Service Marketplace at service.sap.com/download &#8594; SAP NetWeaver &#8594; Release ‘04. In this case JDK version 1.3 or higher must be installed on the system. The java version must be same on the server and the client.
    In the SAP Web AS Java 6.30 installation a folder named logviewer_standalone can be found under: <path Of J2EE installation>/<SysID>/JC<nr>/j2ee/admin/logviewer_standalone. Verify that the batch file logviewer.bat is installed in the directory logviewer-standalone.
    (source -> http://help.sap.com/saphelp_nw04/helpdata/en/e4/540c404a435509e10000000a1550b0/frameset.htm)
    Best wishes,
    Noel

  • Tkprof could not open trace file

    Hi,
    I am trying to run tkprof on a big file and get the following error message:
    -rw-r--r-- 1 oracle dba 6983899698 Feb 19 13:59 ora_27073_qa2_10046.trc
    /software/oracle/admin/qa/udump >tkprof ora_27073_qa2_10046.trc tk1.prf
    TKPROF: Release 8.1.7.4.0 - Production on Tue Feb 19 21:16:16 2008
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    could not open trace file ora_27073_qa2_10046.trc
    Please note that i cant open it also in vi. its gets too big.
    Any Suggession ?
    Thanks

    Have a CSI?
    Subject:TKPROF returns "could not open trace file"
    Doc ID: Note:300439.1
    Cause
    TKPROF has a 2Gb filesize limit on the input tracefile.
    Fix
    To implement the solution, please execute the following steps:
    1. Assume "tracefile" is the name of the 3.5Gb raw tracefile.
    2. We will need two Unix sessions, both as "oracle",
    in the same directory holding the "tracefile".
    3. Session A:
    unix$ mkfifo mypipe
    unix$ tkprof mypipe reportfile options
    --> this should show the TKPROF banner and will then wait
    without returning a Unix prompt
    4. Session B:
    unix$ cat tracefile > mypipe
    --> this will feed the tracefile into the named pipe
    5. The result should be that TKPROF is able to process the tracefile via the named pipe and write the reportfile.
    Note: the above solution can only be carried out on a Unix system. If you encounter this problem e.g. on a Windows system, you could transfer the problematic file onto a Unix server and perform the workaround on it, as TKPROF works with tracefiles regardless of the originating platform.

  • Help to interpret trace file

    Hi,
    Can someone please tell me what is the meaning of stack number in the file generated ny dbms_trace. how to interpret the trace file.
    Thanks in advance.
    Mathew

    Hi,
    The cause of an ORA-1555 is quite simple :
    U start a long transaction (named T1) at time t1. Ur transaction T1 made lots of things such as
    insert/update/delete, ...
    At time t1, ur transaction T1 update a block named b1. This block is copied in the rolback segment with a "non commited" status in the block header. This "before image" of ur block cannot be deleted from the RBS cause of his "non committed" status.
    Ur transaction T1 now commit the modifications => the header of the block b1 in the RBS is upadted with the status "commited". Once the block has the "commited" status, he can be removed from the RBS and Oracle may remove this one if he needs some space in the RBS for some other before image.
    At time t2, another transaction (named T2) start and update some rows so T2 will need some space in the RBS and then erase the version of the block b1 (in the RBS).
    At time t67 (some time after), ur transaction T1 (the long one) need to read again the block b1. But as T1 has been started at time t1, Oracle will search for an image of the block b1 at time t1 (to ensure read consistency). But, as transaction T2 erased this before image of the block b1, Oracle cant find it and send u the error ORA-01555...
    To avoid ORA-015[i]Long postings are being truncated to ~1 kB at this time.

  • Not able to get the actual plan from trace file

    Hi all
    I have a Db package and want to get actual execution plan of all the statements in that pakcage it does provides the plan for System's statements but does not displays the plan for Sql statements
    DB version 9.2.0 using the following sequence of insructions
    set timing on
    set serveroutput on
    alter session set events '10046 trace name context forever ,level 12';
    begin
    run_service.collect_data(sysdate);
    end;
    alter session set sql_trace=false;
    exit; ---exit from Sql
    now look at the output
    select distinct obj#,containerobj#,pflags,xpflags,mflags
    from
    sum$, suminline$ where sumobj#=obj# and inline#=:1
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.00 0 0 0 0
    Execute 1 0.00 0.00 0 0 0 0
    Fetch 1 0.00 0.00 1 1 0 0
    total 3 0.00 0.00 1 1 0 0
    Misses in library cache during parse: 0
    Optimizer goal: CHOOSE
    Parsing user id: SYS (recursive depth: 2)
    Rows Row Source Operation
    0 SORT UNIQUE
    0 NESTED LOOPS
    0 TABLE ACCESS BY INDEX ROWID SUMINLINE$
    0 INDEX RANGE SCAN I_SUMINLINE$_2 (object id 1614116)
    0 TABLE ACCESS BY INDEX ROWID SUM$
    0 INDEX UNIQUE SCAN I_SUM$_1 (object id 319)
    Elapsed times include waiting on following events:
    Event waited on Times Max. Wait Total Waited
    ---------------------------------------- Waited ---------- ------------
    db file sequential read 1 0.00 0.00
    SELECT SEQ_NUM, S_DATE, S_TIME, CSTATUS, G_SERVICE,
    B_REFERENCE, V_REFERENCE, M_PRIORITY
    FROM GL_HIST
    ORDER BY S_DATE DESC, S_TIME DESC
    call count cpu elapsed disk query current rows
    Parse 1 0.01 0.01 0 0 0 0
    Execute 2819 0.37 0.32 0 0 0 0
    Fetch 2819 2.50 20.47 2786 20164 0 2819
    total 5639 2.88 20.81 2786 20164 0 2819
    Misses in library cache during parse: 1
    Optimizer goal: CHOOSE
    Parsing user id: 15550 (recursive depth: 1)
    Elapsed times include waiting on following events:
    Event waited on Times Max. Wait Total Waited
    ---------------------------------------- Waited ---------- ------------
    db file sequential read 2786 0.05 18.19
    latch free 4 0.04 0.06
    UPDATE G_ORIG SET G_SERVICE = :B1
    WHERE
    SEQ_NUM = :B5 AND S_DATE = :B4 AND S_TIME = :B3 AND
    C_STATUS = :B2 AND NVL(G_SERVICE, '+') <> NVL(:B1, '+')
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.03 0 0 0 0
    Execute 3731 0.74 0.99 261 18712 119 54
    Fetch 0 0.00 0.00 0 0 0 0
    total 3732 0.74 1.02 261 18712 119 54
    Misses in library cache during parse: 1
    Optimizer goal: CHOOSE
    Parsing user id: 15550 (recursive depth: 1)
    Elapsed times include waiting on following events:
    Event waited on Times Max. Wait Total Waited
    ---------------------------------------- Waited ---------- ------------
    db file sequential read 261 0.01 0.19
    latch free 9 0.01 0.04
    COMMIT

    Remove the line alter session set sql_trace=false and just exit/disconnect. The explain plain is contained in the STAT lines in the trace file and are only written when the cursor closes. If you turn off tracing before the cursor closes the STAT lines will not get written.

  • How to create the trace file using run_report_object at runtime

    Dear All
    using :
    Oracel Application Server 10g
    Oracle Database 11g
    Windows XP/sp3
    I'm using run_report_object to call a report inside the form. THis report is running OK from reports builder, however it's too slow when run from Application server.
    How Can I create a trace file (at runtime) that contains the time spent in sql and formating the layout of the report ??
    Here is My code :
    repid := find_report_object('report5');
    SET_REPORT_OBJECT_PROPERTY(repid,REPORT_FILENAME,'INVOICE.REP');
    v_url :='paramform=no';
    v_url := v_url||' FROM_NO=' || :PRINT_BLOCK.FROM_NO ;
    v_url := v_url ||' TO_NO=' || :PRINT_BLOCK.TO_NO ||' FROM_DATE=' || v_from_date ||' TO_DATE='|| v_to_date ||' NO_DATE=' ;
    v_url := v_url ||:PRINT_BLOCK.NO_DATE||' IDENT=' ||:PRINT_BLOCK.IDENT_NO||' REPORT_HEADING='''||V_REPORT_HEADING||'''' ;
    v_url := v_url||' COMPANY_NO='||:global.company_no;
    SET_REPORT_OBJECT_PROPERTY(repid,REPORT_OTHER,v_url);
    SET_REPORT_OBJECT_PROPERTY(repid,REPORT_SERVER,:GLOBAL.INV_REPORT_SERVER_NAME);
    SET_REPORT_OBJECT_PROPERTY(repid,REPORT_DESFORMAT,'pdf');
    v_rep := RUN_REPORT_OBJECT(repid);
    IF rep_status = 'FINISHED' THEN
    V1:='/reports/rwservlet/getjobid'||substr(v_rep,instr(v_rep,'_',-1)+1);
    WEB.SHOW_DOCUMENT('/reports/rwservlet/getjobid'||substr(v_rep,instr(v_rep,'_',-1)+1)||'?server='||REPORT_SERVER_NAME,'_blank');
    END IF;
    Thanks a lot

    Slow running reports often are not the result of a flawed report, but rather a flawed configuration. For example:
    1. If you call your reports (from Forms) via the default or inProcess Reports Server, often because startup time is slow, it will appear that it took too long for the report to be delievered. Using a stand-alone Rep Server is the preferred way to do this.
    2. If your Forms application makes numerous calls to RRO (RUN_REPORT_OBJECT), this can tend to result in what might appear as a memory leak (although it is not). The result is delayed processing because of the excessive memory use. This problem has been overcome in Forms/Reports 11 by the use of JVM pooling. However in v10 enabling "6i compatibility" mode is the way to overcome the issue. See Note 266073.1
    3. If the report runs fine from the Builder and it is connecting to the same db as when you run it from App Server, the issue is unlikely a db problem. However, if you want to look anyway, enable sqlnet tracing.
    4. To enable Reports tracing and investigate other tuning options, refer to the Reports 10 documentation:
    http://docs.oracle.com/cd/B14099_11/bi.1012/b14048/pbr_tune.htm
    Almost forgot to mentioned this one....
    If you are using a v11 db with App Server 10, you will probably want to consider reviewing Note 1099035.1 as it discusses an issue related to performance with such a configuration.
    Edited by: Michael Ferrante on Apr 10, 2012 8:49 AM

  • Unable to generate trace file

    Hi,
    I have written the stored procedure for starting sql trace on a given session for say n number of seconds.
    create or replace procedure start_trace
    v_sid in number,
    v_serial# in number,
    seconds in number)
    IS
    v_user varchar2 (32);
    duration number;
    dump_dest varchar2 (200);
    db_name varchar2 (32);
    no_session_found exception;
    stmt varchar2(100);
    stmt1 varchar2(100);
    BEGIN
    begin
    select username into v_user
    from v$session
    where sid= v_sid and
    serial# = v_serial#;
    exception
    when NO_DATA_FOUND then
    raise no_session_found;
    end;
    dbms_output.put_line('Tracing Started for User: '|| v_user);
    dbms_output.put_line('Tracing Start Time: '|| TO_CHAR(SYSDATE, 'MM-DD-YYYY HH24:MI:SS'));
    dbms_system.set_sql_trace_in_session(v_sid,v_serial#,true);
    if seconds is null then
    duration := 60;
    else
    duration := seconds;
    end if;
    dbms_lock.sleep(duration);
    dbms_system.set_sql_trace_in_session(v_sid,v_serial#,false);
    dbms_output.put_line ('Tracing Stop Time: '|| TO_CHAR(SYSDATE, 'MM-DD-YYYY HH24:MI:SS'));
    select value into dump_dest
    from v$parameter
    where name = 'user_dump_dest';
    dbms_output.put_line('Trace Directory: ' || dump_dest);
    exception
    when no_session_found then
    dbms_output.put_line('No session found for sid and serial# specified');
    END start_trace;
    The above procedure compiles successfully and when I call it from sql prompt it gives me the message that the pl/sql procedure was completed successfully and all put_line statements are displayed.
    Real problem comes when I check udump for the trace file. I can not find it there. It seems all the statements in the procedure are executed successfully except dbms_system.set_sql_trace_in_session(v_sid,v_serial#,true) and dbms_system.set_sql_trace_in_session(v_sid,v_serial#,false) for some strange reasons.
    Any help will be appreciated.
    Thanks.

    Thanks for the reply.
    I do not get any error message. The following is the output:
    SQL> exec start_trace(118,6243,30);
    Tracing Started for User: SVCWRK
    Tracing Start Time: 09-26-2011 16:28:29
    Tracing Stop Time: 09-26-2011 16:28:59
    Trace Directory: /orasoft/app/oracle/admin/testsvcb/udump
    PL/SQL procedure successfully completed.
    But the trace file is not generated.
    I am using Oracle 10.2.0.4.0.
    Will try using DBMS_MONITOR.
    Thanks again.

Maybe you are looking for

  • Is there a street view on maps?

    Is there a street view on maps?

  • Windows doesn't see my iPod, nor does iTunes

    The iPod 3d is just dead, and it doesn't appear on My Computer or on iTunes, and it won't even turn on. I have had it charged for a long time, both on the computer and at an electric outlet. I get an error message on iTunes that says it detects an iP

  • How to keep aggregated link interface across live upgrade partitions?

    I'm running Solaris 10 11/06 s10x_u3wos_10 X86 on a 2100. I have nge1 and nge0 in an aggregated link interface aggr1. I have the /etc/hostname.aggr1 file, and aggr1 comes up fine on reboots. I also have a Live Upgrade partition, and it doesn't come u

  • Excise transaction type-Regarding

    hi i want to update RG23C register, when i post purchase order (me21n), it automatically taking GRPO Excise tran.type, as per my knowledge it should take CAPE. i maintained GL accounts for CAPE. can anybody suggest me how to post the capital goods, h

  • Flash CS6 and iOS Publishing

    Hi. Has anyone had any experience with iOS publishing using Cs6? What are the difficulties in this? Anything you can explain would be nice as i am a student and need to think before i spend $100 on a license. Thank you.