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

Similar Messages

Changing trace file name giving odd results - 10.2.0.2

Hello,
I'm trying to run a trace on a particular session. Using this:
execute dbms_monitor.session_trace_enable(122, 58)
It creates a tracefile in udump just fine. I turn tracing off:
execute dbms_monitor.session_trace_disable(122, 58)
Then the trace usually catches the next sql statement after I issued the disable and I've got a complete trace file.
If I use the statement:
alter session set tracefile_identifier = 'TEST';
With or without quotes, what ends up happening is the tracefile is created with TEST tacked onto the end but what's inside the file is the full path to the file itself, no trace. The previous trace file before setting the identifier then gets all the trace output. This is on Red Hat. After this the only way to get tracing to work again is to close both sessions and start over.
Am I forgetting to set another parameter when doing this? The litteral set of steps is:
-open session 1
-open session 2
-session 1 run alter session set tracefile_identifier = 'TEST';
-session 1 run execute dbms_monitor.session_trace_enable(122, 58)
-session 2 run some sql
-session 1 run execute dbms_monitor.session_trace_disable(122, 58)
-session 2 run another sql statement
-check the udump for the trace file
Now the ultimate goal here is to be able to tag a trace with a name so I can trace a specific session (made by an application) and then find it later in udump. If the tracefile_id needs to be set in the offending session...well then I need another solution.
Thanks

Once the session starts writing to the trace file it
is going to write to the same file until the session
is closed.
Until the session is closed...aaahhhh gotcha. Well that explains that.
I tried the above with a new session and immediately set the identifier and got the same result, except it created the default trace file name as well as the new identifier copy with the path in it.
The logon trigger might be a workaround but it's not killing me at the moment.

Trace File Name

In a R12 Dev instance, we have trace files generated after turning on the "Concurrent: Allow Debugging" option at the user level (ID 301372.1).
Is there a way to identify the trace file names?
From prior runs, it seems that the trace file name is formatted as "<instance name>_ora_<a number>_<user name>.trc".
I thought that the "a number" field would be the same as the oracle_process_id value from fnd_concurrent_requests, but it is not.
Is there a way to get the "a number" from Oracle so that we can let the DBA know which specific file needs to be TKProf? This will help as we do not want all the files for the user to have TKProf run on.

Jai001 wrote:
In a R12 Dev instance, we have trace files generated after turning on the "Concurrent: Allow Debugging" option at the user level (ID 301372.1).
Is there a way to identify the trace file names?
From prior runs, it seems that the trace file name is formatted as "<instance name>_ora_<a number>_<user name>.trc".
I thought that the "a number" field would be the same as the oracle_process_id value from fnd_concurrent_requests, but it is not.
Is there a way to get the "a number" from Oracle so that we can let the DBA know which specific file needs to be TKProf? This will help as we do not want all the files for the user to have TKProf run on.Please run the query in (How To Trace a Concurrent Request And Generate TKPROF File [ID 453527.1]).
Thanks,
Hussein

How to get the trace file name for current running application?

Hi, I want to know if it is possible to get the file name directly for current running application instance which is launched by javaws.
There is a property "deployment.user.logdir" tells the log directory, it would be great if a file name property
is available. something like "instance.trace.file".
Our application wants it because we would like our client send use the application log by clicking a "send error"
button, the codes finds the trace file and compress it and send it by using a smtp server.
In 1.5, we can do it by using a shell program.

I found other asked it before, but I tried to set both properties, but neither works. my sun JRE version :java version "1.6.0_04"
<property
name="deployment.javaws.traceFileName"
value="abcfefsfdsf"/>
<property
name="deployment.javapi.trace.filename"
value="235235235"/>
But it always write to one trace file with name lik javaws63645.trace

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 ?

Getting trace file names for a conc program

