SQLBase 11.7.3 permanent U-Locks

Discussion forum about all things SqlBase.
Plasti

SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 19 Nov 2015, 16:27

Dear all,

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
Regards

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 21 Nov 2015, 16:04

Dear all,

I can send the fail.sql if you need to check it..... :(

Thanks all in advance for your support

Regards

Mike Vandine

Re: SQLBase 11.7.3 permanent U-Locks

Post by Mike Vandine » 23 Nov 2015, 02:30

Hi,

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).

Best regards,

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 23 Nov 2015, 06:12

Dear Mr. Vandine,

thank you, here attached our sql.ini and fail.sql file.
We already upgrade to the new SP4 but without success.

Many thanks for yor help
Regards
You do not have the required permissions to view the files attached to this post.

Mike Vandine

Re: SQLBase 11.7.3 permanent U-Locks

Post by Mike Vandine » 23 Nov 2015, 06:29

Hi,

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.

Best regards,

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 23 Nov 2015, 08:24

Dear Mr. Vandine,

here our replies:

1) Isolation Level: RL
2) TCPV4
3) More or less 40/45 Users
4) Windows 2003 Server
5) 32-bit

Thank you so much

Regards

Mike Vandine

Re: SQLBase 11.7.3 permanent U-Locks

Post by Mike Vandine » 23 Nov 2015, 10:39

OK, here are a few things I would recommend:

[dbntsrv]
readonly=0 <-- Uncomment this line. This will turn off the history file that could be causing some of your problems
;cache=412500
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=LocalOnly
NamedPipes=No <-- To remove any possible connection attempts with npipe before choosing TCP/IP

[win32client]
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!

Best regards,

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 23 Nov 2015, 11:18

Dear Mike,

ok, thank you, I'll let you know the result

Regards

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 24 Nov 2015, 10:02

Dear Mike, thanks, it seems that your suggestions solved the problem :D
Just one small question, what can we try to set up to try to speed up the system a little bit? maybe the cache?

Mike Vandine

Re: SQLBase 11.7.3 permanent U-Locks

Post by Mike Vandine » 24 Nov 2015, 10:07

You can try popping up the cache= a bit more to see if that helps. I think the thing that did it for you was the readonly=0 setting.

Another suggestion would be to have a look at SQLBase 12.0. Great performance improvements there.

Mike

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 25 Nov 2015, 06:17

Dear Mike,

unfortunately tonight we had a new DataBase shut down again....
Can I send the fail.sql to you again?

Regards

FRBhote
India
Posts: 2176
Joined: 09 Mar 2017, 05:32
Location: Hyderabad, India

Re: SQLBase 11.7.3 permanent U-Locks

Post by FRBhote » 25 Nov 2015, 06:52

Wow. 1312 Transaction terminated. Wonder what that means - never seen that before...

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 25 Nov 2015, 08:24

we really don't know where the problem is, it goes well for 2 days and crash for a table lock.
there is no possible way to prevent the DB goes down throwing out the transaction that is blocking the table?

Plasti

Re: SQLBase 11.7.3 permanent U-Locks

Post by Plasti » 25 Nov 2015, 08:49

Another question,
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

Regards
You do not have the required permissions to view the files attached to this post.

Mike Vandine

Re: SQLBase 11.7.3 permanent U-Locks

Post by Mike Vandine » 26 Nov 2015, 07:39

Hi,

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. :)

Best regards,

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot] and 0 guests