lkrela – What OpenEdge 10.1B users need to know and why it matters.
Progress users have come to expect extreme reliability from the Progress DB. This is no accident and has taken much consistent work over many years by the Progress Engine Crew. It is amazing how the Progress DB keeps ticking given what’s thrown at it in the field.
If you aren’t already aware, you should know that something bad has slipped through Progress’ regression tests.
If you are a 10.1B user, especially if you aren’t yet on Service Pack 3, your transactions may be exposed to data corruption. Tom Harris, OpenEdge RDBMS Development, calls it “a bad bug”. In an e-mail to the PEG DBA Forum, Tom has asked for users to “please” use the lkrela startup parameter “if you are running 10.1B prior to service pack 3″.
On OpenEdge versions 10.1B through Service Pack 2 inclusive there are critical bugs in locking that affect how locks are released, which in turn affect transaction consistency.
For your reference, the link to Solution ID is P126982.
While there is a fix in Service Pack 3, until Progress updates its regression tests for this and possibly related conditions, we are recommending to our clients that they keep using the lkrela startup parameter on 10.1B.
Comments
Leave a Reply
You must be logged in to post a comment.
Sponsored by Solvepoint
This blog is sponsored by Solvepoint, a leader in Progress performance tuning, database administration, software development, maintenance and integration. More Information