Slave Repository not able to Sync second time.

[former_member201266]

Hi,

I am using MDM 7.1 SP5, I have two slaves created for my repository on the same server, after making changes I Synchronize the slave, when I did do it first time (after creating slave) its working fine, but when I try to do it second time (after making changes in my master repository) i get the following error, "This slave cannot be synchronized because its master is invalid",

If any one faces similar problem please help me out.

Thanks,

Cherry.

[Former Member]

Hi,

Please delete the slave repository and mount the slave again and then try to Syncronize. It might be due to server malfunctioning. Otherwise make a fresh Slave from Master and mount that. It will be more useful rather than trying the first option.

Hopefully it should be resolved by above method. I am not sure whether you will be able to unload/load the Master repository, bacuse 90% of the times, the issues are with MDM Product and the workaround is to Unload/Load the repositories/servers. If you can unload and then load->Update Indices, then please do the same. Also please Repair your master repository before creating the slave of it.

Regards:

Gaurav

[former_member181958]

Hi Cherry,

Master - Slave sync is little tricky. Remember this:

1) Master Repository DATA updates into Slave Repo require the slave repository to be loaded.

2) Master Repository SCHEMA updates require the Slave Repo to be unloaded.

So if you changed any schema in Master Repo, then to have the Slave Repo synchronized with latest schema, unload the Slave Repo, then sync it with Master. Then you would not get this error.

Let me know if this resolves your issue.

Regards

Pravin Bhute

[former_member201266]

Hi All,

Thanks for your responses.

Kanstantsin : As said I am using same MDM server and following the same process of normalizing and recreating slaves but its time consuming.

Pravin: Surly I will try out your suggestion and let see how it works.

Cheers,

Cherry.

[Former Member]

Hello Cherry.

You should normalize your master repository and than delete and recreate its slave repositories.

Nothing more nothing less

Very important thin - if you used different mdm server installation for master and slave repositories servers should have the same version

Regards

Kanstantsin Chernichenka

[Former Member]

Hi,

Bounce the Master server and verify and check the master reposiotry. If you found some errors repair it and then try to synccronize slave repository.

Hope it may help you.

Regards,

Srinivas