Bug 24908321 - Huge trace files in ASM on ODA due to kgfmReadOak (Doc ID 24908321.8)
Versions confirmed as being affected
12.1.0.2 (Server Patch Set)

Description
This bug is only relevant when using Automatic Storage Management (ASM)
Many traces on ODA systems are produced in ASM due to kgfmReadOak details.

Rediscovery Information:

GI installations dumping traces with kgfmReadOak details for processes other than GMON, like:

kgfmReadOak: max_disk_count is 100
kgfmReadOak: appliance_name is ODA
kgfmReadOak: diskstring is /dev/mapper/D_p
kgfmReadOak: file_version is 2
kgfmReadOak: oda_version is 2
kgfmReadOak: jbod_count is 1
kgfmReadOak: jbod_slot_count is 24
kgfmReadOak: data_slot_count is 20
kgfmReadOak: reco_slot_count is 20
kgfmReadOak: redo_slot_count is 4
kgfmReadOak: max_missing is 0
kgfmReadOak: min_partners is 2
kgfmReadOak: agent_sql_identifier is /+ _OAK_AsmCookie
kgfmReadOak: rdbms_compatibility is 12.1.0.2
kgfmReadOak: asm_compatibility is 12.1.0.2
kgfmReadOak: _asm_hbeatiowait is 100

Workaround

Remove the trace files in a cron job

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.
References
Bug:24908321 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this articl

The fix for 24908321 is first included in

建议你从MOS检索一下，是否匹配这个Bug或者其它的Bug信息，这个mos是说触发ASM kgfmReadOak 在ODA上产生大量的追踪文件，MOS检索Bug号看看能不能打个补丁，或者选择RU包含这个bug的安装之后看看效果

一般这种情况就是触发BUG了，尤其是在升级、打补丁之类的动作后，可以在mos中搜索下。在巡检确认无误的情况下，如果没有匹配到对应的bug，也可以手工写个脚本定期清理，避免inode满影响数据库实例