More on Luminis IV migration

0
No votes yet

I finally did get a (possibly) successful migration. Some accounts can login and others can't. Don't know why. I probably won't try to fix it, but will re-install and migrate again. Notes from this attempt:

Read 1-21BG0A and 1-2AG4ZG and used the new migrator script, installed a_mig-1.8.jar and migration-config.properties in the appropriate places.

Problems:
1 New migrator script did not work on unix.
Script contained CR and LF which does no work in unix. Fixed: removed CR.

2 Database inconsistencies.
ERROR The source and target table names are UP_CARS and UP_CARS.
For some reason my III.3.3 database is missing UP_CARS and UPC_XML_DATA.
Solved - created the tables in the III.3.3 Oracle instance based on the IV instance.

3. Can't make LDAP backup files.
There seems to be a security constraint on backing up the LDIF files and the migrator exits.

INFO: backing up current directory data...
ldiffile: /opt/migdata/gen-Oct0107-102539/pds-before-import.ldif
01/Oct/2007:10:32:52 -0700 - can't open /opt/migdata/gen-Oct0107-102539/pds-before-import.ldif for export: 

Response Centre replied and indicated this is because I was running the migrator script as root. The script runs some commands as the unix Luminis owner which does not have write access to directories created by root. So this means that page 3-18 of the Installation Guide (Version F, Mar 6, 2007) is wrong! You must run the migrator script as your Luminis unix owner (mines called lmadmin), not root.

Note: I ran the migrate directly to IV.0.1.5. This may be part of my problem. If you really want to do this (not sure I should have) you need two small changes to the migrator script: change the ImportVersionCheck() function to accept 4.0 instead 4.0.0.0 and change the StopLdap() function, adding a -a to the stop command.