Internal error in AUTO_STATS_ADVISOR_TASK unless table stats on spatial tables are locked
I am working on a legacy system and found some code in which table stats are locked for one specific table, which happens to be the only table in the database with spatial columns (and indexes). A comment near this line of code indicates that this was done to avoid an internal error which occurs on Oracle 12.2 on spatial indexes in the AUTO_STATS_ADVISOR_TASK.
We are currently running Oracle 19c. I am trying to figure out whether locking of table stats for this table is something that still needs to be done. To that end I'm trying to find a bug report, or patch notice, or something describing this problem, as step 1 to tracking down whether and when it was fixed.