Comments on: Too many trace files on 11G

By: Aun Shakeel

Aun Shakeel — Wed, 16 Jan 2013 14:39:05 +0000

thanks for your reply …
i would like to mention here that my problem is not the generation of the trace files.
my problem is generation of log files in two different places simultaneously specially in the /var filesystem
all my oracle parameters point the trace location to the oracle folder which has more than sufficient space.
but for some reasons the files are also generation in a filesystem that is only 5 gb.
and i want to stop that particularly.
any ideas on that.

By: wolfee

wolfee — Wed, 16 Jan 2013 13:20:25 +0000

Couple things. First, look at the alert_.log file that is writing so much trace and see if there is actually a problem going on. One time my Jr. DBA was running a load script and the device had run out of space. The disk filled up, the load couldn’t continue and the database trace files started writing and very soon thereafter crashed the database. Second, consider relocating the diagnostic_dest to a place with more disk space. Third, once that is done, you can look into creating nightly cron jobs (or whatever you prefer) to zip and relocate the trace files or if you aren’t required to retain a years worth of logs, you can just write the script to delete anything older than x-amount of hours/days. If you have oracle support, open up a Service Request (SR) with them and see if they give you a solution. If they do, make sure you reply here

By: Aun shakeel

Aun shakeel — Wed, 16 Jan 2013 07:10:12 +0000

I am facing the same problem but it is little more complicated ….. i am having trouble with trace files on only one node …. i have a 2 node production server …
the details are as such IBM power 7servers and oracle version 11.2.0.3 RAC

The issue is that on node 2 the trace files are generating on a huge level and i have to manually delete them every 2 hours other wise the space is filling up fast. And to add to my misery the trace files are generating in two separate locations

One location is the default oracle location folder which has a space of 200 gb and it is some how manageable by adrci

but the main issue with me is that some fiels are getting created int he /var folder under /tmp/oradiag_oracle forlder also
and this /var folder is only 5 gb
if i ignore it for one hour the space reaches 100%

i am trying to find what traces are enabled on the system so i can disable any unwanted traces.

Can anyone help me by telling me how to check for enable tracing events and how to disable them manually

Thank you .

By: Todd Wolfe

Todd Wolfe — Thu, 26 Apr 2012 11:00:56 +0000

I’ve upgraded our 10.2.0.4 RAC environments to 11.1.0.7.10 on two environments and 11.2.0.3 on one environment and I am really tired of all the .trm and .trc files as well. If something actually goes wrong and .trc and .cdmp that we actually need start to get written, you will find out rather quickly that your database environment will run out of disk and crash. I had this problem and could not delete as fast as they were being written, ran out of space and crashed the instance. We’ve been at 11g for about a month now and after zipping all the .trc, .trm and cdmp files (have to retain them for at least a year) the “trace” directory alone is over 200M zipped. 99% of which is garbage. And of course it is a much easier path to view the trace files “/opt/grid/app/oracle/diag/rdbms///trace” vs. “/opt/oracle/admin//bdump”

By: coskan

coskan — Tue, 14 Jul 2009 21:22:08 +0000

Magical steps to Self managed database )

By: Aman....

Aman.... — Tue, 14 Jul 2009 18:31:28 +0000

Trm files are yet another thing to make something simple more complex . First alert log gets changed to XML and to read it, comes a magical util ADRCI and then comes these TRM files which according to oracle are used to search the actual trace files! Huh? Why not let the trace be, well, just good-ol trace only?

Ok rant over .

Aman….

By: coskan

coskan — Wed, 03 Jun 2009 15:37:57 +0000

They are all trace and trm files but at least after changing this parameter I dont get auto traces for every user session. Background session trace still continues with boh trm and trc files.

TRM files are more than annoying but I have no solution for them. I think They should at least put them to separate directory. It is very hard to find your file in this new architecture unless you have a tracefile identifier.

By: John Hallas

John Hallas — Wed, 03 Jun 2009 15:31:37 +0000

What were the names of the trace files?
Have you found a way of inhibiting trm files yet in 11g. It is rather frustrating generating twice the files you need and we are not likely to use the XML format.