cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Data Services Job running slow

rm24
Explorer
0 Kudos

Hello,


Recently our SAP bods batch job have been running slowly, from 1-2 hours to 12 hours. No change in table configuration,No disk space outage, No OOM, No errors, no reboots. Data source is OLFM and target is HANA.

After 11 hours the job failed and restarted.

(14.2) 12-06-17 13:41:55 (E) (11989:537925376) DBS-070401: Dataflow DF_Init_OLFM_XLA_XLA_AE_LINES|XLA_AE_LINES ODBC data source <VHPBIPH1DB> error message for operation <SQLExecute>: <[SAP AG][LIBODBCHDB SO][HDBODBC] General error;129 transaction rolled back by an internal error: Allocation failed ; $size$=40000; $name$=libhdbrskernel.so; $type$=pool; $inuse_count$=1726511; $allocated_size$=1226819927>. (14.2) 12-06-17 13:59:40 (E) (11941:2113906464) RUN-050316: |Session Job_Init_XLA_XLA_AE_LINES Job failed (14.2) 12-06-17 13:59:40 (E) (11941:2113906464) RUN-050304: |Session Job_Init_XLA_XLA_AE_LINES Function call <raise_exception ( Job failed ) > failed, due to error <50316>: <Job failed>. (14.2) 12-06-17 13:59:40 (E) (11941:2113906464) RUN-050316: |Session Job_Init_XLA_XLA_AE_LINES Job failed.

Kindly let us know your thoughts. dirk.venken werner.daehn

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Ravi,

we had faced similar issue, when back tracked issue was with the target system ( HANA ) where in there was an dead lock applied on the table which our job was dumping the data, so lock was released. This resolved our issue.

Track down all the source\Target as well as BODS bottle neck's to over come this long running issue.

Regards,

Shashi

rm24
Explorer
0 Kudos

Hi Sashi,

Thanks for the response. But we didn't find any deadlock on the target table. When we tried to do the same thing using snowflake instead of HANA the jobs are still running the same way. The source is OLFM. Any advice or suggestions will be really appreciated.

Thanks.

Answers (0)