Re: Managing large ASM trace files

  • From: Mladen Gogala <gogala.mladen@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Mon, 25 Feb 2019 22:27:55 -0500

There most certainly is "truncate" command in Linux:

TRUNCATE(1)                      User Commands                     TRUNCATE(1)

NAME

       truncate - shrink or extend the size of a file to the specified size

SYNOPSIS

       truncate OPTION... FILE...

DESCRIPTION

       Shrink or extend the size of each FILE to the specified size

       A FILE argument that does not exist is created.

       If  a  FILE  is larger than the specified size, the extra data is lost.

       If a FILE is shorter, it is extended and the extended part (hole) reads

       as zero bytes.

       Mandatory  arguments  to  long  options are mandatory for short options

       too.

       -c, --no-create


On 2/25/19 1:36 PM, Tanel Poder 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@xxxxxxx <mailto:dougk5@xxxxxxx>> 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




--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217

Other related posts: