Snapshot too old during stress test... how to avoid

From: <rgaffuri_at_cox.net>
Date: Wed, 04 Jun 2003 04:59:44 -0800
Message-ID: <F001.005A9C13.20030604045944@fatcity.com>

Im testing worst case scenarios right now. So Im doing batch updates,inserts,deletes and 'create table as' from a staging tablespace of approximately 5GBs to a master tablespace of approximately 11GBs.

Ive got my job queue processes set to 36 and Im running 36 at a time in the background in order to gather statistics and timing under worst case scenarios.

Im in 8.1.7.3 and I have increased the size of my RBS tablespace to 11GB for this test. I have 4 standard RBS with optimal size set to 1GB. Why would I get a snapshot too old? I would think that 11GBs of rollback would be big enough. Would increasing the number of Rollback segments avoid this even though I have the same amount of space in the tablespace?

In reality Im going to seriallize the process to avoid this and to improve performance, however, I want to stress the system.

any advice?

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: <rgaffuri_at_cox.net
  INET: rgaffuri_at_cox.net

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: 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 Wed Jun 04 2003 - 07:59:44 CDT