Post reply

Memory Error - Failed to reserve contiguous memory

  • November 22, 2002 at 4:06 am

    #159068

    I had the following warning in the sql log file 'WARNING: Failed to reserve contiguous memory of Size= 65536'. (SQL 2000 SP2)

    Having looked on Google groups I see this 'generally implies that there is insufficient contiguous free memory in the MemToLeave area'

    Does anyone know if there an alert condition which I can use to monitor this 'MemToLeave' area?

    thanks

    Steven

    Steven

  • November 22, 2002 at 5:17 am

    #442085

    Not that I am aware of. However this should have been fixed from what I recall in SP2. Are you sure something installed afterwards did not break SP2 in some way? Also, how often does this happen and have you checked both SQL Logs and Event Viewer logs to see if anymore details have been otuput to one of them?

  • November 22, 2002 at 5:22 am

    #442086

    I have the post sp2 hotfix Q314003 installed on that server.

    Happened lots of times over an hour, then its was okay. That server does run lots of DTS jobs using the Oracle OLE-DB provider.

    That may be the cause, but no way to know at the moment.

    Steven

  • November 22, 2002 at 5:32 am

    #442088

    If you think it is that then keep and eye on next time would occurr. If same thing occurrs you might try reinstall SP2 and see if goes away, if so then add the hotfix back and if returns report immediately to MS as a break in the hotfix. Otherwise may be something with the Oracle Driver in some way and you need to update the Oracle one instead (might try that first thou).

  • November 22, 2002 at 5:36 am

    #442090

    Thanks anyway.

    I had already concluded all I could do was keep an eye on it, hence the question about moniting it.

    I have to have the hotfix installed or the CRM software won't work. Roll on SP3.

    Also I'm looking at using the MS provider rather than the Oracle one.

    Steven

  • November 22, 2002 at 5:43 am

    #442091

    Understandable about the hotfix. Curious and may test the hotfix to see if is breaking at some point.

    Just a heads up. As for the MS Provider, if you are using later than Oracle 7 or maybe 8 then you have to be carefull of unknown datatypes. There were datatypes introduced by Oracle that the MS rovider does not handle, nor is MS going to undate that provider.

  • November 22, 2002 at 5:56 am

    #442093

    Using 8i , went for the oracle one because we are running oracle stored procedures.

    If you do manage to break it, update the thread.

    Steven

    Steven

  • November 22, 2002 at 6:26 am

    #442098

    Sure will.

  • March 7, 2013 at 10:25 am

    #1594576

    Try to read the following articles:

    http://support.microsoft.com/kb/832674?wa=wsignin1.0

    http://sql-blogs.com/2012/07/09/sql-server-how-can-you-say-its-memory-pressure/

    André CR

  • March 7, 2013 at 10:26 am

    #1594578

    Please note: 11 year old thread.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • March 7, 2013 at 10:47 am

    #1594590

    O.o Sorry

    André CR

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply