Control Plan Periodic Charges Fail to Find a Control Plan in NCC 5.0.2.0 with "WARNING: No matching Product Type Capability configured for Capability [X] Product Type [Y]"
(Doc ID 1964228.1)
Last updated on MARCH 28, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.2 to 5.0.2 [Release 5.0]Oracle Solaris on SPARC (64-bit)
Symptoms
In Oracle Network Charging and Control (NCC) 5.0.2.0 (Miranda), changes were made which unfortunately mean Control Plan Periodic Charges fail to trigger a Control Plan (CP) in slee_acs resulting in the following error:
This results in an error being returned by osdInterface to beServiceTrigger and the Control Plan Periodic Charge trigger being stored/retried until this issue is resolved. This will also cause seemingly random Wallet updates due to the indefinite storage/retry mechanism of beServiceTrigger/beEventStorageIF once this is resolved.
Changes
Installation of NCC 5.0.2.0 and the implementaion of Control Plan Periodic Charges.
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 |