ASAP Is Not Writting Anything To Sarm Diagnostic Files
(Doc ID 1348066.1)
Last updated on AUGUST 31, 2020
Applies to:
Oracle Communications ASAP - Version 4.7.2 to 7.0.2 [Release 4.7 to 7.0.0]Information in this document applies to any platform.
Symptoms
SARM stopped writing any info to its diagnostic file when the diagnostic file is rolling over to a new diagnostic files. We have to restart SARM server to recover from this situation.
In ASAP.Console, the following info can be found:
<SARM_SERVER_NAME>: Can't Create Server Diagnostic File , ErrorNum 24.
Note: Unix errno 24 EMFILE means "Too many open files"
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |