PEGGING_ID Not Unique Across ASCP Plans (Doc ID 2371735.1)

Last updated on AUGUST 17, 2022

Applies to:

Goal

After upgrading from VCP 12.2.3 to 12.2.6, noticed an issue with uniqueness of PEGGING_IDs. Was able to maintain uniqueness of PEGGING_IDs across plans in 12.2.3.
However, in 12.2.6, noticed the reuse of PEGGING_IDs across plans. The PEGGING_ID is unique within a given plan though. This makes sense according to the setup of the sequence.
It appears that the sequence and the index is the same between both releases. The sequence can be recycled after it reaches its maximum value over 2 billion. Therefore, it does not appear to be an issue with the sequence.

Need to confirm the following:

1) Has there been any change to the sequence between the earlier and the current releases?

2) How is uniqueness intended to be maintained? Is it intended to be maintained per plan? Or across all plans? What is the strategy going forward? Do they intend to change the design in a future release? Or is it currently very stable?
The reason why they ask, is because they need to know if they should fix their custom reports, to accommodate the uniqueness only within a given plan (instead of across plans).
They said that this would require some time and labor, which may be ok. They are just wanting to confirm that this is the correct path, and that the design is very unlikely to change again any time soon.

3) Is there a profile or some other instance setup to revert back to the 12.2.3 functionality? Or just to enforce uniqueness across plans?
 

Solution

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