Troubleshooting: Application migration fails during SDO regeneration from WebSphere Commerce Version 6 to Version 7

During application migration, any custom physical SDO classes are automatically regenerated. Automatic regeneration reduces the possibility of the custom SDO classes becoming incompatible with the updated WebSphere Commerce components that they extend.

Problem

The automatic regeneration of your customized SDO can fail in some unexpected situations, and the migration ANT task fails with the following message: 
[2009.07.17.08.23.16] VERBOSE: LaunchSDORegenforServer:
[2009.07.17.08.23.16] WARNING: [echoNL] Start to build regenSDO
[2009.07.17.08.23.16] WARNING: [echo] dbType:db2
[2009.07.17.08.23.33] ERROR: BUILD FAILED
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/xml/build.xml:32: The following error occurred while execut
ing this line:
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/xml/build.xml:47: The following error occurred while execut
ing this line:
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/xml/app.xml:151: The following error occurred while executi
ng this line:
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/xml/build.xml:56: The following error occurred while execut
ing this line:
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/xml/build.xml:60: The following error occurred while execut
ing this line:
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/xml/features/BASE/app/60/build.xml:33: The following error
occurred while executing this line:
[2009.07.17.08.23.33] ERROR: /opt/IBM/WebSphere/CommerceServer70/migration/components/component-services/xml/regenerateSDOs.xml:43: Ja
va returned: 13
[2009.07.17.08.23.33] ERROR: Total time: 40 minutes 25 seconds
[2009.07.17.08.23.33] ERROR: [WCIMANT] WCIM has completed the job(s) with errors. Check the log files for details.
.

Solution

If you can determine why your custom SDO regeneration failed, correct the problem and rerun the migration. However, an equivalent solution is detailed in the following steps:

You can manually regenerate the classes by performing the following steps:
  1. In WebSphere Commerce Developer, manually regenerate the physical SDO classes for your customization extension, using the Data Service Layer Wizard. See Migrating custom Physical Service Data Objects.
  2. On your WebSphere Commerce server, rerun the migration of the WebSphere Commerce Application, specifying an additional parameter: -DskipRegenSDO=true.
  3. Deploy your regenerated physical SDOs that you regenerated in WebSphere Commerce Developer to your production environment.
Note: Ensure you successfully regenerate your custom physical SDO classes before attempting to start the WebSphere Commerce Server.