our Real time Individual match job is erroring out with above error code. Real time Individual clean and Real time Individual Cluster are working fine. What could be the reason for this?
(log file extract:
SEVERE: 06-May-2013 14:54:39: Cannot acquire lock: already locked (Code: 207,002)
com.datanomic.director.missionmanager.exceptions.MissionExecutionException: Cannot acquire lock: already locked (Code: 207,002)
we do have setup OEDQ for key generation (Our Siebel OCH is on 220.127.116.11). When we run Siebel Key Generate jobs on Contacts and Accounts, we do get records created in SIEBEL.S_DQ_ORG_KEY and SIEBEL.S_DQ_CON_KEY. Is this table where they are supposed to be generated?
Does Siebel OCH support Address matching?
more questions to come in near future
THANKING YOU IN ADVANCE!!
Edited by: user3035423 on 6.5.2013 8:18
Hi Nick. thanks for your reply.
I am newbie to the OEDQ. When you say that proces is open in Director, what does it mean? How can i close it?
In order to overcome this situation i did
1. stop datanomic service on Win2003 server
2. started Job Main Initialize reference Data in EDQ-CDS - initialize Reference Data project and waited to finish
3. started Job Real- time START ALL in EDQ-CDS project
4. this is the step where some of the jobs are errorong out, as stated before
From above to mee it looks like there should not be any process open in Director.
can you please share your thoughts
Are you running these jobs from the Server Console or Director application? They must be run from the Server Console using a run label and run profile setting. See the CDS Installation Guide for instructions. Note that you only need to run the initialize job once - not each time you restart. Also, if you are using CDS 9.0.4 with the default language domain settings then we supply pre-initialized data so you don't need to run the initialize job at all.