CM Is Not Up When Config_taxs_t.rec_id With Migrated Big Tax_supplier_id_id0
(Doc ID 1957055.1)
Last updated on APRIL 19, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
There has been an BRM upgrade from 7.0 to 7.5. During upgrade, config_taxs_t.rec_id is set with the original 7.0 tax_supplier_id_id0 which is a big value(13756915559).
When starting cm, cm start failed.
Error in cm.pinlog:
Also expecting, since event_t.tax_supplier also references config_taxs_t.rec_id, robj - DB /event xxxxxx could also fail.
Changes
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 |
Changes |
Cause |
Solution |
References |