Issues with AEM Upgrade from 6.2 to 6.3 | Community
Skip to main content
Level 2
June 5, 2017
Solved

Issues with AEM Upgrade from 6.2 to 6.3

  • June 5, 2017
  • 4 replies
  • 3631 views

Hi All,

  we are upgrading our AEM from version 6.2 to 6.3.  we are facing issues when we run pre-upgrade-tasks from the JMX console.

below are the steps we followed and the issues faced.

1. Took the backup of complete instance.

2. downloaded pre-upgrade-tasks-content-cq62-1.2.4.zip package from package share and installed.

3. we ran runAllPreUpgradeTasks() from the JMX Web Console prechecks.

4. when we ran the above we see below information in the logs

        Startup mode is RESTART, nothing to do

        /var/upgrade/status/preUpgradeBackup.force does not exist, backup will not be forced

        UPGRADE NOT NEEDED - StartupMode is RESTART

5. to run the instance in the upgrade mode we restarted the instance with below command

 

     java -jar -Xmx3072m -Dorg.apache.sling.launchpad.startupmode=update  aem-author-p4502.jar

6. when we restarted the instance in the update runmode and ran runAllPreUpgradeTasks() from the JMX Web Console , we could see in the logs it is preparing for the upgrade with below errors:

    1.  com.day.cq.compat.codeupgrade.impl.mergebackup.CqMergeBackupUpgrade Exception in                                               CqMergeBackupUpgrade.run()     

    javax.jcr.AccessDeniedException: OakAccess0000: Access denied

  2. and we see in the preupgrade popup msg 'disabling replication agents' and the file preUpgradeHCStatus.properties has below content

areAllPreUpgradeHealthChecksOK=false

Maintenance\ Task\ WorkflowPurgeTask=OK

Maintenance\ Task\ RevisionCleanupTask=OK

Modified\ Deprecated\ Indexes=OK

Maintenance\ Task\ com.day.cq.audit.impl.AuditLogMaintenanceTask=OK

Replication\ Agents\ Disabled=HEALTH_CHECK_ERROR

Couldn't figure out the root cause of the issue. Need help and the steps to be followed with upgrade.

Thanks,

Lakshmi.

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 smacdonald2008

This looks like some sort of bug - i advice opening a Support ticket.

4 replies

smacdonald2008
smacdonald2008Accepted solution
Level 10
June 5, 2017

This looks like some sort of bug - i advice opening a Support ticket.

Level 2
August 22, 2017

Lakshmi,

How was this resolved?

Level 2
February 5, 2018

Hi,

Were you able to resolve the issue?

Thanks

kautuk_sahni
Community Manager
Community Manager
February 6, 2018

6.3 includes pre-upgrade checks that need to pass for the upgrade to complete successfully.

You need to disable all the replication agents on your system and make sure the audit log maintenance is configured correctly (“Audit Log Purge Scheduler” in configMgr) so it could be executed pre-upgrade.  .

Kautuk Sahni