I am using Hibernate v2.1.3 against Oracle 9i, and am having problems using SchemaUpdate where tables with the same name exist in different schemas.

For example, when the target table is not present, but there is a table with that name in another schema, its details are retrieved by the metadata query, which seems to match on table name but not schema... UpdateSchema then generates an 'alter table' script based on alterations needed to the existing table in the other schema - but then tries to run it against the missing table in the correct schema - so it hits a ORA-00942: table or view does not exist error.

(This seems to be happening even when the 'duplicate' table is not in the schema specified in the mapping file or in the hibernate connection schema...)

Has anyone else encountered this problem? Is there a setting I could be using to avoid it?

Thank you!

I had the same problem here ...

I was lucky, that this was only a test system.

I changed the SchemaUpdate-Tool in the way, that you can tell it which schema to update.

I'll try to make a patch and post it in Jira.