Migration from previous versions of ID Builder service
New version of ID Builder service can be used in two different modes – preserving dependency of service on MESInstaller-installed Oracle database instance (not recommended) or using a non-legacy approach without the dependency (recommended). Although the latter option could entail some additional effort in migrating data from old Oracle database to a new instance, this is the recommended approach that is considered a much more beneficial way of utilizing ID Builder service in the long run.
Migration from old MES ID Builder
ID Builder offers an Import-UI to perform the Migration. Follow the steps described there.
You’re done! You should now be able to use the new version of ID Builder service with your data.
Counter Definition name and Counter name uniqueness problem
There is one more consideration that needs to be taken into account. During data migration, one needs to guarantee that both Counter Definition name and Counter name remain unique in the scope of the entire database. This condition should be met for already existing databases, but a conflict could occur when merging data from different databases. ID Builder does not offer any support in performing such merge automatically.