ETSAuthoringService Not Throwing Exceptions On DB Errors
(Doc ID 2923404.1)
Last updated on FEBRUARY 26, 2023
Applies to:
Oracle Healthcare Data Repository - Version 8.1.3 and laterInformation in this document applies to any platform.
Symptoms
ISSUE CLARIFICATION
===================
On HDR 8.1.3 version,
ACTUAL BEHAVIOR
---------------
When there is an error at the DB side, the authoring service does not throw an exception.
Instead it appears as if concepts were added to ETS successfully.
EXPECTED BEHAVIOR
-----------------------
It would be expected that an exception to be thrown in this case.
STEPS
-----------------------
The issue can be reproduced in Customer's environment with the following steps:
1. After adding some concepts and descriptions to ETS, the sequence that controls the internal concept description term text should be reset to its starting value to force sequence numbers to be re-used.
2. Use the ETSAuthoringService.addConcepts() API to attempt to add more concepts.
This will report as success but at the DB side it will result in:
ORA-00001: unique constraint (ETS.OHF_ETS_ET_DESCS_U1) violated
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 |