[resolved] Having trouble creating data container

[Anonymous]

When I create a new data container called 'CHCSDataContainer' and try to deploy it to my MDM server, I get this error:
"Unable to physically create the data cluster CHCSDataContainer: Could not create storage 'CHCSDataContainer' with data model 'CHCSDataContainer'."
The odd things is, I never told it to use CHCSDataContainer as the data model, as I already have a data model defined that uses another name. Is this a permission issue?

[Anonymous]

Hello,
I was trying to create a data model, a data container and a data view, and while trying to deploy them on server, I had the same error "unable to physically create the date cluster <PRODUCT>: could not create storage".
A reply to a similar post ( https://jira.talendforge.org/browse/TMDM-4484) gave me an idea, and IT WORKED!
Although it may seem absurd, but to avoid error, you have to follow this order:
1-right-click Data Model, and create a category, example: Product
2-under category Product, create the data model Product. add some elements to it.
3-go to Data Container and do the same thing: create a category Product, then inside it, a new data container with same name
4-creating a view: go to Data Model Entity, right-click on Product ---> "Generate default browse items view"
DEPLOYING ON SERVER:
Now, we will deploy each element on server, in the following order:
5-right-click the newly created view -->deploy to server
6-now deploy the Data Model: Product
7-finally, deploy the Data Container : Product
This is how the 3 deployments worked error-free for me!
Best regards,
Amin ELMASRI

[Anonymous]

Thanks Amin. However, if:
1- in the MDM repository view you select both data model(s) *and* data container(s) (hold the ctrl key).
2- right click
3- click on "deploy to server..."
4- select your MDM server
... the MDM studio will deploy all the selected items in the correct order.
A quick (but rather technical) explanation on why data model needs to be present before the data container can be created: the database schema is created based on the data model's content (i.e. a entity "Address" leads to a table named "ADDRESS"), thus data model needs to be present server-side before the container can be created.
But since this is a bit too technical (and not very user friendly), the MDM studio (starting from 5.2) deploys selected items in the correct order.