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

Home -> Community -> Usenet -> c.d.o.server -> Re: Transaction size limitation for serializable isolation level?

Re: Transaction size limitation for serializable isolation level?

From: VC <boston103_at_hotmail.com>
Date: Sun, 18 Apr 2004 22:55:45 GMT
Message-ID: <QHDgc.22780$yD1.53695@attbi_s54>


Hello Joe,

"Joe Weinstein" <joeNOSPAM_at_bea.com> wrote in message news:40829C6F.2000803_at_bea.com...

>

> Hi.
> Oracle does require some extra memory for serializable transactions, and
this
> comes from the configurable per-table memory you can adjust. If the DBMS
> runs out of this memory during a transaction, you will get the 8077 error,
> even if you're the only user logged in. The Oracle documentation would be
better
> if it was explicit about that.

It's unclear what exactly you mean by "memory" here.

If you are talking about the INITRANS parameter, then the Oracle documentation _is_ explicit about it:

"Under some circumstances, Oracle can have insufficient history information to determine whether a row has been updated by a "too recent" transaction. This can occur when many transactions concurrently modify the same data block, or do so in a very short period. You can avoid this situation by setting higher values of INITRANS for tables that will experience many transactions updating the same blocks."

Assuming the above and remembering that the OP mentioned that they'd already tried to increase the parameter to no avail., your suggestion does not make much sense.

VC Received on Sun Apr 18 2004 - 17:55:45 CDT

Original text of this message

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