For more information, see Online Revision Cleanup. Courses Tutorials Certification Events Instructor-led training View all learning optionsI have a scenario where the customer is on AEM 6. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. 11. This contains Quickstart Jar and the dispatcher tools. Learn. 3:. The AEM documentation clearly states it: Offline revision cleanup is the only supported way of performing revision cleanup. Follow these 6 steps for a stress-free and successful content migration process and redesign: Analyze Data from Your Old Website. Along with the transition to Oak in AEM 6, some major changes were made to the way that queries and indexes are managed. Make sure online compaction is disabled to avoid the nodes getting corrupted or removed by data store garbage collection. In AEM Permissions define who is allowed to perform which actions on a resource. • Identify the steps to perform online and offline compaction • Identify the steps to perform AEM maintenance tasks • Given a scenario, determine monitoring criteria and analyze. Offline compaction command fails with "Invalid entry checksum" Search. You can schedule online Tar compaction during weekdays after business hours & offline compaction on weekends (Non-business hours or during your designated Maintenance. OR. Offline compaction needs free disk space (in the size of the segment store = tar files); that's the reason why I recommend to run Datatstore GC before trying to free up space upfront. apache. segment. So, what is the benefit of Offline. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message:Just want to add 1 more point that. In some instances Adobe Customer Care may recommend to checkpoints rm-all along with offline compaction: Download. Get file . AEM 6. - Running offline compaction. Last updated on May 18, 2021 03:09:03 AM GMT. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. run Datastore GC again. Select the “flush type”. Sign In. Last updated on Dec 27, 2022 06:24:18 AM GMT. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Infact its compaction is one of the phases of maintaining the repository. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message:In order to encrypt a string, follow the below steps: 1. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. From the Package Manager UI, select Upload Package. stat files invalidating the cache. AEM as a Cloud Service customers may download the Oracle JDK from the Software Distribution portal and have Java 11 Extended Support until September 2026 due to Adobe’s licensing and support terms for the Oracle Java technology when used in Adobe. Steps to Perform AEM Offline Compaction:1. Offline compaction command fails with "Invalid entry checksum" Search. total crx. 6. As for local AEM development will always need the latest Jar file, so we need to find which one is the latest file by checking the date published column. Continue Reading AEM — Offline Compaction [LINUX] Posted February 17, 2019 Adobe Experience Manager. Check AuthenticationSupport dependencies | And we were able to get the server up and running after following the. In Package Manager UI, locate the package and select Install. Adobe AEM Curl. Also the offline compaction is extensively supported as against the Online compaction which has limited support and available only in AEM 6. Set the log level to “Debug” and point its log output to a separate logfile, like /logs/tarmk-coldstandby. A check mark indicates that an action is allowed. OR. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Issue. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. Offline compaction command fails with "Invalid entry checksum" | AEM. 3:. There are two ways to run tar compaction in aem Online Tar Compaction and Offline Tar Compaction. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. See this article with more tips on how to reduce memory utilization of. How to Use 1. I am using OAK offline tar compaction to reduce the disk space. 6) In order to reduce time spent on offline compaction, make sure the customer has latest Oak version and also they use memory mapped file access option with compaction command. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. Sair, I think Opkar requires the offline tar scripts that you are using to run compaction. As part of the initial source preparation, the Architect is going to run the offline compaction on the on-premise AEM. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. Courses Tutorials Events Instructor-led training View all learning optionsCan you make sure AEM is not running when you are copying over the crx-quickstart folder? If the issue is still there, try to run offline compaction and then try. In some instances Adobe Customer Care may recommend to checkpoints rm-all along with offline compaction: Download. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. x , AEM , AEM TAR Compaction , AEM TAR Compaction Linux , aem63 , centos , Linux , rhel , TAR Compaction , Terminal11. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. You can plan and schedule offline compaction once a month/fortnight if the downtime is affordable. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. . Running an Offline Compaction can fail with. 2: Garbage. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. If you are running AEM version 6. 3 on Windows using oak-run. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. - 280789 Adobe. A Stack Trace similar to the one below can be found in the logs:. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Else, if everything is done on local AEM, and working fine, then create a package of template and deploy on server. Any ways to disable this in AEM 6. Steps to Run Offline Tar Compaction in AEM:-Make sure that you are using correct version of oakrun jar that matches you repository or aem repository version (Refer faq below on how to find correct version of oakrun. o. OR. Offline compaction command fails with "Invalid entry checksum" | AEM. Go to /system/console/configMgr in the AEM instance. Offline compaction : Few may face issues with disk space issue on Segment store folder . The AEM documentation clearly states it: Offline revision cleanup is the only supported way of performing revision cleanup. comp. 6. See this article with more tips on how to reduce memory utilization of. Please consult with AEM Customer Care team for assistance with the. This maintenance functionality is called Revision Cleanup. - Offline indexing of TarMK using oak-run. Kunwar , i have tried with other environment where i have cleanup activities, old package cleanup, offline compaction, version purge( weekly configured) etc. 3:. Work on AEM Infrastructure Dev-Ops practice on AWS. xml with full re-indexing. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. oak-core bundle - Download the oak-run version matching the. 2. Get file . 3 with Oak 1. The console looks like below: 2. 13. AEM Tar Compaction is useful when your AEM Instance start working slowly and your local disk space it is getting Increase. Designed and developed websites/pages in Adobe CQ/AEM by implementing theresponsive design Extensively used Adobe CRX, CRXDE, WCM, Package Manager, Components, Templates, Experience Fragments and DAM Extensively used Adobe Infrastructure and Expert in Online, Offline Compaction. 1 consist of modules associated with release 1. 8-windows . In order to use the script, you should:Report this post Report Report. Based on the log you have provided, you are using the oak run version of 1. 3K. More tasks 30 Enable/disable SAML Enable/disable CRXDE Promote Author Standby to Primary. 3. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. apache. 1, now oak version upgraded to 1. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message:Hi, yes, you should run offline compaction and datastore garbage collection. Carried out AEM maintenance activities involving Monthly backup, workflow purging, Data store garbage collection, Version cleanup Data inconsistency check and offline tar compactionTo determine which version is in use, navigate to /system/console and search for the bundle named O ak Core and check the version. Download the ACS commons tool from ACS Commons Official page 3. 1: Tar Compaction (also known as Revision Cleanup) By running the regular tar compaction, you can not only control the AEM repository size growth, but it will also. arch. memoryMapped=true -Dupdate. Ultima actualizare la May 21, 2021 04:44:38 AM GMT. I had added some package dependencies and then removed them before the issue started. Oak Offline Compaction - Improve performance, avoid memory issues and track progress. AD0-E117 Exam Official Topics: Topic 1: Given a scenario, assess the current state of an architecture/ Determine non-functional technical requirements for solution design. Steps to Run Offline Tar Compaction in AEM:-Make sure that you are using correct version of oakrun jar that matches you repository or aem repository version (Refer faq below on how to find correct version. Topic 2: Identify The Steps To Deploy AEM Packages/ Given A Scenario, Determine The Prerequisites Needed For The Installation Of AEM Instance;. 2 of Apache Oak content repository. Offline Revision cleanup should be used only. If you have the need to run Offline Revision Cleanup prior to the release of Oak 1. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message: Running an Offline Compaction can fail with SegmentNotFoundException when there are integrity issues of the repository. Run Offline Compaction when needed. Duration: 100 Minutes. I am doing an offline Tar compaction on AEM 6. 3, Online compaction is not good in reclaiming disk space. You can plan and schedule offline compaction once a month/fortnight if the downtime is affordable. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. However, in this case, AEM instance needs to be shut down to free up the space. Offline Revision Cleanup: Offline Revision Cleanup (aka Offline Compaction) also helps in reclaiming disk resources by cleaning up old revisions. Adobe CQ 5 blog, AEM blog, AEM 6. A Stack Trace similar to the one below can be found in the logs: Ran Online compaction from Daily and Weekly Maintenance tasks Ran offline compaction The DAM packages were uploaded and installed via CURL commands (Total size of all DAM packages is about 55GB). The permissions are the result of access control evaluations. It is not recommended to run online tar compaction as it affects the performance of current running instance and takes very log time upto 24 hours to complete. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. data. AboutAEM Stack Manager Lambda functions. Trigger offline compaction. Running an Offline Compaction can fail with SegmentNotFoundException when there are integrity issues of the repository. • Identify the steps to perform online and offline compaction • Identify the steps to perform AEM maintenance tasks • Given a scenario, determine monitoring criteria and analyze reports • Determine the correct method to remove a publish instance out of production • Determine the correct method to clone the AEM environmentNote that offline compaction requires a long duration of downtime from 30 minutes to 7 hours (and in extreme cases more time). SKYDEVOPS on Tumblr. Offline compaction command fails with "Invalid entry checksum" | AEM. 15-02-2018 16:48 PST. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Step-02: Setup a parameterized build job, create a string parameter for remote Host. 18. tools. Learn. Specific Issues of AEM 6. Transient workflows do not create child nodes under an. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Päivitetty viimeksi May 06, 2021 05:52:10 AM GMT. 3 for running Offline Revision Cleanup. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Courses Tutorials Events Instructor-led training View all learning optionsSign In. Exam Version: Nov. Create a New Sitemap. A Stack Trace similar to the one below can be found in the logs:You observe SegmentNotFoundException in AEM log files and AEM is not working as expected. 2019 1 an 7 luni. ) Using ACS Commons' Bulk Workflow tool. This is the important part - 366280SYNOPSIS AEM Offline TAR Compaction script, using a custom logback configuration file with custom encoder for better logging. This mechanism will reclaim disk space by removing obsolete data from the repository. Increase the -Xms16G -Xmx16G and retry the offline compaction. Browse to the location where you downloaded the AEM package. Hi All, As AEM 6. This will significantly ease the maintenance of AEM by eliminating the need for offline compaction. Ned - 280789Offline compaction command fails with "Invalid entry checksum" | AEM. Tar compaction reclaims the disk space by removing the obsolete/redundant data from your AEM application. Author servers were scaled up to support upload and install of huge packages, and was later downsized. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. After the package is uploaded, you install it. Scenario 2. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. java -server -XX:MaxPermSize=256m -Xmx1024M -jar aem-author-p4502. 9. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. Issue. It needs to be run manually using a set of commands and oak-run JAR. Courses Tutorials Certification Events Instructor-led training View all learning optionsI am trying to perform a Revision Cleanup activity on AEM Repository to reduce the size of the same by Tar Compaction. apache. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message: The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. If you have the need to run Offline Revision Cleanup prior to the release of Oak 1. As part of the initial source preparation, the Architect is going to run the offline compaction on the on-premise AEM. 3. The console looks like below: 2. Download the oak-run-1. Offline compaction command fails with "Invalid entry checksum" Keresés. model=32 e. I am. In order to complete full re-indexing on AEM the oak-run tool should be leveraged with checkpoints argument. See this article with more tips on how to reduce memory utilization of. Learn. Ostatnia aktualizacja May 21, 2021 12:08:21 AM GMT. 6. We are using AEM 6. If the maximum latency is compatible with the requirements, for. Stop the AEM instance 2. Currently my system having 20GB of RAM, this is pre prod environment and i think 20GB would be sufficient. Hi Federico, have you informed daycare and got their support for online compaction, as the is the only way it is supported. . AEM can be configured to store data in Amazon’s Simple Storage Service (S3). If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message: The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. Offline compaction command fails with "Invalid entry checksum" بحث. aem; or ask your own question. Increase the -Xms16G -Xmx16G and retry the offline compaction. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. Increase the -Xms16G -Xmx16G and retry the offline compaction. Solved: Hi All, I have completed the migration from AEM 6. You observe SegmentNotFoundException in AEM log files and AEM is not working as expected. By running the regular tar compaction, you can not only control the AEM repository size growth, but it will also help improve the AEM application performance. Technical BlogAny ways to disable this in AEM 6. 0 consumes too much disk space because of Tar files getting created after every package install. Offline compaction command fails with "Invalid entry checksum" Szukaj. An AEM Architect is moving existing content from an on-premise AEM to an AEM Cloud Service instance using the Content Transfer Tool. The Repository Size is 730 GB and Adobe Version is 6. 3- Make the necessary changes and push the details. jackrabbit. Resolved it by running offline compaction. May 8, 2019 July 14, 2020 by Shashi, posted in ACS Commons Versioned Clientlibs, Adobe Experience Manager, Adobe Experience Manager 6. x or. 5 introduces two new modes for the compactionphase of the Online Revision Cleanup process: 1. 3 offline Tar compaction error under Windows. In the past the revision cleanup was often referenced as compaction. 1: Tar Compaction (also known as Revision Cleanup) By running the regular tar compaction, you can not only control the AEM repository size growth, but it will also. The 'checkpoints'. 8 and can't guarantee having available disk space 2 times higher than the size of the repository, an early build can be downloaded from here. run offline compaction. 2 to 6. S. An AEM Architect is moving existing content from an on-premise AEM to an AEM Cloud Service instance using the Content Transfer Tool. Here, I have posted the information which I know or gathered from different sources. Ask Question. See this article with more tips on how to reduce memory utilization of. Configure Dispatcher in AEM. Oak Offline Compaction - Improve performance, avoid memory issues and track progress. A Stack Trace similar to the one below can be found in the logs:You observe SegmentNotFoundException in AEM log files and AEM is not working as expected. 6. datastore. If you have the need to run Offline Revision Cleanup prior to the release of Oak 1. You should not expect removed content to be garbage collected right away as the content might still be referenced by other sessions Going forward, keep the online compaction running every day and run offline compaction once a month. In this post, I want to share a few AEM utilities & methods which can help you to not only manage the AEM repository size but also help to improve the AEM application performance. To add more into this, there are many things that can cause unusual increases in disk utilization. Continue Reading AEM — Offline Compaction [LINUX] Posted February 17, 2019 Adobe Experience Manager. Steps to. Offline compaction command fails with "Invalid entry checksum" Search. Run Online and Offline TAR Compaction. Courses Tutorials Events Instructor-led training View all learning optionsPerform offline compaction using steps below - Go to /system/console/bundles and note down the version of org. So, adobe come up with two housekeeping activities online and offline tar compaction to control the size of aem repository. I was doing exactly that. An alphanumeric value will get generated in “Protected Text” field. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. We ran it for 24 hours straight but the activity is still running and no output. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. Offline Revision Cleanup: Offline Revision Cleanup (aka Offline Compaction) also helps in reclaiming disk resources by cleaning up old revisions. Attend local and virtual eventsIn order to complete full re-indexing on AEM the oak-run tool should be leveraged with checkpoints argument. Offline compaction command fails with "Invalid entry checksum" Search. Issue. Open the newly created page and edit the component. Because full. jar version. You can use both online and offline compaction. 1. See this article with more tips on how to reduce memory utilization of. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message:Tar compaction reclaims the disk space by removing the obsolete/redundant data from your AEM application. You can use both online and offline compaction. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. تاريخ آخر تحديث May 06, 2021 05:46:29 PM GMT. Request for Feature Enhancement (RFE) Summary: Online compaction not that effective and observed repository growth and which is causing slowness in author. based on AEM version. And AEM SDK for AEM as a Cloud Service. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. With AEM 6. 1 author . The commands are bing run in an administrative command window and AEM has been sucessfully shut down (ie no Java processes are running) I am seeing the following error: 10:35:14. If you have the need to run Offline Revision Cleanup prior to the release of Oak 1. Check at the OS level if the AEM java process is causing high CPU utilization: If AEM is causing high CPU utilization then run the out-of-the-box profiling tool for a few minutes and analyze the result. jackrabbit. 3. Topic 13: Determine The Correct Method To Perform A Back-Up And Restore/ Identify The Steps To Perform Online And Offline Compaction;Yes its the same. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. 2- Bring it to local IDE. i. 3? We have come across this blog post when solving inconsistency in AEM publish instance segment store. An example of a complete script - offline compaction and logback. The full compactionmode rewrites all the segments and tar files in the whole repository. You can use both online and offline compaction. Tar compaction reclaims the disk space by removing the obsolete/redundant data from your AEM application. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. AEM_61_FASTER_OFFLINE_COMPACTION. Opkar, Nope, I wasn't using the rm-all flag. Migration Checklist. Back Submit SubmitOffline compaction command fails with "Invalid entry checksum" | AEM. If you have the need to run Offline Revision Cleanup prior to the release of Oak 1. This is offered out-of-the-box for both AEM assets authoring and publishing. 8 and can't guarantee having available disk space 2 times higher than the size of the repository, an early build can be downloaded from here. Courses Tutorials Certification Events Instructor-led training View all learning options Tutorials Certification Events Instructor-led training View all. 3 the compaction job is not working, as the OAK version seems to be changed. To perform the Online AEM Tar Compaction for AEM Quick-start repository, so it can free unwanted disk space and increase the performance of the AEM instance can speed up the working of AEM Instance. Meet our community of customer advocates. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message:AEM — Offline Compaction [LINUX] March 28, 2019 July 14, 2020 by Shashi , posted in Adobe Experience Manager , Adobe Experience Manager 6. . 3 for running Offline Revision Cleanup. If you had "logging enabled" during the Offline Revision Cleanup, watch out for the message: The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. 0. Try Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6. jar). Running an Offline Compaction can fail with SegmentNotFoundException when there are integrity issues of the repository. 1 which is old. Offline compaction command fails with "Invalid entry checksum" Vyhľadať. Offline compaction : Few may face issues with disk space issue on Segment store folder . Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. Learn. run Datastore GC again. . Please suggest how to resolve it. The current major release of Oak (1. 4 is not recommended as per the official documentation at [1] When to use Online Revision Cleanup as opposed to Offline Revision Cleanup? Online Revision Cleanup is the recommended way of performing revision cleanup. You can use both online and offline compaction. This post explains about offline compaction techniques. Tar compaction reclaims the disk space by. A Stack Trace similar to the one below can be found in the logs:Hi ! So from your posting I understand that you are experiencing unusual and unexpected repository growth. In order to complete full re-indexing on AEM the oak-run tool should be leveraged with checkpoints argument. 3, the repository growth will increase rapidly due to oak bug. Is that correct? (Although I'm - 417379Can you make sure AEM is not running when you are copying over the crx-quickstart folder? If the issue is still there, try to run offline compaction and then try. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. Adobe Documentation:. 1/6. 1 or 6. In this post, I want to share a few AEM utilities & methods which can help you to not only manage the AEM repository size but also help to improve the AEM application performance. The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. ) Using ACS Commons' Bulk Workflow tool. Step-04: Setup a String parameter for Remote User. We are using AEM 6. From startup to Google and back again (Ep. Confidential . 964 h (17870089 ms). Running an Offline Compaction can fail with SegmentNotFoundException when there are integrity issues of the repository. Some potential causes: The instance doesn't start at this point, and performing a repository check ("oak-run check" tool) cannot detect this corruption. Offline compaction scripts is basically divided into 5 parts:-Shutdown AEM Instance Find Old Checkpoints This version of oak-run should be used on AEM 6. md. Find the version against the oak files. By running the regular tar compaction, you can not only control the AEM repository size growth, but it will also help improve the AEM application performance. jar is the simplest oak-run. 2: Garbage Collection By running. On the other hand: If you can attach temporarily more disk space, you can omit step 1. The estimated time is 7-8 hours for the activity to get completed. The Repository Size is 730 GB and Adobe Version is 6. The subsequent cleanup phase can thus remove the maximum amount of garbage across the repository. See this article with more tips on how to reduce memory utilization of. Increase the -Xms16G -Xmx16G and retry the offline compaction. . AEM System Administrator. Step-03: Setup a string parameter for remote User. Topic 2: Translate high-level business goals to functional requirements/. 11 and our online revision cleanup is failing for quite some time and as a result segment store size has increased to 1178%. to gain points, level up, and earn exciting badges like the newOffline compaction command fails with "Invalid entry checksum" | AEM. We are observing errors in the output of the checkpoints command during offline compaction of AEM6. AEM 6. arch. As to which is recommended, Offline compaction is to be preferred in most of the cases and Online to be used in case when AEM instance can not be brought offline for compaction. Offline Compaction fails with SegmentNotFoundException & IllegalArgumentException. Make sure that the oak-run tool version matches the oak-core version installed in your AEM instance. AEM OAK Offline Compaction on Remote Windows Server. Running an Offline Compaction can fail with SegmentNotFoundException when there are integrity issues of the repository. If you have the need to run Offline Revision Cleanup prior to the release of Oak 1. 1. xml with full re-indexing. Repair is not possible since the data was deleted by the failed Offline Revision Cleanup. We ran it for 24 hours straight but the activity is still running and no output. Disclaimer: This is just a custom guide to run compaction on AEM Author/Publish service on remote windows server, this could be more technical and advanced guide, if you do not understand or don’t know what you are doing, I kindly request you to take extreme caution. Going through all the AEM systems configuration (workflows, any orphan process, etc. Hi, Seems same exception is answered in below post How to cleanup unavailable blob id?SYNOPSIS AEM Offline TAR Compaction script, using a custom logback configuration file with custom encoder for better logging. The first try with 32 GB RAM failed. Please let me know any docs to implement online compaction. In addition to what Hamid mentioned, run the following : - Offline compaction - Followed by Datastore Garbage Collection Going forward, keep the online compaction running every day and run offline compaction once a month. Tools Needed: Download Oak-run JAR form here. 3 for running Offline Revision Cleanup. Offline compaction command fails with "Invalid entry checksum" | AEM.