LDN - Luminis Developer Network

There is no way to migrate the data without using the supplied migration process.
Are you in contact with connect.sungardhe.com and working through the issues one at a time? The migration takes most people months to accomplish. At least it did for myself and a few other Luminis admins that I've talked to.

If sungard is unable to resolve your issues, your next step would be to contract them to do it. It is probably cheaper in the long run if you consider your pay for 3 months:) At least, that is how I'd phrase it to my managers if I had to do it again:)

Hi Alan,

I had the same thought before and got the "partial" solution from SunGard a month ago:

This is only limited supported but has been done by other schools and should work fine. You can modify the $CP_ROOT/bin/migrator script so that only the data you want will be migrated to the new server. In the script, search for "import-platform" and edit the execution plan in there. Just remove the bits you don't want to import. Then run a complete export of your LP III.3.3 system and run the modified migrator script.

Here is the "How To":
Editing the 'import-platform' BuildExecutionPlan in the migrator script will determine which procedures will run when the migrator is executed with migration.mode=import and migration.subsystem=platform.

There is no documentation available with regards to hacking the migrator script, so SunGard advise extreme caution if you decide to proceed at your own risk with editing the migrator script before execution. You should be prepared to start over the import completely (including restoring the target LDAP and database tables to their clean pre-migration state) if something goes amiss.

The first few specs in the BuildExecutionPlan...

"$IMPORT_VCHECK_SPEC" \
"$PLATFORM_SHUTDOWN_SPEC" \
"$LOAD_IMPORT_PROPERTIES_SPEC" \
"$GENERATE_MAPPINGS_SPEC" \

... should never be removed, except possibly in the latter case (GENERATE_MAPPINGS_SPEC) if you are reusing existing mappings files that were already successfully generated and exist in your migration.dataroot directory.

Beyond that, as a case in point, "$IMPORT_PDS_SPEC" is defined like this...

IMPORT_PDS_SPEC="ImportPds:import directory service data" (~line 1793)

... so this spec of the import-platform BuildExecutionPlan will execute the 'ImportPds' procedure (~line 1028).
---End of How To---

I decided not to do it because our LP IV will go live after July 4 weekend and I don't have time to try what to modify, so we are using the original migration plan.

Good luck if you chose to go this way and hope it helps.

Thanks,
Arion