topic Re: Error occured while doing full load in Qlik Replicate

Error occured while doing full load

Megha_More — Fri, 24 Mar 2023 07:16:10 GMT

Hello team,

We faced following error while moving data from SQL to postgres .

RetCode: SQL_ERROR SqlState: 42000 NativeError: 701 Message: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is insufficient system memory in resource pool 'default' to run this query. Line: 1 Column: -1

What will be the reason behind this.

Thanks,

megha

Re: Error occured while doing full load

Steve_Nguyen — Fri, 24 Mar 2023 12:25:00 GMT

@Megha_More

The error could be many think.

1. what is the Replicate server memory size

2. what was the exact query that was running that cause the memory usage.

3. how many table are on that task

4. does the tables in the task have LOBS

5. have you test on smaller table to check if the issue exist with small table ?

Re: Error occured while doing full load

Heinvandenheuvel — Sat, 25 Mar 2023 14:37:09 GMT

- This is 99.99% sure to be a SQLserver issue where things like Replicate Server memory are irrelevant. Involved your source DBA!

- This is likely to be a VIRTUAL memory issue, not physical, or it could be 'total confusion - as suggested by the 'line 1, column -1'. Check out https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/performance/701-error-large-batches - it mentions DBCC MEMORYSTATUS

- Did it ever work?

- Is there a TABLE associated with the error ? If there is no immediate name on the message use the THREAD NUMBER from the line with the error, to look back (NotePad++ 'find all in current document') to see what happend prior, and how long ago.

- How quickly does the error come up - right after starting the task? After hours of running, Gigabytes transferred?

- Does it come up right after a particular table is started, or deep into a particular table? For clarity you may want to run the task configured to SINGLE load stream.

- Assuming it is triggered by a specific table, what is special about it? LOBS? Computed / linked columns? Maybe drop some suspect columns from the replication request. Are you using filters or passthru queries?

- Activate logging for SOURCE UNLOAD level TRACE to see the queries used. Execute those in SMSS studio and hopefully get more complete messages?

Good luck,

Hein.

Re: Error occured while doing full load

Barb_Fill21 — Sun, 26 Mar 2023 19:36:54 GMT

HI @Megha_More

I would also show this error to the SQL Server DBA. I agree with @Heinvandenheuvel that this is probably a Sql Server issue. I recommend as well to answer @Heinvandenheuvel 's question to give us more information about the issue.

Thanks

Barb

Re: Error occured while doing full load

Megha_More — Thu, 30 Mar 2023 09:25:22 GMT

Hi Team,

Thanks for the responses. Error resolved after doing full load again by cross checking all the connections.

Thanks,

Megha.