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
