For the last week, I have been trying to troubleshoot an issue we are having with our ER Studio Data Architecture version 17. We are unable to check in any diagrams/data dictionaries and we are getting a Repository Merge error, operation halting. (Id=3). In the repo_merge_error document, we are seeing this.
Missing Node Exception - occurs when diagram node cannot look up a parent node
Missing Parent GUID: 197027ef240f4f01bb24a7c27eb43edbChild Section ID: DIAGRAM (-1)Child GUID:
Does anyone have any idea what to look for or what needs to be done? I opened a ticket with Idera but they have yet to respond to me.
There's one thing you can try but you may need to send a backup of your database to support to get it fixed.
Here's what you can try in the meantime:1) Go to your active file directory and move the models out of this folder2) Get a fresh copy from the repository3) Do a check out/in. If there are no problems here then you can move to step 4. If there are problems then there's something wrong in the database and support will need a backup of it.4) Compare and merge what you have from the moved model to the fresh copy 5) Check in the model
Thank you Stan, We have tried that and get the same error when we try to check in, even though we didn't make any changes. Is there a way to tell what changes it is trying to make in the merge? Are we able to do a database restore to before we started having issues? If so, what precautions or steps should we follow?
Unfortunately I don't think there's a way to determine what changes it's trying to merge or what the cause is.
You could try to restore but this could take more time and be more troublesome. If you do a compare and merge between this current model and a restored model, it could be something in the current model that would corrupt the model in the database again. I think it'd probably be best to wait for support to get you a fix.
You should still be able to work on the model locally, you just won't be able to add it into the repository until it's fixed.
We have an automated process that checks in the data dictionary after adding objects, etc. My gut feeling is one of these objects corrupted the data dictionary. Is there a way to make the repository think a certain version of the data dictionary is the most current and load it all from there? I can see a version number for what I would like it back to but don't know if I can restore the file to that version. Unfortunately the compare and merge doesn't work because it is a model with only 2 data dictionaries and I don't think we can do a compare and merge on a data dictionary.