Flashes (Alerts)
Abstract
When running arsmaint -c to expire cache documents in IBM® Content Manager OnDemand server, not all cache file systems are being inspected for expiration.
Content
A defect was found, APAR PM07636, where cache expiration stops when a cache file system is encountered that has a utilization lower then the maximum cache threshold specified, by default it is 80%. Cache expiration will also stop unexpectedly if a cache file system is expired below the maximum cache threshold.
Content Manager OnDemand inspects cache file systems in the order that they are listed in the ars.cache and should evaluate every cache file system to determine whether each has reached the maximum cache threshold. The APAR fix will be included in the next fixpack of Content Manager OnDemand, V8.4.1.5.
Workarounds for this issue are:
- Run cache expiration more frequently, specifying a maximum cache threshold below the cache file system with the lowest utilization. If cache is expired beyond the maximum cache threshold specified, expiration will still stop though.
- Comment out cache file systems in the ars.cache that you do not wish to be inspected before running cache expiration. For example, the lowest utilized file systems. This change requires the OnDemand server to be restarted. The first cache file system should never be commented out.
Related Information
Was this topic helpful?
Document Information
Modified date:
25 September 2022
UID
swg21421795