1,126
edits
m (Tweaked the content Manager OnDemand troubleshooting section for ARS0106E.) |
|||
| Line 22: | Line 22: | ||
There are four scenarios when this error can occur: | There are four scenarios when this error can occur: | ||
* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload. | * While running [[arsadmin]] unload - IBM CMOD was unable to delete a file during the unload. | ||
* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache. | * While running [[arsload]] - during a failed load, IBM CMOD was unable to delete the objects it inserted into the cache. | ||
* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration. | * While running [[arsmaint]] - during regular expiration processing, IBM CMOD couldn't delete an object eligible for expiration. | ||
* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it. | * While running [[arsload]] - the file already exists in the cache, and IBM CMOD couldn't delete it before overwriting it. | ||
The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]]. | The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]]. | ||
The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time *prior* to when the cache filesystem was backed up. | The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time *prior* to when the cache filesystem was backed up. | ||