Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Content package import from 5.6.1 to 6.0.0

Avatar

Level 1

Hi,

We are experiencing an issue when trying to import content packages from an existing  5.6.1 installing towards a new 6.0.0 (SP1 / hotfix-5176) Installation. We use MongoDB together with customBlobStore (file based). Although it seem to be in a full MongoDB persistence config as well.

We get either Merge Errors or if we increase the save threshold the installation just seems to give up without any error.

I don't understand why content made by 5.6.1 is not compatible with 6.0.0. 

 

Anyone an idea how to tackle this or point me in the right direction;

Thanks!

 

Kind regards,

Kris.

Examples of the mergeErrors.

 *ERROR* [qtp14120923-628] org.apache.jackrabbit.vault.fs.io.Importer Error while committing <path>: javax.jcr.InvalidItemStateException: OakMerge0001: OakMerge0001: Failed to merge changes to the underlying store (retries 5, 122695 ms)

 

com.day.jcr.vault.packaging.PackageException: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.InvalidItemStateException: OakMerge0001: OakMerge0001: Failed to merge changes to the underlying store (retries 5, 24423 ms)
    at com.day.jcr.vault.packaging.impl.JrVltJcrPackageAdapter.install(JrVltJcrPackageAdapter.java:109)

   ...
Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakMerge0001: OakMerge0001: Failed to merge changes to the underlying store (retries 5, 24423 ms)
    at org.apache.jackrabbit.oak.spi.state.AbstractNodeStoreBranch.merge(AbstractNodeStoreBranch.java:331)
    at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreBranch.merge(DocumentNodeStoreBranch.java:148)
    at org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder.merge(DocumentRootBuilder.java:159)
    at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1306)
    at org.apache.jackrabbit.oak.core.MutableRoot.commit(MutableRoot.java:247)
    at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.commit(SessionDelegate.java:390)
    at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.save(SessionDelegate.java:536)
    ... 83 more
Caused by: org.apache.jackrabbit.mk.api.MicroKernelException: The node 10:/oak:index/cqTags/:index/<tag>/<path> was already added in revision
r149aa1ccfcc-1-1, before
r149cdcde6ad-0-1; document:
{_lastRev={r0-0-1=r149aa1ccfcc-1-1},
_id=10:/oak:index/cqTags/:index/<tag>/<path>,
_modified=1416497055,
_modCount=1056,
_commitRoot={r149aa1ccfcc-1-1=0},
_children=true,
_deleted={r149aa1ccfcc-1-1=false}},
revision order:

    at org.apache.jackrabbit.oak.plugins.document.Commit.checkConflicts(Commit.java:510)
    at org.apache.jackrabbit.oak.plugins.document.Commit.createOrUpdateNode(Commit.java:428)
    at org.apache.jackrabbit.oak.plugins.document.Commit.applyToDocumentStore(Commit.java:330)
    at org.apache.jackrabbit.oak.plugins.document.Commit.applyToDocumentStore(Commit.java:226)
    at org.apache.jackrabbit.oak.plugins.document.Commit.applyInternal(Commit.java:195)
    at org.apache.jackrabbit.oak.plugins.document.Commit.apply(Commit.java:180)
    at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreBranch.persist(DocumentNodeStoreBranch.java:179)
    at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreBranch.persist(DocumentNodeStoreBranch.java:87)
    at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreBranch.persist(DocumentNodeStoreBranch.java:39)
    at org.apache.jackrabbit.oak.spi.state.AbstractNodeStoreBranch$InMemory.merge(AbstractNodeStoreBranch.java:515)
    at org.apache.jackrabbit.oak.spi.state.AbstractNodeStoreBranch.merge(AbstractNodeStoreBranch.java:309)
    ... 89 more

Error: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.InvalidItemStateException: OakMerge0001: OakMerge0001: Failed to merge changes to the underlying store (retries 5, 24423 ms)

1 Accepted Solution

Avatar

Correct answer by
Level 2

We had a reply on this issue via Adobe support.

You can remove the index and let it rebuild like this.

Instruction to remove index from MongoDB directly(Bring the cq offline is required so please performe the same in a scheduled maintenance activity)

Stop all AEM instances connected to MongoDB

Run the following
$ wget https://svn.apache.org/repos/asf/jackrabbit/oak/trunk/oak-run/src/main/js/oak-mongo.js
$ mongo <your-mongo-host>/<aem-db> --shell oak-mongo.js
$ oak.removeDescendantsAndSelf('/oak:index/cqTags')

Restart one CQ instance at a time. This will automatically rebuild the index because it is required by AEM.

 

Good to know

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

We had a reply on this issue via Adobe support.

You can remove the index and let it rebuild like this.

Instruction to remove index from MongoDB directly(Bring the cq offline is required so please performe the same in a scheduled maintenance activity)

Stop all AEM instances connected to MongoDB

Run the following
$ wget https://svn.apache.org/repos/asf/jackrabbit/oak/trunk/oak-run/src/main/js/oak-mongo.js
$ mongo <your-mongo-host>/<aem-db> --shell oak-mongo.js
$ oak.removeDescendantsAndSelf('/oak:index/cqTags')

Restart one CQ instance at a time. This will automatically rebuild the index because it is required by AEM.

 

Good to know