Re: How does schema name affect allocation of PGA memory in dedicated server?

Billy >> > >> My only guess on why Oracle might behave this way is that it is
> >> trying to protect the privacy of data between the different schemas. <<

> This statement is essentially correct.

Beg to differ a tad Mark. The statement implies schema run-time states when in fact it is connection session states.. where a session just happens to use a schema as authentication and for security and default scope.

More a terminology issue than a technical one I realise, but I feel that the distinction needs to be made as there is a single session state irrespective of how many schemas you access via that session. Someone that does not know Oracle may thus interpret that statement incorrectly.
<<

You are correct in that the post mentioned schemas but my response specifically stated that the isolation is by sessions so I am not sure a newbie would get the idea the isolation was by sessions. I made the reference to the IBM transaction managers to show that what Oracle was doing is also done by other vendors but your clarification doesn't hurt. More importantly your last point "bad code/design that will cause similar problems" is dead on the money.

• Mark D Powell --