we migrated our 9.0.1 to a 11.7.3 SQLBase version.
We made to download from the 9.0.1 and the load to the 11.7.3.
But we are experiencing frequently locks to the tables that are not resolved with the consequences that lot of user are in blocked state. The result is that the DB crash itself..
We set the parameter cmdtimeout and we set it to 300 but without success.
Someone has already had this problem with this version?
as it has solved?
Thanks you all
Yes, please include the fail.sql file. Also please send us the sql.ini file for the server. Zip them both up.
What isolation level are you using?
Please note that there is a fix in the 11.7 SP4 for an issue where a 'timeout' is sensed as a 'deadlock', which is different than in prior versions. I would recommend that you download that version from our Product Downloads website and install it.
http://www.guptatechnologies.com/Servic ... loads.aspx
Expand the SQLBase section and then download the appropriate version (32-bit or 64-bit).
A couple of questions:
1. What isolation level are you using?
2. How is the connection made? TCP/IP, npipe? To confirm, start up the SQLBase console and set the display level to 2. Now look at the connections. You will see a 'transport' column. What does that say?
3. How many users do you have connected at the same time?
4. What is your OS?
5. What version of SB are you using? 32-bit or 64-bit?
I can see a couple of possible problems with the sql.ini file, but will wait to hear back from you on the above before making suggestions.
The fail.sql file shows that something has caused the server to terminate (apparently outside of the SQLBase engine itself - no idea about this; check the service logs, which might show more), thus the 1312 error and then there was a rollback problem, i.e. the transaction could not be rolled back (probably because the engine was in the process of terminating). This would have rolled back OK after the server was brought back up and connected to.
readonly=0 <-- Uncomment this line. This will turn off the history file that could be causing some of your problems
cache=256000 <-- Try this value. Combined with the turning off of the history file, this could do wonders.
;Sortcache=10000 <-- Remove this line! It is not valid for this version and is not used like previous versions.
;disablelogspacecheck=1 <-- No longer necessary
NamedPipes=No <-- To remove any possible connection attempts with npipe before choosing TCP/IP
transports=tcp,npipe,apipe <-- To remove any possible connection attempts with npipe before choosing TCP/IP
Hope that one of these setting changes helps you out!
into our SQLBase consolle we have ever some clients with X-Locks (also negative ??) but, under LOCKS section the locks is not present.
Attached the situation that we have
Yes, please attach the fail.sql file (zipped up).
The negative x-locks are really meaningless. It's more of a history thing since the transaction is not active and SQLConsole might not be that accurate with the latest versions of SB. That is a *very* old application.
Who is online
Users browsing this forum: [Ccbot] and 0 guests