Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

No value display in Alarms button after delete nosql module use mango 2.4.2 enterprise version.

  • I use mango 2.4.2 enterprise version.and delete nosql module because stop received data in 8 hours.and use h2 database.but I find the alarm button have no value to display.below is display content.

    “Server error: Timeout
    Server error: PreparedStatementCallback; uncategorized SQLException for SQL [SELECT,evt.typeName,evt.subtypeName,evt.typeRef1,evt.typeRef2,evt.activeTs,evt.rtnApplicable,evt.rtnTs,evt.rtnCause,evt.alarmLevel,evt.message,evt.ackTs,evt.ackUserId,evt.alternateAckSource,u.username,(select count(1) from userComments where commentType=1 and as cnt ,ue.silenced FROM events AS evt left join users u on left join userEvents ue on WHERE evt.ackTs IS NULL AND evt.alarmLevel >= 1 AND ue.userId IN (?) ORDER BY evt.activeTs DESC]; SQL state [90031]; error code [90031]; IO Exception: " org.h2.jdbc.JdbcSQLException: IO Exception: ""Missing lob: 8317"" [90028-171]"; "lob: null table: 79 id: 8317" [90031-171]; nested exception is org.h2.jdbc.JdbcSQLException: IO Exception: " org.h2.jdbc.JdbcSQLException: IO Exception: ""Missing lob: 8317"" [90028-171]"; "lob: null table: 79 id: 8317" [90031-171]
    Server error: Timeout
    ??? Alarm Report [Beta] Help”

    how to solve?

  • It's possible you have too many events in the events table.

    In the SQL consol in Mango run this query:

    select count(*) from EVENTS

    We are finding some performance issues with the H2 database and lots of un-acknowledged events. It's a issue we are currently working on but in the mean time if you don't need any of your events you could manually purge the events table by running:

    delete from EVENTS

    This statement is done by clicking the Submit Update button in the SQL Console within Mango. Please note this will delete all your alarms and events. Please let us know if this resolves the issue.


  • yes. when I submit query"delete from EVENTS" and display
    "org.h2.jdbc.JdbcSQLException: Method is only allowed for a query. Use execute or executeUpdate instead of executeQuery; SQL statement: delete from EVENTS [90002-171]"

    and I submit update display "arning: use this facility at your own risk. Incorrect usage may result in corrupted data and/or system failures".

    Now I test the result seem is ok now .

  • Excellent, glad that resolved it. We are working on a solution so this won't happen in the future.

  • @JoelHaggar said:

    delete from EVENTS

    The above SQL statement successfully purged a large number of events from my mango installation (mySQL), which has hopefully fixed the exceptions, and made it a lot snappier!