cancel
Showing results for 
Search instead for 
Did you mean: 

Records are updating slowly in DB by receiver JDBC channel.

former_member308994
Participant
0 Kudos

Dear All,

My Scenario is JDBC to RFC synchronous scenario. we have used "RequestResponseBean" in Sender Jdbc channel for syncronous. So we have used 2 jdbc channles 1 for selecting the records from DB and 2nd for updating the response in DB.

The select query is working fine and it is selecting the records properly with in time,but while updating the response in DB coming from ECC is taking time .

The other scenarios with same configurations are working fine. we are getting issue with only for one plant.

for your reference am attaching the screen shots for both plants please find.

Is it PI issue or DB issue?

Kindly help me how to check and resolve this issue.

Regards,

Ramu

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member190681
Active Participant
0 Kudos

hi ram mohan,

According to my knowledge

1.first check for the scenario perfomance monitoring in "RWB" or Component Monitoring Home" check the pipe line steps where is the time gap happening in pipeline steps.

2. Check in RFC Program performance tunning as well. for inserting/executing the records SAP Program may be taking longer time due to that a response coming late.

3. Check PI Server Level Worker Threads are free for JDBC? Check Backlog Monitoring -->Addition Data

it should not be for example by default 5/5 like that, then you need to increase Thread according to SAP suggestion.

Regards,

Kiran Polani

apu_das2
Active Contributor
0 Kudos

Hi Ramu,

I believe it's insert query issue.

If it is your Test system then separately perform one direct insert query as you are sending in the response through PI. It may happen that system is taking more times to filter data for a particular plant.

Thanks,

Apu

former_member308994
Participant
0 Kudos

Dear Das,

Thanks for quick reply.

It is production issue. Is there any way to check this.

apu_das2
Active Contributor
0 Kudos

If it's in production, then testing insertion query is definitely not possible. In this case, I will suggest you to reach to the team supporting the Oracle database and ask then if they have any log which contains db access data.

You may check that and have an idea of data processing time.

Thanks,

Apu