Hi,
We referenced the upgrade article at https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html
We are trying to upgrade our CQ 5.6.1 to AEM 6.1 with MongoDB.
We unpacked aem-quickstart-6.1.0.jar, we ran the -v -x crx2oak twice to generate the crx2oak.properties and OSGI configuration.
We have a mongodb installed and running.
We performed the migration and the upgrade.log showed CRX2Oak.java:358 Conversion to MongoDB took 18678314 msec
We ran the actual AEM upgrade by specifying -r crx3,crx3mongo,author and referenced the mongodb instance on our server. We saw database activities and then everything stopped. The error.log showed
10.09.2015 19:38:24.007 *INFO* [FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type change for sling:Folder requires repository scan: org.apache.jackrabbit.oak.plugins.nodetype.NodeTypeDefDiff[
nodeTypeName=sling:Folder,
mixinFlagDiff=NONE,
supertypesDiff=NONE,
propertyDifferences=[
org.apache.jackrabbit.oak.plugins.nodetype.NodeTypeDefDiff$PropDefDiff[itemName=*, type=MAJOR, operation=MODIFIED]
],
childNodeDifferences=[
org.apache.jackrabbit.oak.plugins.nodetype.NodeTypeDefDiff$ChildNodeDefDiff[itemName=*, type=TRIVIAL, operation=MODIFIED]
]
]
10.09.2015 19:38:24.008 *INFO* [FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type cq:ClientLibraryFolder was not changed
10.09.2015 19:38:24.008 *INFO* [FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type sling:OrderedFolder was not changed
10.09.2015 19:38:24.008 *INFO* [FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type granite:Component was not changed
10.09.2015 19:38:24.008 *INFO* [FelixStartLevel] org.apache.jackrabbit.oak.plugins.nodetype.TypeEditorProvider Node type cq:ContentSyncConfig was not changed
10.09.2015 19:39:23.676 *INFO* [oak-repository-executor-1] com.adobe.granite.repository Service [380, [org.apache.jackrabbit.oak.api.jmx.SessionMBean]] ServiceEvent REGISTERED
When we looked into the /system/console, we saw
Bundle information: 409 bundles in total, 174 bundles active, 3 active fragments, 22 bundles resolved, 209 bundles installed
The upgrade process seemed to have just stopped. Any ideas?
Thank You
Solved! Go to Solution.
Views
Replies
Total Likes
If you followed the AEM docs and ecounterted this issue - this looks like a bug or issue that was encountered due to something in your specific environment. This looks like you need to get support to help you address the issues described here. I recommend opening a support ticket here:
https://helpx.adobe.com/marketing-cloud/contact-support.html
Views
Replies
Total Likes
If you followed the AEM docs and ecounterted this issue - this looks like a bug or issue that was encountered due to something in your specific environment. This looks like you need to get support to help you address the issues described here. I recommend opening a support ticket here:
https://helpx.adobe.com/marketing-cloud/contact-support.html
Views
Replies
Total Likes
Views
Likes
Replies