Hi Ramesh
i found this error log for my job in previous date and from next day the job is running for 0s and is in green.
Job name: Data_Job
(E) (11496:10724) SYS-: |Session Data_Job|Workflow T_WF|Dataflow T_WF
System Exception <ACCESS_VIOLATION> occurred. Process dump is written to <C:\SAPDI\Data
Services and <C:\SAPDI\Data Services
Process dump is written to <C:\SAPDI\Data Services\ and <C:\SAPDI\Data
Services\
Call stack:
0023:00, Flat_file::getColumn()+1563 byte(s), x:\src\filespec\flat_file.cpp, line 2619+0006 byte(s)
0023:00, Delim_C1array::getColumn()+0050 byte(s), x:\inc\filespec\delim_file.h, line 0124
0023:00, SapDB::srcDB_getnext()+0676 byte(s), x:\src\dbspec\sapdb.cpp, line 1457
0023:00, RdrR3Tab::getnext()+0237 byte(s), x:\src\reader\rdrr3tab.cpp, line 0345
0023:00, RdrSAPTree::execute()+0029 byte(s), x:\src\reader\rdrtree.cpp, line 0382
0023:00, XTran_desc::execute()+0231 byte(s), x:\src\core\xtran.cpp, line 0578
0023:00, Rww_thread::main()+0083 byte(s), x:\src\rww\rww.cpp, line 0406
0023:01, RWThreadFunctionImp::run()+0139 byte(s)
0023:01, RWRunnableImp::exec()+0226 byte(s)
0023:01, RWThreadImp::exec()+0076 byte(s)
0023:01, RWThreadImp::_setTimeSliceQuantum()+0249 byte(s)
0023:7, FlsSetValue()+0316 byte(s)
Registers:
EAX=080 EBX=0858 ECX=7 EDX=0418 ESI=480
EDI=7FFFFFFF EBP=0701F73C ESP=0701F548 EIP=00EB FLG=046
CS=23 DS=02 SS=02 ES=00 FS=03 GS=02
Exception code: C005 ACCESS_VIOLATION
Fault address: 00BEB 01:002EB C:\SAPDI\Data Services\
==========================================================
Please collect the following and send to Customer Support:
1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
2. Exported Atl file of this failed job.
3. DDL statements of tables referenced in this failed job.
4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
the job failed.
5. Core dump, if any, generated from this failed job.
==========================================================
R3C-: |Dataflow FAGLFLEXT_DF
Error calling R/3 to get table data: <RFC Error:
Key: RFC_GET6
Status:
connection closed without message
>.
R3C-: |Dataflow R3_DF_T1
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C-: |Dataflow Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C-: |Dataflow R3_Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C- : |Dataflow BSEGR3_Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C- : |Dataflow BSEGR3_Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C- : |Dataflow BSEGR3_Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C- : |Dataflow BSEGR3_Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
R3C- : |Dataflow BSEGR3_Loop_DF
R/3 CallReceive error <Function Z_RFC_ABAP_INSTALL_AND_RUN: . Time limit exceeded.>.
FIL-: |Dataflow R3_Loop_DF|Reader BSEG_Loop_R3DF
A row delimiter was seen for row number <21319> while processing column number <3> in file <E:/DI_Working_Dir/t.dat>. The
row delimiter should be seen after <6> columns. Please check the file for bad data, or redefine the input schema for the file
by editing the file format in the UI.
FIL-: |Dataflow R3_Loop_DF|Reader Loop_R3DF
A row delimiter was seen for row number <24500> while processing column number <5> in file <E:/DI_Working_Dir/t.dat>. The
row delimiter should be seen after <6> columns. Please check the file for bad data, or redefine the input schema for the file
by editing the file format in the UI.
DBS-: |Dataflow R3_Loop_DF|Loader STG_ _CO_STG_ _CO
ODBC data source <10.250.4.44> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server Driver][SQL
Server]Violation of PRIMARY KEY constraint 'PK___BSEG_CO__6D3EB'. Cannot insert duplicate key in object
'DBO.STG_BSEG_CO'.>.
RUN-: |Dataflow R3_Loop_DF|Loader STG_BSEG_CO_STG_ _CO
Execution of <Regular Load Operations> for target <STG_BSEG_CO> failed. Possible causes: (1) Error in the SQL syntax; (2)
Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the
datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for
regular load operation and load triggers are defined, please check the SQL. Otherwise, for (3) and (4), please contact your
local DBA.