It seems the DTM process got stuck for some reasons, and the error file I think won't help in understanding the issue.
You can find the file in Installation_Agent_folders\apps\Data_Integration_Server\data\error\s_dss_012PU10I000000000005_9_error.csv.
You would need to check the session log though.
Hope it helps.
Please access the session log from the below location in agent server and share it with us for analysis,
As we are the non admin user , we aren't able to get the DTM error logs, however, I have asked our client to provide the same. Menwhile i have checked the session log but the last entry in that file is related to some row
TRANSF_1_1_1> CMN_1053 [2021-03-02 03:59:15.316] LOOKUP_012PU10I000000000007_1:INPUT row pushed from Expr_DSS_012PU10I000000000007_1: Control=[None]
LOOKUP_012PU10I000000000007_1:INPUT row pushed from Expr_DSS_012PU10I000000000007_1: Rowdata: ( RowType=0(insert) Src Rowid=165099 Targ Rowid=165099
AccountId_c1 (External_Id__c:UniChar.20:): "00120000008PB3lAAG"
LastName_OUT (LastName_OUT__expr_:UniChar.80:): "Dettori"
FirstName_OUT (FirstName_OUT__expr_:UniChar.40:): "Ombretta"
Salutation_OUT (Salutation_OUT__expr_:UniChar.40:): ""
RecordTypeId_OUT (RecordTypeId_OUT__expr_:UniChar.18:): "012000000004xuiAAA"
MailingCountry_OUT (MailingCountry_OUT__expr_:UniChar.80:): "Italy"
Phone_OUT (Phone_OUT__expr_:UniChar.40:): "+39 0227076491"
Email_OUT (Email_OUT__expr_:UniChar.80:): "firstname.lastname@example.org"
Department_OUT (Department_OUT__expr_:UniChar.80:): "Sviluppo"
HasOptedOutOfEmail_OUT (HasOptedOutOfEmail_OUT__expr_:Int:): "0"
DoNotCall_OUT (DoNotCall_OUT__expr_:Int:): "0"
EmailBouncedReason_OUT (EmailBouncedReason_OUT__expr_:UniChar.255:): "(NULL)"
EmailBouncedDate_OUT (EmailBouncedDate_OUT__expr_:Date:): "(NULL)"
Job_Role__c_OUT (Job_Role__c_OUT__expr_:UniChar.255:): "Mid Management"
S6_Quote_Link__c_OUT (S6_Quote_Link__c_OUT__expr_:UniChar.255:): "(NULL)"
Language__c_OUT (Language__c_OUT__expr_:UniChar.4099:): "Italian"
inactive_contact__c_OUT (inactive_contact__c_OUT__expr_:Int:): "0"
External_Id__c_OUT (External_Id__c_OUT__expr_:UniChar.20:): "0032000000VEXmxAAH"
Date_Made_Inactive__c_OUT (Date_Made_Inactive__c_OUT__expr_:Date:): "(NULL)"
thanks for sharing this.
It seems the Session process got stuck. Usually, this is due to a memory heap size.
Can you increase the -xmx value within the JVMOPTION1 - 5 in DTM at runtime environment?
Please let us know.
Okay thanks for that , will check and confirm.
Moreover, is there a way that row level error gets logged into the session logs itself rather than in the DTM logs?
If yes then how to enable it ?
1. If the job is running in Bulk API mode than the bad records are redirect to a bad file.
2. If the job is on Standard API mode that you should see the row errors in session log, even if you set the error file in a different path. So yuo will have bad records in error file and session log .
okay there is no way that row-level error we can redirect into the session log for Bulk API ?
As mentioned earlier, the only available parameter to switch off the error file - it is for standard API
Set the JVMOption1 as-DSFDCCreateSuccessErrorFileFromParams=trueOn Bulk API, there is no custom property to achieve this. It is not possible.