Oak traversal warnings and performance issues with Content Fragment Models in AEM LTS

Last update: July 20, 2026

This article explains how to resolve Oak traversal warnings and performance issues with Content Fragment Models in Adobe Experience Manager (AEM) LTS after migrating from AEM 6.5 by ensuring the required Content Fragment index is installed and active.

Description description

Environment

Adobe Experience Manager (AEM) LTS, after migration from AEM 6.5.

Issue/Symptoms

Oak traversal warnings appear in logs when opening or editing Content Fragment Models (CFMs) in the author environment.
Performance degradation is observed during CFM operations.
Example query from logs:

select *
from [ dam:Asset]  as a
where [ jcr:content/contentFragment]  = 'true'
and [ jcr:content/data/cq:model]  = '/conf/

The query traverses all descendants under /content/dam and does not use an index.

Cause

After migration, the required out-of-the-box fragments index is missing. As a result, queries with option(index tag [ fragments] ) traverse the repository instead of using an index, causing warnings and performance issues.

Resolution resolution

To fix the Oak traversal warnings and Content Fragment Model performance issue, follow these steps:

In AEM, navigate to the Oak indexes at /oak:index and check for an index named fragments.
Ensure the index is present and that its status is active.
If the fragments index is missing or not active, download the supported Content Fragment and GraphQL index package for AEM 6.5 LTS from the official Adobe distribution site.
Install the package using AEM Package Manager.
Confirm that /oak:index/fragments is present and its status is active.
If the index status is not active, trigger reindexing by setting reindex=true on the index definition and saving the changes.
Confirm that Oak traversal warnings no longer appear during Content Fragment Model operations.
Validate improved performance when opening or editing CFMs.

recommendation-more-help

experience-cloud-kcs-help-kbarticles