LDN - Luminis Developer Network

Well, its been nearly 3 weeks of attempting migrations, and I think we nearly have all the bugs worked out. We are moving from HP-UX to Solaris, and from LPIII to LPIV, so it is not always cut and dry. We also wanted to move from Oracle 9i to 10g.

The first error we got was:
ERROR The error code is 17041
ERROR The Sql Error Code is 17041
ERROR Error encountered while executing Sql Statement INSERT INTO gt_user(USER_ID,DATE_CREATED,USER_ROLE,GT_STATUS,DISPLAY_NAME,EMAIL_ADDRESS)VALUES(?,?,?,?,?,?)
java.sql.SQLException: Missing IN or OUT parameter at index:: 6

We were first advised to edit the migrator script and add the compliant=true statement to all MainRDBTransformer lines:
"${JAVA}" -Doracle.jdbc.J2EE13Compliant=true com.sct.pipeline.migration.rdb.MainRDBTransformer

That didn't help. Same error.
We next tried putting some updated RDB files (a_mig-1.2.jar) in our WEB-INF directory that SCT gave us. Didn't help.
We next tried using various different versions of the JDBC driver. Didn't help.
We were next advised to try migrating from 9i to 9i, instead of 9i to 10g. Didn't help.

Finally, we were told to try this:
Before you do the migration make sure and only pass this to the migration import.
migration.mode=import
migration.subsystem=platform
migration.dataroot=/mnt/dmp/LPIII/LPIII_data

And that worked. I guess there is a bug in the import properties file. Before that suggestion, I had all our database connection information in the import properties file. I guess that that makes the process buggy.

Next we got this error:
/mnt/dmp/LPIII/LPIII_data/gen-Jul1207-142129/pds-before-import.ldif for export: 13 (Permission denied)
migrator encountered an error: operation ImportAG encountered an error

As it turns out, you have to be running the migration as the luminis administrator account, NOT as root. It was also suggested to us to umask 022 when running the migration.

And as of today, we've hit this error:
INFO: executing modifications to restored directory entries...
ldap_modify: No such object
ldap_modify: matched: o=cp
migrator encountered an error: operation ImportPds encountered an error

Apparently it has to do with the ldap path to the uid=calmaster entry being wrong in the tfm-pds-changes.ldif file, and SCT is writing a patch for us to fix this issue.

In the meantime, I'm going to manually add a uid=calmaster entry to the new LDAP in the place that the change ldif is directing its ldap mod commands.

------------------------
July 20th additions:
------------------------

We were able to run the migration script from start to finish, although the system wasn't allowing logins properly when it was done.

I'm waiting for a detailed list of what changes SCT made, but as I understand it now, there were several problems that needed to be overcome. In addition to what was listed above, the following caused problems:

going from port 389 to port 636 on the ldap server (require additional property=remove values in the migration-config.properties file located in CP_WEBINF/config).

using a different cpadmin name (migration-config.properties additions again).

I'll update the exact changes when I get them.