Re: 10046 trace question

[Daniel Fink]

Raj, Could you create a stored proc/function that  opens each of their trace files, writes a line, then releases the file? Daniel Fink "Jamadagni, Rajendra" wrote: Thanks KG, I think I wasn't very clear so here is version 1.1 ...BTW this is all in a Oracle Forms custom application that we (developed and) use in-house 07:00am Johndoe logs in and his session automatically starts tracing 10046^8 through a login trigger. 10:00am Johndoe experiences slowness in the session. 10:01am johndoe runs a program in windows, that sends out an email to admin group informing them about the slowness. 10:02am johndoe continues processing probably till COB so the trace file is not complete. Plus johndoe has ONE windows session but multiple oracle sessions, so (in most cases) neither user nor anyone else can tell us which session out of 4 to 5 session experienced a problem. By the time we find out which session, it is too late anyway. Now my question is "is there a way to be able to insert a marker (preferably a slow session indicator with timestamp) into the trace file that is being generated on the server from another session?"I probably want to do this on each session that user is running ... just to be safe. This way, later on I can scan through the trace files and find the marker and see what was happening around the (slow session) marker and maybe guess what happened?And no, I am not talking about granting privileges on dbms_system to anyone, it is restricted to sys and system only. Is this doable at all?Raj-------------------------------------------------------------------------------- Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art ! -----Original Message----- From: K Gopalakrishnan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 22, 2003 3:19 PM To: Multiple recipients of list ORACLE-L Subject: Re: 10046 trace question   Raj: THe simple option is to run the ALTER SESSION command to set some session level parameter like 1=1 and get the timings. Giving the EXECUTE  on DBMS_SYSTEM is not a good idea. KG ----- Original Message ----- From: Jamadagni, Rajendra To: Multiple recipients of list ORACLE-L Sent: Wednesday, October 22, 2003 10:09 PM Subject: 10046 trace question   Hi all, I am monitoring a production database and while we have performance issues looked at, I have 10046^8 running on all user session in this RAC db. The scenario is as follows ... user logs in through a windows terminal server, opens multiple sessions (oracle forms) to connect to database. Whenever they see a performance issue (AKA slowness) they hit a button on their windows session, that sends an email to us informing that user experienced slowness at say 10am. Now normally because users don't exit their session till COB, the trace files are still incomplete at the time when user reported slowness. While these trace files are useful to look at next day, there is no way (that I know of) to go into the trace file and answer questions like "what was this user doing around 10am" ... is there? Also is there an easy way to put a marker in the trace file (something like dbms_system.ksdddt) that can be invoked preferable triggered from a script ... and then we can go back to trace file and find out what the session was doing by looking at trace lines around the marker? I don't know if anyone has done this before, or I am really trying to offset the US debt by collecting pennies? Any help in this regard is greatly appreciated. Raj -------------------------------------------------------------------------------- Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art ! ************************************************************************************** This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you. **************************************************************************************4 ************************************************************************************** This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you. **************************************************************************************4