Skip to Content
0

BODS DUMP ERROR

Jan 02, 2017 at 04:21 AM

293

avatar image

Hello All,

If i try to extract data from SQL SERVER to FlatFile, job is loading data successfully.

When i am trying to extract data from Legacy (Oracle) to Flatfile, I am facing this issue.

can anyone help me on this..Facing issue while connecting to Oracle database only

We are using Oracle 12c and DS 4.2 sp4.

171409004RUN-0504062017-01-01 11:08:29 PM|Session New_Job|Work flow New_WorkFlow1|Data flow New_DataFlow4 171409004RUN-0504062017-01-01 11:08:29 PMData flow <New_DataFlow4> received a bad system message. Message text from the child process is <blank message, possibly due to 171409004RUN-0504062017-01-01 11:08:29 PMinsufficient memory (use NT Task Manager to monitor memory usage during the 171409004RUN-0504062017-01-01 11:08:29 PMjob)========================================================== 171409004RUN-0504062017-01-01 11:08:29 PMCollect the following and send to Customer Support: 171409004RUN-0504062017-01-01 11:08:29 PM1. Log files(error_*, monitor_*, trace_*) associated with this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM2. Exported ATL file of this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM3. DDL statements of tables referenced in this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when 171409004RUN-0504062017-01-01 11:08:29 PMthe job failed. 171409004RUN-0504062017-01-01 11:08:29 PM5. Core dump, if any, generated from this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM==========================================================>. The process executing data flow <New_DataFlow4> has died 171409004RUN-0504062017-01-01 11:08:29 PMabnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical Support. 171409004RUN-0504092017-01-01 11:08:29 PM|Session New_Job|Work flow New_WorkFlow1 171409004RUN-0504092017-01-01 11:08:29 PMThe job process could not communicate with the data flow <New_DataFlow4> process. For details, see previously logged error 171409004RUN-0504092017-01-01 11:08:29 PM<50406>. 171409004RUN-0504062017-01-01 11:08:29 PM|Session New_Job|Work flow New_WorkFlow1|Data flow New_DataFlow4 171409004RUN-0504062017-01-01 11:08:29 PMData flow <New_DataFlow4> received a bad system message. Message text from the child process is <blank message, possibly due to 171409004RUN-0504062017-01-01 11:08:29 PMinsufficient memory (use NT Task Manager to monitor memory usage during the 171409004RUN-0504062017-01-01 11:08:29 PMjob)========================================================== 171409004RUN-0504062017-01-01 11:08:29 PMCollect the following and send to Customer Support: 171409004RUN-0504062017-01-01 11:08:29 PM1. Log files(error_*, monitor_*, trace_*) associated with this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM2. Exported ATL file of this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM3. DDL statements of tables referenced in this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when 171409004RUN-0504062017-01-01 11:08:29 PMthe job failed. 171409004RUN-0504062017-01-01 11:08:29 PM5. Core dump, if any, generated from this failed job. 171409004RUN-0504062017-01-01 11:08:29 PM==========================================================>. The process executing data flow <New_DataFlow4> has died 171409004RUN-0504062017-01-01 11:08:29 PMabnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical Support.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Aasavari Bhave
Jan 05, 2017 at 02:54 PM
0

I see

insufficient memory error in the log.

Some of the things to check are:

1. Running pageable cache vs in- memory

2. Since SQL - flat file works - is it same number of rows\ data ?

3. what's the difference in job design for sql - flat file vs oracle - flat file

Share
10 |10000 characters needed characters left characters exceeded