on 10-02-2015 4:51 PM
Hi Experts,
When I try to load the data from Oracle to BPC 10.0 MS version through FIM, I am able to load the data for 4-5 line items.
But when I try to load the data for multiple line items with the same mapping , data is not loading to BPC.Could you please help me to solve this issue.
1) In below scenario I'm able to load the data successfully.
2) In below scenario the data is not getting loaded. All other mappings would remain same.
Kindly share your ideas on the above.
Thanks
Srikanth
Hi srikanth,
wich version of service pack is using?
Did you try to open log in DataServices Management Console?
Duration of jobs is big, may be something with time out on FIM or BPC side. Did you try to decrease data?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daulet,
The below is the version we are using.
The below is the error log in Dataservices.
(14.2) 10-03-15 01:46:21 (E) (3188:8472) RUN-050406: |Session AUG_HO_2|Data flow DF_LOAD_AUG_HO_2
Data flow <DF_LOAD_AUG_HO_2> received a bad system message. Message text from the child process is
<P P ==========================================================
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 <DF_LOAD_AUG_HO_2> has died
abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt. Also, notify Technical Support.
(14.2) 10-03-15 01:46:21 (E) (3188:8472) RUN-050409: |Session AUG_HO_2
The job process could not communicate with the data flow <DF_LOAD_AUG_HO_2> process. For details, see previously logged error
<50406>.
(14.2) 10-03-15 01:46:21 (E) (3188:8472) RUN-050316: |Session AUG_HO_2
Data flow <DF_LOAD_AUG_HO_2> received a bad system message. Message text from the child process is
<P P ==========================================================
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
(14.2) 10-03-15 01:46:21 (E) (3188:8472) RUN-050304: |Session AUG_HO_2
Function call <raise_exception ( Data flow <DF_LOAD_AUG_HO_2> received a bad system message. Message text from the child
process is <P P ==========================================================
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 ) >
failed, due to error <50316>: <Data flow <DF_LOAD_AUG_HO_2> received a bad system message. Message text from the child process
is <P P ==========================================================
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>.
(14.2) 10-03-15 01:46:21 (E) (3188:8472) RUN-050316: |Session AUG_HO_2
Data flow <DF_LOAD_AUG_HO_2> received a bad system message. Message text from the child process is
<P P ==========================================================
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
Regarding the job duration, there is a large amount of data nearly 5600000 line items in the source.
Thanks
Srikanth
Srikanth
Looks like your running out of memory on the DS side ,see https://scn.sap.com/thread/3253215
Thanks
Marc
Hi Srikanth,
Similar to this post you opened a few days back
I honestly think you have some configuration issues that are beyond what can be discussed on SCN.
There is nothing wrong with this mapping in FIM itself, it is purely at execution level in DS that you have issues (data volume, memory etc.)
Thanks
Marc
Srikanth
What does the run history show, are these lines "unmapped' or 'rejected' ?
Marc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.