Background jobs are failing, and attempting to drop and recreate a Search Domain's underlying index (like ACTIVITY_TIX or DOCUMENT_CONTENT_TIX) reports that the index doesn't actually exist — even though nothing was intentionally dropped.

All FAQ questions / Document management

Answer

This can happen without anyone deliberately dropping anything — Search Domain indexes have been observed getting invalidated by activities like database cloning, not just manual index changes. Rather than trying to manually recreate the missing index directly, reactivate the affected Search Domain(s) from their configuration screen, which rebuilds the underlying index structures properly as part of reactivation. If this isn't a recurring pattern for your environment, it's reasonable to treat a one-off occurrence like this as expected fallout from whatever database-level operation (such as a clone or refresh) preceded it, rather than a sign of an ongoing problem.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Document management questions