Cleaning Up Terracotta Persistent Caches
In a clustered environment, if Analytic Engine is configured to use Terracotta persistent caches, and you accidentally modify the Analytic Engine database while the Analytic Engine is shut down, then the caches become inconsistent with the database. As a result, Analytic Engine fails during startup.
To enable the Analytic Engine to start up properly, you must use the flushCaches tool to clear any inconsistent Terracotta persistent caches. The tool is available in the Software AG_directory \optimize\analysis\bin directory.
Important:
Before you run the flushCaches tool, verify that all Analytic Engine nodes are shut down.
To clean up
Terracotta persistent caches
1. In your Software AG installation folder, navigate to Software AG_directory\optimize\analysis\bin and open a command prompt.
2. Run flushCaches.bat/sh.
3. To clear the required caches, perform one or more of the followig operations by entering the corresponding command in the console:
To list all known caches in a file, enter the following command:
On a Windows environment:
flushCaches -dump [fileName]
On a Unix environment:
./flushCaches.sh -dump [fileName]
where you must provide a new file name using the fileName parameter.
To clear caches that are listed in the specified file, enter the following command:
On a Windows environment:
flushCaches -file [fileName]
On a Unix environment:
./flushCaches.sh -file [fileName]
where you must provide a file that contains caches to be cleared using the fileName parameter. Before you use this command, you must verify that all required caches are listed in the file. You can edit the file by adding and/or removing cache names.
To clear all clustered caches, specified in the sag.opt.clusterable.caches.xml file available in your
Software AG_directory \optimize\analysis\conf\Caching directory, enter the following command:
On a Windows environment:
flushCaches -all
On a Unix environment:
./flushCaches.sh -all
Note:
If you must clear caches that are not clustered or listed in the sag.opt.clusterable.caches.xml file, you must add their names in a file and clear them using the flushCaches -file [fileName] command instead.
4. Restart the Analytic Engine.
When you restart the Analytic Engine, the cleared caches are reloaded from the Analytic Engine database, thus ensuring that the Terracotta persistent caches are in a consistent state.