000035827 - OEM XML files are consuming excess disk space in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 3, 2018Last modified by RSA Customer Support Employee on Mar 5, 2018
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000035827
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Product/Service Type: 
Access Certification Manager (ACM)
RSA Version/Condition: All
IssueA large number of XML files are being generated in /u01/app/oracle/product/11.2.0/db_1/NODE/sysman/emd/upload and are taking up large amounts of space in RSA Identity Governance & Lifecycle.

 
CauseThese files are related to Oracle Enterprise Manager (OEM) and are created by the OEM Agent. These are files that are ready to be uploaded to Oracle Management Service (OMS). The OMS Repository is where all the details about your databases are stored centrally.
 
The files are as follows:
  • _configuration_old Last recorded inventory snapshot
  • A*.XML Target metadata
  • B*.XML Severity/Blackout/Error data
  • C*.XML Upload-On-Fetch metric data
  • D*.XML Normal metric data
  • rawdata.dat Raw data currently being gathered
ResolutionThe amount of space Oracle uses for these files is configured in $ORACLE_HOME/{machineName}/sysman/config/emd.properties with the parameter UploadMaxBytesXML=20M The setting of 20M is the default.

This parameter is the maximum size in MB that the upload manager will support in the upload directory before temporarily being disabled. Change to a smaller size if needed.

Before making any changes, OEM must be stopped.
  1. Run the command below the stop the OEM

    acm stopoem

  2. Remove the XML files from the upload directory.
  3. Open the emd.properties file in a text editor.
  4. Modify the UploadMaxBytesXML parameter in the emd.properties file.
  5. Save the file
  6. Run the command below to start the OEM:

    acm startoem

Attachments

    Outcomes