How to determine which user has a record lock (epicor 9.05.702A)

Yahoo Archive
1
We are a Progress shop as well and just recently has a similar issue. We found the Promon tool to be rather useless because it only tells you the table number that is locked not the table ID. According to Epicor you would have to stop the DB and run more Progress commands to determine what table ID matched the table numbers.

In the end we were able to trace ours back to a bad BPM, specifically one that was missing the no-lock. It took a while to find but we have not had an issue since.

Make sure you check your B1 file as well to see if it needs truncated.

John
2

We just upgraded from Vantage 5.2 to Epicor 9.05.702A (progress) last week.  In Vantage in system management -> utilities you could see which user had the record lock on a specific table.  I need to know how to access this record lock information in epicor 9.05.  We seem to be having an inordinate amount of record-locking issues sicne upgrading and I cannot seem to find where they have hidden the information to view the record locks in Epicor 9.05.

 

I did also submit this to epicor support, but if the response is like the other issues I have submitted, I will be waiting a while and I really need to access this information so I thought maybe someone here would know.

Thanks!

3

Sarah,

 

I haven't seen this functionality in 8.x or 9.x.Â

 

Why do you believe you have record locking issues?

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of sarah.vareschi@...
Sent: Tuesday, April 01, 2014 3:52 PM
To: vantage@yahoogroups.com
Subject: [Vantage] How to determine which user has a record lock (epicor 9.05.702A)

 

 

We just upgraded from Vantage 5.2 to Epicor 9.05.702A (progress) last week.  In Vantage in system management -> utilities you could see which user had the record lock on a specific table.  I need to know how to access this record lock information in epicor 9.05.  We seem to be having an inordinate amount of record-locking issues sicne upgrading and I cannot seem to find where they have hidden the information to view the record locks in Epicor 9.05.

 

I did also submit this to epicor support, but if the response is like the other issues I have submitted, I will be waiting a while and I really need to access this information so I thought maybe someone here would know.

Thanks!

4

Thanks for replying--

1) when our scheduler tries to run global scheduling it sometimes just "hangs" going into the server log we see message "'CommitJob es/SchedEngine.p' Line:59722) Lock wait timeout of 180 seconds expired (8812)"  (I took that as failure to get a record lock after 3 min - and he could get this repeatedly)

2) We have only been live for a week and when our person who does the time/expense entry has been going in to edit the labor transactions (from prior days) she has several times gotten "4GL stop" error (after system seemingly hanging for several minutes).  Most times it is fine, but she has gotten this error enough times in 1 week to give me a cause for concern.  Looking into this error seems to be also related to failure to get record lock.


 

5

OK, so yeah, that's bad.Â

 

Who did your upgrade? Yourself? Epicor consultants? 3rd party?

 

I've seen locking before, but only on earlier versions with SQL server as the DB. Can't say I've ever seen record locking on Progress. Obviously something else is awry, there are many customers on your version without locking problems.Â

 

Good luck and keep the list posted on any headway you may make.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of sarah.vareschi@...
Sent: Tuesday, April 01, 2014 4:12 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] How to determine which user has a record lock (epicor 9.05.702A)

 

 

Thanks for replying--

1) when our scheduler tries to run global scheduling it sometimes just "hangs" going into the server log we see message "'CommitJob es/SchedEngine.p' Line:59722) Lock wait timeout of 180 seconds expired (8812)"  (I took that as failure to get a record lock after 3 min - and he could get this repeatedly)

2) We have only been live for a week and when our person who does the time/expense entry has been going in to edit the labor transactions (from prior days) she has several times gotten "4GL stop" error (after system seemingly hanging for several minutes).  Most times it is fine, but she has gotten this error enough times in 1 week to give me a cause for concern.  Looking into this error seems to be also related to failure to get record lock.


 

6

Epicor did it all for us – they did the Epicor server install and the database upgrade. Of course when we were “testing” we never ran into any of these issues, but most users were not really in there using it all that often.

 

 

__________________________________________________________________________

This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
__________________________________________________________________________

7

Do you have any custom code?  We found some code either did not “RELEASE” the table after use or there was not a “no-lock” placed.  We also have several “custom” pieces that if ran at the same time we where scheduling caused timeouts and locks.  After reviewing code the errors were reduced significantly, but not totally.

 

Brenda

