OS Watcher is Taking Huge Space on Database Server
Last updated on MARCH 14, 2014
Applies to:Linux OS - Version Oracle Linux 5.8 and later
Exadata Database Machine V2 - Version All Versions and later
Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata Database Machine X2-8 - Version All Versions and later
Exadata X3-2 Hardware - Version All Versions and later
Information in this document applies to any platform.
OS Watcher is consuming huge space on database nodes when there are many instances (100+ ) and many (ten thounsands) processes on the compute nodes.
Example for a system with 110 instances and 10000 processes, OS watcher archives takes 56GB space when OS watcher is run with default settings.
top, RDS, ExadataOSW (includes lsof command output) dumps are particularly taking significant space due to high number of processes, and high number of open file and network descriptors.
** IMPORTANT NOTE **
OS watcher tool will be disabled in upcoming releases and be replaced by a complete rewrite named ExaWatcher. New version comes with more configuration options, proactive compression and clean up. The folllowing solution is a workaround in the current version of OS watcher for large customer systems.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms