I don't think it's a lock problem for your record. Much more likely is a data 
problem. Also a possibility is file corruption. Third thing that pops to mind 
is the program that does the update encountering a weird condition that sends 
it into a rarely used set of instructions.
 
I'd also look for a null (or weird, or incorrect) value in a foreign key. I 
once worked at an HMO where somebody somehow created a null vendor record. So, 
every doctor who didn't have a vendor record had a null in that field, and this 
little 4-doc practice, the null vendor, was getting checks for $2-5M every 
month. You'd think they'd be happy, but they actually were a bit freaked out 
about it.
 
What generates the order number? Are there conditions where that logic can fail?
 
This sounds like an excellent opportunity to use the debugger. Set a break 
point in the program, and step through, examining the variables as you go. Pay 
special attention to whatever generates/assembles the order #.
 
> From: micha...@plumbersstock.com
> Date: Wed, 2 Feb 2011 17:35:48 -0700
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] How to find and fix a broken lock?
> 
> I don't see it listed. Here is what it did return. I'm looking for entity
> 40936.
> 
> 
> >list.readu every
> 
> Active Group Locks: Record Group Group
> Group
> Device.... Inode.... Netnode Userno Lmode G-Address. Locks ...RD ...SH
> ...EX
> 2686979 462014 0 53135 5 IN 10D000 1 0 0
> 0
> 2686979 7005 0 53135 24 IN 4800 1 0 0
> 0
> 655364 4098 0 57139 26 IN 1 1 0 0
> 0
> 2686979 462014 0 53135 31 IN 23A000 1 0 0
> 0
> 2686979 154 0 40639 42 IN 600 2 0 0
> 0
> 2686979 7039 0 40789 59 RD 5AAE000 0 1 0
> 0
> 2686979 154 0 44775 64 IN 1600 1 0 0
> 0
> 2686979 154 0 53135 80 IN 1000 1 0 0
> 0
> 2686979 462014 0 53135 81 IN 521000 1 0 0
> 0
> 2686979 462014 0 53135 81 IN 5E3000 1 0 0
> 0
> 
> Active Record Locks:
> Device.... Inode.... Netnode Userno Lmode Pid Login Id
> Item-ID.............
> 2686979 462014 0 61405 5 RU 528386 eclipseB
> %WEB.PH.SESSION.MONITOR
> 2686979 7005 0 57139 24 RU 368822 eclipseB
> FAX.FEEDBACK3
> 655364 4098 0 57139 26 RU 368822 eclipseB fax_feed3
> 2686979 462014 0 52985 31 RU 471274 eclipseB
> WIDGET.PHANTOM
> 2686979 154 0 40639 42 RU 1302770 eclipseB
> JOB.SCHEDULER
> 2686979 154 0 65263 42 RU 1179848 eclipseB
> TC.TIMESHEET.PH.SERVER
> 2686979 154 0 44775 64 RU 512250 eclipseB
> SOCKET.PH.SERVER
> Press any key to continue...
> 2686979 154 0 53135 80 RU 1683466 eclipseB
> SYSTEM.ADMIN
> 2686979 462014 0 65461 81 RU 557096 eclipseB
> THREAD.MANAGER
> 2686979 462014 0 52973 81 RU 1061074 eclipseB
> MSG.PH.SERVER
> 
> 
> 
> Thanks,
> Michael McGlothlin
> 
> 
> 
> On Wed, Feb 2, 2011 at 5:18 PM, Dan Fitzgerald <dangf...@hotmail.com> wrote:
> >
> > What does the TCL command LIST.READU EVERY return?
> >
> > Do you see that customer # or order # in there?
> >
> >> From: micha...@plumbersstock.com
> >> Date: Wed, 2 Feb 2011 16:26:18 -0700
> >> To: u2-users@listserver.u2ug.org
> >> Subject: [U2] How to find and fix a broken lock?
> >>
> >> I'm not greatly familiar with Universe but I have a background in
> >> programming and Unix so I hope I can figure this problem out. I have
> >> access to AIX and DataVu Query.
> >>
> >> We use Activant Eclipse which seems to be built on Universe and their
> >> support is completely useless. Their technical support keeps blaming
> >> our problem on a network issue which doesn't even make sense and their
> >> networking department has already proven isn't the issue. We've been
> >> working with them on the issue for more than a month without progress
> >> so I need to find another way to fix the issue.
> >>
> >> We have a process that takes a customer id and some order parameters
> >> and pushes an order into the system and returns the resulting order
> >> number or an error. Our problem is that for a certain customer that we
> >> use a lot is that it allows the order to be pushed in, without
> >> failing, but does not return an order number or an error. Orders from
> >> other customers work as expected. Originally the problem started when
> >> we were pulling a report for that customer with their order history -
> >> which failed. To me this suggests that someplace there is a lock in
> >> place for that customer that hasn't been removed or something of that
> >> nature. Any ideas how I could look for this or fix it?
> >>
> >>
> >> Thanks,
> >> Michael McGlothlin
> >> _______________________________________________
> >> U2-Users mailing list
> >> U2-Users@listserver.u2ug.org
> >> http://listserver.u2ug.org/mailman/listinfo/u2-users
> >
> > _______________________________________________
> > U2-Users mailing list
> > U2-Users@listserver.u2ug.org
> > http://listserver.u2ug.org/mailman/listinfo/u2-users
> >
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users
                                          
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to