This content has been marked as final. Show 5 replies
I guess you can get some help here...1 person found this helpful
My experience of this is that any problem in a RAC would have been a problem single instance, too. However, some things that you can get away with single instance MUST be fixed in a RAC.1 person found this helpful
An example of the first is the sequence issue: contention for a well designed sequence will be no worse in a RAC than single instance. If scalability is a problem in one environment, it will be a problem in the other.
An example of the second is ASSM. Freelist contention is bad single instance, and it may be worse in a RAC. Therefore conversion to ASSM should be on your to-do list as part of the move to RAC. But then, it should be on the list anyway.
That's always a good question. Rac and sequences has a seriosly content do discuss..1 person found this helpful
I always try to use NOCACHE + NOORDER as mentioned on the MOS NOTE: ID 853652.1 The default is CACHE + NOORDER and has the least performance impact on RAC.
HOwever, each app has your own characteristcs to use sequence, so the best way is always take the subject with the app team.
>1 person found this helpful
I always try to use NOCACHE + NOORDER as mentioned on the MOS NOTE: ID 853652.1 The default is CACHE + NOORDER and has the least performance impact on RAC.Victor, this has yo be a typing error: NOCACHE is disastrous for single instance, even worse in a RAC. Always cache, and cache a lot: the default of 20 is too low, got for a 200000 perhaps if you are issueing millions a day.
Yes... sorry.. CACHE + NOORDER....1 person found this helpful