Originally posted by ngdh
This incident has only happened once so there is no pattern to confirm.
Does this means that with out touching the configuration/parameter file it just work fine?

Originally posted by ngdh
Apologies if I was too brief in my original information but since the hash area size refers to PGA for a process I didn't think SGA was patricularly relevant.
yes you're right, but I only brought that up thinking that the problem was recurring. And just being curious of how do you manage your physical memory.

Originally posted by ngdh
Also since the error refers specifically to a process memory shortage I didn't feel CPU usage at the server level was poignant either.
again you are right, and the only solution to your problem is what tamil have already told you. Haven't you change the value of
HASH_MULTIBLOCK_IO_COUNT and HASH_AREA_SIZE and yet your problem just didn't reoccur again? I don't think so.

But going back to your concern regarding the comment of your colleague about "clashing transaction", I believe this program/query was just use lately, and it will be easily accepted if the real occurence will just be brought up to contradict the "clashing transaction" theory. And that is letting them know that the server needs reconfiguration.