Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: avoiding ora-1652 on temp tablespace

Re: avoiding ora-1652 on temp tablespace

From: <nlzanen1_at_EY.NL>
Date: Fri, 06 Apr 2001 01:41:40 -0700
Message-ID: <F001.002E38F8.20010406000526@fatcity.com>

Hi,

Users will also get error message when this happens. Ask them to watch out for this error and report back what they were doing at the time they got it.
With only 20 users this should not be a big hassle.

Jack

                                                                                       
                          
                    "Seley, Linda"                                                     
                          
                    <LSeley_at_IQNavi       To:     Multiple recipients of list ORACLE-L 
<ORACLE-L_at_fatcity.com>     
                    gator.com>           cc:                                           
                          
                    Sent by:             Subject:     avoiding ora-1652 on temp 
tablespace                       
                    root_at_fatcity.c                                                     
                          
                    om                                                                 
                          
                                                                                       
                          
                                                                                       
                          
                    05-04-2001                                                         
                          
                    19:40                                                              
                          
                    Please respond                                                     
                          
                    to ORACLE-L                                                        
                          
                                                                                       
                          
                                                                                       
                          



We recently released a new version of our software and suddenly we're blowing out our temp tablespace. The previous version never complained at 1000m. The new version is choking on 2500m. I don't want to keep adding space, although that's the conventional wisdom. I want to find the query or queries that are being pigs and get the developers to fix 'em!

By the time I get notification that there's been an ora-1652 I can't find much info in the system. All of the currently running queries are small, we only have 20 users connected at any time, v$sort_usage is empty, and v$sort_segment shows one segment taking the full 2500m. I also can't turn on tracing, these 20 users are persistent and trace files will fill up in no time. Our entire database is VERY small, only about 60m!

Any advice on how to catch these queries? The ora-1652 errors are occuring about a week apart so it isn't practical for me to personally babysit the database.

Thanks!

Linda



De informatie verzonden in dit e-mailbericht is vertrouwelijk en is uitsluitend bestemd voor de geadresseerde. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan derden is, behoudens voorafgaande schriftelijke toestemming van Ernst & Young, niet toegestaan. Ernst & Young staat niet in voor de juiste en volledige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor tijdige ontvangst daarvan. Ernst & Young kan niet garanderen dat een verzonden e-mailbericht vrij is van virussen, noch dat e-mailberichten worden overgebracht zonder inbreuk of tussenkomst van onbevoegde derden.

Indien bovenstaand e-mailbericht niet aan u is gericht, verzoeken wij u vriendelijk doch dringend het e-mailbericht te retourneren aan de verzender en het origineel en eventuele kopieën te verwijderen en te vernietigen.

Ernst & Young hanteert bij de uitoefening van haar werkzaamheden algemene voorwaarden, waarin een beperking van aansprakelijkheid is opgenomen. De algemene voorwaarden worden u op verzoek kosteloos toegezonden.



The information contained in this communication is confidential and is intended solely for the use of the individual or entity to whom it is addressed. You should not copy, disclose or distribute this communication without the authority of Ernst & Young. Ernst & Young is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Ernst & Young does not guarantee that the integrity of this communication has been maintained nor that the communication is free of viruses, interceptions or interference.

If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies.

In carrying out its engagements, Ernst & Young applies general terms and conditions, which contain a clause that limits its liability. A copy of these terms and conditions is available on request free of charge.


--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: nlzanen1_at_EY.NL

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
Received on Fri Apr 06 2001 - 03:41:40 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US