Oracle-L: RE: 10046 tracing in PRO C programs?

From: Cary Millsap <cary.millsap_at_hotsos.com>
Date: Thu, 22 May 2003 14:18:09 -0800
Message-ID: <F001.005A0DA5.20030522141809@fatcity.com>

Glenn,

I think the "TRACE DUMP CONTINUED FROM FILE" message occurs because file is actually opened by the SET TRACEFILE_IDENTIFIER command, and then "re-opened" by the SET EVENTS command. I see this all the time, except that after the "***" line, there's a whole trace file full of stuff.

Please forgive me if the following question seems impertinent (you seem to well know what you're doing)... Are you sure that in your test situation, your code actually makes database calls that should show up in your trace data?

Aside from that, you can try leaving out the SET TRACEFILE_IDENTIFER out and seeing what happens. This will at least get rid of the "TRACE DUMP CONTINUED FROM FILE" message.

Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com

Upcoming events:
- Hotsos Clinic 101 in Reykjavik, Ottawa, Dallas, Washington, Denver, Sydney - Visit www.hotsos.com for schedule details...

-----Original Message-----
Sent: Thursday, May 22, 2003 12:07 PM
To: Multiple recipients of list ORACLE-L

We're examining performance of a PRO*C program supplied by our software vendor and I'm looking at how I can get it to generate a 10046 trace file. There is a section in the code that allows the program to be executed with a trace flag set and this code section then runs:

EXEC SQL ALTER SESSION SET SQL_TRACE TRUE; I replaced this with these statements to setup the session for a 10046, level 8 trace:

EXEC SQL ALTER SESSION SET TIMED_STATISTICS=TRUE; EXEC SQL ALTER SESSION SET MAX_DUMP_FILE_SIZE=UNLIMITED; EXEC SQL ALTER SESSION SET TRACEFILE_IDENTIFIER='APPCODE'; EXEC SQL ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT FOREVER, LEVEL 8'; The program compiles and runs and the program execution produces a trace file, however, the trace file contains only the text:

TRACE DUMP CONTINUED FROM FILE ***

No other information appears after this.

What's this all about? And, what is the best way to run a 10046 trace on a proC program? This program runs in a nightly batch job, so I really want to start the tracing within the program rather than start tracing from another session.

Thanks for any tips,

Glenn Stauffer

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Glenn Stauffer
INET: stauffer_at_swarthmore.edu

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Cary Millsap
INET: cary.millsap_at_hotsos.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------