E9.05.702

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of sarah.vareschi@...
Sent: Tuesday, April 01, 2014 4:23 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] How to determine which user has a record lock (epicor 9.05.702A)

 

 

Epicor did it all for us – they did the Epicor server install and the database upgrade. Of course when we were “testing” we never ran into any of these issues, but most users were not really in there using it all that often.

 

 

__________________________________________________________________________

This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. __________________________________________________________________________

8
Progress has a PROMON command that can show locking, but it is not really useful by itself as it shows a table number instead of the table name.  We received something called an "enhanced" locks logger from Epicor support when we were having some lock wait timeout issues that outputs the table name, locking type (exclusive, etc) and if it is caused by an ODBC connection which was the cause of my issue so it helped in our situation.  We had a shop manager querying and updating records using Access (words were exchanged).  Support also included this when we opened the ticket with the lock wait time out..



What is a lock wait timeout?
A lock wait timeout occurs when a process already has a lock on a resource that another process is requesting a lock on, and after a period of time if it can't get a lock it times out.


ANALOGY:
I am requesting the jelly that you are currently using, and after 3 minutes (the default lock wait timeout value in Epicor 9.05) if you still aren't finished with it I just stop waiting so I can do other things.

Should you increase the lock wait timeout?
Going back to the above analogy, if you are still using the jelly after 3 minutes, the odds that you are still using it after 4-30 minutes is pretty high because most of the time you are finished within a few seconds so something is generally wrong if you are still using it after 3 minutes(you can't get the lid open, for example). If I change the amount of time I wait, it just takes longer for me to move on to other things.

In short, we don't generally recommend increasing the lock wait timeout from the defaults because if the client can't get a lock after 3 minutes, the odds are very high that waiting longer would still result in not obtaining the lock.



On Tue, Apr 1, 2014 at 3:12 PM, <sarah.vareschi@...> wrote:

  
<div>
  
  
  <p></p><p>Thanks for replying--</p><p>1) when our scheduler tries to run global scheduling it sometimes just&nbsp;&quot;hangs&quot; going into the server log we see message &quot;<span style="font-size:11pt;">&#39;CommitJob es/SchedEngine.p&#39; Line:59722) Lock wait

timeout of 180 seconds expired (8812)"  (I took that as failure to get a record lock after 3 min - and he could get this repeatedly)

2) We have only been live for a week and when our person who does the time/expense entry has been going in to edit the labor transactions (from prior days) she has several times gotten "4GL stop" error (after system seemingly hanging for several minutes).  Most times it is fine, but she has gotten this error enough times in 1 week to give me a cause for concern.  Looking into this error seems to be also related to failure to get record lock.


 

</div>
 


<div style="color:#fff;min-height:0;"></div>

9
I'm not sure if you have the answer yet. We are live on your version without issues. You did mention Time and Expense entry and locked records so I'm not sure if this is related but it's worth a look. Go into the Shop Tracker and look to see if you have "Old" "Active Transactions".  
10

Catching this mid conversation:

1. YES check for in process activity and end activity.
2. I assume the labor entries are not yet posted? If posted, not editable. I believe you can unpost but not sure how cleanly that impacts GL.
3. Time & Expense introduced an approval layer so even if you haven't set up that flow, you still need to Recall the entry to edit it.
4. If there was a nonconformance qty in the record, you must inspect (pass - back to job wip, fail - to dmr) in order to then edit labor. (Same for a setup with unapproved 1st article inspect pending).

Beyond that, your conversion was likely flawed (bad record) or a bpm has trapped you.

Rob Brown
Versa Products
Sent from Yahoo Mail on Android


From: jsmith@... <jsmith@...>;
To: <vantage@yahoogroups.com>;
Subject: RE: [Vantage] How to determine which user has a record lock (epicor 9.05.702A)
Sent: Wed, Apr 2, 2014 5:25:39 PM

 
<div id="ygrps-yiv-554186945ygrp-text">
  
  
  <p>I&#39;m not sure if you have the answer yet. We are live on your version without issues. You did mention Time and Expense entry and locked records so I&#39;m not sure if this is related but it&#39;s worth a look. Go into the Shop Tracker and look to see if you have &quot;Old&quot; &quot;Active Transactions&quot;. Â </p>

</div>
 


<div style="color:#fff;height:0;"></div></div>