Hi All,
We are using Oracle EBS 11i with Oracle 9i database.
The Apps version is 11.5.9 and database version is Release 9.2.0.6.0.
I am trying to trace a custom program which runs the pl/sql procedure.
I have enabled the tracing in the custom program definition.
This procedure has several blocks inside and also has many commits.
Due to this the SID for the session changes frequently.
Now my question is how can I get all the SIDs for this conc program and get the trace files for each SID.
My goal is to get all the trace file generated for this conc program and use them for analysis.
Any help is appreciated !
Thanks,
DR.

Sending again with formatting.
SELECT c.*, b.accounting_date,
          a.segment1
       || '.'
       || a.segment2
       || '.'
       || a.segment3
       || '.'
       || a.segment4
       || '.'
       || a.segment5 accrual_account
FROM gl_code_combinations a,
       ARCHIVE.ap_ae_headers b,
       ARCHIVE.ap_ae_lines c,
       ARCHIVE.po_distributions d,
       ARCHIVE.ap_invoice_distributions e
WHERE e.po_distribution_id IS NOT NULL
   AND d.po_distribution_id = e.po_distribution_id
   AND c.source_table = 'AP_INVOICE_DISTRIBUTIONS'
   AND c.source_id = e.invoice_distribution_id
   AND b.ae_header_id = c.ae_header_id
   AND b.accounting_date <= :b1
   AND a.code_combination_id = d.accrual_account_id
   AND a.segment3 = '3010'
UNION ALL
SELECT c.*, b.accounting_date,
          a.segment1
       || '.'
       || a.segment2
       || '.'
       || a.segment3
       || '.'
       || a.segment4
       || '.'
       || a.segment5 accrual_account
FROM gl_code_combinations a,
       apps.ap_ae_headers b,
       apps.ap_ae_lines c,
       apps.po_distributions d,
       apps.ap_invoice_distributions e
WHERE e.po_distribution_id IS NOT NULL
   AND d.po_distribution_id = e.po_distribution_id
   AND c.source_table = 'AP_INVOICE_DISTRIBUTIONS'
   AND c.source_id = e.invoice_distribution_id
   AND b.ae_header_id = c.ae_header_id
   AND b.accounting_date <= :b1
   AND a.code_combination_id = d.accrual_account_id
   AND a.segment3 = '3010'
