zmmaintaintables fails - SOAP fault - TABLE_SCHEMA does not exist

[lanstar]

I have three installations of Zimbra on three different servers for three different user communities/domains at 2 different locations. All are the latest version. All three give the following error when zmmaintaintables is run:

[zimbra@mail ~]$ /opt/zimbra/libexec/zmmaintaintables
Received SOAP fault: system failure: java.lang.IllegalArgumentException: Column 'TABLE_SCHEMA' does not exist
Can't call method "to_string" on an undefined value at /opt/zimbra/libexec/zmmaintaintables line 64.

Version information:

[zimbra@mail ~]$ zmcontrol -v


Release 6.0.6_GA_2324.RHEL5_20100406144520 CentOS5 FOSS edition.

Has anyone else experienced this issue? FWIW, two of the three began life at a 6.x version prior to 6.0.6. The third was a fresh 6.0.6 install.

Thanks in advance for any insight!

Tim Pearson
Pittsburg State University

[cailleaux]

Hi,

Yes, I have exactly the same issue here :

$ zmcontrol -v
Release 6.0.6_GA_2330.DEBIAN5_64 DEBIAN5_64 FOSS edition.

$ /opt/zimbra/libexec/zmmaintaintables
Received SOAP fault: system failure: java.lang.IllegalArgumentException: Column 'TABLE_SCHEMA' does not exist
Can't call method "to_string" on an undefined value at /opt/zimbra/libexec/zmmaintaintables line 64.

And in the mailboxd.log :

2010-06-20 01:30:17,973 INFO [btpool0-7377://localhost:7071/service/admin/soap/] [name=zimbra;ip=127.0.0.1;] sqltrace - Slow execution (3390ms): SELECT table_schema, table_name FROM INFORMATION_SCHEMA.TABLES WHERE table_schema = 'zimbra' OR table_schema LIKE 'mboxgroup%'
2010-06-20 01:30:17,989 WARN [btpool0-7377://localhost:7071/service/admin/soap/] [name=zimbra;ip=127.0.0.1;] SoapEngine - handler exception
java.lang.IllegalArgumentException: Column 'TABLE_SCHEMA' does not exist
at com.zimbra.cs.db.DbResults.getIndex(DbResults.java :309)
at com.zimbra.cs.db.DbResults.getString(DbResults.jav a:213)
at com.zimbra.cs.db.DbResults.getString(DbResults.jav a:221)
at com.zimbra.cs.db.DbTableMaintenance.runMaintenance (DbTableMaintenance.java:41)
at com.zimbra.cs.service.admin.MaintainTables.handle( MaintainTables.java:42)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:419)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:273)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:157)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)

I looked in the database : the TABLE_SCHEMA column exists...


Thanks