Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

AEM 6.3 Error installing dam package using packageMgr console.


Level 2

Hi, We are using AEM 6.3 and require to upload install prod dam assets and prod content pages into lower environment on a monthly basis. Is there a recommended/efficient (packaging only recent modified/created content) way of doing it. prod dam package size is 3.5 GB - 4GB.  It takes almost an hrs to upload the dam assets package. Installing this prod dam package gives below error for one of the lower instances, 

{"success":false,"msg":"javax.jcr.nodetype.ConstraintViolationException:         OakConstraint0021: /content/dam/myproj/promotional/some-pages/brand-logos/puma-logo.png/jcr:content/renditions/cq5dam.thumbnail.319.31        9.png/jcr:content[[oak:Resource]]: Mandatory property jcr:data not found in a new node"}  But the same prod dam package installs successfully on another lower environment. What could we do to fix this error. And what is the recommended way to  transfer prod assets from one environment to another and replicate.  @kautuk_sahni  @Jörg_Hoh 

5 Replies



jcr:data is the actual binary object. So no - it did not successfully install. 


You'd likely see a missing blob / datastore exception if something referenced this thumbnail rendition.



Use crx2oak to migrate content between repositories.


Are you disabling workflow launchers before you install this enormous content package?

Conceivably the DAM Update Asset workflow is going to run on every asset you add which would add a tremendous amount of needless overhead -- especially given that you're packaging up thumbnail renditions which would automatically be created anyways. 


Level 2

Thanks @aemmarc  We did not get this error on another qa1aem6.3author instance. But we only got this error on qa2aem6.3author. And do we need to use crx2oak to migrate content between different instances of same aem versions aem 6.3.  I assumed only in case of repository difference like migrating content from cq5.6 to aem6.3 we would use crx2oak but in our case it is within prodaem6.3 and qaaem6.3. Yes the dam update asset workflow is disabled. And we see a valid jcr:data present in prod aem6.3 author so not sure what is the error. 



RE : we see a valid jcr:data


Click on "View" which will download the binary as a file.

Save it as "pic.png" and see if the image actually exists. I'd be interested to see if it's a 0-byte file.