Event Data Is Not Migrated Completely Using Pin_amt Utility
(Doc ID 2158468.1)
Last updated on FEBRUARY 01, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.15.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On : 7.5.0.6.0 version, Account Migration Manager (AMM)
Event sub balance impacts at level other than 0 is set with source data even after successful migration of an account from source schema DB1 to target schema DB2.
Ex:
In the below mentioned migrated object, event sub balance impacts at level 1 & 2 is still tagged with source objects instead of the target one i.e. 0.0.0.2
0 PIN_FLD_POID POID [0] 0.0.0.2 /event/delayed/session/telco/come 1445866586921067401 1
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.2 /account 302566950 0
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.2 /service/telco/gsm 302567239 0
0 PIN_FLD_SUB_BAL_IMPACTS ARRAY [0] allocated 20, used 3
1 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.2 /balance_group 302566983 0
1 PIN_FLD_RESOURCE_ID INT [0] 978
1 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 8
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.0 0 0
0 PIN_FLD_SUB_BAL_IMPACTS ARRAY [1] allocated 20, used 3
1 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 302566983 0 -- Source data before migration
1 PIN_FLD_RESOURCE_ID INT [0] 2200003
1 PIN_FLD_SUB_BALANCES ARRAY [1] allocated 20, used 8
2 PIN_FLD_AMOUNT DECIMAL [0] -6240
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_discount 302566343 0 -- Source data before migration
0 PIN_FLD_SUB_BAL_IMPACTS ARRAY [2] allocated 20, used 3
1 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 302566983 0 -- Source data before migration
1 PIN_FLD_RESOURCE_ID INT [0] 4200004
1 PIN_FLD_SUB_BALANCES ARRAY [1] allocated 20, used 8
2 PIN_FLD_AMOUNT DECIMAL [0] -10
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_discount 302566343 0 -- Source data before migration
STEPS
-----------------------
The issue can be reproduced by following below steps:
1. Create an account in DB1 and perform some usage
2. Ensure that multiple sub balances are created on /event object
3. Execute AMM to migrate the account to DB2
4. Read the migrated event object after executing AMM
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 |