We hit this bug the other day. The oracle note references creating an index as part of this bug. As far as I can tell, we weren’t doing that when we hit this. It is a vendor application though, and I know they do some DDL such as creating tables on the fly. I was never able to reproduce the bug at will, but I was getting flooded with these alerts.
Oracle support recommended we change the _db_cache_pre_warm parameter to false
SELECT ksppinm, ksppstvl, ksppdesc FROM x$ksppi x, x$ksppcv y WHERE x.indx = y.indx AND translate (ksppinm, '_', '#') like '#%' AND ksppinm = '_db_cache_pre_warm'; KSPPINM KSPPSTVL KSPPDESC -------------------------- ---------- ------------------------------------------------------------ _db_cache_pre_warm TRUE Buffer Cache Pre-Warm Enabled : hidden parameter
We changed it to false, and did a rolling restart of the database
alter system set "_db_cache_pre_warm " = FALSE scope=spfile;
after restarting
SELECT ksppinm, ksppstvl, ksppdesc FROM x$ksppi x, x$ksppcv y WHERE x.indx = y.indx AND translate (ksppinm, '_', '#') like '#%' AND ksppinm = '_db_cache_pre_warm'; KSPPINM KSPPSTVL KSPPDESC -------------------------- ---------- ------------------------------------------------------------ _db_cache_pre_warm FALSE Buffer Cache Pre-Warm Enabled : hidden parameter
The errors have stopped. This appears to be bugĀ 21864012
Recent Comments