Get Rid of Show-Stopping Record Locks
Unpredictable blocked sessions irritate users, hurt business performance, and upset management. The worst part – you can’t always pinpoint what or who causes it. In this webinar, we’ discuss the record lock experience from both the user’s and the DBA’s point of view. You’ll learn how to troubleshoot this problem and fix it forever – for FREE. In this 20-minute interactive webinar, you’ll discover…

•   The different types of record locks and what causes them
•   Ways to monitor
•   Ways to troubleshoot sporadic locks that cause a ton of trouble
•   and a FREE utility and instructions so you can fix them forever

Questions from the webinar

Does the utility work on older versions of QAD?
Does this utility work with QAD Cloud?
What is best procedure for ending background Progress processes that are causing locks?
Is this something that is easily installed?
Can this be run from .Net UI?
If our users are using .Net UI, will the report say the record is locked by that user, or will it show a generic produi user?
How can I use the software — it´s outside QAD, correct?
Does it matter what release of QAD/Progress we are running?
Why is it free? You cannot live on air :) What is the business objective behind giving the utility away for free?
Open or Encrypted source?
Is the utility able to detect locks in all databases or just the qaddb database?
Once installed, what process do you use to run the program, etc.?
Where can I download this software?
We have many different and important programs that can use the same tables at the same time. What is your recommendation to eliminate locks in this environment?
Often times the record locks are caused by a barcode scanner’s battery giving out in the middle of a transaction, so that the system doesn’t know when the barcode scanner operator has started a fresh session after changing the battery.

Q: We have installed the utility and it works fine. We are working in a factory environment with warehouse people managing inventory and SO using handheld scanners. Some scanner menu functions create an exclusive lock in a table for a long period of time. Could you build another utility for us that we could hook into a QAD menu that will allow an administrator to easily kill a task if it is blocking QAD?

A: Yes, however killing a session could potentially cause larger issues with data integrity, so we don’t recommend it. This problem definitely sounds like a software bug since tables should only be locked for a short period of time. We would advise you to collect data like the program name(s) and the length of time the tables were locked and report the issue to QAD or your barcode data collection software vendor. They may be able to give you a patch to fix this.

If you don’t succeed with QAD or your barcode data collection vendor, we may be able to write a script that will automatically and gracefully exit a specific table when it is locked for more than a certain amount of time. We can work with you on a time and material basis. We would be happy to offer you the alternative solution of our Data Loaders that will help you manage SOs and inventory efficiently and would not create locks in your system.