Offer_attribute_t View is not Getting Persisted in Secondary Schemas But is Present in Primary Schema
(Doc ID 2972562.1)
Last updated on SEPTEMBER 14, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
In Oracle Communications Billing and Revenue Management (BRM) version 12.0.0.4 and further, charge offers can be get persisted to offer_attribute_t table.
In a multi-schema setup, it is noticed that the data is not getting mitigated to secondary schemas, but is present in primary schema. How to solve this issue?
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |