May 27, 2004 at 7:19 am
Anyone know of a fix for this error (other than using the oracle provider).
Its is running on SQL 2000 SP3a running MDAC 2.71a.
OLE DB provider 'MSDAORA' reported an error. The provider ran out of memory.
[OLE/DB provider returned message: Out of memory.]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IRowset::GetNextRows returned 0x8007000e: The provider ran out of memory.].
thanks
Steven
May 28, 2004 at 11:48 am
Check out this article
http://support.microsoft.com/default.aspx?scid=kb;en-us;268520
June 1, 2004 at 1:13 am
Thanks, but I had found that artitle and it relates to SQL 7 not 2000, hence the server doesn't use the dll versions mentioned in the article.
Steven
June 1, 2004 at 6:40 am
Hi,
My 2 cents.. Does the Oracle table contain a numeric field? If so what is the precision? I can't remember the "cut off" precision that the provider can't handle. But a precision of 30 cannot be handled.
If there is a numeric column in Oracle sometimes converting the numeric column to a nvarchar in the select statement overcomes this issue. M
Andy.
June 1, 2004 at 6:43 am
Thanks I'll take a look
Steven
June 1, 2004 at 7:02 am
Had that error too on an Oracle linked server, and was able to ask about it at a SQL Server Connections conference recently. The memory management instructor recommended that I add the -g startup parameter on the box (which I did on a test box first), and it fixed my problem and the error went away. (See Using Startup Options in BOL.) I used -g384 on a server that has 2.5 GB RAM.
Linda
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply