The error message will contain a key (e.g.):
“Unable to import molecule with key 1101010960388”
Run this query (be careful, the table owner and name are in uppercase):
It is advised always to check your select sql statement by generating its explain plan.
The following example will import the example.sdf file records into the mol column. Note that the fields of the sdf records are not separated and imported into separate columns.
Create table in the database (this table will be used to import the data into):
Create an sqlldr control file with the following content.
Load the sdf file from command line with sqlldr command (the command will ask you username and password to access the database). The sqlldr command should be executed in the directory where the example.sdf and sdfload.ctl are located.
As a result of the previous operations you will have a table with primary keys in id column and the molecules with additional fields (which are not extracted) in the mol column.
Inconsistent search results might be received if during the run of the search some modifications (insert, update or delete) of stored chemical structures of the chemical structure table(s) affected by the search are committed by a different user than the searcher one.
Uncommitted chemical structures are always at the end of the order by queries in index mode.
Indexing can be slow due to not doing calculations in parallel in special cases. If the indexed table is not owned by the user who issued the CREATE INDEX command and the indexing user don’t have select role with grant option on the indexed table or doesn’t have the create view role and the cartridge owner doesn’t have select role on the indexed table.
If the Oracle Cost Based Optimizer chooses not to use the index at similarity search, ordering based on similarity relevance will be corrupted.
Calculation of chemical terms for great number of structures might be slow.
Cost estimation does not work for query structures in CLOB.
The following workarounds are suggested to convert the CLOB query to VARCHAR2 and run the search (then cost estimation will work):
Cost estimation automatically runs for a given environment using predefined values. It is not possible to run an automated calibration for it to adjust to the custom environment. However, cost estimation factors can be adjusted manually and thus the plan selected for chemical search by Oracle can be influenced. See how to make calibration settings manually.
After an apparently successful installation and index creation, the search processes can throw No more data read from socket error.
Ocassionally, the error appears also at the end of the installation process.
At the moment, the only viable workaround is repeating the installation.