Erro on StorageDemo sample   

Hello,
I've downloaded and installed IODT 1.5 from alphaWorks, and I'm using it on Eclipse. I'm using Derby as DB (version 10.1.2.1 recommended at site and docs), but I'm getting a strange error on running StorageDemo.java sample (after take off the comments on source code):

WARN main (DAO.java:539) - Ontology store has already been created.
com.ibm.iodt.sor.utils.SORException: Ontology Store: default does not exist.
at com.ibm.iodt.sor.db.DAO.getInstance(DAO.java:1112)
at com.ibm.iodt.sor.OntologyStoreManager.<init>(OntologyStoreManager.java:102)
at com.ibm.iodt.sor.OntologyStoreManager.<init>(OntologyStoreManager.java:93)
at StorageDemo.loadOWLDocuments(StorageDemo.java:81)
at StorageDemo.main(StorageDemo.java:253)

I don't understand. Warning says that the Ontology Store already exists. Error says it don't exists. Do i need setting something? I've tried with Derby embedded and Derby client.

I thank some help.

Ely Matos
UFJF
Brazil

Thanks for answer!
I already tried to create another Ontology Store. The message remains, changing "default" by the name of the store, like:

OntologyStoreManager sor = new OntologyStoreManager("mystore");

give me

com.ibm.iodt.sor.utils.SORException: Ontology Store: mystore does not exist.

I've tried use new libs for Derby, without success. Tried to change to Java 1.4, without success.

How can I see if the Store really exists on database? Is this a "schema", a table, a set of tables?

When I run at first time (and the database do not exists), the message is about:

1328 main 2008-02-21 09:30:04,897 ERROR com.ibm.iodt.sor.db.DAO - Ontology store "default" has not been created.
ERROR X0X05: Table 'COMMONURI0' does not exist.

After running again, the message about Table 'COMMONURI0' disappear, but returns the

com.ibm.iodt.sor.utils.SORException: Ontology Store: mystore does not exist.

Have you tested with Derby or with another database? Is It suggested that I try with Oracle, for example?

I'm in trouble because I intend to use IODT/SOR in my MSc research...

Thanks for any support,

Ely

Hi,
we checked derby database locally and found the similar problem. Previously, we tested IODT using cloudscape which is the earlier version of derby, and there is no problem. But with the latest derby, there may have some system changes resulting in the problem. So now, we strongly encourage you use DB2 as the backend store of IODT. IODT leverages a unique feature of DB2 (not supported by derby) for performance improvement. Also, derby is an embeded database with limited scalability and performance. In terms of performance evaluation, you may want to use DB2, rather than derby.
Thanks for your report again.