Hi, we encountered this same issue in our SSM 10.0 development system. After some 
digging we found the culprit: a bug in the Admin interface when saving changes to contexts. The issue arises when, if after pressing the "Save" button after making changes to a particular context, the user selects another context BEFORE the save confirmation dialog pops-up. It seems that if you change the context before the commit is confirmed, the system will mix-up the contexts and one of them will become corrupted and partially overwritten by the other one.
Solution: If it happened, you must reconfigure your corrupted context (We found no other way of recovering). And in the future, ask your configuration team to BE PATIENT and ALWAYS WAIT FOR THE SAVE CONFIRMATION!
Hope this helps.
Regards,
Rodolfo