When you update an alert on the Alerts tab, the following application error is displayed on the alert detail page:
An unexpected error has occurred in the application. Click Resume to continue working. If the problem persists, please contact an administrator.
The error message written to the web application server log is as follows:
2026-02-16 14:56:33,391 ERROR [tomcat-http--19] util.ApplicationDefaultExceptionHandler (ApplicationDefaultExceptionHandler.java:47) -
============================== SAS® Fraud Management ==============================
com.sas.finserv.creditfraud.common.persistence.DataAccessRuntimeException: org.springframework.dao.DataIntegrityViolationException:### Error updating database. Cause: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-304, SQLSTATE=22003, SQLERRMC=null, DRIVER=4.21.29
### The error may exist in com/sas/finserv/creditfraud/fcm/sqlMaps/db2/Alert.xml
### The error may involve com.sas.finserv.creditfraud.persistence.saveActionParamMap
### The error occurred while setting parameters
### SQL: { call SAVE_ALERT(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,
?,?,?,?,?,?,?,?,?,?,?,?,?) }
### Cause: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-304, SQLSTATE=22003, SQLERRMC=null, DRIVER=4.21.29
; DB2 SQL Error: SQLCODE=-304, SQLSTATE=22003, SQLERRMC=null, DRIVER=4.21.29; nested exception is com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-304, SQLSTATE=22003, SQLERRMC=null, DRIVER=4.21.29
at com.sas.finserv.creditfraud.common.persistence.IbatisBaseDAO.update
(IbatisBaseDAO.java:338)
The above database error occurs in the SAVE_ALERT stored procedure on IBM DB2 systems. One of two scenarios might cause this issue to occur.