My Oracle Support Banner

Bug 28322973 not fixed in ASM/GI 19.9 - gen0 excessive trace (Doc ID 2788743.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


On : ASM 19.9

Seeing the symptoms of Bug 28322973 in 19.9 ASM / Grid Infrastructure.

Doc ID 28322973.8 states this is fixed in 19.8.

19.9 and a 19.10 GI installation on ExaCC doing it ... constantly having to clean up these files to prevent /u01 from filling up.


e.g. from gen0 trace file


# tail -f /u01/app/grid/diag/asm/+asm/+ASM1/trace/*gen0*.trc
detected remote cgid 0x10036, rcl 0x10000ca78
detected remote cgid 0x10007, rcl 0x10357e050
detected remote cgid 0x1000c, rcl 0x1011990a0
detected remote cgid 0x10010, rcl 0x106ac3ce8
detected remote cgid 0x1001a, rcl 0x106ac33d0
detected remote cgid 0x10008, rcl 0x10357c690
detected remote cgid 0x1000e, rcl 0x101198e60
detected remote cgid 0x1000b, rcl 0x101198e60
detected remote cgid 0x10018, rcl 0x106ac3628
detected remote cgid 0x10039, rcl 0x101199520


Select a.ksppinm, a.ksppdesc, b.ksppstvl
From x$ksppi a, x$ksppcv b
Where a.indx = b.indx and a.ksppinm like '%_asm_ownerid_trace_timeout%';


ownerid tracing threshold in seconds


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.