Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 7 of 7 total |
Weird problem with restricted transactions |
Wed, Nov 1 2006 4:09 PM | Permanent Link |
"Jose Eduardo Helminsky" | I have been playing with a very weird problem (at least for me) with
transactions. I have an application running on a customer with around 30 users. It is running DBISAM 4.22 b4 using C/S hosted at Win2003 with 1G Ram and HD Sata. All workstations are XP SP2. It is running since Jan/2005 without any problems except some normal freezing when users start a transaction/commit routine. Trying to solve the problem I´ve changed the transactions to restricted transactions. After that it shows a transaction lock error (#10224) in random situations. If I remove restricted transaction and put back to ALL tables transaction the problem disapear. I don´t know from where I have to start looking to find the problem. Could someone drive me ? Thanks. Eduardo |
Wed, Nov 1 2006 7:48 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eduardo,
<< Trying to solve the problem I´ve changed the transactions to restricted transactions. After that it shows a transaction lock error (#10224) in random situations. If I remove restricted transaction and put back to ALL tables transaction the problem disapear. >> Did you modify the TDBISAMEngine.TableTransLock* settings at all ? -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Nov 2 2006 8:39 AM | Permanent Link |
Jose Eduardo Helminsky | Tim
<< Did you modify the TDBISAMEngine.TableTransLock* settings at all ? >> The application has at Datamodule create a following code but I think it doesn´t do anything in C/S mode. with Engine do begin MaxTableDataBufferSize := MaxTableDataBufferSize * 4; MaxTableDataBufferCount := MaxTableDataBufferCount * 4; // Some to Index and BLOB CreateTempTablesInDatabase := True; TableMaxReadLockCount := 10; TableTransLockRetryCount := 3000; end; The server is a stock version of DBSRVR. Last Monday I´ve been at customer site and can see the error happening but it is almost impossible to create a code to reproduce. As I told before, without restricted transaction the problem does not exist. It is very weird. As I know, the locks are placed in the DBISAM.LCK, ok ? Other doubt, a restricted transaction involving ALL tables in the database run the same code as a non-restricted transaction ? Or at least perform the same tasks. Eduardo |
Thu, Nov 2 2006 10:49 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eduardo,
<< The application has at Datamodule create a following code but I think it doesn´t do anything in C/S mode. >> Correct. << Last Monday I´ve been at customer site and can see the error happening but it is almost impossible to create a code to reproduce. As I told before, without restricted transaction the problem does not exist. It is very weird. >> Is it only this customer that is having the problem with restricted transactions ? << As I know, the locks are placed in the DBISAM.LCK, ok ? >> Yes. << Other doubt, a restricted transaction involving ALL tables in the database run the same code as a non-restricted transaction ? Or at least perform the same tasks. >> Basically, yes. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Nov 3 2006 6:33 AM | Permanent Link |
Jose Eduardo Helminsky | Tim
<< Is it only this customer that is having the problem with restricted transactions ? >> Yes, fortunately. I have other customers using restricted transactions without problems, instead of, with very good answers from DBISAM. When I changed to restricted-transactions, the freeze problem disapear. As I told before, I don´t know from where I have to start. Eduardo |
Fri, Nov 3 2006 7:14 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eduardo,
<< Yes, fortunately. I have other customers using restricted transactions without problems, instead of, with very good answers from DBISAM. When I changed to restricted-transactions, the freeze problem disapear. As I told before, I don´t know from where I have to start. >> Is there more than one application accessing the database tables, or is it 100% client-server with only the database server accessing the tables ? -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Nov 4 2006 6:17 AM | Permanent Link |
"Jose Eduardo Helminsky" | Tim
<< Is there more than one application accessing the database tables, or is it 100% client-server with only the database server accessing the tables ? >> It is 100% C/S with just one application accessing the data. I am investigating a SQL (unoptimized) that run against a locked table, after that I edit the table using a table component just before the COMMIT. Eduardo |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |