It means what it says. One process is trying to access a certain table, and is locked out by the DBMS by another process. Click the message away and try again. You get that message because the table lock takes longer than the value in the 'Lock Timeout' value in your database setup.
It means what it says. One process is trying to access a certain table, and is locked out by the DBMS by another process. Click the message away and try again. You get that message because the table lock takes longer than the value in the 'Lock Timeout' value in your database setup.
I have met this issue and tried to put a higher value but it didn't change anything : no matters if I put 10 or 50000 the lock message appears immediately.
It seems that it is an issue between NAV 5.0 and SQL 2005. Could anybody confirm ?
In SQL you actually don't get a message until the lock timeout occurs. You will get an hourglass until the locktimeout has been reached then you will get a message. This is getting into a pretty complicated subject but you can monitor locks in the session table to see who is locking who and for how long.
We have our lock timeout set to 120 sec's. If it is set to 10 seconds you might have postings fail more often becasue the lock timeout will be reach more often. If you set your lock timeout to 50000 you would have an hourglass for a really long time! You can also set the value to zero so there is no lock timeout at all.
You get that message because the table lock takes longer than the value in the 'Lock Timeout' value in your database setup.
I just don't think that DuyGiang has the same issue, becasue he says he's getting an error immediately, so that would mean it's something else than lock timeout.
It means what it says. One process is trying to access a certain table, and is locked out by the DBMS by another process. Click the message away and try again. You get that message because the table lock takes longer than the value in the 'Lock Timeout' value in your database setup.
Is it possible to increase the 'lock timeout '?
I've a native database 2.60B can you tell me the right method to increase ?
The SQL message is wrong BTW. The message is a table lock but it actualy means that a single row or resource is locked and cannot be locked by another process.
Comments
RIS Plus, LLC
Is it possible to increase the 'lock timeout '?
RIS Plus, LLC
I have met this issue and tried to put a higher value but it didn't change anything : no matters if I put 10 or 50000 the lock message appears immediately.
It seems that it is an issue between NAV 5.0 and SQL 2005. Could anybody confirm ?
RIS Plus, LLC
We have our lock timeout set to 120 sec's. If it is set to 10 seconds you might have postings fail more often becasue the lock timeout will be reach more often. If you set your lock timeout to 50000 you would have an hourglass for a really long time! You can also set the value to zero so there is no lock timeout at all.
jwilder@stonewallkitchen.com
RIS Plus, LLC
I've a native database 2.60B can you tell me the right method to increase ?
Thanks
The SQL message is wrong BTW. The message is a table lock but it actualy means that a single row or resource is locked and cannot be locked by another process.