Symptom
-
The following error appears in the SMP server log:
2016-02-24 08:29:13.271 ERROR MMS Thread-61 [com.sybase.sup.server.monitoring.MonitoringDBUtil] [] []
com.sybase.sup.server.monitoring.MonitoringDBUtil.flushDataToDB()
com.sybase.jdbc4.jdbc.SybBatchUpdateException: JZ0BE:
BatchUpdateException: Error occurred while executing batch statement:
SQL Anywhere Error -195: Column 'id' in table 'mms_data_change_notification' cannot be NULL
at com.sybase.jdbc4.jdbc.ErrorMessage.raiseBatchUpdateException (ErrorMessage.java:1319)
at com.sybase.jdbc4.jdbc.SybStatement.batchLoop(SybStatement.java:2133)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeBatch(SybPreparedStatement.java:2069)
at com.sybase.sup.server.monitoring.MonitoringDBUtil.executeBatchUpdate(MonitoringDBUtil.java:665)
at com.sybase.sup.server.monitoring.MonitoringDBUtil.flushDataToDB(MonitoringDBUtil.java:768)
at com.sybase.sup.server.monitoring.MonitoringDBUtil_DJC.access$501(MonitoringDBUtil_DJC.java:4)
at com.sybase.sup.server.monitoring.MonitoringDBUtil_DJC$6.invoke(MonitoringDBUtil_DJC.java:248)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:857)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:759)
at com.sybase.sup.server.monitoring.MonitoringDBUtil_DJC.flushDataToDB(MonitoringDBUtil_DJC.java:252)
at com.sybase.sup.server.monitoring.StartMonitoringService$MonitoringScheduledThread.run(StartMonitoringService.java:192) - Data is no longer being entered into the monitordb database.
Read more...
Environment
- SMP 2.3.x
- SMP MBO runtime server 3.0.x
Product
Keywords
SMP monitordb SQLAnywhere error 195 column null primary key autoincrement , KBA , MOB-ONP , SAP Mobile Platform on Premise , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview