cancel
Showing results for 
Search instead for 
Did you mean: 

Longer job runtimes after upgrading to Data Integrator 6.5 to 11.7.4.3

Former Member
0 Kudos

Hello folks,

Being an ActaWorks/Data Integrator customer for about 9 years, we upgraded this week to version 11.7.4.3.

An upgrade should normally result in better performance but in our case, our jobs runs much longer (runtimes are even doubled) causing conflicts with other jobs.

A review of the job loggings suggests that DI is switching to IN MEMORY mode what does not seem to be the most performant setting. Who can advice how we should tune our jobs ?

I'm pasting a part of the job logging:

Job name: DAILY_UPDATE_JOB

(11.7) 08-27-08 21:00:02 (2936:2800) ORA_LIB: Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(11.7) 08-27-08 21:00:02 (2936:2800) JOB: Reading job <ade21ffe_3eb5_11d3_bfa6_10005affe6f3> from the repository; Server version is <11.7.3.4>; Repository version is

<11.7.0.0000>.

(11.7) 08-27-08 21:00:02 (2936:2800) JOB: Current directory of job <ade21ffe_3eb5_11d3_bfa6_10005affe6f3> is <C:\Program Files\Business Objects\Data Integrator 6.5\bin>.

(11.7) 08-27-08 21:00:02 (2936:2800) JOB: Starting job on job server host <RBRMSACTA03>, port <3790>.

(11.7) 08-27-08 21:00:02 (2936:2800) JOB: Job <DAILY_UPDATE_JOB> of runid <2008082721000229362800> is initiated by user <SOEadmin>.

(11.7) 08-27-08 21:00:02 (2936:2800) JOB: Processing job <DAILY_UPDATE_JOB>.

(11.7) 08-27-08 21:12:06 (2936:2800) JOB: Optimizing job <DAILY_UPDATE_JOB>.

(11.7) 08-27-08 21:12:06 (2936:2800) JOB: Job <DAILY_UPDATE_JOB> is started.

(11.7) 08-27-08 21:12:06 (2936:2800) WORKFLOW: Work flow <PRODUCT_WF> is started.

(11.7) 08-27-08 21:12:07 (1032:1320) DATAFLOW: Process to execute data flow <PRODUCT_OTHERSAP_DF> is started.

(11.7) 08-27-08 21:13:00 (1032:1320) DATAFLOW: Data flow <PRODUCT_OTHERSAP_DF> is started.

(11.7) 08-27-08 21:13:00 (1032:1320) ABAP: ABAP flow <PRODUCT_ZTABLES_R3> is started.

(11.7) 08-27-08 21:13:10 (1032:1320) ABAP: ABAP flow <PRODUCT_ZTABLES_R3> is completed.

(11.7) 08-27-08 21:13:10 (1032:1320) DATAFLOW: *Cache statistics determined that data flow <PRODUCT_OTHERSAP_DF> uses <0> caches with a total size of <0> bytes. This is less

than(or equal to) the virtual memory <1610612736> bytes available for caches. Statistics is switching the cache type to IN

MEMORY.*

(11.7) 08-27-08 21:13:10 (1032:1320) DATAFLOW: Data flow <PRODUCT_OTHERSAP_DF> using IN MEMORY Cache.

(11.7) 08-27-08 21:13:10 (1032:1320) FTP: Started FTP transfer of file: </sap_interfaces/BODI/be/PRODUCTZTABLES2.dat>.

(11.7) 08-27-08 21:13:11 (1032:1320) FTP: Completed FTP transfer of file: </sap_interfaces/BODI/be/PRODUCTZTABLES2.dat>.

(11.7) 08-27-08 21:13:13 (1032:1320) DATAFLOW: Data flow <PRODUCT_OTHERSAP_DF> is completed successfully.

(11.7) 08-27-08 21:13:13 (1032:1320) DATAFLOW: Process to execute data flow <PRODUCT_OTHERSAP_DF> is completed.

(11.7) 08-27-08 21:13:13 (1684:0392) DATAFLOW: Process to execute data flow <PRODUCT_HIERAR_DF> is started.

(11.7) 08-27-08 21:13:46 (1684:0392) DATAFLOW: Data flow <PRODUCT_HIERAR_DF> is started.

(11.7) 08-27-08 21:13:46 (1684:0392) ABAP: ABAP flow <PRODUCT_HIERAR_R3> is started.

(11.7) 08-27-08 21:13:47 (1684:0392) ABAP: ABAP flow <PRODUCT_HIERAR_R3> is completed.

(11.7) 08-27-08 21:13:47 (1684:0392) DATAFLOW: Cache statistics determined that data flow <PRODUCT_HIERAR_DF> uses <0> caches with a total size of <0> bytes. This is less

than(or equal to) the virtual memory <1610612736> bytes available for caches. Statistics is switching the cache type to IN

MEMORY.

(11.7) 08-27-08 21:13:47 (1684:0392) DATAFLOW: Data flow <PRODUCT_HIERAR_DF> using IN MEMORY Cache.

(11.7) 08-27-08 21:13:49 (1684:0392) FTP: Started FTP transfer of file: </sap_interfaces/BODI/be/Product-hierar.dat>.

(11.7) 08-27-08 21:13:49 (1684:0392) FTP: Completed FTP transfer of file: </sap_interfaces/BODI/be/Product-hierar.dat>.

(11.7) 08-27-08 21:13:57 (1684:0392) DATAFLOW: Data flow <PRODUCT_HIERAR_DF> is completed successfully.

(11.7) 08-27-08 21:13:57 (1684:0392) DATAFLOW: Process to execute data flow <PRODUCT_HIERAR_DF> is completed.

(11.7) 08-27-08 21:13:58 (1052:3136) DATAFLOW: Process to execute data flow <PRODUCTSAP_DF> is started.

(11.7) 08-27-08 21:14:42 (1052:3136) DATAFLOW: Data flow <PRODUCTSAP_DF> is started.

(11.7) 08-27-08 21:14:42 (1052:3136) ABAP: ABAP flow <PRODUCT_R3> is started.

(11.7) 08-27-08 21:14:44 (1052:3136) ABAP: ABAP flow <PRODUCT_R3> is completed.

(11.7) 08-27-08 21:14:44 (1052:3136) DATAFLOW: Cache statistics determined that data flow <PRODUCTSAP_DF> uses <0> caches with a total size of <0> bytes. This is less than(or

equal to) the virtual memory <1610612736> bytes available for caches. Statistics is switching the cache type to IN MEMORY.

(11.7) 08-27-08 21:14:44 (1052:3136) DATAFLOW: Data flow <PRODUCTSAP_DF> using IN MEMORY Cache.

(11.7) 08-27-08 21:14:44 (1052:3136) FTP: Started FTP transfer of file: </sap_interfaces/BODI/be/PRODUCTSAP.DAT>.

(11.7) 08-27-08 21:14:45 (1052:3136) FTP: Completed FTP transfer of file: </sap_interfaces/BODI/be/PRODUCTSAP.DAT>.

(11.7) 08-27-08 21:14:52 (1052:3136) DATAFLOW: Data flow <PRODUCTSAP_DF> is completed successfully.

Thanks for your input!

Kris

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Exporting our repository to an .ATL file, deleting the repository & recreating it followed by an import of the created export file solved the issue...

The repo upgrade got seriously polluted by the upgrade; the above cleaning steps saved the show...

werner_daehn
Active Contributor
0 Kudos

Thanks Kris.

Answers (2)

Answers (2)

Former Member
0 Kudos

As compare material, i'm adding an old job logging under 6.5 & new logging from version 11.7:

Job name: ORDER_VALIDATION_JOB

(6.5) 08-25-08 08:07:00 (2792:3252) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:07:00 (2792:3252) JOB : Reading job <897b8167_b347_4496_98c5_d55afbd5d621> from the repository; Server version is <6.5.0.1>; Repository version is

<6.5.0000>.

(6.5) 08-25-08 08:07:00 (2792:3252) JOB : Current directory of job <897b8167_b347_4496_98c5_d55afbd5d621> is <C:\Program Files\Business Objects\Data Integrator 6.5\bin>.

(6.5) 08-25-08 08:07:00 (2792:3252) JOB : Starting job on Job Server <RBRMSACTA03>.

(6.5) 08-25-08 08:07:00 (2792:3252) JOB : Job <ORDER_VALIDATION_JOB> of runid <2008082508070027923252> is initiated by user <SOEadmin>.

(6.5) 08-25-08 08:07:00 (2792:3252) JOB : Processing job <ORDER_VALIDATION_JOB>.

(6.5) 08-25-08 08:07:05 (2792:3252) JOB : Optimizing job <ORDER_VALIDATION_JOB>.

(6.5) 08-25-08 08:07:05 (2792:3252) JOB : Job <ORDER_VALIDATION_JOB> is started.

(6.5) 08-25-08 08:07:05 (2792:3252) WORKFLOW: Work flow <ORDER_VALIDATION_SALES_WF> is started.

(6.5) 08-25-08 08:07:06 (1108:1160) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:07:06 (1108:1160) DATAFLOW: Process to execute data flow <ORDER_VALIDATION_SALES_DF:ORDER_VALIDATION_SALES_WF> is started.

(6.5) 08-25-08 08:07:06 (1108:1160) DATAFLOW: Data flow <ORDER_VALIDATION_SALES_DF> is started.

(6.5) 08-25-08 08:07:28 (1108:1160) DATAFLOW: Data flow <ORDER_VALIDATION_SALES_DF> is completed successfully.

(6.5) 08-25-08 08:07:28 (1108:1160) DATAFLOW: Process to execute data flow <ORDER_VALIDATION_SALES_DF> is completed.

(6.5) 08-25-08 08:07:28 (2792:3252) WORKFLOW: Work flow <ORDER_VALIDATION_SALES_WF> is completed successfully.

(6.5) 08-25-08 08:07:28 (2792:3252) WORKFLOW: Work flow <ORDER_VALIDATION_WF> is started.

(6.5) 08-25-08 08:07:28 (1108:1608) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:07:28 (1108:1608) DATAFLOW: Process to execute data flow <OPEN_ORDERS_BLOCKED_DF:ORDER_VALIDATION_WF> is started.

(6.5) 08-25-08 08:07:31 (1108:1608) DATAFLOW: Data flow <OPEN_ORDERS_BLOCKED_DF> is started.

(6.5) 08-25-08 08:07:31 (1108:1608) ABAP : ABAP flow <OPEN_ORDER_BLOCKED_R3> is started.

(6.5) 08-25-08 08:08:35 (1108:1608) ABAP : ABAP flow <OPEN_ORDER_BLOCKED_R3> is completed.

(6.5) 08-25-08 08:08:35 (1108:1608) FTP : Started FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_BLOCKED.DAT>.

(6.5) 08-25-08 08:08:38 (1108:1608) FTP : Completed FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_BLOCKED.DAT>.

(6.5) 08-25-08 08:08:39 (1108:1608) DATAFLOW: Data flow <OPEN_ORDERS_BLOCKED_DF> is completed successfully.

(6.5) 08-25-08 08:08:39 (1108:1608) DATAFLOW: Process to execute data flow <OPEN_ORDERS_BLOCKED_DF> is completed.

(6.5) 08-25-08 08:08:39 (3396:1720) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:08:40 (3396:1720) DATAFLOW: Process to execute data flow <OPEN_ORDER_DF:ORDER_VALIDATION_WF> is started.

(6.5) 08-25-08 08:08:42 (3396:1720) DATAFLOW: Data flow <OPEN_ORDER_DF> is started.

(6.5) 08-25-08 08:08:42 (3396:1720) ABAP : ABAP flow <OPEN_ORDER_RX_DF> is started.

(6.5) 08-25-08 08:09:48 (3396:1720) ABAP : ABAP flow <OPEN_ORDER_RX_DF> is completed.

(6.5) 08-25-08 08:09:48 (3396:1720) FTP : Started FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_RX.DAT>.

(6.5) 08-25-08 08:09:54 (3396:1720) FTP : Completed FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_RX.DAT>.

(6.5) 08-25-08 08:10:43 (3396:1720) DATAFLOW: Data flow <OPEN_ORDER_DF> is completed successfully.

(6.5) 08-25-08 08:10:43 (3396:1720) DATAFLOW: Process to execute data flow <OPEN_ORDER_DF> is completed.

(6.5) 08-25-08 08:10:44 (3052:2676) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:10:44 (3052:2676) DATAFLOW: Process to execute data flow <OPEN_ORDER_II_DF:ORDER_VALIDATION_WF> is started.

(6.5) 08-25-08 08:10:45 (3052:2676) DATAFLOW: Data flow <OPEN_ORDER_II_DF> is started.

(6.5) 08-25-08 08:10:50 (3052:2676) DATAFLOW: Data flow <OPEN_ORDER_II_DF> is completed successfully.

(6.5) 08-25-08 08:10:50 (3052:2676) DATAFLOW: Process to execute data flow <OPEN_ORDER_II_DF> is completed.

(6.5) 08-25-08 08:10:51 (2676:3052) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:10:51 (2676:3052) DATAFLOW: Process to execute data flow <OPEN_ORDER_III_DF:ORDER_VALIDATION_WF> is started.

(6.5) 08-25-08 08:10:52 (2676:3052) DATAFLOW: Data flow <OPEN_ORDER_III_DF> is started.

(6.5) 08-25-08 08:11:10 (2676:3052) DATAFLOW: Data flow <OPEN_ORDER_III_DF> is completed successfully.

(6.5) 08-25-08 08:11:10 (2676:3052) DATAFLOW: Process to execute data flow <OPEN_ORDER_III_DF> is completed.

(6.5) 08-25-08 08:11:10 (2792:3252) WORKFLOW: Work flow <ORDER_VALIDATION_WF> is completed successfully.

(6.5) 08-25-08 08:11:10 (2792:3252) WORKFLOW: Work flow <OPEN_ORDER_REPORT_WF> is started.

(6.5) 08-25-08 08:11:11 (3052:2676) ORA_LIB : Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(6.5) 08-25-08 08:11:11 (3052:2676) DATAFLOW: Process to execute data flow <OPEN_ORDER_REPORT_DF:OPEN_ORDER_REPORT_WF> is started.

(6.5) 08-25-08 08:11:12 (3052:2676) DATAFLOW: Data flow <OPEN_ORDER_REPORT_DF> is started.

(6.5) 08-25-08 08:11:14 (3052:2676) DATAFLOW: Data flow <OPEN_ORDER_REPORT_DF> is completed successfully.

(6.5) 08-25-08 08:11:14 (3052:2676) DATAFLOW: Process to execute data flow <OPEN_ORDER_REPORT_DF> is completed.

(6.5) 08-25-08 08:11:14 (2792:3252) WORKFLOW: Work flow <OPEN_ORDER_REPORT_WF> is completed successfully.

(6.5) 08-25-08 08:11:14 (2792:3252) JOB : Job <ORDER_VALIDATION_JOB> is completed successfully.

version 11.7

Job name: ORDER_VALIDATION_JOB

(11.7) 08-28-08 08:07:03 (3316:0540) ORA_LIB: Loaded Oracle Client library <OCI.DLL> is in the path: <C:\Oracle9i\bin\OCI.DLL>.

(11.7) 08-28-08 08:07:03 (3316:0540) JOB: Reading job <897b8167_b347_4496_98c5_d55afbd5d621> from the repository; Server version is <11.7.3.4>; Repository version is

<11.7.0.0000>.

(11.7) 08-28-08 08:07:03 (3316:0540) JOB: Current directory of job <897b8167_b347_4496_98c5_d55afbd5d621> is <C:\Program Files\Business Objects\Data Integrator 6.5\bin>.

(11.7) 08-28-08 08:07:03 (3316:0540) JOB: Starting job on job server host <RBRMSACTA03>, port <3790>.

(11.7) 08-28-08 08:07:04 (3316:0540) JOB: Job <ORDER_VALIDATION_JOB> of runid <200808280807033316540> is initiated by user <SOEadmin>.

(11.7) 08-28-08 08:07:04 (3316:0540) JOB: Processing job <ORDER_VALIDATION_JOB>.

(11.7) 08-28-08 08:08:27 (3316:0540) JOB: Optimizing job <ORDER_VALIDATION_JOB>.

(11.7) 08-28-08 08:08:27 (3316:0540) JOB: Job <ORDER_VALIDATION_JOB> is started.

(11.7) 08-28-08 08:08:27 (3316:0540) WORKFLOW: Work flow <ORDER_VALIDATION_SALES_WF> is started.

(11.7) 08-28-08 08:08:28 (3164:3220) DATAFLOW: Process to execute data flow <ORDER_VALIDATION_SALES_DF> is started.

(11.7) 08-28-08 08:08:39 (3164:3220) DATAFLOW: Data flow <ORDER_VALIDATION_SALES_DF> is started.

(11.7) 08-28-08 08:08:39 (3164:3220) DATAFLOW: Cache statistics determined that data flow <ORDER_VALIDATION_SALES_DF> uses <0> caches with a total size of <0> bytes. This is

less than(or equal to) the virtual memory <1610612736> bytes available for caches. Statistics is switching the cache type to IN

MEMORY.

(11.7) 08-28-08 08:08:39 (3164:3220) DATAFLOW: Data flow <ORDER_VALIDATION_SALES_DF> using IN MEMORY Cache.

(11.7) 08-28-08 08:09:03 (3164:3220) DATAFLOW: Data flow <ORDER_VALIDATION_SALES_DF> is completed successfully.

(11.7) 08-28-08 08:09:04 (3164:3220) DATAFLOW: Process to execute data flow <ORDER_VALIDATION_SALES_DF> is completed.

(11.7) 08-28-08 08:09:04 (3316:0540) WORKFLOW: Work flow <ORDER_VALIDATION_SALES_WF> is completed successfully.

(11.7) 08-28-08 08:09:04 (3316:0540) WORKFLOW: Work flow <ORDER_VALIDATION_WF> is started.

(11.7) 08-28-08 08:09:04 (3220:3164) DATAFLOW: Process to execute data flow <OPEN_ORDERS_BLOCKED_DF> is started.

(11.7) 08-28-08 08:09:57 (3220:3164) DATAFLOW: Data flow <OPEN_ORDERS_BLOCKED_DF> is started.

(11.7) 08-28-08 08:09:57 (3220:3164) ABAP: ABAP flow <OPEN_ORDER_BLOCKED_R3> is started.

(11.7) 08-28-08 08:10:49 (3220:3164) ABAP: ABAP flow <OPEN_ORDER_BLOCKED_R3> is completed.

(11.7) 08-28-08 08:10:49 (3220:3164) DATAFLOW: Cache statistics determined that data flow <OPEN_ORDERS_BLOCKED_DF> uses <0> caches with a total size of <0> bytes. This is

less than(or equal to) the virtual memory <1610612736> bytes available for caches. Statistics is switching the cache type to IN

MEMORY.

(11.7) 08-28-08 08:10:49 (3220:3164) DATAFLOW: Data flow <OPEN_ORDERS_BLOCKED_DF> using IN MEMORY Cache.

(11.7) 08-28-08 08:10:50 (3220:3164) FTP: Started FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_BLOCKED.DAT>.

(11.7) 08-28-08 08:10:51 (3220:3164) FTP: Completed FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_BLOCKED.DAT>.

(11.7) 08-28-08 08:10:54 (3220:3164) DATAFLOW: Data flow <OPEN_ORDERS_BLOCKED_DF> is completed successfully.

(11.7) 08-28-08 08:10:54 (3220:3164) DATAFLOW: Process to execute data flow <OPEN_ORDERS_BLOCKED_DF> is completed.

(11.7) 08-28-08 08:10:55 (2976:1688) DATAFLOW: Process to execute data flow <OPEN_ORDER_DF> is started.

(11.7) 08-28-08 08:11:56 (2976:1688) DATAFLOW: Data flow <OPEN_ORDER_DF> is started.

(11.7) 08-28-08 08:11:56 (2976:1688) ABAP: ABAP flow <OPEN_ORDER_RX_DF> is started.

(11.7) 08-28-08 08:12:29 (2976:1688) ABAP: ABAP flow <OPEN_ORDER_RX_DF> is completed.

(11.7) 08-28-08 08:12:29 (2976:1688) DATAFLOW: Cache statistics determined that data flow <OPEN_ORDER_DF> uses <0> caches with a total size of <0> bytes. This is less than(or

equal to) the virtual memory <1609564160> bytes available for caches. Statistics is switching the cache type to IN MEMORY.

(11.7) 08-28-08 08:12:29 (2976:1688) DATAFLOW: Data flow <OPEN_ORDER_DF> using IN MEMORY Cache.

(11.7) 08-28-08 08:12:30 (2976:1688) FTP: Started FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_RX.DAT>.

(11.7) 08-28-08 08:12:42 (2976:1688) FTP: Completed FTP transfer of file: </sap_interfaces/BODI/be/OPEN_ORDERS_RX.DAT>.

(11.7) 08-28-08 08:13:59 (2976:1688) DATAFLOW: Data flow <OPEN_ORDER_DF> is completed successfully.

(11.7) 08-28-08 08:13:59 (2976:1688) DATAFLOW: Process to execute data flow <OPEN_ORDER_DF> is completed.

(11.7) 08-28-08 08:14:00 (3312:3000) DATAFLOW: Process to execute data flow <OPEN_ORDER_II_DF> is started.

(11.7) 08-28-08 08:14:40 (3312:3000) DATAFLOW: Data flow <OPEN_ORDER_II_DF> is started.

(11.7) 08-28-08 08:14:40 (3312:3000) DATAFLOW: Cache statistics for data flow <OPEN_ORDER_II_DF> are not available to be used for optimization and need to be collected before

they can be used.

(11.7) 08-28-08 08:14:40 (3312:3000) DATAFLOW: Data flow <OPEN_ORDER_II_DF> using PAGEABLE Cache with <1276 MB> buffer pool.

(11.7) 08-28-08 08:14:59 (3312:3000) DATAFLOW: Data flow <OPEN_ORDER_II_DF> is completed successfully.

(11.7) 08-28-08 08:15:00 (3312:3000) DATAFLOW: Process to execute data flow <OPEN_ORDER_II_DF> is completed.

(11.7) 08-28-08 08:15:04 (2908:1688) DATAFLOW: Process to execute data flow <OPEN_ORDER_III_DF> is started.

(11.7) 08-28-08 08:15:36 (2908:1688) DATAFLOW: Data flow <OPEN_ORDER_III_DF> is started.

(11.7) 08-28-08 08:15:36 (2908:1688) DATAFLOW: Cache statistics for data flow <OPEN_ORDER_III_DF> are not available to be used for optimization and need to be collected

before they can be used.

(11.7) 08-28-08 08:15:36 (2908:1688) DATAFLOW: Data flow <OPEN_ORDER_III_DF> using PAGEABLE Cache with <1280 MB> buffer pool.

(11.7) 08-28-08 08:15:56 (2908:1688) DATAFLOW: Data flow <OPEN_ORDER_III_DF> is completed successfully.

(11.7) 08-28-08 08:15:56 (2908:1688) DATAFLOW: Process to execute data flow <OPEN_ORDER_III_DF> is completed.

(11.7) 08-28-08 08:15:56 (3316:0540) WORKFLOW: Work flow <ORDER_VALIDATION_WF> is completed successfully.

(11.7) 08-28-08 08:15:56 (3316:0540) WORKFLOW: Work flow <OPEN_ORDER_REPORT_WF> is started.

(11.7) 08-28-08 08:15:57 (1688:2908) DATAFLOW: Process to execute data flow <OPEN_ORDER_REPORT_DF> is started.

(11.7) 08-28-08 08:16:47 (1688:2908) DATAFLOW: Data flow <OPEN_ORDER_REPORT_DF> is started.

(11.7) 08-28-08 08:16:48 (1688:2908) DATAFLOW: Cache statistics for data flow <OPEN_ORDER_REPORT_DF> are not available to be used for optimization and need to be collected

before they can be used.

(11.7) 08-28-08 08:16:48 (1688:2908) DATAFLOW: Data flow <OPEN_ORDER_REPORT_DF> using PAGEABLE Cache with <1277 MB> buffer pool.

(11.7) 08-28-08 08:17:02 (1688:2908) DATAFLOW: Data flow <OPEN_ORDER_REPORT_DF> is completed successfully.

(11.7) 08-28-08 08:17:03 (1688:2908) DATAFLOW: Process to execute data flow <OPEN_ORDER_REPORT_DF> is completed.

(11.7) 08-28-08 08:17:03 (3316:0540) WORKFLOW: Work flow <OPEN_ORDER_REPORT_WF> is completed successfully.

(11.7) 08-28-08 08:17:03 (3316:0540) JOB: Job <ORDER_VALIDATION_JOB> is completed successfully.

In this simple example the job that only run 4 minutes, takes now 10 minutes. it looks like it's for all steps; hardware is still the same; memory is 1GB...

Former Member
0 Kudos

Are you running on the same hardware or different?

Where exactly is the performance difference to be found? Is it related to specific steps in the job, the R/3 flow, starting the job, or in general on all parts when processing on the BODI server?

How is your memory usage during the execution of the job? IN MEMORY only means that it will be processed in the memory and not using the hard disk cache. At least, that is what it should be according to the collected statistics.

However it could be that during the execution of the job it runs out of memory. I have not tested it that much, but the job server is supposed to kick in the disk cache to prevent running out of (virtual) memory. Usage of the disk cache was for us such a dissappointing result that we see the only advantage of it that not brings the complete server and all running jobs.

But that depends on how far you are on the edge of running out of normal memory. Just a bit, then the disk cache is a nice feature. If your dataset is way too big the job should simply be redesigned not to use any memory on the BODI server and pushed down to databases/source/target systems.

Edit:

(11.7) 08-27-08 21:00:02 (2936:2800) JOB: Processing job <DAILY_UPDATE_JOB>.
(11.7) 08-27-08 21:12:06 (2936:2800) JOB: Optimizing job <DAILY_UPDATE_JOB>.

Okay, ignore my text. Here seems to be the biggest delay is it? I checked with our version 11.7.3 and this parts even for big jobs with a lot of datastores it takes just a few seconds. Definitely not minutes and for sure not 12 minutes.

Edited by: Johannes Vink on Aug 28, 2008 2:08 PM