Too many columns to be shown in the Enterprise Manager 11g?

Question

Hello,
we are having some problems with the Enterprise Manager 11g. When we want to VIEW DATA of a specific table, we get this exception. We think that our table has too many columns to be displayed. If we delete some of the columns, the data is shown in the enterprise manager. But this cannot be a solution for us. Can you help us with this point?
2009-08-03 10:07:04,210 [EMUI_10_07_04_/console/database/schema/displayContents] ERROR svlt.PageHandler handleRequest.639 - java.lang.ArrayIndexOutOfBoundsException: -128
java.lang.ArrayIndexOutOfBoundsException: -128
     at oracle.sysman.emo.adm.DBObjectsMCWInfo.getSqlTimestampIndexes(DBObjectsMCWInfo.java:194)
     at oracle.sysman.emo.adm.schema.TableViewDataBrowsingDataSource.executeQuery(TableViewDataBrowsingDataSource.java:167)
     at oracle.sysman.emo.adm.DatabaseObjectsDataSource.populate(DatabaseObjectsDataSource.java:201)
     at oracle.sysman.emo.adm.DatabaseObjectsDataSource.populate(DatabaseObjectsDataSource.java:151)
     at oracle.sysman.emo.adm.schema.DisplayContentsObject.populate(DisplayContentsObject.java:369)
     at oracle.sysman.db.adm.schm.DisplayContentsController.onDisplayAllRows(DisplayContentsController.java:303)
     at oracle.sysman.db.adm.schm.DisplayContentsController.onDisplayContents(DisplayContentsController.java:290)
     at oracle.sysman.db.adm.schm.DisplayContentsController.onEvent(DisplayContentsController.java:136)
     at oracle.sysman.db.adm.DBController.handleEvent(DBController.java:3431)
     at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:577)
     at oracle.sysman.db.adm.RootController.handleRequest(RootController.java:205)
     at oracle.sysman.db.adm.DBControllerResolver.handleRequest(DBControllerResolver.java:121)
     at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:781)
     at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:337)
     at oracle.sysman.eml.app.Console.doGet(Console.java:318)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:109)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at oracle.sysman.db.adm.inst.HandleRepDownFilter.doFilter(HandleRepDownFilter.java:153)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
     at oracle.sysman.eml.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:122)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
     at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:102)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:336)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:627)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)When we select the table via SQL, everything works fine.

Answer 1

Hi,
I'm Galit from the QE team of VIN.
All the things that you've described are correct.
It is actually an edge case where the only VM, that the manual App can be managed from its Map view, was removed from the App.
The Manual App management is as designed, and may be changed in the future.
There are 2 ways to overcome this situation:
1.You can, as you stated, create another Manual App with similar name and remain with the "Zombie App".
2. To run a specific command that will remove the Zombie App from the DB.
Please note that option no. 2 involves using an API that we do not publish.
If you would like to use option no. 2 contact me in private and we will see about supplying the relevant commands to run in order to delete the "zombie" application.
Thanks,
Galit Gutman