03-26-2014 07:20 PM
An error being received when searching interactions using the ‘Text Search” tab:
Query request not processed because of previous I/O error on file ir.incident(cc.search, select)
I am not sure why this is happening.
Which logs can I look at to trouble shoot this further?
03-26-2014 07:58 PM - edited 03-26-2014 07:58 PM
03-26-2014 08:13 PM
I have searched the change and incident module using the same search criteria and those searches both bring results back.
So this points to the incident table IR index.
Before I reg this however the sm.ini file has this parameter:
Should it all have the following set to something?
03-26-2014 09:51 PM - edited 03-26-2014 09:52 PM
ir_asynchronous:1 (1 enabled, 0 disabled)
IR Asychronous is usually recommended. If disabled, the IR updates take place at record save which can impact performance. Enabling it creates a queue for IR indexing functions.
Optional parameter. The default value is 50 if this parameter is not present.
04-03-2014 06:19 PM
I believe that the average IR Regen time is 1 minute for each 2,500 records in a base table. Is this correct?
04-03-2014 08:55 PM
I don't believe it can be stopped in progress, but open a ticket with support (or open a ticket in the Customer forum--support users monitor that forum).
The best practice to reindex against a large production system is to take a backup, disable IR on the table in prod (allowing new tickets to queue for processing), complete the IR Index process using the restored backup in DEV or TEST, replace the corrupt Prod index with the newly generated one, then restart indexing on PROD to index any new records.
04-03-2014 10:14 PM
Its just that the following knowledge article specifies stopping the IRQUEUE process:
It also specifiies deleting scirexpert records before the regen.
04-03-2014 10:23 PM
This would mean stopping and restarting the sm service.
04-04-2014 12:21 AM
04-06-2014 05:45 PM
"disable IR on the table..." Is this equivalent to what the knowledge article referenced above refers to as "Stop IRQUEUE process"
"Restart indexing on PROD" Is this equivalent to what the knowledge refers to as "start IRQUEUE process"?