Float Field Values Could Be Too Big for Field Width But No Verification in Default Behavior
(Doc ID 2023914.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Agile Engineering Data Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
It should not be possible for end users to enter values too large for a float field and then receive a db error message if the value is too large for the field:
Internal Database Error in "dmi_upd_mas_elm" (EPSQL "EPQUPD") Code -910 OCI Error: -1438 / ORA-01438: value larger than specified precision allowed for this column.
For classification lists: Even though there might be no error message it is possible for end users to insert float values that do not fit into the field according to the field definition. Anyway, there is no error message because of the database precision.
This should be verified automatically and an appropriate message should be given without additional customizing (of for example cch_chk_rng).
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|