I am tying to build a job which loads data into salesforce regularly - the job is divided into three parts:
- Import of CSV into Database
- Matching of data in Salesforce
I am able to complete the first job, however running into random problems in the second job. Surprisingly the component works sometimes but most of the times struck and ultimately i have to kill the job (screen shot attached).
The second problem on the same job is it process more records but only report very less in the Error and Success files after UPSERTING.
Solved! Go to Solution.
Try to connect subjobs using "OnSubjob OK" link between both tXxxxxInput components.
However, maybe a problem due to your network connection (a microcut and your job will wait for the response which will never arrive).
thanks for your reply, really appreciate you time.
I just wanted to say that this sound familier because job runs fine sometimes. for example i ran the job today and it worked fine but stuck again.
If i remove oracleoutput and connect it to tlogrow then it shows the expected result. (even if i run the job 10 times) can you please tell me the way i can find out if problem is related to network?
Delete the "On Component OK" on tOracleOutput component.
Right click on 1st tOracleInput component then Trigger, click on the "On Subjob OK" and drag the link to then 2nd tOracleInput.
I have tried that but no luck, the job stuck at first part when updating the database.
I am trying to update the SFID in the database table as you can see the job, it updates one row and stuck there. The database field is not the primary key but i am making it a key in the job. The reason it is not a primary key because it has nulls and i want to update only row which has values. Any thoughts on this?
thanks for drawing me to the right direction, it was indeed a dead lock in the database side. I clicked commit on the oracle side and problem was resolved. Now i am following your instructions to avoid the same situation.