I have a 2gb UNDO tablespace. A third-party application continually runs out of UNDO when it joins two tables to produce a result table. Our retention time is set to 15 minutes, the NoSpaceErrCnt in V$UNDOSTAT is always zero. The answer for this from our vendor is to increase the size of the UNDO based on their DBAs statement that UNDO is consumed rapidly because every query makes a physical copy of all tables and holds on to them for the retention period. I can find nothing that discusses exactly how UNDO physically works, and am not sure that this can be true. That would mean that every user querying our database would have copies of the tables in the UNDO, and I'd need about a gazillion gb to handle that. Does anyone have any insights on how the UNDO physically works?
--------------- Sherrie Kubis Southwest Florida Water Management District 2379 Broad Street Brooksville FL 34604-6899 Phone: (352) 796-7211, Ext. 4033 Fax: (352) 754-6776 Email: Mailto:[EMAIL PROTECTED] http://WaterMatters.org -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
