Difference between revisions of "ARS0023E"
(Created page with "{{TOCright}} == What was the error? == '''Message Number''': 23 '''Message Severity''': Error (Corrective action is required to continue) '''Message Name''': ARS0023E '''M...") |
|||
| Line 34: | Line 34: | ||
== Articles Related to this message == | == Articles Related to this message == | ||
[ | [https://ODUG.net/index.php?topic=2640.0 ODUG Webinar on CMOD Cache Filesystem Internals with Alessandro Perucchi] (Registration required, new registrations are usually approved within 24h.) | ||
Latest revision as of 18:08, 20 August 2024
What was the error?
Message Number: 23
Message Severity: Error (Corrective action is required to continue)
Message Name: ARS0023E
Message Text: Object >object< in Application Group >AppGroup< not found in cache, no other storage defined Srvr->server<-
Example
Object >123FAAAB< in Application Group >Customer Statements< not found in cache, no other storage defined Srvr->cmod.example.com<-
Related Errors
ARS0024E - Object >object< in Application Group >AGP< not found in node
The server failed while retrieving a document
The server failed while retrieving from Storage Set
What were you doing?
A user was likely requesting a document, and the retrieval of that document failed on the server, because the file could not be accessed in the cache filesystem.
What happened?
The Application Group was defined with the 'Cache Only' Storage Set. During the retrieval, the Content Manager OnDemand object file couldn't be found in the cache filesystems. A search of TSM or Cloud Storage wasn't conducted, because it wasn't configured.
Troubleshooting
There is likely an issue with your cache filesystems. If you are seeing many of these errors, it's possible that one of the cache filesystems listed in the [ars.cache] config file in not accessible, damaged, corrupted, or otherwise offline.
Check with your System Administrator to ensure that all of the CMOD cache filesystems that are configured are actually mounted. If any of the caches are missing, correct the problem and attempt the retrieval again.
If all cache filesystems are accounted for, consider running the [arsmaint|arsmaint -v] command to validate the cache filesystems. Check the System Log for any errors, and perform the necessary repairs. You may need the assistance of IBM or a CMOD Consultant to correct the issue.
Articles Related to this message
ODUG Webinar on CMOD Cache Filesystem Internals with Alessandro Perucchi (Registration required, new registrations are usually approved within 24h.)