Skip to Content

DB_SPLITTER_QUEUING takes long time

Dear Experts,

I need some advice for the DB_SPLITTER_QUEUING takes a long time.

Here's the scenario.

We have a master data interface that is triggered from a background job. The interface scenario is IDoc -> File. The interface could be massive as 600k files alone not summed with other interfaces that is triggered by other background job that is scheduled at the same time.

Looking at the SXMB_MONI, processing one IDoc could take 3.662 seconds.

Seeing the trace message I see the following:

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="host">20131209090923.973893</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="host">20131209100704.156858</SAP:Timestamp>

</SAP:RunTimeItem>

This interface is put to the XBTZ queue. This actually affects other interfaces too, the interface that usually takes only 1 second to finish, when the Queue is full with the interface, could take from 30 - 120 secs.

I wonder if there's any tuning that I can do about this? Another thing is that If we tune this to be faster, I afraid things will fail at the adapter engine because the outbound AE will be stormed with many files since the IE processing is faster.

Thank you,

Suwandi C.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Dec 09, 2013 at 01:46 PM

    Hi Suwandi - Not sure if you have gone through the performance check report.

    There might not be enough dialogue processes to handle the incoming load and It is expected when you trigger such volume into PI.

    Increasing the Dialogue processes mat not solve your issue. As you mentioned now the load will be shifted to Java stack.

    You can define the interface priority and processing queues in SXMB_ADM so that this load will have no impact on business critical interfaces.

    Depending on your memory, you can also increase the parallel threads in the adapter engine to handle such volume.

    However Please refer to the below section and recommendations to handle such situations:

    4.4.5 Long Processing Times for “DB_SPLITTER_QUEUEING”

    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782?quicklink=index&overridelayout=true

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 09, 2013 at 01:59 PM

    Hi Suwandi,

    Kindly follow the SAP Note : 894509 also the below link to solve this DB_SPLITTER_QUEUING issue.

    http://scn.sap.com/people/prasad.illapani/blog/2007/03/08/performance-tuning-checks-in-sap-exchange-infrastructure

    Best Regards,

    Monikandan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 11, 2013 at 05:03 AM

    Hi,

    Thank you for the reply. I have do the performance tuning, and the performance is raised. But seems there's another problem.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.