Re: oracle tuning

Hi Gerd,

That is no protection against ORA-1555 errors due to discrete transactions, or any ORA-1555 errors for that matter. See the tip on my web site (1st URL below) called "Avoiding ORA-1555 (Snapshot Too Old) Errors".

Regards,
Steve Adams

http://www.ixora.com.au/

http://www.oreilly.com/catalog/orinternals/

http://www.christianity.com.au/

On Fri, 12 Nov 1999 22:22:40 GMT, info_at_gerd-kock.de (Gerd Kock) wrote:

>you may bind the full table scanning transactions to extra large
>rollback segments, look at the manual SET TRANSACTION USE ROLLBACK
>SEGMENT rbs_xyz is the command if you use Oracle 7
>
>Gerd Kock
>info_at_gerd-kock.nospam.de
>
>
>
>On Fri, 12 Nov 1999 20:00:53 GMT, Greg Stark <greg-spare-1_at_mit.edu>
>wrote:
>
>>
>>We have a largely OLTP database driving a web site where I imagine discrete
>>transactions would be a really big win. However there are occasional queries
>>that do full table scans to generate reports or queries. Will enabling
>>discrete transactions cause those queries to break completely? (with "snapshot
>>too old")?
>>
>>Or is there a strategy for dealing with this -- only using discrete
>>transactions when no big queries are running, for example. And if I enable
>>"discrete_transactions_enabled" is that all I need to do or do I have to
>>change every sql call to make it a discrete transaction and fall back to
>>normal transactions?
>>
>>--
>>greg
>
Received on Sat Nov 13 1999 - 05:06:28 CST