Use
Synchronization of Page Cache
Prerequisites
Our runtime processes in Fiori rely on consistent Page Cache data. Unfortunately, there are special transports which should indicate a Page Cache update, but no proper event handling is supported all time. With the run of the report differences of the Page Cache in comparison to the primary persistence are detected and resolved. Only relevant changes are written to the Page Cache.
Features
Report synchronizes Page Cache tables for Configuration (cross-client) and Customizing (client-dependent) layer, for all languages in the system.
Use case: support / troubleshooting / periodical run to ensure consistency
Selection
Log Level
You can select different log levels. Depending on this level you get either more basic information about the report run or more detailed information about issues or additional analysis of the primary persistence.
The levels are:
- 0 : minimal
- basic information about the synchronization process
- 1 : default
- basic information about the synchronization process including locking and change-information, providing a comprehensive overview of the mechanisms involved.
- 2 : detail
- detailed information about the synchronization process (currently only with few extensions in comparison to detail level)
- 3 : extended
- analysis mode to get all information about synchronization and hints about issues of content in primary persistence
Client Range
You can select in which clients of the actual system the synchronization should run. As default the range is initially set to the actual client. You can extend the range to synchronize the scope for Customizing on different clients.
