Re: Managing large ASM trace files
Date: Mon, 25 Feb 2019 13:36:31 -0500
Message-ID: <CAMHX9J+kVbN7e385jzxpnqd2aWr+Cr6SpXrY1AmV66N489fCiQ_at_mail.gmail.com>
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> 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
Received on Mon Feb 25 2019 - 19:36:31 CET