I read a post on the Oracle-L yesterday regarding Bug 5458753 where “SQL can execute in wrong Schema”. According to Metalink Note 392673.1, there is a patch currently available for it and the problem should be fixed in 10.2.0.3.
Might not be an issue in most Production environments, but in a shared development environment like ours where developers are using the same object names in different schemas, it could be quite a problem. Imagine issuing a query and getting unexpected results. I mean sometimes you expect the unexpected when developing, but not to this extreme.
I applied patch 5458753 on Friday (20-Oct-2006) and it appears to have resolved the problem in my 10.2.0.2 installation on Solaris 9 (64-bit).
I actually reviewed Metalink Note 391116.1. The way I understand it, the problem is expected to be fixed when 10.2.0.3 is released. Guess we’ll have to wait and see for sure.