Kbase P95919: Database crashes with error 3723 while running online proutil utilities
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2008 |
|
Status: Verified
SYMPTOM(s):
Database crashes
mtusrwake: wrong queue, usr <num>, queue <num>, waiting for <lock>. (3723)
Usr 45: mtusrwake: wrong queue, usr 46, queue 1, waiting for 5. (3723)
The usernum associated with the 3723 message is running an online proutil utility
The usr referenced in the 3723 error message is also running an online proutil utility
Database goes through crash recovery correctly when restarted
FACT(s) (Environment):
Progress 9.1D
OpenEdge 10.1A
All Supported Operating Systems
CAUSE:
Bug# OE00075923
CAUSE:
This behavior doesn't indicate corruption or damage to the database, but that the shutdown was a result of us trapping the potential problem. The error 3724 describes a race condition/ congruency issue and is a rare occurrence, occasioned upon in prior releases as described in Progress Solution 21276.
In this case, it is caused by running the same or more than one of the database online utilities at the same time, against the same database, which use index admin locks AND recwaits and rgetlock waits. (eg: dbanalys, tabanalys, idxanalys, idxfix, tablemove, idxmove)
In most cases, when these utilities run concurrently, they complete without incidence - but in one rare case it causes the releaser of the admin lock for index 0 to have a problem with which user should legitimately wake up for the record admin lock they are waiting on.
FIX:
Either ensure that you're only running one instance of the online proutil at any time, or apply Progress 9.1D09, OpenEdge 10.1A01 or later where this particular instance has been addressed.