This content has been marked as final. Show 2 replies
You can not use the classic 5.2 java console to trigger online initialization to a node in the topology. The 11.x DSCC web GUI will not allow you to manage the 5.2x instances either. (you might see 'ghost' entries representing the masters in the topology.
Review the discussion on mixed release replication configuration, here. While your migration might not flow as the scenarios described, its still important to be aware of the mixed topology requirements and limitations.
Generally speaking you would do an LDIF based initialization in this scenario. So if you have the MMR set up and the 11.x suffix is empty (needs to be initialized with data)
db2ldif on the 5.2x instance, make sure to include 'replication data'
gzip if necessary and bring that file over to your 11.x server, unpack
do an offline import to your 11.x MMR instance(s) (see dsadm import command)
Thanks for your response.
We've migrated the 5.2 DS server to the 220.127.116.11 instance using dsmig with the -R switch and imported the current ldif with replication information.
The tricky part was setting the replication manager password to a known value on the 18.104.22.168 DS. Once that was complete and a rep agreement set up on the 5.2 instance replication seems to start fine.