Order Creation Failure In OSM Due To "invalid Date Value : Wrong Type"
(Doc ID 2310601.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.2.4 to 7.2.4 [Release 7.2]Information in this document applies to any platform.
Symptoms
On : 7.2.4.1.2 version, AIA Cartridge
Order creation failure in OSM due to "invalid date value : wrong type"
Few orders are failing during creation in OSM throwing the following error; "
However, upon re-firing the same order XML through SOAP-UI, order is successfully created and is completed without any manual intervention.
There is no alterations/modifications made to the order request XML during re-firing it through SOAP-UI.
ERROR
-----------------------
BEA-000000 : "Failed to create and start the order due to java.lang.RuntimeException: com.mslv.oms.OMSException: encountered error starting orchestration caused by:Invalid date value: wrong type: "
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 |