Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
In some cases of the Multi Schema installation, there is an issue that the class id for some classes in the primary and in the secondary schemas are different.
This causes issues in the scenario's where we store these class id's in to the database (for example event_essentials_t and Virtual Column).
The issue comes up when we use the AMT tool to migrate event from one schema to another or use the new Global Transaction Feature.
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