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

From: Jesse, Rich <Rich.Jesse_at_quadtechworld.com>
Date: Mon, 14 Jun 2004 16:11:36 -0500
Message-ID: <FBE1FCA40ECAD41180400050DA2BC54004E93AE7@qtiexch2.qgraph.com>

9.2.0.5.0 on HP/UX 11.11, newly created from an 8.1.7.4.0 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???

TIA!
Rich

Rich Jesse                           System/Database Administrator
Rich.Jesse_at_quadtechworld.com         QuadTech, Sussex, WI USA


----------------------------------------------------------------

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

To unsubscribe send email to: oracle-l-request_at_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

Received on Mon Jun 14 2004 - 16:08:41 CDT