Hi
I am using AEM 6.5, and it is observed that we are getting frequently below error when we have taken PROD instance copy to lower environment.
Error occurred while obtaining InputStream for blobId {.....}.
Steps followed: 1) Index consistency, which has shown 20 invalid indexes
2) Fixed all invalid indexes through offline index
3) Removed unreferenced files and then offline compaction completed, after that restarted AEM but when we deploy code we are facing above blob id issue.
Please suggest how to resolve it.
Solved! Go to Solution.
Views
Replies
Total Likes
Hello @pradeep_kumarb1,
Looks like the issue is because some files in your data store are missing when moving production instance to lower environment.
How did you manage to copy production instance? Was it running while copy was in progress? If yes, then please re-consider taking the copy after the AEM is gracefully stopped.
Have a look on this document: https://helpx.adobe.com/in/experience-manager/kb/oak-blobstore-inconsistency-blobId.html and ensure all the steps are followed properly.
Hope this helps!
Jineet
Hello @pradeep_kumarb1,
Looks like the issue is because some files in your data store are missing when moving production instance to lower environment.
How did you manage to copy production instance? Was it running while copy was in progress? If yes, then please re-consider taking the copy after the AEM is gracefully stopped.
Have a look on this document: https://helpx.adobe.com/in/experience-manager/kb/oak-blobstore-inconsistency-blobId.html and ensure all the steps are followed properly.
Hope this helps!
Jineet
@Jineet_Vora- Thanks for the update.
How did you manage to copy production instance? Was it running while copy was in progress? : We have taken PROD copy after stop AEM instance.
https://helpx.adobe.com/in/experience-manager/kb/oak-blobstore-inconsistency-blobId.html - We have already followed this document, which did not helpful to fix the issue.
The error shows blob id missing when we deploy code but we tried to fix the blob id, which we taken from another instance to running instance but the problem here is same error occurred and display different blob id when we deploy the code again.
Views
Replies
Total Likes