Re: Managing large ASM trace files
Date: Mon, 25 Feb 2019 22:31:07 -0500
Message-ID: <674a7e09-9e09-32f8-7335-b7f4a4243d0a_at_gmail.com>
Have you tried using SET CONTROL from ADRCI? I really like it in 12c.
You should set SHORTP_POLICY and LONGP_POLICY.
Regards
On 2/25/19 11:59 AM, DOUG KUSHNER 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
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Feb 26 2019 - 04:31:07 CET