Stuck Threads on OSM database: UPDATE OM_RULE_DEF SET STATUS = 'CACHED'
Last updated on JULY 19, 2016
Applies to:Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
This is a performance issue. Under certain conditions, the status in om_rule_def is set to CACHED. In some cases (mainly in failure scenarios),
several threads attempt to so that concurrently causing contention in the DB, such as row-lock waits. The issue is worse on Oracle RAC.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms