Hi
Is it possible not to use migration shell script provided by Sungard and manually move customized data from luminis 3.3.3.* to luminis IV?
I'd been having so much problems trying to migrate data from our school luminis 3.3.3.64 to newly installed luminis IV server using migration script.
If it is possible, what do we need to move and how? Thanks in adbvance.
Alan
PCOM
Comments
Nope
I do not believe that would be possible. There is no extensive documentation on the internal workings of Luminis, so you would be having to analyze the database and ldap changes, for example, by hand, and then writing transformation scripts.
I started trying to migrate from 3.3 to 4 very early in the migration script version, and worked through almost every problem with SCT. Contact Luminis support. By now, they should have easy answers to most of the problems with the migration script.
Thanks for reply!
Hi Jason
There were 2 questions that I dont understand with the migrator script:
1. "${JAVA}" com.sct.pipeline.migration.ds.PermissionHandler "${GEN_DIR}/mta.txt" || exit 1 (There is no mta.txt anywhere in luminis 3.3.3.* and luminis IV)
2. cp "${IO_DIR}"/jaas.conf "${SECURITY_DIR}" (SECURITY_DIR was pointed to luminis 3.3.3 structure d:\luminis\products\jdk.... and it gives no file found error. I put the following line SECURITY_DIR="${JAVA_HOME}/jre/lib/security" in LoadImportProperties() because the error)
I had to comment out the first line and make changes to the 2nd line in order for the migrator to complete with 1 error and did you have the same errors???
Alan
I did not have those
I did not have those specific errors.
I listed several of my errors on my blog at this site at http://www.lumdev.net/node/1436
Use the script
I think you pretty much have to use the script. Having said that, I've had to dive into it a few times to see what's going on.
I think it's a matter of dogged pursuit. Keep trying, read all the notes here, and keep in constant touch with the Response Centre.
Also, make note of all the gotcha's. For example: the migration manual is *wrong* on page 3.18. On unix, you must import as the cp user, *not* as root.
bob.