Red Hat Bugzilla – Bug 779307
jUDDI database initialization fails on Oracle and db2 - not an issue for PostgreSQL
Last modified: 2010-01-29 02:46:37 EST
Date of First Response: 2009-12-10 11:15:15
jUDDI 3 uses Hibernate to access db. During server startup it tries to update db schema to conform mapping files. Unfortunately on Oracle if tables with the same name exists in an other schema then jUDDI thinks that db is correctly initialized and tables are not created.
To fix this issue it is necessary to use hibernate options hibernate.default_schema and/or hibernate.default_catalog in persistence.xml file. This can cuase problems with other databases.
I have tried to change hibernate.hbm2ddl.auto from update to create and issue has disappeared. Moreover this approach is better aligned with other db components using static sql files - no schema change is done inadvertently.
SOA-1599 is also a symptom of visibility across multiple schemas.
Link: Added: This issue is related to SOA-1599
This seems to be more a database setup problem, where multiple schemas are visible.
Changing the schema visibility in the database would fix this.
hbm2ddl.auto should never carry the "update" value in the first place - it doesn't properly create indices. For more information, see http://www.hibernate.org/119.html#A10 and HHH-1012 (fixed only recently).
Link: Added: This issue depends JBESB-3097
Will also modify our base one in case that makes your job easier
ESB configuration has been changed, will be in next commit.
Resolving this, as the ESB JIRA (JBESB-3097) has been resolved.
Verified in ER7