Path: news.easynews.com!easynews!news-xfer.siscom.net!btnet-peer0!btnet-peer!btnet!newspeer.clara.net!news.clara.net!oleane.net!oleane!bnewspeer00.bru.ops.eu.uu.net!bnewsifeed02.bru.ops.eu.uu.net!lnewspost00.lnd.ops.eu.uu.net!emea.uu.net!not-for-mail From: "Niall Litchfield" Newsgroups: comp.databases.oracle.server References: <3CFCE560.9EB15807@exesolutions.com> <7utpfuooqromk8krj1dd3nj0b73a8go8ga@4ax.com> <3cfd30be$0$8506$cc9e4d1f@news.dial.pipex.com> Subject: Re: intermittent commit on insert ? Date: Thu, 6 Jun 2002 11:52:32 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Lines: 22 Message-ID: <3cff47b4$0$8512$ed9e5944@reading.news.pipex.net> NNTP-Posting-Host: host9.audit-commission.gov.uk X-Trace: 1023362997 reading.news.pipex.net 8512 193.128.236.219 X-Complaints-To: abuse@uk.uu.net Xref: easynews comp.databases.oracle.server:149734 X-Received-Date: Thu, 06 Jun 2002 05:12:05 MST (news.easynews.com) "Chuck" wrote in message news:adl8ln$1tk4$1@ID-85580.news.dfncis.de... > In an ideal world and in text books that would be possible - but so would > having one CPU for each process, and terabytes of real memory so no tasks > ever swap out. In the real world rollback segments fill up, disk size is > limited, and sometimes you have to commit more frequently than you want to. > I would not want to be in the position of having to explain to my boss why > I'm tying up gigabytes of space for a rollback segment that gets used once > in a blue moon. Well then don't do it. We do have a process that we run once a year that takes an exceptional amount of rollback space. So what do we do. Once a year take all the other rollback segments offline (having shrunk them). We then create our large segment run the transaction and then drop the rollback segment and put everything back. The point being that we want to run processes like this in 'off hours' just because of the impact of this one process on the system (not to mention the fact that it does intermediate commits so I want to make damn sure I can't leave the db in an unknown state).