Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

FTSIncrementalIndexer agent is not working



FTSIncrementalIndexer agent is not able to process the requests in the queue especially when there are some work items getting created in bulk or updates to existing work item during the process.

Error Messages code: 16943 SQLState: S0004 Message: Could not complete cursor operation because the table schema changed after the cursor was declared.

Steps to Reproduce

Not Applicable

Root Cause

Proper indexes are not picking at runtime.


Perform the following local-change steps:

  1. Ensure that the FTSIncrementalIndexer run on all nodes. This takes care of keeping Rules, Data and Work indexes in synchronization.
    One can turn off SystemWorkIndexer and SystemIndexer agents on all nodes.
  2. Take backup of pr_sys_queue_ftsindexer table.
  3. Truncate pr_sys_queue_ftsindexer table.
  4. Create an index on pr_sys_queue_ftsindexer table as follows:
  5. Stop the JVM.
  6. Remove all the contents in the search index directory.
  7. Start the JVM.
  8. Go to search landing page and manually begin re-indexing WORK-,RULE-,DATA-.
  9. Go to SMA and restart FTSIncremental Agent.
  10. Make sure FTSIncremental Agent is running every 60 seconds.
  11. Create and search newly created work objects.

Published February 14, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us