Database Persistence Unique Constraint Violated Error
(Doc ID 2851535.1)
Last updated on OCTOBER 11, 2022
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Elastic Charging Engine (ECE), 12.0.0.3.0 version, Rating business logic
below unique constraint errors are observed in ecs.logs on multiple environments.
ERROR:
---------------------------
The insert statements on balance and customer is getting called but those records are already persisted in the database. This is causing unique constraint error. There are continuous usage and order flow testing which might be triggering this. This insert process is continuously triggering and which is polluting the log and also taking resources. This needs to be handled.
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 |