Scribd
Upload
30 views2 pages

Attachment

A data flow process received an error message and died abnormally, causing a job to fail communicating with it. Details are provided on log files and other information to collect and send to support for troubleshooting.

Uploaded by

Nihar Mayekar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
30 views2 pages

Attachment

A data flow process received an error message and died abnormally, causing a job to fail communicating with it. Details are provided on log files and other information to collect and send to support for troubleshooting.

Uploaded by

Nihar Mayekar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

2023-10-13 08:10:13 (E)(1136:605484864)RUN-50406 |Session

Z01_CDP_STOCK_ONHAND_CURRENT_copy|Data flow
Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT
Data flow
<Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT> received a bad
system message. Message text from the
child process is <ﾸ
=Q#s==========================================================
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.

==========================================================>. The process executing


data flow

<Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT> has died


abnormally. For NT, check errorlog.txt. For HPUX,
check
stack_trace.txt. Also, notify Technical Support.
2023-10-13 08:10:13 (E)(1136:605484864)RUN-50409 |Session
Z01_CDP_STOCK_ONHAND_CURRENT_copy
The job process
could not communicate with the data flow
<Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT>
process. For
details, see previously logged error <50406>.
2023-10-13 08:10:13 (E)(1136:605484864)RUN-50406 |Session
Z01_CDP_STOCK_ONHAND_CURRENT_copy|Data flow
Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT
Data flow
<Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT> received a bad
system message. Message text from the
child process is <ﾸ
=Q#s==========================================================
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.
==========================================================>. The process executing
data flow

<Z01_CDP_STOCK_ONHAND_CURRENT_copy_Z01_CDP_STOCK_ONHAND_CURRENT> has died


abnormally. For NT, check errorlog.txt. For HPUX,
check
stack_trace.txt. Also, notify Technical Support.

You might also like