on 07-05-2012 7:51 PM
I went to the "Export Change File" tool in my MDM 7.1 development system and received a warning that my reference file version did not match the current repository version. The reference file is 7.1.06.211. The current MDS version is 7.1.06.260. Our basis team patched the system since the reference file was created so they could pick up some CCMS Monitory functionality.
QA and Prod are at the 7.1.06.260 versions now too.
Has anyone experienced this? Should I blow past the warning and just export my map change? Should I create a new reference file (and I assume I will need to redo my map changes)?
Thanks,
Keith
Hi Keith,
Generally reference file is created when you have both repositories (source and target) at the same schema level. So that any change in source file will be captured and would be available during "Export Change File" command.
Now in your case you need to first make sure that both repositories are at the same schema level.
To ensure this, you should export your changes to target repository using Export Schema and then Import schema command. When your repositories become similar in structure, then you should delete this old reference file and create new reference file.
After that you can use "Export Change File" command at your will. I hope this helps you.
Kindly test this scenario in test system first and then implement for other environments.
Kindly let me know the results as well.
Thanks and Regards,
Ankush Bhardwaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Keith,
As told by my friend Ankush that reference file is created when both the source and target repositories are at same schema level, and to check their level we use the Create Transport Reference command which creates an XML file of a repository’s schema. This reference schema is identical to the XML file created by the Export Schema command. Users should create the
reference file on the originating repository at a time when the originating and target repositories have identical schemas.
The Export Change File command compares the repository’s current schema against the schema contained in its latest reference file. From the Export Changes dialog (similar in appearance to the Import Schema dialog), the user can see where the current schema differs from the reference schema and choose which of these differences to export.
The resulting changes file does not contain an entire schema but instead contains only the changes selected from the Export Changes dialog. Changes that are not selected for the current export remain available for future exports.
i would suggest you to create a new reference file and compare the schema levels and yes you will have to redo the map changes in order to avoid any issue.
Also, please refer to the link
I hope it helps you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.