upgradeConfigEngine.sh wp_profile task may fail with message "Duplicate target 'localize-clone'"

upgradeConfigEngine.sh wp_profile task may fail with message "Duplicate target 'localize-clone'"

You may see this error when running task
[exec] BUILD FAILED
[exec] .../PortalServer/installer/wp.profile/config/includes/localize_clone.xml:20: Duplicate target 'localize-clone'
[exec] Total time: 0 seconds
[exec] java.lang.NullPointerException
[exec] at java.util.StringTokenizer.<init>(StringTokenizer.java:83)
[exec] at java.util.StringTokenizer.<init>(StringTokenizer.java:61)
[exec] at com.ibm.wps.config.ConfigEngineUtils.isPropertyInStringList(ConfigEngineUtils.java:478)
[exec] at com.ibm.wps.config.ConfigEngineListener.buildFinished(ConfigEngineListener.java:249)
[exec] at org.apache.tools.ant.Project.fireBuildFinished(Project.java:1848)
[exec] at org.apache.tools.ant.Main.runBuild(Main.java:688)
[exec] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[exec] at org.apache.tools.ant.Main.start(Main.java:150)
<truncated>

The reason for the 'Duplicate' exception may be due to a download of the 61X Portal cloning files at some previous point. The Portal cloning tasks were incorporated into Portal 7 and so already exist in the binary installation.

http://www-01.ibm.com/support/docview.wss?uid=swg21390600

This can typically occur when you migrate Portal v6.1/WAS 7 to Portal7/WAS 7 and copy the profile and might have extracted the localize-clone scripts into the ConfigEngine directory. In Portal 7, localize-clone was actually included in the product, so this can cause a conflict.

If this is the case, you need to install the Portal 7 environment to use the same WAS binaries as the Portal v6.1 environment:

http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=IBM+WebSphere+Portal+7+Product+Documentation#action=openDocument&res_title=Setting_up_the_target_portal_when_the_source_portal_runs_on_a_V7_application_server_wp7&content=pdcontent

So you do not copy the profile at all.