[resolved] Unable to create table when using MySQL

[Anonymous]

Talend MDM Server is unable to create table for the entity when using MySQL as the repository database. It is throwing the following message: 'Unable to single search::java.lang.IllegalArgumenException:Type '<Object Name>' does not exist in data cluster '<Container/DB name>'.;nested exception is: com.amalto.core.util.XtentisException: Unable to singel search::java.lang.IllegalArgumentException: Type '<Object Name>' does not exist in data cluster '<Container/DB name>'.
Below is the stack trace:
------------------------------------------------------------------------------------

2013-02-19 09:54:02,232 INFO starting event executor threads for event executor 'EventExecutor-10.66.81.209-default'...
2013-02-19 09:54:02,234 INFO starting dispatcher thread for event executor 'EventExecutor-10.66.81.209-default'...
2013-02-19 09:54:02,246 INFO Registered MBean: Bonitasoft:name=JVM,type=JVMMBean 2013-02-19 09:54:13,165 ER

To see the whole post, download it here

[Anonymous]

Please attach the full server.log

[Anonymous]

Please find the log attached.

[Anonymous]

Please find attached the zip for Server.log

[Anonymous]

hi
It is impossible to attach a file to the forum, you have to copy and paste it to your post.

Shong

[Anonymous]

MDM cannot seem to find an Entity or a complex type called 'ResourceType'.
I received a full server.log separately. The first time this exception occurs is when performing a ViewSearch, probably by selecting the view in the Web UI. In the code, we explicitly throw this exception when the corresponding Entity to the view doesn't exist in the model:

java.lang.IllegalArgumentException: Type 'ResourceType' does not exist in data cluster 'md'.
at com.amalto.core.delegator.IItemCtrlDelegator.viewSearch(Unknown Source)
at com.amalto.core.ejb.ItemCtrl2Bean.viewSearch(Unknown Source)
(...)

[Anonymous]

Also check both MDM data-model and data-container have the same name. It is a requirement in 5.2 + relational storage.

[Anonymous]

The issue was I had different names for data model and data container. Thanks for the help!!

[Anonymous · Accepted solution]

It is definitely a source of confusion. It is a legacy. We will enforce the names in the Studio in next versions.