Adaptive Server cannot process one or more ocm_lock requests because:
Another lock request is holding the lock
In this situation, a high value indicates there are numerous exclusive lock requests that need to perform heavy operations without losing the ocm_lock. This is an internal issue.
To improve performance, determine why Adaptive Server is holding the lock for so long.
Another request is pushing the data.
In this situation, a high value may indicate that data resides only in memory and Adaptive Server must regularly push this data to other nodes to avoid loosing data in the case of node failure. This adversely affects performance because Adaptive Server performs no useful work while it is pushing the data to other nodes. This is an internal isssue.
To improve performance, determine why Adaptive Server is holding the lock or pushing the data for so long.
A canceled transaction is pending (the requested data is probably not being delivered, and the OCM on this node is taking corrective action).
This wait event is rare (usually when an instance is expecting data from a node that just crashed). A high value for this wait event may result from a high rate of node or hardware failure.
