We realise that after installing the Table Grid Editor and adding 2 tables to our screen the error below keep popping up in our error log. We've tried renaming the table differently but it didn't work. Any advice?
2015-04-15 16:41:06,381 http-bio-8180-exec-15 ERROR projectadmin 1001x300977x1 1a0qe26 10.238.2.22,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] The operation failed because an index or statistics with name 'screening_checklist2_iId' already exists on table 'screening_checklist2_c14597'. 2015-04-15 16:41:06,381 http-bio-8180-exec-15 WARN projectadmin 1001x300977x1 1a0qe26 10.238.2.22,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1913, SQLState: 42S11 2015-04-15 16:41:06,162 http-bio-8180-exec-15 ERROR projectadmin 1001x300976x1 1a0qe26 10.238.2.22,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] The operation failed because an index or statistics with name 'screening_checklist_iId' already exists on table 'screening_checklist_c14552'. 2015-04-15 16:41:06,162 http-bio-8180-exec-15 WARN projectadmin 1001x300976x1 1a0qe26 10.238.2.22,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1913, SQLState: 42S11 2015-04-15 16:15:46,085 http-bio-8180-exec-14 ERROR wopqmh 975x300395x1 1am8h9y 10.240.104.160,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] The operation failed because an index or statistics with name 'screening_checklist2_iId' already exists on table 'screening_checklist2_c14597'. 2015-04-15 16:15:46,085 http-bio-8180-exec-14 WARN wopqmh 975x300395x1 1am8h9y 10.240.104.160,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1913, SQLState: 42S11 2015-04-15 16:15:45,366 http-bio-8180-exec-14 ERROR wopqmh 975x300394x2 1am8h9y 10.240.104.160,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] The operation failed because an index or statistics with name 'screening_checklist_iId' already exists on table 'screening_checklist_c14552'. 2015-04-15 16:15:45,366 http-bio-8180-exec-14 WARN wopqmh 975x300394x2 1am8h9y 10.240.104.160,127.0.0.1 /rest/idalko-igrid/1.0/datagrid/data [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1913, SQLState: 42S11
Hi Thomas,
The subject of the log statements is harmless - when accessing a grid table, hibernate does a couple of checks like 'is the index available'. The way it does this check is by trying to create it, which results in this error.
Still the logging is troubling quite a bit of users, so I created a bug to be resolved in an upcoming release
https://support.idalko.com/browse/IGRID-3265
Thanks for raising the issue.
Francis
Thanks for such a quick response. Looking forward to the fix in the new version. Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.