Marlene DeNardi
New Member
We have a progress V9.1D, QAD 9.1 database. We are having preformance issues and while monitoring I see the following symptom:
In promon R&D I see high numbers of locks for users, when I called one user she was not running anything. So, I had her log out - the locks went away, I had her log back in she immediately showed up with 7 locks, I had her run a short report she went to 312 locks and stayed there, had her re-run report went to 594 locks, re-run went to 601 this keeps going up to she has hundreds of thousands of locks which stay there until she logs out. Now, I have looked over this code several times and it is written with NO-LOCK statements everywhere. The only other thing code wise I see is it uses temp-tables which per Dan Foreman's book causes preformance issues. I have to wonder if this is the problem - or something else since the minute she logs in she shows up with locks. I have many users who appear to be doing the same thing. Any ideas?
In promon R&D I see high numbers of locks for users, when I called one user she was not running anything. So, I had her log out - the locks went away, I had her log back in she immediately showed up with 7 locks, I had her run a short report she went to 312 locks and stayed there, had her re-run report went to 594 locks, re-run went to 601 this keeps going up to she has hundreds of thousands of locks which stay there until she logs out. Now, I have looked over this code several times and it is written with NO-LOCK statements everywhere. The only other thing code wise I see is it uses temp-tables which per Dan Foreman's book causes preformance issues. I have to wonder if this is the problem - or something else since the minute she logs in she shows up with locks. I have many users who appear to be doing the same thing. Any ideas?