Transaction Isolation
We are running 10g (10.2.0.4) on a Windows 2008 r2 64-bit server.
During high concurrency spikes all sessions within our single instance seem to be impacted even though the concurrency is related to an application locking tables on an individual schema. Is there something with Transaction Isolation settings that we need to change to prevent this from happening? Which settings should we be concerned about? We want to prevent the wide spread slow down to all connected sessions.
Please seen the screen shot of the average active sessions graph from oem
JanV