DRG-10705: invalid value 149 for attribute TYPE_ID

Question

When doing a call to the procedure ctx_report.index_stats on one of my index, I get a DRG-1075 and the procedure fails. I don't think it is data related because I can reproduce the error on multiple databases with different datasets. It is specific to the index I am analyzing though, I don't have the error on another domain index. A rebuild did not help.
There is nothing in metalink or elsewhere about that error, I don't really understand it.
If someone has a clue, it is welcome
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-10705: invalid value 149 for attribute TYPE_ID
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_REPORT", line 534
ORA-06512: at line 4
Regards,
Pierre

Answer 1

Thanks a lot for the answer, I have been under pression because of deadlines but I'll focus on this problem next week.
We have a serious performance issue with a text index on a XMType column (the index is very big one, 14G). The only way to get decent performance is to pin the DR$ I table in memory, but I had a bad surprise : when one do a ctx_ddl.optimize_index with rebuild the index becomes much bigger (from 14G to 18G) and so it does not fit in the keep cache anymore. A rebuild or a drop/create put back the index to the original size. I suspect that some storage options are changed but could not understand which. I'll do a test case and post it on this forum.
That's why I wanted the ctx_report.analyze_index but it fails (even when the base table is truncated, so you might be right, there could be a leftover from a previous index). I'll set-up a test case with a freshly created database.
The product manager, Richard Ford, wrote a white paper about putting the index in the keep cache, it makes a very big difference for us. But I think it should be adapted to the Oracle 12c case (with separate offset and BIG_IO for example).
I'll post the test case asap, thanks already for pointing me to the right direction.
Pierre