Hi guys
I am trying to copy the data from oracle database using odbc and getting below mentioned error...
dataflow is very simple:-
dataflow cache type is set to pageable and source table contains only 90+ records..
source table -> Query -> target table ---- nothing fancy happening in query... only copy
see below error file:-
(14.2) 03-30-16 11:27:54 (E) (3736:5728) RUN-050406: |Session New_Job1|Data flow New_DataFlow3
Data flow <New_DataFlow3> received a bad system message. Message text from the child process is
<C==========================================================
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 <New_DataFlow3> has died
abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical Support.
(14.2) 03-30-16 11:27:54 (E) (3736:5728) RUN-050409: |Session New_Job1
The job process could not communicate with the data flow <New_DataFlow3> process. For details, see previously logged error
<50406>.
(14.2) 03-30-16 11:27:54 (E) (3736:5728) RUN-050406: |Session New_Job1|Data flow New_DataFlow3
Data flow <New_DataFlow3> received a bad system message. Message text from the child process is
<C==========================================================
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 <New_DataFlow3> has died
abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical Support.
see below server_eventlog_2016-03-30
(14.2) 03-30-16 11:27:47 (1692:2720) JobServer: Starting job with command line -PLocaleUTF8 -Udata_services -P******** -eg -G"7d8071d3_699b_4732_875d_6af742695835" -t5
-T14 -ClusterLevelJOB -CmSDDS-DS-BIPROD -CaDesigner -CjSDDS-DS-BIPROD -Cp3500 -CtBatch -LocaleGV -BOESsdds-ds-biprod
-BOEAsecEnterprise -BOEU"Administrator"
-BOEP+04000000001A0B01001000009D8B3408A3420A6AF67D5B16EDF89891D51BC145FBD869947FAC74D488368FB220FA096F75B3AC4396C9F5EC4FE1A55217
42F2B3404A20 -E2 -SSDDS-SQL-BIPROD -NMicrosoft_SQL_Server -QPMS_NIGHTLY_LOAD_REPO
-Rsdds-sql-biprod_pms_nightly_load_repo_data_services -E2 -l"C:\ProgramData\SAP BusinessObjects\Data
Services/log/SDDS-DS-BIPROD/sdds-sql-biprod_pms_nightly_load_repo_data_services/trace_03_30_2016_11_27_46_614__7d8071d3_699b_473
2_875d_6af742695835.txt" -z"C:\ProgramData\SAP BusinessObjects\Data
Services/log/SDDS-DS-BIPROD/sdds-sql-biprod_pms_nightly_load_repo_data_services/error_03_30_2016_11_27_46_614__7d8071d3_699b_473
2_875d_6af742695835.txt" -w"C:\ProgramData\SAP BusinessObjects\Data
Services/log/SDDS-DS-BIPROD/sdds-sql-biprod_pms_nightly_load_repo_data_services/monitor_03_30_2016_11_27_46_614__7d8071d3_699b_4
732_875d_6af742695835.txt" -Dt03_30_2016_11_27_46_614 (BODI-850052)
(14.2) 03-30-16 11:27:47 (1692:2720) JobServer: StartJob : Job '03_30_2016_11_27_46_614__7d8071d3_699b_4732_875d_6af742695835' with pid '3736' is kicked off
(BODI-850048)
(14.2) 03-30-16 11:27:47 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <4> (BODI-850170)
(14.2) 03-30-16 11:27:47 (1692:2720) JobServer: AddChangeInterest: log change interests for <03_30_2016_11_27_46_614__7d8071d3_699b_4732_875d_6af742695835> from client
<inet:10.251.16.145:61849>. (BODI-850003)
(14.2) 03-30-16 11:27:47 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:48 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:49 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:50 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:52 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:53 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:53 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <9> (BODI-850170)
(14.2) 03-30-16 11:27:53 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:53 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <9> (BODI-850170)
(14.2) 03-30-16 11:27:54 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <7> (BODI-850170)
(14.2) 03-30-16 11:27:54 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <8> (BODI-850170)
(14.2) 03-30-16 11:27:54 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <9> (BODI-850170)
(14.2) 03-30-16 11:27:59 (1692:6260) JobServer: Sending notification to <inet:10.251.16.145:61849> with message type <5> (BODI-850170)
(14.2) 03-30-16 11:27:59 (1692:2720) JobServer: GetHistoricalLogStatus() Success. 03_30_2016_11_27_46_614__7d8071d3_699b_4732_875d_6af742695835 (BODI-850001)
(14.2) 03-30-16 11:27:59 (1692:2720) JobServer: GetHistoricalLogStatus() Success. 03_30_2016_11_27_46_614__7d8071d3_699b_4732_875d_6af742695835 (BODI-850001)
Data flow <New_DataFlow3> received a bad system message. Message text from the child process is <blank message, possibly due to
insufficient memory (use NT Task Manager to monitor memory usage during the job.
Could you please help me what is wrong happening..
regards