Re: Managing large ASM trace files

Doug,

If you are on Linux, you might want to automate this with the logrotate command (with the copytruncate option as the file handle is still open)

Neil.
sent from my phone

On 25 Feb 2019, at 20:16, DOUG KUSHNER <dougk5_at_cox.net<mailto:dougk5_at_cox.net>> wrote:

Thanks! Also have a few *.trm files approaching 700Mb. Adrci purge doesn't shrink them. Can they be truncated as well?

Doug

On February 25, 2019 at 1:36 PM Tanel Poder <tanel_at_tanelpoder.com<mailto:tanel_at_tanelpoder.com>> wrote:

Hi Doug,

At OS level, you can truncate the file using:

echo > filename.trc

or just

> filename.trc

Apparently there's a truncate command in Linux as well (but I've never used it).

--
Tanel Poder
https://blog.tanelpoder.com/seminar

On Mon, Feb 25, 2019 at 12:00 PM DOUG KUSHNER < dougk5_at_cox.net<mailto:dougk5_at_cox.net>> wrote:

Is there a way to manage the size of 12.2 ASM trace files? Several trace files for gmon, lmhg, gen0 and mmon processes appear to keep the same PID for the instance lifetime, resulting in very large trace files. Setting MAX_DUMP_FILE_SIZE will prevent the trace file from growing beyond the max size, but does this by not logging new events to the files.

I'm looking for a way to trim or otherwise manage the size of these files, which have open file handles so it is not as simple as deleting or archiving them.

Thanks,

Doug

--
http://www.freelists.org/webpage/oracle-l