DBUnit@Oracle DB時のAmbiguousTableNameException


org.dbunit.database.AmbiguousTableNameException: AQ$_SCHEDULES
 at org.dbunit.database.DatabaseDataSet.initialize(DatabaseDataSet.java:140)
 at org.dbunit.database.DatabaseDataSet.getTableMetaData(DatabaseDataSet.java:186)
 at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:98)
 at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:67)


This exception is thrown by IDataSet when multiple tables having the same name are accessible. This usually occurs when the database connection have access to multiple schemas containing identical table names.
Possible solutions:
1) Use a database connection credential that has access to only one database schema.
2) Specify a schema name to the DatabaseConnection or DatabaseDataSourceConnection constructor.
3) Enable the qualified table name support (see How-to documentation).

Another common reason for this exception to be thrown is when an XML file contains the same table multiple times whereas a different table is between the definition of the duplicate table.



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.