Hi,
we did upgradation bods4.0 to bods4.2 … so we testing prod jobs into dev environment… job is running successfully but when i select check box for COLLECT STATISTICS FOR OPTIMIZATION while running the same job for performance purpose… after some time job fails with error:
|Session JOB_LOAD_FRAUD_FAD_DAILY_FILE|Work flow WF_DIM_CARD_ACCT|Data flow DF_DIM_CARD_ACCT_INSERT
Data flow <DF_DIM_CARD_ACCT_INSERT> received a bad system message. Message text from the child process is
==========================================================
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.
(14.2) 07-17-14 17:26:41 (3176:6500) WORKFLOW: Work flow <WF_DIM_CARD_ACCT> is started.
(14.2) 07-17-14 17:26:43 (4208:5140) DATAFLOW: Process to execute data flow <DF_DIM_CARD_ACCT_INSERT> is started.
(14.2) 07-17-14 17:26:44 (4208:5140) DATAFLOW: Data flow <DF_DIM_CARD_ACCT_INSERT> is started.
(14.2) 07-17-14 17:26:44 (4208:5140) DATAFLOW: Data flow <DF_DIM_CARD_ACCT_INSERT> using PAGEABLE Cache with <3327 MB> buffer pool.
(14.2) 07-17-14 17:29:51 (3176:6500) WORKFLOW: Work flow <WF_DIM_CARD_ACCT> is terminated due to an error <50406>.
(14.2) 07-17-14 17:29:51 (3176:6500) WORKFLOW: Work flow <DBI_JOB_ERROR_WF> is started.
(14.2) 07-17-14 17:29:52 (3176:6500) WORKFLOW: Work flow <DBI_JOB_ERROR_WF> is terminated due to an error <50316>.
(14.2) 07-17-14 17:29:52 (3176:6500) JOB: Job <JOB_LOAD_FRAUD_FAD_DAILY_FILE> is terminated due to error <50316>.
It’s possible that this is a DS bug and you should open a case with SAP tech support.
Otherwise, you may have to dig into the Dataflow to figure out why it is using a lot of memory. Look at the monitor log to see if the number of rows processed makes sense.
I have recently found that there is different behavior between Designer and the Export Execution Command in how statistics are handled. See this thread for more information: Where are my cache statistics???.
How are you running the job?
What version are you on?
Which O/S?
Error messages?
(BOB member since 2007-09-12)