Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Progress 10.2B08 Solaris 11
We started receiving this error in the database log continually, along with clients being disconnected immediately afterwards:
SYSTEM ERROR: lkrels record 0 not locked
Clients were reporting this error:
Disconnect from server, server received invalid message code (2661)
Unable to commit the transaction in one database. (1417)
Disconnecting from database prod, user number 1809. (9545)
Certain database tables were showing very high and unusual read activity while the errors were occurring.
Restarting the DB broker stopped the error and all went back to normal.
We have a case open with support, but was wondering if anyone had seen this and might know the root cause?