Symptom
Execute a job using a Base_EntityExtraction transform with run as separate process set to no and the degree of parallelism (DOP) set to 2 or Default will result in the following error message
2160 4804 RUN-050406 11/6/2018 11:40:41 AM |Session Job_Test_1|Data flow Test_1
12160 4804 RUN-050406 11/6/2018 11:40:41 AM Data flow <Test_1> received a bad system message. Message text from the child process is
12160 4804 RUN-050406 11/6/2018 11:40:41 AM <C==========================================================
12160 4804 RUN-050406 11/6/2018 11:40:41 AM Collect the following and send to Customer Support:
12160 4804 RUN-050406 11/6/2018 11:40:41 AM 1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
12160 4804 RUN-050406 11/6/2018 11:40:41 AM 2. Exported ATL file of this failed job.
12160 4804 RUN-050406 11/6/2018 11:40:41 AM 3. DDL statements of tables referenced in this failed job.
12160 4804 RUN-050406 11/6/2018 11:40:41 AM 4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
12160 4804 RUN-050406 11/6/2018 11:40:41 AM the job failed.
12160 4804 RUN-050406 11/6/2018 11:40:41 AM 5. Core dump, if any, generated from this failed job.
12160 4804 RUN-050406 11/6/2018 11:40:41 AM ==========================================================>. The process executing data flow <Test_1> has died
12160 4804 RUN-050406 11/6/2018 11:40:41 AM abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical Support.
12160 4804 RUN-050409 11/6/2018 11:40:41 AM |Session Job_Test_1
12160 4804 RUN-050409 11/6/2018 11:40:41 AM The job process could not communicate with the data flow <Test_1> process. For details, see previously logged error
12160 4804 RUN-050409 11/6/2018 11:40:41 AM <50406>.
Read more...
Environment
- SAP Data Services 14.2.10.1748
- SAP Information Platform Services 14.2.5.2618
- Windows Server 2016
Product
Keywords
ACCESS VIOLATION, crash, DS, SP10 , KBA , EIM-DS-EXE , Job Execution , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.