Constraint Is Working Unexpectedly In OSM 7.5 CNE
(Doc ID 3054317.1)
Last updated on OCTOBER 18, 2024
Applies to:
Oracle Communications Order and Service Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.5.0.0.0 version, Other
A Constraint behavior which is present at order level is working unexpectedly, it contains a regular expression which is checking for IPv4 format. This constraint has worked previously in existing OSM 7.3.1 env but getting error in OSM 7.5 CNE.
Below is the constraint condition.
match('^([01]?\d\d?|2[0-4]\d|25[0-5])\.([01]?\d\d?|2[0-4]\d|25[0-5])\.([01]?\d\d?|2[0-4]\d|25[0-5])\.([01]?\d\d?|2[0-4]\d|25[0-5])$')
ERROR
-----------------------
<SQL Exception ORA-20006: Workflow thread does not exist. The order may have been moved by another user. Refresh your worklist and try again. order id = 26, hist_seq_id = 2944
ORA-06512: at "OSMUSER.ERROR_MSG", line 8
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 |