Close Menu
Oracle

Cleaning the OEM Software Library: Safe Purge and swlib Growth Control

HenriqueBy Updated:4 Mins Read

This post is also available in: Português (Portuguese (Brazil))

This guide focuses exclusively on the correct technical procedure to execute a purge and reclaim space without compromising the OEM repository.

When to Execute Software Library Cleanup

Run a purge when:

  • OMS filesystem usage exceeds 80%
  • Deployments start failing
  • Critical space alerts appear
  • swlib grows disproportionately

Quick validation (example output)

$ df -h
/dev/mapper/vg_oracle-middlewarelv  127G  116G  4.9G  96% /middleware

Identifying internal consumption

cd $MW_HOME
du -sk * | sort -n

Typical output:

16      lost+found
252     PatchSearch.xml
636940  bi_publisher
798916  wclient
800744  windows_agent
808712  stagetfa
1051016 ahfinstall
2374560 agent_inst
2581840 plugins
17970752        gc_inst
26109920        oem134
27883528        WLS
40388796        swlib

If swlib is the largest consumer, the growth is directly related to the Software Library.

Understanding the Problem

The swlib directory stores:

  • Provisioning artifacts
  • Installation images
  • Plugins
  • Patchsets
  • Imported content
  • Deleted entities still referenced

Over time, OEM accumulates:

  • Orphaned content
  • Unreferenced older versions
  • Artifacts linked to removed entities

Without periodic purge, growth is cumulative and expected.

There is no automatic full garbage collection mechanism for the Software Library.

How to Purge the OEM Software Library

Recommended Method — Via OEM Console

  1. Log in to OEM as SYSMAN
  2. Navigate to:
Enterprise → Provisioning and Patching → Software Library
  1. Click Purge
  2. Define retention criteria
  3. Execute

The purge process removes:

  • Deleted entities
  • Orphaned content
  • Unreferenced artifacts
  • Objects outside retention policy

In large environments, the process may take time and generate moderate OMS load.
Execution outside peak hours is recommended.

Validate Reclaimed Space

After completion:

df -h
Filesystem                          Size  Used Avail Use% Mounted on
devtmpfs                             12G     0   12G   0% /dev
tmpfs                                12G     0   12G   0% /dev/shm
tmpfs                                12G  1.2G   11G  10% /run
tmpfs                                12G     0   12G   0% /sys/fs/cgroup
/dev/mapper/vg_root-lv_root         4.0G  317M  3.7G   8% /
/dev/mapper/vg_root-lv_usr          6.0G  2.2G  3.9G  37% /usr
/dev/sda1                          1014M  237M  778M  24% /boot
/dev/mapper/vg_oracle-lv_oracle     5.8G  932M  4.6G  17% /oracle
/dev/mapper/vg_oracle-oggmonlv      9.8G   37M  9.2G   1% /oggmon
/dev/mapper/vg_oracle-middlewarelv  127G   86G   36G  71% /middleware
/dev/mapper/vg_root-lv_var          4.0G  1.3G  2.7G  33% /var
/dev/mapper/vg_root-lv_home        1014M  829M  186M  82% /home
/dev/mapper/vg_root-lv_tmp          5.0G   97M  4.9G   2% /tmp
tmpfs                               2.4G     0  2.4G   0% /run/user/1022
/dev/mapper/vg_dados-lv_dados       2.0T  1.3T  635G  67% /dados

Compare before and after.

In enterprise environments, it is common to recover tens of GB per purge cycle.

⚠ What NOT to Do

Never manually remove files under:

$MW_HOME/sysman/swlib

The Software Library maintains metadata in the SYSMAN repository.

Manual deletion can cause:

  • Catalog inconsistencies
  • Provisioning failures
  • Patching errors
  • Internal ORA errors
  • Logical corruption of the library

The only supported method is purge via the OEM console.

When purge does not fully resolve the issue

If growth persists, verify:

  • Active jobs using artifacts
  • Content still referenced by deployments
  • Misconfigured retention policies
  • Frequent patch imports without cleanup

Environments with continuous patching cycles require periodic Software Library maintenance.

Best Practices for Large Environments

  • Monitor swlib growth monthly
  • Define a clear retention policy
  • Avoid redundant versions
  • Plan OMS storage considering cumulative growth
  • Include purge as part of operational routines

The Software Library does not self-maintain — accumulation is expected without governance.

References

Oracle Enterprise Manager Cloud Control Administrator’s Guide
https://docs.oracle.com/en/enterprise-manager/cloud-control/

OEM Cloud Control Advanced Installation and Configuration Guide
https://docs.oracle.com/en/enterprise-manager/cloud-control/installation-guide/

Oracle Enterprise Manager Cloud Control Provisioning and Patching Guide
https://docs.oracle.com/en/enterprise-manager/cloud-control/provisioning-patching/

Enterprise Manager Cloud Control Documentation Library
https://docs.oracle.com/en/enterprise-manager/

Oracle Support (My Oracle Support – MOS)
https://support.oracle.com

Share.

Related Posts

Add A Comment
Leave A Reply