“Node Ancestry” Feature In O2A Orders
(Doc ID 1944566.1)
Last updated on NOVEMBER 18, 2020
Applies to:
Oracle Communications Order and Service Management - Version 7.2.0 and laterInformation in this document applies to any platform.
Symptoms
Customer is observing that OSM DATA and INDEX table-space is filling up at very fast rate during O2A order processing. The following is a summary of their analysis
Orders Number 500 100 100
Large Data 680M 130M 180M
Large Index 1600M 207M 299M
Archive log 15000M 2500M 2900M
After some testing and they found there are 6,000 records inserted to the OM_ORDER_INSTANCE for each order. Is this normal behavior? Even DB REDO logs space of 120GB space is filling up within 4-5 hours, while running performance testing with 15,000 orders.
Following is a summary of the customer solution architecture.
1) O2A PIP between AIA and OSM
2) Around Three functions for every order i.e. SYNC CUSTOMER, PROVISIONING and FULFILL BILLING.
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 |