From oracle-l-bounce@freelists.org Wed Mar 31 08:22:18 2004 Return-Path: Received: from air189.startdedicated.com (root@localhost) by orafaq.com (8.11.6/8.11.6) with ESMTP id i2VEMHR22912 for ; Wed, 31 Mar 2004 08:22:17 -0600 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air189.startdedicated.com (8.11.6/8.11.6) with ESMTP id i2VEMHo22905 for ; Wed, 31 Mar 2004 08:22:17 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C6624635339; Wed, 31 Mar 2004 09:18:41 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25265-50; Wed, 31 Mar 2004 09:18:41 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id C12356353C4; Wed, 31 Mar 2004 09:16:54 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Wed, 31 Mar 2004 09:15:43 -0500 (EST) X-Original-To: oracle-l@freelists.org Delivered-To: oracle-l@freelists.org Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 79A436354C6 for ; Wed, 31 Mar 2004 09:15:42 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24353-74 for ; Wed, 31 Mar 2004 09:15:42 -0500 (EST) Received: from www.hotsos.com (hotsos.com [209.120.206.15]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id CC9CE635383 for ; Wed, 31 Mar 2004 09:14:05 -0500 (EST) Received: from CVMLAP02 (66.169.163.33.ts46v-12.otne2.ftwrth.tx.charter.com [66.169.163.33]) (authenticated (0 bits)) by www.hotsos.com (8.12.11/8.11.0) with ESMTP id i2VEMEsI003403; Wed, 31 Mar 2004 08:22:15 -0600 From: "Cary Millsap" To: Subject: RE: Re[2]: what exactly 'tim' means in a 10046 TRACE file ? Date: Wed, 31 Mar 2004 08:19:25 -0600 Message-ID: <006c01c4172b$2eecf410$6601a8c0@CVMLAP02> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <31855406.20040331132321@tsi.lv> Importance: Normal X-Virus-Scanned: by amavisd-new at freelists.org X-archive-position: 2175 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: cary.millsap@hotsos.com Precedence: normal Reply-To: oracle-l@freelists.org X-list: oracle-l X-Virus-Scanned: by amavisd-new at freelists.org I hadn't noticed that ERROR lines had tim values in different units than dbcalls' tim values. I'm sure that error handling does consume CPU time. It would be difficult to consider them on par with Oracle timed events because there's no e or ela statistic associated with them. But if you can crack the mapping between ERROR tim values and dbcall tim values, then you might have something there. I'm thinking back to when I've needed the ERROR information at all, and in the one case I can recall, it was a "user requested end of txn" kind of thing, which helped me understand that the user was doing something the DBA didn't tell me (got tired of waiting and hit Ctrl-C, basically). But I've not yet cared about how long the error-processing was taking. Sounds like you're on an interesting trail of discovery. :) Cary Millsap Hotsos Enterprises, Ltd. http://www.hotsos.com * Nullius in verba * Upcoming events: - Performance Diagnosis 101: 4/6 Seattle, 5/7 Dallas, 5/18 New Jersey - SQL Optimization 101: 4/19 Denver, 5/3 Boston, 5/24 San Diego - Hotsos Symposium 2005: March 6-10 Dallas - Visit www.hotsos.com for schedule details... -----Original Message----- From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Edgar Chupit Sent: Wednesday, March 31, 2004 4:23 AM To: Cary Millsap Subject: Re[2]: what exactly 'tim' means in a 10046 TRACE file ? Hello Cary, CM> The fortunate thing is that it's rarely necessary to be able to convert CM> a tim into a wall time and vice versa. But how should we treat ERROR lines in trace files, for example on 9iR2 I have this lines in trace file: EXEC #31:c=0,e=3083,p=0,cr=9,cu=17,mis=0,r=1,dep=1,og=4,tim=1055355471165039 ERROR #31:err=24381 tim=694217847 As I understood from your book and metalink first time is in hsecs and second time is in msecs. How should I compare this two times? simply convert two tim values to wall clock and subtract values or somehow differently? Can I treat ERROR lines as wait events, because as I saw from some tests ERROR handling consumes some amount of cpu time? -- Edgar ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@freelists.org put 'unsubscribe' in the subject line. -- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html ----------------------------------------------------------------- ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@freelists.org put 'unsubscribe' in the subject line. -- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------