Re: Managing large ASM trace files

My experience with adrci purge with 11.2 databases and 12.2 GI, is that it will effectively remove files of a certain age, but it is not capable of removing aged log entries from a file. For that I will need to run logrotate.

Have not tried any autopurging yet. All purging here is scripted and scheduled, using -age parameter.

Doug

On February 25, 2019 8:31:07 PM MST, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:
>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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
http://www.freelists.org/webpage/oracle-l