Correlations not Working After Migrating to Version 12.2.1.x (Doc ID 2724016.1)

Last updated on FEBRUARY 14, 2023

Applies to:

Symptoms

After migrating from 11g or 12.1.3.0 to a 12.2.1.x (for example, 12.2.1.4) environment any communication using correlations to pre-existing instances failed, while instances created in the new version worked normally.  This could also affect event subprocesses and other designs that use correlations.

There will be no exceptions in the logs to help identify the problem.  The only way to identify it is to check the DLV_SUBSCRIPTION table, find the listening event for the correlation, check the CONV_ID column and compare it to the CONV_ID column of the DLV_MESSAGE table and see if they match.  If they had the same correlation value then they should have a matching conv_id.  If the conv_id doesn't match then this issue is the likely cause.

Query to DLV_SUBSCRIPTION table:

 In the previous logs, the value MD5{<md5-code>} must match with the conv_id stored in the DLV_SUBSCRIPTION table for the instance we want to correlate with.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.