Ok. I hate to say that because I prefer Oracle more than others.
But Oracle 10.2.0.2 has a lot of memory leaks which won’t show until you build it on your live Server. The problem is that to starting observing the problem, the database needs to get some workload so it won’t show on a test or train server.
The reason is that there are bugs into this particular release that will threaten your critical systems.
The symptoms where we installed it are as follow:
1) Inability for new users to login to Oracle after a while because new sessions are not properly closed.
This problem can be solved with a tool such as currport. You should be able to see that you got a lot of sessions without a session ID. Oracle is not even able to kill them. Currports fortunately allows us to look into the sessions at OS level and kill the Close_wait sessions.
There are a few actions to take on the server which involve addind new keys in the registry.
2) Impossibility to perform a proper shutdown without Oracle shutting down the service.
3) Oracle shutting down without warning
After looking into the problem and searching on Metalink, I found a list of bug full of memory leaks.
These issues appeared only on this particular release. This means that if you are on Oracle 10.2.0.1, you should skip this version and upgrade to Oracle 10.2.0.3.
Oracle 10.2.0.3 get one problem with bind variable but it’s minor compared to the bugs of 10.2.0.2.
Recent Comments