Some ASAP Diagnostic Files Are Not Created Even Though The Servers Are Running
(Doc ID 1617128.1)
Last updated on AUGUST 31, 2020
Applies to:
Oracle Communications ASAP - Version 5.2.4 and laterInformation in this document applies to any platform.
Symptoms
ASAP diagnostic files for CTRL/NEP/ADMIN etc were not created for a few days, even though the servers seemed to be up and running.
$ASAP_BASE/DATA/logs/20131216$ ls -alrt
total 1868
drwxr-xr-x 179 asap asap 189 Dec 16 00:00 ..
drwxr-xr-x 2 asap asap 6 Dec 16 00:00 .
-rw-r--r-- 1 asap asap 24198 Dec 16 09:00 SARMXXXX.diag
-rw-r--r-- 1 asap asap 146301 Dec 16 09:02 FORKAGNT.diag
-rw-r--r-- 1 asap asap 368534 Dec 16 09:20 JNEP_XXXX.diag
-rw-r--r-- 1 asap asap 245091 Dec 16 09:20 DAEMXXXX.diag
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 |