During Upgrade To BRM 7.4 Duplicated Node Location Found On BRM 7.2.1
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
Found a data migration problem. There are two or more records on the purchased_product_t (migrated from account_products_t on 7.2.1) table for the same node location, but with different status. This is caused on 7.2.1 when transferring the subscription service from Account A to Account B, and then from Account B to Account A, then from Account A to Account B or from Account B to Account C. First transfer operation leaves a record with status cancelled and the last one with active status; both with the same node_location.
The following query on 7.4 shows
4. Prepare a similar input flist to transfer the same /service/ip from Acct2 to Acct1. Run the same queries again.
5. Using the same input flist to transfer /service/ip again from Acct1 to Acct2. Run the same queries again
6. Repeat if necessary.
You will find the same NODE_LOCATION will be in Acct1 and Acct2.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms