Shipment Stop Count Incorrect or "ORA-01438: value larger than specified precision allowed for this column" Generated When Entering a Shipment Event with the SHIPMENT EVENT TRACKER Agent Enabled
(Doc ID 1541646.1)
Last updated on FEBRUARY 22, 2019
Applies to:
Oracle Transportation Management - Version 6.2.8 to 6.2.8 [Release 6.2]Information in this document applies to any platform.
Symptoms
When entering a shipment event for a shipment and the SHIPMENT EVENT TRACKER agent is enabled the NUM_STOPS field on the SHIPMENT table is being updated with an incorrect value. The value is equal to the number of ship units on the shipment multiplied by the number of stops. In cases where the number of ship units and stops the following exception would be generated instead of corrupting the value in the NUM_STOPS field.
java.sql.SQLDataException: ORA-01438: value larger than specified precision allowed for this column
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:79)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
Changes
Clients reporting this issue have recently installed OTM 6.2.8
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 |