Oracle database trace files (.trc and .trm) consume large amounts of disk space
search cancel

Oracle database trace files (.trc and .trm) consume large amounts of disk space

book

Article ID: 328920

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
When using an Oracle database instance, you see these symptoms:
  • The Oracle trace and incident directories consume large amounts of disk space.

    Note: In some cases, each directory may consume more than 10 GB of space.

  • The Oracle database halts, causing vCenter Server to fail.

    Note: This issue can also occur with any VMware product with a database on an Oracle database instance.

  • In the trace files located within the trace directory, you may see traces similar to:

    Trace file /db_path/trace/vpx_ora_18020.trc
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /home/app/oracle/product/11.2.0/dbhome_1
    System name: Linux
    Node name: NodeName
    Release: 2.6.18-308.4.1.0.1.el5
    Version: #1 SMP Tue Apr 17 16:33:59 EDT 2012
    Machine: x86_64
    Instance name: InstanceName
    Redo thread mounted by this instance: 1
    Oracle process number: 39
    Unix process pid: 18020, image: [email protected]


    *** 2014-07-29 00:00:08.561
    *** SESSION ID:(205.27280) 2014-07-29 00:00:08.561
    *** CLIENT ID:() 2014-07-29 00:00:08.561
    *** SERVICE NAME:(ServiceName) 2014-07-29 00:00:08.561
    *** MODULE NAME:(OEM.CacheModeWaitPool) 2014-07-29 00:00:08.561
    *** ACTION NAME:() 2014-07-29 00:00:08.561
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : JOB_EXEC_DELETE_TRIGGER
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    trigger sublist 2 :
    trigger sublist 3 :
    Trigger Owner : SYSMAN
    Trigger Name : JOB_EXEC_DELETE_TRIGGER
    trigger sublist 4 :
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_PARAM_DELETE
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    trigger sublist 2 :
    trigger sublist 3 :
    Trigger Owner : SYSMAN
    Trigger Name : MGMT_JOB_PARAM_DELETE
    trigger sublist 4 :
    --------Dumping Sorted Master Trigger List --------
    Trigger Owner : SYSMAN
    Trigger Name : JOB_SUMM_INS_TRIGGER2
    Trigger Owner : SYSMAN
    Trigger Name : JOB_SUMM_INS_TRIGGER
    --------Dumping Trigger Sublists --------
    trigger sublist 0 :
    trigger sublist 1 :
    Trigger Owner : SYSMAN
    Trigger Name : JOB_SUMM_INS_TRIGGER
    trigger sublist 2 :
    trigger sublist 3 :
    Trigger Owner : SYSMAN
    Trigger Name : JOB_SUMM_INS_TRIGGER2
    trigger sublist 4 :






Resolution

To resolve this issue, upgrade to Oracle 12C or Oracle 11G patch 9382101.

To work around this issue:
  1. Login to the Oracle database server.
  2. Navigate to the database trace directory.
  3. Delete all files with the extension .trc and .trm within the trace directory.

    For Linux systems, run these commands:

    rm -f *.trc
    rm -f *.trm

    Note: Do not delete alert.log file or files that do not contain the .trc and .trm extension.

  4. In some cases, you may require to restart the VMware service accessing the database to restore connectivity. In most cases a restart of the Oracle database instance is not required.