Expand my Community achievements bar.

SOLVED

CQ 5.4 -> 6.1 Migration Issue: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001

Avatar

Level 1

I am getting the following exception when uploading a package to 6.1 AEM instance: 

com.day.jcr.vault.packaging.PackageException: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /apps/test-config/config[[nt:folder]]: No matching definition found for child node test with effective type [nt:unstructured]

    at com.day.jcr.vault.packaging.impl.JrVltJcrPackageAdapter.install(JrVltJcrPackageAdapter.java:109)
    at com.day.crx.packaging.impl.J2EEPackageManager.consoleInstall(J2EEPackageManager.java:329)
    at com.day.crx.packaging.impl.J2EEPackageManager.doPost(J2EEPackageManager.java:171)
    at com.day.crx.packaging.impl.PackageManagerServlet.doPost(PackageManagerServlet.java:144)

...

I understand that the childnode type [nt:unstructured] is not allowed under [nt:folder] node. 

What is the normal approach to carry out such content migration?

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

you can either upgrade in place or deploy your codebase to a new instance. By deploying to a new instance you will lose all your version and audit history. 

If you try deploying again, delete the folder "/apps/test-config/config" before deploying.

I you are doing an upgrade, please be aware of the known issues when upgrading to AEM 6.1

Regards,

Opkar

[1] http://docs.adobe.com/docs/en/aem/6-1/release-notes/known-issues.html

View solution in original post

4 Replies

Avatar

Employee

Hi,

at what stage in the migration process are you? Have you successfully run through all the steps in[1], you have no errors in your error.log when starting your migrated instance?

Are you now importing your custom codebase?

Regards,

Opkar

[1] https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html

Avatar

Level 1

Ja. I am importing my custom codebase from 5.4. But I didn't run through the steps in [1]. Let me try it out and get back to you if I still get the same issue. Thanks a lot.

Avatar

Correct answer by
Employee

Hi,

you can either upgrade in place or deploy your codebase to a new instance. By deploying to a new instance you will lose all your version and audit history. 

If you try deploying again, delete the folder "/apps/test-config/config" before deploying.

I you are doing an upgrade, please be aware of the known issues when upgrading to AEM 6.1

Regards,

Opkar

[1] http://docs.adobe.com/docs/en/aem/6-1/release-notes/known-issues.html