CMT COME_ENTR_NO_OBJ_DB Issue For Come_estb_account_profile_t, come_account_profile_t
(Doc ID 2018170.1)
Last updated on OCTOBER 09, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Goal
On : 7.5.0.6.0 version, Conversion Manager
BRM migration has two step process, the import step and the deploy step.
During the import step, the user always provides the staging DB number as 9 which is the number on the XML tags COME_ENTR_NO_OBJ_DB,
e.g.
Why the DB number is still 9 for come_estb_account_profile_t and come_account_profile_t after CMT deploy step?
Solution
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
Goal |
Solution |