© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.
The scenario of the migration applies when migrating from either:
- WebSphere® Application Server Toolkit V6.0.x (or earlier) to V6.1.x
- IBM Rational® Software Development Platform V6.0.x (or earlier) to V7.0.x
Hereafter, the term product represents WebSphere Application Server Toolkit or IBM Rational Software Development Platform, the term latest version represents version 6.1.x for Application Server Toolkit and version 7.0.x for IBM Rational Software Development Platform, and the term earlier version represents version 6.0.x (or earlier) for both Application Server Toolkit and IBM Rational Software Development Platform.
Problem Symptom:
If you migrate EJB projects, EAR or JAR files, the backends might fail to migrate to the latest version of the product. For example in the latest version of the product, you might experience the Map.mapxmi file fails to open in the editor, and the .log file contains NonUniqueException stack traces.
Verify if your EJB project or JAR file contains any EJB to RDB mapping backends using a relational table where a column and constraint have the same name.
Solution:
In the earlier version of the product, edit the .tblxmi file in question with the table editor. Change the primary key or foreign key constraint name to another name, other than an existing name of a column.