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/ProfileIncrementalScheduleConfig/
schedule=calendar * * * * * 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59
Explanation from Oracle can be found in here, it affects ATG 11.1:
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=284080926304738&id=1930422.1&displayIndex=1&_afrWindowMode=0&_adf.ctrl-state=hfbbbr18i_34#SYMPTOM
Comments
Post a Comment