AEM SegmentNotFoundException
When these occur on tarMK-based AEM instances, shutdown the instance ASAP and run oak-run check to determine if the repository journal must be rolled back. If the journal is rolled back, some amount of data will be lost. Note that one must use the oak-run version matching the version of oak used in the AEM instance. To determine which version is in use, navigate to /system/console and search for the bundle named O ak Core and check the version. Note that the -Xmx argument used below should be adjusted for the memory available on the system but is a reasonable number for the AEM systems in production. ● One should log all the work done using standard methods such as terminal logging, screen logging, script, etc. in case problems occur. ● Shutdown AEM ● Ideally make a full backup ● cd LOCAL-INSTANCE-DIRECTORY/crx-quickstart/repository ● java -Dtar.memoryMapped=true -Xmx 32G -jar ...