The Scenario Pattern Is Not Appearing In The KDD_PTTRN Table. (Doc ID 2908758.1)

Last updated on APRIL 24, 2023

Applies to:

Goal

A TBAML scenario pattern is not appearing in KDD_PTTRN table after applying the BD patches. Previously, the BD version was 8.0.8.0.0 and after applying patches on UAT, in order to resolve some product defects, the BD version upgraded to 8.0.8.1.0.
We've just upgraded the UAT environment as of now and our production servers are still on version 8.0.8.0.0. For the better understanding, I'll be sharing the results of both, The Pre-Installation (from Prod Servers) and Post-Installation (from UAT Servers) of the patches.

We've a TBAML scenario (scnro_id = 118860008) whose pattern is not available in KDD_PTTRN table in our UAT env (8.0.8.1.0 version) but the pattern (pttrn_id = 118860009) is available for the same scenario in our prod env (8.0.8.0.0 version) so it is clear that the changes are made by the patches applied.

Furthermore, when we run the below query in our UAT env (8.0.8.1.0 version), the kdd_pttrn_dataset include datasets of two different scenarios i.e. scnro_id=118860008 & scnro_id=118860014 having same order numbers which will cause errors while job execution.
select * from kdd_pttrn_dataset where pttrn_id = 118860009;

Solution

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