Solution : https://service.sap.com/sap/support/notes/921951 (SAP Service marketplace login required)
Summary :
SAP Note addresses an issue where switching data export from XSTRING format in OLAP cache to an internal table causes format errors during IMPORT operations across servers. This occurs because the system expected data to be stored as XSTRING in media (cluster table and shared memory), and not as an internal table. The solution includes expanding the deletion functionality in reports, allowing users to clear all cache storage media on application servers without changing cache modes. From Support Package Stack 31 onwards, cache clearing across servers is automated by RFC. Prior to this, manual report execution on each server is necessary with specific configurations.
Key words :
sapbwnews bw support package 17 netweaver'04 stack 17, shared memory/main memory, 10 content import support package 25, 0b import support package 31, server-dependent storage media, olap cache storage media, support package stack 30, support package stack 31, 50 import support package 17, 1 content support package 25
Related Notes :
982402 | Import_Container_Missing and cache entries w/o buffer ID |
935656 | Cache enqueue attempts cause performance problems |
914677 | Long runtime in the cache with export to XSTRING |
913324 | Cache commit time is relatively long in the statistics |
898545 | OLAP cache, entries disappear |
885837 | References to deleted cache entries remain |
872277 | SAPBWNews BW Support Package 17 NW'04 Stack 17 RIN |
872274 | SAPBWNews BW 3.1 Content Support Package 25 |
872272 | SAPBWNews BW 3.0B Support Package 31 |
859456 | Increasing performance using the cache |
856221 | Deletion of entire cache with BLOB and Cluster table |
790859 | Dump with OLAP cache with file access due to netwk problems |
766431 | Cache displacement (shared memory) does not work correctly |
751402 | Cache use: Can change queries w/ variables during navigation |