Xref: alice comp.databases.oracle.server:83146 Path: alice!news-feed.fnsi.net!newsfeed.icl.net!newspeer.clara.net!news.clara.net!nnrp3.clara.net.POSTED!not-for-mail From: "Dave Wotton" Newsgroups: comp.databases.oracle.server References: <38977b43.1272342793@news.erols.com> <878s25$42l$1@news.rinet.ru> <3898b7b5.1353365401@news.erols.com> Subject: Re: rollback/commit question Lines: 30 X-Newsreader: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Message-ID: Date: Wed, 02 Feb 2000 22:49:59 GMT X-Complaints-To: abuse@clara.net X-Trace: nnrp3.clara.net 949531799 195.8.78.71 (Wed, 02 Feb 2000 22:49:59 GMT) NNTP-Posting-Date: Wed, 02 Feb 2000 22:49:59 GMT Jay Scheiner wrote in message <3898b7b5.1353365401@news.erols.com>... .... >Please comment on other reply to my post, if you could- that I am >committing too frequently. I have not yet looked at the author's web >site. Yes, you are committing too frequently. Committing without closing and re-opening your read cursor will make you prone to snapshot too old, as you've discovered. The best solution is to close and reopen the cursor immediately after your commit statement. This will prevent snapshot too old, and the commits prevent your rollback segment growing too big. However, closing and opening the cursor is very expensive, so you should try to minimise the number of times you do it by decreasing the number of commits - I'd suggest every 2000-3000 rows. (But this must be balanced by the maximum size you want your rollback segments to grow: the fewer the commits, the bigger the rollback segments you will need.) For more details, as an alternative to the Ixora website, see my web-page: http://home.clara.net/dwotton/dba/snapshot.htm BTW, your email address doesn't appear to work. Dave. -- There's no need to reply to this posting by email, but if you do, remove the "nospam" from my email address first.I provide a