Issues with AEM 6.4 Upgrade | Community
Skip to main content
veereswarasastr
Level 2
October 23, 2018
Solved

Issues with AEM 6.4 Upgrade

  • October 23, 2018
  • 5 replies
  • 3753 views

When upgrading from AEM 6.2 to AEM 6.4, THe below step is aborting.

C:\Workstation\AEM6.2\author>java -Xmx4096m -jar aem64-author-p4504.jar -v -x crx2oak -xargs --load-profile segment-no-ds

Loading quickstart properties: default

Loading quickstart properties: instance

org.apache.commons.cli2.OptionException: Unexpected --load-profile while processing Use these options on the Quickstart command line.

        at org.apache.commons.cli2.commandline.Parser.parse(Parser.java:99)

        at com.adobe.granite.quickstart.base.impl.Main.<init>(Main.java:594)

        at com.adobe.granite.quickstart.base.impl.Main.main(Main.java:981)

Quickstart: aborting

Please assist

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by veereswarasastr

java -Xmx4096m -jar aem64-author-p4504.jar -v -x crx2oak -xargs -- --load-profile segment-no-ds

This worked for me

5 replies

Hemant_arora
Level 8
October 23, 2018

Use --skip-checkpoints to force the migration

veereswarasastr
veereswarasastrAuthorAccepted solution
Level 2
October 23, 2018

java -Xmx4096m -jar aem64-author-p4504.jar -v -x crx2oak -xargs -- --load-profile segment-no-ds

This worked for me

smacdonald2008
Level 10
October 23, 2018

Is your issue solved.

Nirmal_Jose
Adobe Employee
Adobe Employee
October 24, 2018

java -Xmx4096m -jar aem-quickstart.jar -v -x crx2oak -xargs -- --load-profile segment-no-ds

this will work, as in the command there is a double double dash -> -- --load-profile segment-no-ds

November 9, 2020
Thanks for me only dashes was the issues
Nirmal_Jose
Adobe Employee
Adobe Employee
October 24, 2018

Not relevant, but same error will come https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/in-place-upgrade.html#performing-the-upgradehttps://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/in-place-upgrade.html

Determining the correct upgrade section

Step 3 will show the same error again

This is because of the documentation error. The document says to use
java -jar aem-quickstart.jar start -c crx-quickstart -i launchpad -Dsling.properties=conf/sling.properties -Dsling.run.modes=publish,crx3,crx3tar
But start command is not available for aem-quickstart.jar which is a sibling of crx-quickstart folder.

start is available only for /crx-quickstart/app/aem-quickstart*.jar

I have used the below command

java -jar aem-quickstart.jar -r author,nosamplecontent,websquad3,crx3,crx3tar,crx3tar-nofds -p4502

crx3tar-nofds is used since I have S3 datastore