SQL>select * from table(dbms_xplan.display);
| Id | Operation                        | Name                         | Rows | Bytes | Cost | Inst   |IN-OUT|
|   0 | SELECT STATEMENT                 |                               |    20 | 7545 | 7708 |        |      |
|   1 | UNION-ALL                       |                               |       |       |       |        |      |
|   2 |   NESTED LOOPS                   |                               |    19 | 7201 |   825 |        |      |
|   3 |    NESTED LOOPS                  |                               |    19 | 6612 |   787 |        |      |
|   4 |     NESTED LOOPS                 |                               |    93 | 28737 |   694 |        |      |
|   5 |      NESTED LOOPS                |                               |   119 | 32130 |   456 |        |      |
|* 6 |       FILTER                     |                               |       |       |       |        |      |
|   7 |        REMOTE                    |                               |       |       |       | AJINNI | R->S |
|* 8 |       FILTER                     |                               |       |       |       |        |      |
|   9 |        REMOTE                    |                               |       |       |       | AJINNI | R->S |
|* 10 |      FILTER                      |                               |       |       |       |        |      |
| 11 |       REMOTE                     |                               |       |       |       | AJINNI | R->S |
|* 12 |     FILTER                       |                               |       |       |       |        |      |
| 13 |      REMOTE                      |                               |       |       |       | AJINNI | R->S |
|* 14 |    TABLE ACCESS BY INDEX ROWID   | GL_CODE_COMBINATIONS          |     1 |    31 |     2 |        |      |
|* 15 |     INDEX UNIQUE SCAN            | GL_CODE_COMBINATIONS_U1       |     1 |       |     1 |        |      |
| 16 |   NESTED LOOPS                   |                               |     1 |   344 | 6883 |        |      |
| 17 |    NESTED LOOPS                  |                               |     6 | 1878 | 6871 |        |      |
| 18 |     NESTED LOOPS                 |                               |   572 |   156K| 5727 |        |      |
| 19 |      NESTED LOOPS                |                               |   988 |   248K| 3751 |        |      |
|* 20 |       TABLE ACCESS BY INDEX ROWID| AP_AE_HEADERS_ALL             |   978 | 17604 |   817 |        |      |
|* 21 |        INDEX RANGE SCAN          | AP_AE_HEADERS_N3              | 17595 |       |    82 |        |      |
|* 22 |       TABLE ACCESS BY INDEX ROWID| AP_AE_LINES_ALL               |     1 |   240 |     3 |        |      |
|* 23 |        INDEX RANGE SCAN          | AP_AE_LINES_U2                |     8 |       |     2 |        |      |
|* 24 |      TABLE ACCESS BY INDEX ROWID | AP_INVOICE_DISTRIBUTIONS_ALL |     1 |    23 |     2 |
|* 25 |       INDEX UNIQUE SCAN          | AP_INVOICE_DISTRIBUTIONS_U2   |     1 |       |     1 |        |      |
|* 26 |     TABLE ACCESS BY INDEX ROWID | PO_DISTRIBUTIONS_ALL          |     1 |    32 |     2 |        |      |
|* 27 |      INDEX UNIQUE SCAN           | PO_DISTRIBUTIONS_U1           |     1 |       |     1 |        |      |
|* 28 |    TABLE ACCESS BY INDEX ROWID   | GL_CODE_COMBINATIONS          |     1 |    31 |     2 |        |      |
|* 29 |     INDEX UNIQUE SCAN            | GL_CODE_COMBINATIONS_U1       |     1 |       |     1 |        |      |
Predicate Information (identified by operation id):
   6 - filter(NVL("AP_AE_HEADERS_ALL_H"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
   8 - filter(NVL("AP_AE_LINES_ALL_H"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
10 - filter(NVL("AP_INVOICE_DISTRIBUTIONS_ALL_H"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
12 - filter(NVL("PO_DISTRIBUTIONS_ALL_H"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
14 - filter("A"."SEGMENT3"='3010')
15 - access("A"."CODE_COMBINATION_ID"="PO_DISTRIBUTIONS_ALL_H"."ACCRUAL_ACCOUNT_ID")
20 - filter(NVL("AP_AE_HEADERS_ALL"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
21 - access("AP_AE_HEADERS_ALL"."ACCOUNTING_DATE"<=:Z)
22 - filter("AP_AE_LINES_ALL"."SOURCE_TABLE"='AP_INVOICE_DISTRIBUTIONS' AND
              NVL("AP_AE_LINES_ALL"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
23 - access("AP_AE_HEADERS_ALL"."AE_HEADER_ID"="AP_AE_LINES_ALL"."AE_HEADER_ID")
24 - filter("AP_INVOICE_DISTRIBUTIONS_ALL"."PO_DISTRIBUTION_ID" IS NOT NULL AND
              NVL("AP_INVOICE_DISTRIBUTIONS_ALL"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
25 - access("AP_AE_LINES_ALL"."SOURCE_ID"="AP_INVOICE_DISTRIBUTIONS_ALL"."INVOICE_DISTRIBUTION_ID"
26 - filter(NVL("PO_DISTRIBUTIONS_ALL"."ORG_ID",NVL(TO_NUMBER(DECODE(SUBSTRB(:B1,1,1),'
              ',NULL,SUBSTRB(:B2,1,10))),(-99)))=NVL(TO_NUMBER(DECODE(SUBSTRB(:B3,1,1),' ',NULL,SUBSTRB(:B4
27 - access("PO_DISTRIBUTIONS_ALL"."PO_DISTRIBUTION_ID"="AP_INVOICE_DISTRIBUTIONS_ALL"."PO_DISTRIB
28 - filter("A"."SEGMENT3"='3010')
29 - access("A"."CODE_COMBINATION_ID"="PO_DISTRIBUTIONS_ALL"."ACCRUAL_ACCOUNT_ID")
Note: cpu costing is off
67 rows selected.
{code}

Generate trace file with required name

hi all,
as a sys user i want to trace a user session. so i am using
SQL> EXEC DBMS_SYSTEM.set_sql_trace_in_session(sid=>123, serial#=>1234, sql_trace=>TRUE);
SQL> EXEC DBMS_SYSTEM.set_sql_trace_in_session(sid=>123, serial#=>1234, sql_trace=>FALSE);
to trace. but this trace file is mixing with another trace files in udump.
did some google and found that we can use ALTER SESSION SET TRACEFILE_IDENTIFIER = "MY_TEST_SESSION". but this will generate trace file for sys user account not for the desired user session. how we can define trace file name for desired user session trace.
Please let me...
thanks

>but this trace file is mixing with another trace files in udump.
above is NOT true for any *NIX Operating System.
The trace file name will contain the OS ProcessID#
is this application 3-tier/
does application utilize connection pooling?
It appears that you post frequently & reply/respond very infrequently.
How do I ask a question on the forums?
https://forums.oracle.com/message/9362002#9362002

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

Create trace file on specific location

Hi all,
I'm working with a 11gR2 Enterprise DB on Linux RedHat 5
Now I need to create a trace file. This trace will be huge and I need to create it on an specific folder on my system because the udump fs could be small for it. These are the commands I'll use:
oradebug setospid 3165
oradebug unlimit
oradebug event 10046 trace name context forever, level 12
If I use the "oradebug tracefile_name" I'll get the actual trace file name but, How can I say the specific location where I need to create it?
Best regards,
dbajug

dbajug wrote:
Hi all,
I'm working with a 11gR2 Enterprise DB on Linux RedHat 5
Now I need to create a trace file. This trace will be huge and I need to create it on an specific folder on my system because the udump fs could be small for it. These are the commands I'll use:
oradebug setospid 3165
oradebug unlimit
oradebug event 10046 trace name context forever, level 12
If I use the "oradebug tracefile_name" I'll get the actual trace file name but, How can I say the specific location where I need to create it?
Best regards,
dbajugi dont know of any method that will allow you to do this for a single file, but you can use below workaround since the tracefile name is predictable
lets say your database name is ORCL
the ospid is 3165, so the tracefile will be created as udump/ORCL_ora_3165.trc
before starting the trace, you can pre-create it at different location and point a symlink on it, e.g
touch /lot_of_space_here/trace.trc
ln -s /lot_of_space_here/trace.trc udump/ORCL_ora_3165.trc
and now start tracing

A critical program error has occurred. BEx Analyzer. Cannot find trace file

I have now spent about 20 hours trying to resolve this issue. I receive the following error message when attempting to open any BEx Query: u201CA critical program error has occurred. The program will now terminate. Please refer to the trace for further information()u201D. Iu2019ve provided a video example of the scenario (couple minutes long): http://www.altnetwork.net/misc/Analyzer%20Critical%20Error.html
I cannot find the trace file in the standard C:\DOCUME1\BaldwiJE\LOCALS1\Temp\BexAnalyzerTrace.txt path. I cannot set/change the path/name of the trace file because the Trace File Name text box is grayed out (disabled) in BEx Analyzer > Global Options (see the above flash video link). I know that I am using the same Business Explorer and GUI build as my colleagues and I am able to login with my ID on their machines and not receive an error. We are using SAP BW 7.01 and I am using Excel 2007. I have entirely reinstalled Microsoft Excel, and the SAP Frontend including Business Explorer and SAP GUI. Iu2019ve monitored using both windows process monitor and windows process explorer but nothing is readily apparent as an issue (glad to share the process information if someone thinks it might help). No relevant event logs in the Windows event viewer.
Per the sapbexc.xla file, my system configuration is as follows:
Computer Name:      DEN-SSI-SYS-L61
File Location:      C:\DOCUME1\BaldwiJE\LOCALS1\Temp\sapBEX_PC_0614_103147.xls
Check done on:      6/14/2011   10:31:47 AM
Excel Version:      Excel 2007 (12.0.6535.5002)
Windows Version:      Windows 2000 (2195) Theme: %SystemRoot%\resources\Themes\Windows Classic.theme
Default Browser:      Internet Explorer (7.0.6000.17093)
SAP GUI:      720 Patch 1

Resolved! It actually seemed to be related to my windows profile. I notice that if a co-worker logged into windows on my machine that he was able to run the same BEx queries that I couldn't. I renamed my profile folder at c:\documents and settings\<myaccountname> to ...<myaccountname.bak>. I did this using a local administrator account on my computer. Then I logged back in to windows using my AD credentials. A new profile was created and then I was able to use BEx Analyzer again.
I also went back and tried to reload everything from my .bak profile into the newly created folder under documents and settings and hoped that I could isolate what specifically was causing the issue. However, even after moving everything over to my newly created profile I could not get the error to generate again. Sorry.
Highly recommend to anyone with the same issue that you confirm that a new profile works by a) having someone else login to your computer who has not already logged in before b) if that works, replace your c:\documents and settings\<myaccountname> folder.
Thanks to all who offered support.
Jerimiah

Find out TRACE file of a session

Hi,
I'm generating trace file of a session (not the session where I'm login into) by the following command..
EXEC DBMS_SUPPORT.start_trace(sid=>123, serial=>1234, waits=>TRUE, binds=>FALSE);
Now, after start tracing I cannot find out the trace file which is generated for SID=123.
Can you help me to find out the trace file? I mean, is there anyway to find out the trace file name for SID=123?
Thanks,
Anjan

hi,
Before this user must have sysdba privileges
SQL> ORADEBUG SETMYPID; -- Debug current session.
SQL> ORADEBUG SETOSPID 678; -- Debug session with the specified OS process
SQL > ORADEBUG SETORAPID 6756323; -- Debug session with the specified Oracle process ID.
SQL> ORADEBUG TRACEFILE_NAME; -- Display the current trace file.
- Pavan Kumar N

I am using itunes 10 and trying to consolidate my files. I keep getting the error "Copying files failed. The file name was invalid or too long". How can I indentify what file is causing this problem or resolve this issue?

I am using itunes 10 and trying to consolidate my files. I keep getting the error "Copying files failed. The file name was invalid or too long". How can I indentify what file is causing this problem or resolve this issue?

BUMP
Yes, I just get that message. I don't see how I could investigate this problem.
I didn't mention that this happened when I was consolidating my library, not copying files to another computer.
In other words, I'm using a "normal" itunes procedure, itunes won't complete it, and won't tell me exactly why or how to figure out how to fix it...
Is there at least some easy way to tell which files were successfully copied to my itunes music folder so I can work on moving the uncopied files?
Can anybody help me?

Name of trace file from trace enabled concurrent program

Hi all,
I am looking for a sql script or method to find the name of a trace file in udump for trace enabled concurrent programs. I know the trace files show 11i logon (user_name from fnd_user) in the name of the trace file but I am looking for a sql that would give the exact name of the raw trace file with request id as input.
I have 11.5.10.2.
Any help?
Thanks,

Please see these docs.
11i-How to find the Trace file generated for a concurrent program [ID 270446.1]
How to find the Trace file generated for a concurrent program? [ID 967966.1]
FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12 [ID 296559.1]
Thanks,
Hussein

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

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

Indentifying trace file name?

Similar Messages

Maybe you are looking for