From: "Dave Wotton" Newsgroups: comp.databases.oracle.server References: <9fka71$ies$1@news.netmar.com> Subject: Re: Rollback segment too old Date: Wed, 6 Jun 2001 22:02:12 +0100 Lines: 28 X-Newsreader: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: clara.net http://www.clara.net/ Message-ID: <991861857.711436@dionysos> NNTP-Posting-Host: 195.8.80.18 Lines: 28 X-Complaints-To: abuse@clara.net X-Trace: 6b60800029a283c4f5c10440776608d8858ea6e20c44cae8367070083b1e9c61 peter.mckenzie@health.wa.gov.au wrote in message <9fka71$ies$1@news.netmar.com>... >Is this error logged anywhere at the instance level. I was hoping to see it >in the alert logs or the trace files. I have a long running sql job which >failed but have no log of the failure. I suspect rollback segment too old >and was hoping Oracle tracked this one. Thanks in anticipation. I assume you mean "Snapshot too old"? If so, then no, this isn't logged in the alert log: it's not serious enough. The alert log only contains information about the status of the database as a whole, it doesn't contain information about the failure of individual transactions and queries, unless they're a symptom of a database bug. It *might* be in a user session trace file, but it's unlikely. Your best bet is to modify your application code so that it raises an exception whenever an SQL statement returns an unexpected response code (which, of course, is good programming practice anyway). If you want more information about the causes of "snapshot too old" try my web page: http://home.clara.net/dwotton/dba/snapshot.htm Dave. -- If you reply to this newsgroup posting by email, remove the "nospam" from my email address first.