Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: To set events or not set events, that is the question

RE: To set events or not set events, that is the question

From: Jamadagni, Rajendra <>
Date: Tue, 15 Jun 2004 06:56:40 -0400
Message-ID: <A186CBDC8B1D61438BC50F1A77E91F7309B61A96@xchgbrsm1.corp.espn.pvt>


The times are probably micro/milli/centi/deca seconds. Since Oracle can't make up its mind on one standard, choose one. But I have seen things like this before. I even have a SQL that tkprof claims has been running for 67 years (and Cary will love this with 63 years of Wait time BTW). So, go figure. It is hard to figure them out.

Since so many people wrote various papers about 1555 e.g.

  1. Cats Dogs and 1555
  2. 155 Explained
  3. 1555 Demystified etc ...

Oracle has a compelling reason to make it even more obscure and with RAC it is even easier. See how conveniently they moved deadlock graph dumps to lmd0 trace files rather than process trace files? Makes sense ... But to whom is still the open question.


Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. select standard_disclaimer from company_requirements; QOTD: Any clod can have facts, having an opinion is an art !  

-----Original Message-----

[] On Behalf Of Jesse, Rich Sent: Monday, June 14, 2004 5:12 PM
To: ORACLE-L (E-mail)
Subject: To set events or not set events, that is the question on HP/UX 11.11, newly created from an export. After a week of uptime, we get an ORA-1555 today. The alert.log says:

ORA-01555 caused by SQL statement below (Query Duration=8581 sec, SCN:0x0000.0090c189):

...followed by what I'm hoping is a partial statement (because it's a nasty FTS):

SELECT PARTNO,WHOUSE,ENT_CODE FROM MY_TABLE (schema/table/column names changed to protect the innocent). Now any query that takes 2+ hours to complete during the day on our nice new fast server *deserves* to die a horrible ORA-1555 death, IMHO, but I'd still like to be able to track these down in the future. And without a trace file generated, that's just not gonna happen.

So, I'll set event 1555 as an errorstack. But the last time I did this, then had a Support call a year later, I was told that setting events permanently like this is not a good idea, although I was not able to find out *why* it's not.

I've got a TAR open to get the Official Word, but does anyone have a good reason why this or other "error" event (like 1652 to determine who the hell used up 2GB of TEMP) should NOT be in an init.ora for any version of Oracle???


Please see the official ORACLE-L FAQ:

To unsubscribe send email to: put 'unsubscribe' in the subject line.
Archives are at
FAQ is at

Received on Tue Jun 15 2004 - 05:53:47 CDT

Original text of this message