BAD Performance of JDBC Receiver Adapter

[Former Member]

Hello,

we are using SAP PI 7.10 .

We are attempting to put in the place the following scenario : our SAP

R/3 4.7 system should get data from a remote DB2 zOS database within a

R/3 specific transaction. We would like to use SAP PI between R/3 and

the remote DB2 database :

• the request is sent by R/3 through a RFC call

• this RFC call is handled by PI through a sender RFC Communication

Channel

• the request is sent to DB2 through a receiver JDBC Communication

Channel

We have installed the DB2 driver into the PI system. The connection is

working from a technical standpoint since we get data but the

performance is not good. The processing runtime takes between 1min30s

and 3min.

According to PI logs, the issue comes from the step called "JDBC

Adapter Receiver Channel <XXX> processing started" into

the Audit Log. But we don't know why and how to fix it.

The issue does not come from the remote database since a direct access from a DB client runs quickly.

Have you already encounter this kind of issue ? If so, how could it be fixed ?

Thank you for your help.

Regards,

Fabrice

[Former Member]

Hello Sourabh,

as mentionned in my first message, there is no issue with the remote database. A connection attempted from systhem different from PI is working fine and fast.

Regards,

Fabrice

[rajasekhar_reddy14]

Hi Fabrice,

Which operation you performing on DB using JDBC receiver channel? INSERT operation takes high resources and time(as per my observation) once INSERT operation done then only DB connection will be released.

Option1:

Create Stored Procedure in data base and call SP using JDBC channel def it gives very good performance.

Check with Data base team like DB response time.

Execute DB operation in DB and check the performance too.

Regards,

Raj

[Former Member]

Dear Fabrice

the audit log you are reffering is standard indication that the processing has started, it does not mean that this is an error.

More over if after the begining of process in JDBC adapter if it takes more time then it is a DB issue. Ask the DB asministator for performance tuning

Ask them to check the index building for the table. Maybe the size of the table is too big.

Sourabh