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 -> TRANSACTIONS_PER_ROLLBACK_SEGMENT (the real story)

TRANSACTIONS_PER_ROLLBACK_SEGMENT (the real story)

From: john v <johnvue_at_gte.net>
Date: Tue, 04 Jan 2000 05:34:46 GMT
Message-ID: <sh137sg3nk47lqqk4l3cr7gie6ev5rgnuf@4ax.com>


Can the init.ora parameter "TRANSACTIONS_PER_ROLLBACK_SEGMENT" really affect how Oracle distributes its rollback activity during live use?

I'm aware of the N=TRANSACTIONS/TRANSACTIONS_PER_ROLLBACK_SEGMENT which sounds like the minimum Oracle tries TO BRING ONLINE... but the documentation is not clear on whether
TRANSACTIONS_PER_ROLLBACK_SEGMENT affects anything after Oracle is already up.

I have a system where Oracle unevenly directs many transactions to 2 segments out of 100. This is not due to ALTER SESSION SET TRANSACTION. I was hoping that reducing TRANSACTIONS_PER_ROLLBACK_SEGMENT=1 would help spread things out a bit.

Thanks for any help. Received on Mon Jan 03 2000 - 23:34:46 CST

Original text of this message

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