Managing large ASM trace files
From: DOUG KUSHNER <dougk5_at_cox.net>
Date: Mon, 25 Feb 2019 11:59:23 -0500 (EST)
Message-ID: <1385428067.4893.1551113963764_at_myemail.cox.net>
Date: Mon, 25 Feb 2019 11:59:23 -0500 (EST)
Message-ID: <1385428067.4893.1551113963764_at_myemail.cox.net>
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 - 17:59:23 CET