General discussion

  • Hi

    I am getting the error message "There is already a model with the same name or MUID" when trying to deploy a model clone. I have checked the following:

    - There is no existing model in the target system with the same name or MUID by checking the table [MDS].[mdm].[tblModel]

    - There is no references in the package to either existing model names or MUIDS in the package file

    This is very strange :(

    I noticed that also entities has MUID's which was new information for me. there is also an unique index defined for the table mdm.tblEntity which means that the "deploynew" option on MDSModelDeploy utility must generate new MUID's for all imported entities not only the model itself.  

    After a cross join over mdm.tblEntity on the source and target MDS databases I did not get any hit on the MUID column. This would confirm that the problem is the model and not the entities. 




    Monday, August 18, 2014 8:46 AM

All replies

  • For all readers of this thread I can say that we now got around this problem by doing the following:

    With MDSModelPackageEditor we divided the original package into many smaller pices. We did the deployclone with only the model and one entity. Then by following series of deployupdate we manage to create the complete clone. 

    Best Regards

    Jan Isacsson

    Tuesday, August 19, 2014 2:48 PM