ORA-29902: error in executing ODCIIndexStart() routine

User 0908c5ccdd

05-11-2007 11:09:53

I am getting an error message back when I attempt to search a table using the jc_equals operator. If I type:





Code:
select count(*)


from compounds


where jc_equals(cd_smiles, 'c1ccccc1') = 1;






then I get the error:





Code:
ERROR at line 1:


ORA-29902: error in executing ODCIIndexStart() routine


ORA-29532: Java call terminated by uncaught Java exception:


java.lang.Exception: The following exception has been thrown by the servlet:


Exception: null


ORA-06512: at "JCHEM.JCHEM_CORE_PKG", line 149


ORA-06512: at "JCHEM.JC_IDXTYPE_IM", line 184


ORA-06512: at line 1






The database is running OK, select count(*) from compounds returns the correct result. Tomcat appears to be running OK, I can see the Tomcat homepage if I navigate to http://localhost:8088





Any ideas what I'm doing wrong?

ChemAxon aa7c50abf8

05-11-2007 15:29:40

Please, could you post the corresponding Java stack trace from Tomcat?





Thanks


Peter

User 0908c5ccdd

05-11-2007 15:46:48

Hi Peter





I'm not sure how to get hold of that for you. Would that be the output in my Tomcat console window that shows text like below?





Code:
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol


lowerWorkerThread.java:80)


        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP


ool.java:684)


        at java.lang.Thread.run(Thread.java:619)

ChemAxon aa7c50abf8

05-11-2007 18:46:56

I'd need lines starting with "at chemaxon.".





Maybe you cannot see the message anymore in the console window because it has been pushed out of the window buffer. Is it possible to increase the buffer of your console window and repeat the the same action that led to this problem?





Thanks


Peter

User 0908c5ccdd

06-11-2007 09:50:29

Hi Peter





Many thanks for replying. We needed to restart the server for another reason and this appears to have cleared the problem. All ChemAxon and Java calls are working OK now. Still not sure what caused it, but all seems to be back to normal now.