Duplicated ******_objects folder Error with the Intelligent Cube Cache

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Symptom

After upgrading from 10.3 to 10.11, the size of the Intelligent Cube cache directory increased 4 times due to the amount of ******_objects folders generated under the cache directory. The ******_objects folder size also increased after running the Dossiers against the cube.
Before the upgrade, the size of the Intelligent Cube cache directory was about 60G+. After upgrading to 10.11,  the size of the Intelligent Cube cache directory increased to 300G+. This size includes the ******_objects folder with a size of 277G.

Reproduce Steps

1. Install 10.3 (version 10.4.8 or prior).
2. Publish cubes.
3. Upgrade 10.3 to 10.11+ with the feature "Cube Memory Governing for Attribute Element Indexes" on (in 10.11 and newer versions, this feature is enabled by default).  
4. Upgrade the metadata and use the same cube cache files generated in 10.3.
5. Load cube caches in 10.11+, and select the cube index growth setting “Maximum % growth of an Intelligent Cube due to indexes” (e.g. set it as 50%)
6. Duplicate Element Block files will be dumped into the same ******_objects folder.

Why is this happening?

The issue has to be run against old cube cache files in version 10.4.8 or prior, and loaded on 10.11+ with the feature "Cube Memory Governing for Attribute Element Indexes" enabled (in 10.11+, this feature is enabled by default). After each unload/reload, and running the Dossiers against the cube, the duplicate Element Block files will be dumped into the same *****_objects folder. 
This is because with this feature enabled, the element block ID will be saved to the new cube cache. The old cube files don't have this property, so new IDs will be generated every time the cube is reloaded. Thus, it will create duplicated Element Block files on the disk ******_object folder.

Solution

After republishing the cubes in 10.11+, the new cube files have the element block ID property, and thus duplicated files are not created. The solution is to republish the cube after upgrading instead of reusing old cube caches.
Strategy also recommends that customers to follow best practices for cache files during an upgrade: delete the cube caches > upgrade > republish them.