3.19.197 70439 - Vstp Security Log Fetch Error
Recovery
- Identify the affected MP from the alarm instance and inspect the fetch script log on the Active SOAM. Confirm the SOAM is active and the fetch configuration file, MP list, source directory, destination directory, and free-space setting are valid.
- Check that the affected MP has closed *_logs.csv files, the configured source path exists, and the Active SOAM can reach the MP using the configured account/path. Validate permissions as well.
- Check destination capacity and rsync/SSH failure detail. Correct the topology/path/connectivity or capacity cause through the normal operations process.
- Re-run only the supported scheduled/operational fetch mechanism after correction. Verify successful transfer and the alarm’s MP-specific clear; ensure source files are not manually removed before a successful copy.
- It is recommended to contact My Oracle Support for assistance, if needed.