During API testing or standard operations, calls to the History and Backlog APIs return a 500 Internal Server Error. While these specific endpoints fail, other APIs such as Auth, Master, and Agent function as expected. The spring.log throws error messages "SQL Error: 17026" and "SQLState: 99999".
Symptoms
tasks/history or tasks/backlog return an HTTP 500 response.Could not extract column [2] from JDBC ResultSet [Numeric Overflow]"SQL Error: 17026, SQLState: 99999Could not extract column [2] from JDBC ResultSet [Numeric Overflow] [n/a]Could not extract column [2] from JDBC ResultSet [Numeric Overflow] [n/a]Applications Manager 9.6 to 9.6.2
The so_aw_seq column in the database endpoint is defined as a 32-bit Integer. The maximum limit for a 32-bit Integer is 2,147,483,647. Once the sequence value exceeds this threshold, the API server encounters a numeric overflow, causing the 500 Server Error.
This issue is confirmed as a product defect tracked under DE208291. The fix involves updating the column definition from Integer to Long to support higher sequence values.
Fixed Versions:
Workaround: If an upgrade is not immediately possible, a hotfix is available via an updated api-server.jar.
api-server.jar.api-server.jar.api-server.jar.For tracking updates on this defect, subscribe to this article. See for more information.
To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.