Segment Not Found error during migration to AEM Cloud Service in AEM
In Adobe Experience Manager (AEM), content extraction during migration to AEM Cloud Service can fail with a Segment Not Found error. The issue appears as TAR index errors and unrecognized magic number messages in the logs, preventing successful content extraction. To fix this issue, update the Content Transfer Tool to a version that is compatible with the AEM 6.5 LTS version in use.
Description description
Environment
- Adobe Experience Manager (AEM) 6.5 (AMS or on-premise), migrating to AEM Cloud Service
Symptoms
-
Content extraction fails during Content Transfer.
-
Log entries similar to:
SegmentTarReader - Unable to load index of file dataXXXXXX.tar: Unrecognized magic numberSegmentTarManager - No index found in tar file dataXXXXXX.tar, skipping... -
The issue isn’t resolved by server isolation or offline compaction.
Cause
An outdated or incompatible Content Transfer Tool package doesn’t match the AEM 6.5 LTS version in use. As a result, the tool can’t read the TAR index files correctly, which leads to content extraction failures.
Resolution resolution
Follow these steps to resolve the issue:
- Identify the version of the Content Transfer Tool package currently installed on your AEM author environment.
- Check the version of your AEM 6.5 instance, including the Service Pack level.
- Download the latest Content Transfer Tool package that is compatible with your AEM 6.5 version from the official Adobe documentation.
- Install the updated Content Transfer Tool package on your AEM author environment.
- Verify that all Content Transfer Tool bundles are active by navigating to
/system/console/bundlesand reviewing their status. - Restart the Content Transfer process from your AEM author environment.
- Monitor the logs to confirm that the
Segment Not Founderror no longer occurs and that content extraction completes successfully