When you get that constraint violation error it means indexing jobs on CSC are stepping on each other or even themselves, if you happen to have a schedule without catch up and even running too often then you'll be seeing a lot errors lik this: ERROR [nucleusNamespace.atg.textsearch.indexing.job.IndexingJob] (pool-103-thread-1) ORA-00001: unique constraint (DRESS_CORE.SRCH_ORDER_TOKENS_P) violated And eventually you'll get an error like this: ERROR [nucleusNamespace.atg.dynamo.messaging.SqlJmsProvider] (ServerService Thread Pool -- 102) null: java.sql.SQLExc eption: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:/ATGAgentDS So just update the schedule for the indexing components: /atg/commerce/textsearch/schedule/OrderIncrementalScheduleConfig schedule=calendar * * * * * 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58 /atg/userprofiling/textsearch/schedule/ProfileIncrement