We are frequently getting an error: Memory could not be allocated after upgrading the application from 10g to 11g.
Oracle Database is upgraded from Oracle 10g (10.2.0.4.0) to Oracle 11g (184.108.40.206.0).
Oracle.DataAccess.dll version is upgraded from 10.2.0.100 to 220.127.116.11. This comes as part of the installation of ODP.Net
StackTrace is as below:
ex.Message Memory could not be allocated Trace at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck)
Does anybody have any idea on this issue?
Thanks in advance..
ODP.NET 10.2 was first released in the mid-2000s, which means a lot of functionality has been added since that time. There's nothing that comes to mind that adds a significant amount of memory usage between ODP.NET 10.2.0.1 to 18.104.22.168. If you didn't make any changes in your user population size nor your code that would add significant new memory requirement, then perhaps you're experiencing a memory leak.
You could test a stable load on your machine and see if the memory usage stays stable over time. If so, then it's unlikely to be a memory leak and the solution is to just add more memory or another mid-tier machine to handle the load. If the stable load generates constantly growing memory usage, then it's more likely to be a memory leak. You can try to diagnose where this leak originates yourself or have Oracle Support help you diagnose it. Based on the diagnosis, one can see if there's an existing Oracle or Microsoft patch that could fix the problem.
I saw some weird behavior in an application that had been built against Oracle 10, where the client was updated to 11 but the application wasn't rebuilt. Never figured out exactly why it did that, but changing the references to 11 fixed it.
You could try rebuilding the application with references to 11 and see if that makes it happier.
I don't think this problem had a bug number associated with it. So, I can't say for sure if it was ever resolved. Nonetheless, if you're running into the problem, upgrade to the latest Oracle ODP.NET patch to see if you're still hitting the problem. If you are, I would recommend working with Oracle Support to diagnose the memory issue and get the problem fixed.