Hi,
I found that this problem is not there in other instances. But, I am not sure what is the difference between this and other instances. We have not applied any DB patches recently on any instances.
Can you think of any db parameter that can be causing this issue?
Thanks,




Reply With Quote