Ever seen 'The provider ran out of memory.'?

We're having some general OLEDB problems, most have been solved, but

But when I run:

exec SF_Refresh 'SF_PROD', 'Document', 'Yes'

I'm now getting:

--- Starting SF_Refresh for Document
09:20:36: Using Schema Error Action of yes
09:20:37: Using last run time of 2011-08-02 09:55:00
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "DBAmp.DBAmp" for linked server "SF_PROD" reported an error. The provider ran out of memory.
Msg 7330, Level 16, State 2, Line 1
Cannot fetch a row from OLE DB provider "DBAmp.DBAmp" for linked server "SF_PROD".

Any tuning options or ideas about troubleshooting this?
1 person has
this question
+1
Reply
  • The error message indicates a low VAS memory condition with SQL Server.

    1. What version of DBAmp are you running on this server ?

    2. What is the result of the following SQL command:

    Select @@version

    3. Is CLR enabled on this SQL Server instance ?

    4. What other link servers are used on this SQL instance ?

    5. What is the result of the following query:

    exec sf_vasquery

    A SQL instance restart will restore functionality but we need to identify why you are running low on VAS memory. If you are a heavy user of CLR, then that will cause the issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • 1. DBAmp version 2.13.7

    2. Slect @@version:
    Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    3. SLECT * FROM sys.configurations WHERE name = 'clr enabled' returns:

    configuration_id name value minimum maximum value_in_use description is_dynamic is_advanced
    1562 clr enabled 1 0 1 1 CLR user code execution enabled in the server 1 0

    4. Other Link servers connect to Oracle (using Oracle OLEDB driver since the MS Oracle driver tops out at Oracle 8.1) and other SQL Server instances

    5. exc sf_vasquery returns:
    --- Starting SF_VASQuery
    insrt into VASSnaps(TotalAvail, LargestBlock, MultiPage, CLR_Multi, CLR_VRes, CLR_VCmt) Values(8564074252,6693292352,61496,10264,6310588,63260)

    (1 row(s) affected)
    --- Ending SF_VASQuery. Operation successful.

    As a note, we did a clean restart with –g512 option and the resulting error message was still the original one noted.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Since you are a 64 bit SQL Server, VAS memory is not an issue.

    Is this a new or recent DBAmp install ?

    Can you send me a screenshot of the DBAmp.DBAmp provider options (Server Objects/Link Servers/Providers right click on DBAmp.DBAmp )
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned