sn_vul_vulnerable_item text index events still get created after applying workaround for PRB1248469 - Support and Troubleshooting

sn_vul_vulnerable_item text index events still get created after applying workaround for PRB1248469 Issue sn_vul_vulnerable_item text index events are still created even after setting the no_text_index=true attribute in the dictionary entry for the fields generating events, turning text indexing off for the sn_vul_vulnerable_item table, and deleting sn_vul_vulnerable_item from ts_index_name.

This issue is often will show up after a clone - so likely only on sub-prods, but can happen any time a full text index regeneration is ran.

Cause There are 2 additional places to check which could be triggering these events to get created.

1. The sn_vul_vulnerable_item table is still in the ts_index_name table. If sn_vul_vulnerable_item exists in this table, the events will still get created even if you turn off text indexing for the field.

2. There is a field in the sn_vul_vulnerable_item table which has text indexing turned on at the field level which is adding sn_vul_vulnerable_item BACK into ts_index_name when a text index regeneration is ran.

This will be triggered when one of these events are processed:

text_index.all_no_purge text_index.all

Resolution 1. Delete all of the entries that start with 'sn_vul' from the 'Text Indexes' list, ts_index_name_list.do.

2. Check if there are any fields in sn_vul* tables which have text indexing turned on in the dictionary:

/sys_dictionary_list.do?sysparm_query=nameLIKEsn_vul%5Etext_index%3Dtrue

3. If there are fields with text indexing turned on in sn_vul_vulnerable_item, run the below script to turn text indexing off for all fields:

var gr = new GlideRecord('sys_dictionary'); gr.addQuery('name', 'STARTSWITH', 'sn_vul'); gr.addQuery('text_index', true); gr.query(); while( gr.next() ) { gs.print( gr.getValue('element') ); gs.print( gr.getValue('text_index') ); if (gr.getValue('text_index') == 1) { gr.setValue('text_index', false); gr.update(); gs.log("Attribute Changed"); gs.log(gr.getValue('text_index')); } }

If issue is happening after a CLONE, this script should be ran on the SOURCE of the CLONE as well.

Related Links PRB1248469 - Updates to the sn_vul_vulnerable_item.age column causes text index events to back up

PRB1380716 - sn_vul_vulnerable_item tables are getting added back to the text index list when rebuilding the text indexes even though the table does not have text indexing turned on