I am trying to migrate the Sun One Directory Server 5.2 to Sun Directory Server 6.0. I am getting the following error
bash-3.2# ./dsmig migrate-config /var/Sun/mps/slapd-circb2bld3/ /var/SunDirectoryServer6.0/dsInst/
Launching Configuration Migration of server instance /var/Sun/mps/slapd-circb2bld3 .....
Enter the certificate database password:
Starting server instance /var/SunDirectoryServer6.0/dsInst ..... Instance /var/SunDirectoryServer6.0/dsInst is already running (ns-slapd pid is 3868)
Enter "cn=Directory Manager" password:
Connecting to server localhost:389 .....
Could not bind securely on "localhost:389".
Remote host closed connection during handshake
Details: SSL peer shut down incorrectly
Could not create context for configuration migration.
Operation "migrate-config" failed.
The migration guide has step by step instructions, including command line examples, are you using that as your reference?
Your upgrade should be to (at a minimum) DSEE 22.214.171.124.1. Upgrading to 6.0 is upgrading to a release level that has no patches or fixes to the product. There are significant fixes to the migration command line tools. There is a good chance you will run into issues.
You should install and review migration to ODSEE 126.96.36.199.0 (which would effectively be the 7.2 release of the DS).
There is a specific guide for migration and upgrade, which includes migration from DS 5.2 to 11.x
The full documentation collection for 188.8.131.52.0 is here
I thought you needed to migrate to 6.0 for an intermediate step, otherwise I'd seriously warned before going that way.
As also mentioned in the previous posts of this thread I STRONGLY recommend you to move to a later release.
If you want to remain stick with 6.x release, consider at least upgrading to the latest available revision of that branch (184.108.40.206.1, released July 2012), since the one you're going to install is has been released in 2006/7, and of course is missing MANY fixes/features introduced during the years.
If you have concerns about the integration with Tivoli, if it has been done 'over the protocol' (at the LDAP layer, so that Tivoli is just behaving like a pure LDAP V3-compliant client), then in theory there's really no difference by which LDAP server you have behind so, you could (much more) safely use 220.127.116.11.1 instead of 6.0