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
80

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

View Entire Topic
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.