Hello U2Group,
I'm in a trouble with size of the lock table and transaction,
Here is my situation :
- I run a basic program which analyze a order composed of piece
to manufacture. These analyze is done within a TRANSACTION.
- Each piece analyzed result on a set of tasks
- Each task record is store individually into a file OrderTasks
(+ OrderTasksStatusHistory ~ updated via triggers on OrderTasks.)
- For a piece we get +- 20 tasks.
Then when we analyze a big order which contain more than 150 pieces the
transaction contain at least (150x20x2) 6000 records updates .
Ok, my uvconfig settings about locks mngr are
FSEMNUM = 23
GSEMNUM = 499
FLTABSZ = 11
GLTABSZ = 113
RLTABSZ = 79
RLOWNER = 75
Usually, it works good without problem.
But sometime, I get a very large order with 200 pieces and then the
transaction's locks request exceed the capacity of the locks table (+-
> 9000)
I known the solution reside into a escalate the readu lock to a filelock
for my OrderTask /OrderTaskStatusHistory files but ...
Here is my question :
On a isolate subroutine which perform a readu can I check the number of
recordlock already acquired by "me" ?
- 1 - on a central subr to handle READU
- 2 - on a trigger subr
Any idea is welcome....
Regards.
Manu
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
