on 09-09-2014 8:47 AM
Hi Everyone,
We have implemented PI interface a year ago with JDBC sender (ORACLE) and RFC receiver (SAP) to transfer the goods movements from legacy to SAP and give back the current stock after the goods movement is posted back to ORACLE system.
The interface has been working fine for over an year now but suddenly since 15days we are experiencing the issue of delays in message transmission where-in in SXMB_MONI we see a time difference of 60-90mins between start message start time and end time...
Nothing has been changed from development/design perspective and am unable to understand the reasons for this delay.
Also for the above scenario the message status in MESSAGE MONITORING shows waiting status and i have cross verified for any errors and could not find any errors in given time.
also MDT Screen shot for your reference
I am struggling to figure out the reasons and this is causing stock mismatch between Oracle system and SAP and has become show stopper.
Please guide me in identifying the root cause and fixing this...
Thanking you all in anticipation of help...
Lakshmi
Hi LN,
Please help with more details so that it is better for analysis
Your scenario and PI configurations
Is your scenario synchronous or is it two asynchronous interfaces through proxy ?
What is the poll interval which you have set in JDBC sender ? If the poll interval is short then also it may be occupying all the threads of JDBC adapter and message status is set to "Waiting"
Do you have JDBC receiver as well ?
Are you using any of the below options in JDBC sender or receiver ?
JDBC Sender
JDBC Receiver
Thanks,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
In that case are you using Request Response bean in the module tab of JDBC sender ? as I understand RFC is synchronous.
Are you using ICO or classic configurations(i.e Sender Agreements etc) ?
If you are using ICO then probably the problem could be with Receiver JDBC as until the receiver JDBC completes the process of updating the database the status of sender JDBC cannot be turned to DLVD. I beleive your receiver JDBC also points to same database as sender is querying to.
I would suggest try to check if this gets resolved by using Advanced mode features like "Transaction Isolation level"(pls consult database team for more feasiblity of options there) and "Disconnect from Database after processing each message"
Also,
It would be better if you can provide Audit log for message in waiting status from JDBC sender and receiver channels.
Thanks,
Amit
Hi Lakshmi,
These type of errors occurred when the target is not reachable or down...
Did you check in moni if there are any messages failed with status " system Error" identify and clear the queues. and resend the message..
Regards
Bhargava Krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes Bhargava,
as i mentioned i could not find any errors in moni and also the RFC has posted the goods movement and returned the Latest stock situtation...
However the same is not completed and still in waiting status leading to accumulation of records in queue delaying the next record processing
Lakshmi
hi Claudia,
I have cross verified both and as you can see there are no errors
a
and finally the XML
couldn't figure out why this delay happening... One thing after an hour or so... the things get cleared as one in executing state finishes leading to others to finish.. but by then they are getting accumulated
Appreciate any guidance to figure out the root cause...
Thanks in advance
lakshmi
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.