Bug Information Title:  reverse-eng oracle relations Text:  When reverse-engineering from an oracle schema with referential integrity constraints, dbdesigner4 will throw this error: " a component named ..... already exists" and abort the rev-eng process. I've tested this with: oracle 8.1.7 and 9.0.1 tried connecting as both the schema owner and a system account, always selected the spectific shema tables. This only occurs in some schemas with r.i., but is always reproducible. I've queried the db to try to identify some redundant objects or constraints, but the object in question is not duplicated...