Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 3 of 3 total |
Out of Memory |
Sun, Oct 26 2014 9:10 PM | Permanent Link |
James Summerlin | Getting this error when loading data into a DBISAM table.
[Execute SQL Task] Error: Executing the query "COMMIT FLUSH" failed with the following error: "ERROR [HY000] [Elevate Software][DBISAM] DBISAM Engine Error # 11279 An unknown error ('Out of memory') occurred with the connection to the database server at 'TOTALMDSRV', please check the server log". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. The server tool in DBISAM has memory at a little over 600MB when this occurs and we are inserting about 142,000 rows of data. This error occurs when the COMMIT FLUSH is executed. Any ideas? DBISAM version 4.1. JamesNT |
Sun, Oct 26 2014 11:59 PM | Permanent Link |
Raul Team Elevate | On 10/26/2014 9:10 PM, James Summerlin wrote:
> Getting this error when loading data into a DBISAM table. > [Execute SQL Task] Error: Executing the query "COMMIT FLUSH" failed with the following error: "ERROR [HY000] [Elevate Software][DBISAM] DBISAM Engine Error # 11279 An unknown error ('Out of memory') occurred with the connection to the database server at 'TOTALMDSRV', please check the server log". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. > The server tool in DBISAM has memory at a little over 600MB when this occurs and we are inserting about 142,000 rows of data. This error occurs when the COMMIT FLUSH is executed. Any ideas? How are you executing this exactly? Are you doing a single sql with 142K VALUES lines or something else ? I know we've done that kind of volume (and larger) using table navigation and delphi code with no problems. Straight SQL i believe also uses a transaction all changes would be memory cached until commit so you're potentially looking at double the ram usage so out of memory might be due to that also. The main suggestion would be to split this up and do smaller inserts with commits. The other option might be try the 64bit server so there is a larger memory space available but for that you'd need to be on a lot newer version which might not be an option. > DBISAM version 4.1. Not entirely sure of this version but if it's really 4.1 then we might be talking about something circa 2004-2005 (v 4.10). If so then there has been lot of water under the bridge in terms of fixes etc not to mention the 64bit thing. So it might be worthwhile to try a newer version but again if it's a single 142K SQL insert i would not be surprised if you might need to redesign it anyways (64bit version might be worth a try still). Raul |
Tue, Oct 28 2014 5:42 PM | Permanent Link |
James Summerlin | Upgrading isn't an option since DBISAM came with the application purchased. I guess I'll have to break the data flow up into segments. Pull in by year, I supposed.
FYI - we are using SQL Server Integration Services to enter data into DBISAM. JamesNT |
This web page was last updated on Tuesday, April 23, 2024 at 08:10 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |