This content has been marked as final. Show 2 replies
Now, I am found the reason...
ROW-00001: Can not allocate memory. (11g client can give some information before crash...)
One of our recordset swallow up almost all the memory and the next recordset open failed.
It is a narrow recordset (narrowed because of Oracle), only 3 navigator column in it, but the row count is hight.
We can not narrow it any more.
Can we set the client, to can receive this recordset without crash?
Even if it need 11g client?
Without knowing whether you're out of memory due to some sort of leak or not it's hard to make a good suggestion. I'd certainly recommend trying the latest 11203 oledb provider/client to rule out any sort of known issue provider leak/malfunction.
Short of that, if you're really just trying to stuff too much into memory, you might look into the lowering the fetchsize or changing the CacheType setting..
Hope it helps,