I have seen this when I have created a logon trigger which activates trace but the owner of the trigger did not have ALTER SESSION granted directly to it (instead it was through a role). Sessions logging on ended up creating a trace file but nothing was in it but "TRACE DUMP CONTINUED FROM FILE"
- Ethan -----Original Message----- Sent: Thursday, May 22, 2003 5:18 PM To: Multiple recipients of list ORACLE-L 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... -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Post, Ethan INET: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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).
