Skip to Content

B1iF queue monitor _!!BSTgs(com_sap_b1i_system_xc)

Hi All,

Does anyone know what is "_!!BSTgs(com_sap_b1i_system_xc)"? From time to time it hangs in a queue. What does it do? Is it something important?

Regards

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Oct 24, 2017 at 07:52 AM

    Based on SAP Note 1873607, it seems to me, the scenario is a part of B1if garbage collector's work. To keep the integration framework database in reasonable limits, the integration framework garbage collector (GC) is scheduled to delete the log history.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 09, 2017 at 04:48 PM

    Actually there are 3 GC jobs from the integration technology, running on a regular basis. Queue GC, Transaction Log GC and BizStore GC. All these GCs are triggered by a message in an internal Q. The message is NOT hanging in the Q. The GCs are working block-wise. Triggered by a task-message in the Q, the GC gets started, processes the first block and then pushes the message back into the Q to call itself again for the next block. Due to ACID transactionality, you will always see the message in the Q although it is permanently changing. The timer for GCs can be adjusted by TOOLS-Control Center->CONFIGURATION->Deployment Panel. Here you select the first entry (Default Deployment Document 'xcellerator.cfg'), click [Cfg] button to prepare the configuration (necessary only the first time) and then a second time to open the configuration UI. Scroll down to the GC trigger (*Prep) which you want to change (e.g. BSTgcPrep) and click [Cfg] button. You can change the setting in the Ip area, following the CRON tab logic to define scheduler. Click [Apply] button to activate the new settings.

    Add comment
    10|10000 characters needed characters exceeded