Orphan Automation Correlations And Context Remain In DB After Task Completion (Doc ID 1151103.1)

Last updated on SEPTEMBER 10, 2012

Applies to:

Oracle Communications Order and Service Management - Version 6.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Sep-2012***

Symptoms

When automated tasks are completed manually in OSM webclient (or in Fire & Forget type interaction between OSM and external systems) then automation correlations/contexts are remaining in the database (om_automation_correlation, om_automation_ctx, etc).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms