Re: Temp tablespace Full
From: Dominic Brooks <dombrooks_at_hotmail.com>
Date: Wed, 6 Nov 2013 17:29:32 +0000
Message-ID: <DUB402-EAS39634639103C6986EA73CFFA1F00_at_phx.gbl>
The currently executing SQL id is often not the culprit.
Date: Wed, 6 Nov 2013 17:29:32 +0000
Message-ID: <DUB402-EAS39634639103C6986EA73CFFA1F00_at_phx.gbl>
The currently executing SQL id is often not the culprit.
The sql_id in v$tempseg_usage can be unreliable.
See RTSM via v$sql_plan_monitor.
Also cross reference underlying ASH tables and, depending on version, increasing values in temp_space_allocated column.
Look as well at your top n SQL for the period concerned and between these, it should be easier to track down.
ASH and RTSM require diagnostic pack license.
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Nov 06 2013 - 18:29:32 CET