exactChargeMatchingOption:e

Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production


PL/SQL Release 9.2.0.1.0 - Production


CORE 9.2.0.1.0 Production


TNS for 32-bit Windows: Version 9.2.0.1.0 - Production


NLSRTL Version 9.2.0.1.0 - Production


NLSRTL Version 9.2.0.1.0 - Production


JChem version in the database: 3.2


JChem version in the Tomcat server: 3.2


java.vm.version: 1.5.0_09-b03


java.vm.vendor: Sun Microsystems Inc.


Apache Tomcat/5.5.20


Major JDBC version in Tomcat: 1


Minor JDBC version in Tomcat: 0

Code:

SELECT t1.smiles,t1.cleansmiles,t1.supplier_no,t1.original_molweight,jcf_molweight(t1.cleansmiles),t2.molecule_id,t1.logp,t1.quantity,t1.purity,t1.price,t1.tpsa,t1.meltingpoint,t1.solubility FROM chb_exp_dec06UNQ t1,moleculesvn t2 WHERE t1.smiles IS NOT NULL AND (jc_equals (t2.cd_smiles,t1.cleansmiles) = 1 OR jc_compare (t2.cd_smiles,t1.cleansmiles,'t:e exactChargeMatchingOption:e doubleBondStereo:A HCountMatching:E exactStereoMatching:y absoluteStereo:a stereoSearch:y') = 1)

I get an error...





ORA-29532: Java call terminated by uncaught Java exception: java.lang.Exception: The following exception has been thrown by the servlet:


Exception: Illegal option: exactChargeMatchingOption


ORA-06512: at "SANDPIT.JCHEM_CORE_PKG", line 0


ORA-06512: at "SANDPIT.COMPARE_FUNC", line 28





What have I done wrong? Or perhaps this might be fixed in a later release?





Cheers,


Daniel.

Yes. This problem is fixed in the latest release.





P.

Thanks Peter, Daniel.