Thanks all for your replies. Based on what was said here and by Oracle Support, I'll be setting up the events for the short term, and playing with Niall's example of the SERVERERROR trigger for the long term. We've got an instance bounce for some critical OS patches for next week, so that should be fine. I think it's interesting that the whole SQL statement is in the alert.log. That statement should never appear as-is on our production DB. Perhaps someone was playing around in Production since our Development box isn't yet 100% after our 9i conversion... Thanks again! Rich Rich Jesse System/Database Administrator rjesse@xxxxxxxxxxxx Quad/Tech Inc, Sussex, WI USA -----Original Message----- From: [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jesse, Rich Sent: Monday, June 14, 2004 5:12 PM Subject: To set events or not set events, that is the question 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): ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------