I'm using the Hibernate Tools from org.hibernate.eclipse_3.2.0.beta9a. When I use the hibernate perspective in Eclipse and press on the database icon, the tool is using the

org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect

dialect to scan the available schemas and tables. This is a problem since using this dialect against the Oracle 9i server will throw an exception every time it attempts to get the list of indexes from the metadata for each table. If I use ANT to run the reverse engineering tools they use the same default dialect. The <hdb2hdmxml ...> will issue warnings on each table indicating it can't acquire the index list.

My hibernate configuration file specifies the Oracle 9i dialect.

<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory name="rpmSessionFactory">
<property name="hibernate.connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
<property name="hibernate.connection.password">*****</property>
<property name="hibernate.connection.url">jdbc:oracle:thin:@[server]:[port]:tiny</property>
<property name="hibernate.connection.username">user</property>
<property name="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</property>
</session-factory>
</hibernate-configuration>



I have looked at the Oracle 9i dialect and it uses a SQL SELECT on system tables to gain access to the list of indexes. This does not cause an exception when I run the same SELECT using the same JDBC connection. If the tools and the plugin used the specified dialect I don't believe I would have the issues I'm experiencing.

Is there something wrong with the configuration file that causes the tools to use the default dialect? Can someone suggest how to correct the problem?

Dialect != MetaDataDialect

the sql in the oracledialect does not handle multiple schemas so not usable for reverse engineering.

In b9 the tool should choose to use OracleMetaDataDialect for the reveng.
which uses native oracle system queries.

with respect to the exceptions they shouldn't hurt (except for a speed penalty)