Locking Queue

Hi All
I have created a queue in SAP PI for serializing of IDocs. Now for testing I need to lock this queue, I went to SMQR and unregistered the queue which is resulting in flowing of IDocs using different queues.
Can anyone tell me how can I lock that particular queue.
Regards
Sourabh

Hi Sourabh,
Check this blog: /people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
Check SAP Note: 752194
Normally, when a dedicated queue is assigned then it should be block the message when we de-register the queue.
If you are not able to view the messages in queue, then unlock the queue from smq1/smq2.
Thanks,

Similar Messages

Lock Queue for a particular Partner No.

Hi All,
We want to lock the RFC queue for a particaular partner No. is this possible in SAP?
Background : We are having a maintainace activity on one of our middle ware, hence there would be changes done to a particular and critical interface. The middle ware team has requested that they should not receive any IDOCs during this time but as the activity is for a substantially high time, we cannot stop the batch which generates the critical Idocs during time as the critical IDOCs can be generated only for N and N-1 day only (Activity may last for 3-5 days depending on the outcome). We would want to lock the queue for a particular Partner No. so that once these IDOCs are generated they can be waiting in queue untill the queue is released and the target system has all the IDOCs required by the time the system is handed over to the bussiness.
P.S : We are transfering IDOC through TRFC call to the target system.
Can you please suggest?
Regards,
Anand.

Hi Anand,
As per SAP documentation
Creating an Outbound Partner Profile (SAP Library - IDoc Interface/Electronic Data Interchange)
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f5643d711d1893e0000e8323c4f/content.htm
When you assign a port number for IDOC partner profile, this port number is mapped to a RFC destination.
Either you can hash out port <-> RFC destination mapping or hash out the RFC destination host mentioned in SM59.
Hope this helps.
Regards,
Deepak Kori

Locked Queues

Hello SDN,
Sometimes message processing is not executed successfully and the error lock the queues.
When we check the message status (message monitoring / SXMB_MONI) it is "scheduled for outbound processing" or "System error".
We fixed the errors when they occur but the problem is that the error locks the queue therefore the messages waiting for execution in the same queue have to wait until a manual cancel of the message with problems to be executed.
I wonder if is there any way to configure that when an error occurs during the execution in a queue, the error always can be transfered to the message (as a message with a system error) and do not lock the queue, so the following messages can be executed.
Do someone have had the same problem?
Best regards,
Gustavo P.

Hi Gustavo,
Tine Related Parameter can be checked with ::
There are two ways of changing this timeout:
a) check out note: 824554 and try to change it in the instance profile
b) TCODE SXMB_ADM -> Configure Integration server -> change specific identifiers
Set Runtime parameter: HTTP_TIMEOUT
Rember to restart XI after the change
For Dealing with All knid of Time Out Errors ::
See
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Now Coming back to Queues getting Blocked I dont hink Queue Prioritization is a ggod Idea, We have to manually Deal with Queues and the Data in Ind, remember if are force to delete any data from the Queues Delete the Complete LUW rather then individual message.
Have a Look at this Blog as well::
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Please Keep the Table of important SAP Notes for common XI work::
SAP Note     Description
856597     FAQ: XI 3.0 SOAP Adapter
856346     FAQ: J2EE JMS Adapter: Frequently Asked Questions
821267     FAQ: XI 3.0 File Adapter
831162     FAQ: XI 3.0 JDBC Adapter
730870     FAQ XI 3.0 RFC Adapter
813993     FAQ: Message status in the adapter framework
856599     FAQ : XI 3.0 Mail Adapter
816022     FAQ: XI 3.0 J2EE Adapter Engine / Messaging System
801868     Java(TM) Web Start in XI 3.0: FAQ/Troubleshooting
774854     FAQ XI 3.0 BC Adapter
830039     FAQ: Deployment of the XI adapter framework
813993     FAQ: Message status in the adapter framework
793669     FAQ: SUS in SRM 4.0 with XI 3.0
615740     FAQ: CCMS GRMG Availability Monitoring
872388     Troubleshooting Archiving and Deletion in XI 3.0
872508     XI 3.0 AF: BufferOverflowException when sending large msgs
764417     Information for troubleshooting of the SAP J2EE Engine 6.40
721548     Changing the passwords of the XI service users
886888     XI 3.0 Adapter Framework: XML parsing error for xmlns
885405     Troubleshooting End-to-End Monitoring in XI 3.0
821268     XI 3.0 Adapter Framework: Overview of available FAQ notes
858366     SAP XI 3.0 SP12: iWay Adapter Release Note
801951     XI30: Analyzing mapping problems
711947     ITK 1.5 FAQ
768148     Using a separate SLD for XI
764393     Configuration of the SAP System Landscape Directory
813029     Automatic processing of failed XI messages
913858     XI3.0 Alerting: Troubleshooting (new)
I hope it will help you :::-))
Regards
Piyush
Please reward Points if you find this helpfull::-))

Why the queue is locked in SMQ2?

Sometimes,I find the queue would be locked in SMQ2 ,so i have to release the locked queue so that it can keep on working normally.
I'd like to know what reason can cause the queue locked ?Once the queue is locked,how to get the notificaion?
thanks in advance.
Regards,
brand

Hi
queues are locked when the load to the processor is hight..and the second task is in queue while first one is processing at that time..secodn process will be locked after some time..extent
1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
2)You may need to re-register your queues.
Follow SXMB_ADM -> Manage Queues -> Deregister Queues
Afterwards, re-register the queues and activate from the same screen
3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
a double click on the entry shall take you to detailed list.
if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
Now go to SMQ3, right click on the queue and give Restore LUW.
6)this basically means tht message is waiting in the queue.
in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

Enqueue lock object in abap mapping

Hi,
In a idoc to file scenario, i need to garantee a unique target filename for message.
I have a ZXI_I2155 table to mantain a counter by some key fields (cliente, anyo, mes)
So, in an abap mapping I have:
   CALL FUNCTION 'ENQUEUE_EZXI_I2155'
      EXPORTING
        MODE_ZXI_I2155 = 'E'
        MANDT          = SY-MANDT
        keycli         = d_cliente
        anyo           = d_anyo
        mes            = d_mes
        _WAIT          = 'X '
      EXCEPTIONS
        FOREIGN_LOCK   = 1
        SYSTEM_FAILURE = 2
        OTHERS         = 3.
    if sy-subrc = 0.
      select single * from ZXI_I2155 into wa_registro
                      where keycli = d_cliente and anyo = d_anyo and mes = d_mes.
          add 1 to wa_registro-contador.
        modify ZXI_I2155 from wa_registro.
      endif.
      CALL FUNCTION 'DEQUEUE_EZXI_I2155'
        EXPORTING
          MODE_ZXI_I2155 = 'E'
          MANDT          = SY-MANDT
          keycli         = d_cliente
          anyo           = d_anyo
          mes            = d_mes.
    endif.
concatenate 'ART' d_cliente d_mes wa_registro-contador '.XML' into d_fichero.
l_record-namespace = 'http://sap.com/xi/XI/System/File'.
l_record-name = 'FileName'.
l_record-value = d_fichero.
dynamic_configuration->add_record( l_record ).
With a normal situation, this scenario works well, but with a great volume of messages, some duplicate filename appears.
Why?
Thanks, in advance
Carme

Try increasing the "enque/table_size" parameter to allow more IDOCs to be handled/locked at the same time. You can increase the value for this parameter up to 102400 (beyond that can cause performance issues).
Please refer to the notes below for more information about the lock queue overflow and management.
[Note 552289 - FAQ: R/3 Lock management|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=552289]
[Note 13907 - System error in the block handler, overflow lock table|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=13907]

IDOC Receiver Adapter, getting Lock Table Overflow to CRM System

Hello SDN!!!
This scenario is for PI to process a file and send to CRM via IDOC. The IDOCu2019s are only being created and not processed until later.
Problem: I am getting a Lock Table Overflow error in method IDOC_INBOUND_ASYNCHRONOUS via sm58 in PI which points to the CRM box.
I have been searching many forums and every solution seems to indicate increasing the lock table, the problem with that solution is we are currently trying to create (not process yet) 80000 IDOCu2019s. This would allocate too much for the lock table.
So my question is this, Shouldnu2019t the lock be released when the IDOC gets created or none the less when a packet of IDOCu2019s via content management (breaking up the file in 1000 increments) finish. The lock table in CRM keeps increasing until all rows from the file, sent via IDOC adapter in 80 messages with 1000 IDOCu2019s per messagein the table are complete (80 separate messages in sxmb_moni).
Background:
IDOC was imported, changed to include unbounded and reimported.
Content Management breaks the file into 80 different segments, thus creating 80 distinct mappings with distinct MessageIdu2019s.
80 IDOC packets are sent to CRM, via IDOC adapter and sm58.
TCODE sm12 in CRM shows the table to keep growing and locks not released until full message is complete.
Any help would be appreciated
Cheers
Devlin

The only way to process the IDOCs in this case is by increasing the "enque/table_size" parameter in order to create the required IDOCs. You can increase the value for this parameter up to 102400 (beyond that can cause performance issues). Since you need to handle 80000, this shouldn't be an issue.
Please refer to the notes below for more information about the lock queue overflow and management.
[Note 552289 - FAQ: R/3 Lock management|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=552289]
[Note 13907 - System error in the block handler, overflow lock table|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=13907]

Inconsistent Locking with Select for Update

Hi,
I seem to be having some issues in using SELECT FOR UPDATE and was hoping to get some insight from the Oralce Guru's out there.
I have a J2EE application, running in WebLogic 8.1.4 using Oralce 9.2.0.1.0.
The application contains code that requires locking to be done on a specific table with multiple transactions (tx) requesting the same lock. Eg:
Tx 1: Select * from Zone where Zoneid = 'Zone1' for update (Obtains lock)
Tx 2: Select * from Zone where Zoneid = 'Zone1' for update (waits)
Tx 100: Select * from Zone where Zoneid = 'Zone1' for update
Tx1 commits.
It appears that the following transactions, i.e. Tx2 - Tx100 do not seem to execute in the order the lock was requested. That is Tx 100 always appears to be the second last transaction to execute, after which some arbitrary transaction between Tx2 - Tx99 will execute after Tx100 has committed.
This seems to tell me that the lock is not being handed in a FIFO manner and is causing us great pain as our data is not longer consistent.
Does anyone know how i might be able to trace which transaction is being awarded the lock? Also if anyone has any suggestion on how to troubleshoot/solve this issue, greatly appreciated.
TIA
Prem

Oracle does not have a lock queue/manager at all. The locked status of a record is essentially an attribute of the record itself. It is stored on the datablock header. When a transaction requests a lock and can't get it, and is willing to wait (SELECT FOR UPDATE without NOWAIT), it first spins while waiting for the lock (four times as I recall), then sleeps waiting for the lock. The the more times it sleeps before getting the lock, the longer it will sleep before trying again.
What is likely happening here is that transaction 100 is still spinning when transaction 1 commits, so checks back more frequently and gets the lock first. The rest get the lock whenever they wake up and noone else has taken the lock.
If you need the transaction to occur in order, then I do not think you can use Oracle's native locking mechanism. Depending on what exactly you are trying to do, you may want to look at Advanced Queueing, or possibly the built-in package DBMS_LOCK.
HTH
John

Preventing Outbound Queues during APO Shutdown

Dear All,
Here's my query:
Whenever we go for a APO shutdown with all Users in APO locked, Queues get generated in the R/3 Outbound with SYSFAIL messages: User Locked. After the shutdown, these take a huge amount of time to be cleared and lead to wastage of time.
To prevent, we have tried Stopping APO Inbound Queues during the shutdown. However, the problem continues. I would like to try Using program to Close R/3 Outbound Queues during Shutdown as well. Can this affect in any way the Queues to other R/3 partner systems other than APO?
Also, any other suggestions to prevent this problem during the shutdowns are most welcome.
What are the precautions/steps taken to prevent such situations at various APO Clients.
regards
Sudhir Gulati

Hi,
In program RSTRFCQ1 (in R/3) you can define queue destination to be stopped. So you can stop only queues outbound for your APO system.
You can also restrict by queue name - it tends to be different fro APO-bound queues - CF* and FC* for example.
We always do that before stopping APO to prevent exactly your problems.
br,
Mikhail

Make entire play queue editable

There's currently two queues in Spotify: The locked queue. (White items.)The editable queue. (Yellow items.)If you press the queue button with tracks in both lists, you can see that these two queues are comined into one. The editable queue always plays first. The problem is having a locked queue at all. You can't empty it without interrupting playback, and you'll have to use a workaround to do so. You can't reorder it or add or delete songs. After finishing the editable queue, Spotify always continues playback from the locked queue. The workaround is starting playback at the very last item on a page. The locked queue will then have no further items. Then you can continue by purely using the queue right-click function instead of double-click or enter. This adds items to the editable queue. These tracks can then be reordered and deleted as you wish. This UI behaviour is, however, not very user-friendly and quite frankly really annoying. It's also very unconventional having two queues in a music player. I've never seen any other software using either a dual-queue system or a locked queue system. Here's a good implementation suggestion from user Styrke: ----Google Play Music's queue system is really easy to understand and use. Just do what they do. I can describe it by three (3) easy bullets: Double clicking a song starts playing it and adds the rest of the list that the song came from to the queue. (The queue gets overwritten)Right click one or more songs to add them to the top ("play next") or the bottom ("add to queue") of the queue.Everything in the queue can be removed or rearranged by drag-and-drop----

"It's assumed you want to listen to an entire artist." That's a wrong assumption in most cases. Besides, as pointed out, a search result does not contain only one artist; it usually contains a whole jumble of various artists. Nobody wants to listen to that whole list in sequence. The expected behavior when one double-clicks a track somewhere is that the track is added to the play queue he exact same way tracks are added when you right-click and select "Queue", and that it immediately starts playing. Possibly along with the rest of the tracks in the list you found it on, provided it's an album or a playlist. Never if it's an entire search result or an entire discography (which isn't chronological anyway). The way it appears to be currently done, instead of individually adding tracks to the play queue, some sort of pointer is established in an album, discography, playlist or search result, saying: "Play everything below this point". And then the pointer plays its way relentlessly downward, displaying in the play queue all the tracks it intends to play, without them actually being added to the queue. And with little possibility to remove any of them or change their order in the queue. In my opinion, this entire approach is fundamentally flawed and should be abandoned altogether as soon as possible.

Unblock Queues in APO

Hi All,
i have a small query. Can anyone please tell me how to Unblock Queues in APO. .
i have tried
/sapapo/CIF_QIN_STARTQUEUES
but somehow it dint work. . .
I have somewhere read (on sdn thread), that there's a Transaction in APO wherein you can Lock Queues, even Lock Users. .
All this functions are available with just one button click, but i just cannot recollect that T-code. .
i would really be grateful to know that T-code. .
Awaiting for a positive reply. . .
Regards,
Prasad.

Use /SAPAPO/CIFSTARTQUEUES report to start the queues.
Else you can go to /SAPAPO/CQ and the unlock queues from there.
Regards

ABAP Client Proxy from ECC 6.0 to XI message irregular recieving

Hi Gurus
Any one has come across issue whereby the ECC 6 system trigger ABAP Client proxy to SAP PI 7.0. The first time the PI is able to recieve it in the SXI_MONITOR. But subsequent trigger from the ECC 6.0 system the SAP ABAP program to trigger the Client Proxy, the PI seem to lost connectivity and did not recieve any message. This is pretty strange and hopefully someone in SDN and enlighten me.
Thanks
Regards
On behalf of malcolm

Hi Santosh
I went to SMQR and register the queue, but it still did not reflect the locked queue when i trigger the ECC 6 to SAP PI 7.0. The green flag - schedule still appear in the SXMB_MONI queue. But i am quite puzzle as why the ABAP client proxy after sending message the first time and second time, the third time it stuck? And also it is not practical to everytime go to the SMQ1 or SMQ2 to unlock the queue. I don't think it a good solution for solving my problem, it is just a temporary solution.

Set account's business partners relationships

I'd like to know if there's a way to set an organizational chart of an specific client for use it on the oportunities.
Thanks!

The overview consists of 3 levels:
-1: an overview of the outbound queues
-2: the overview of the queue names
--> here you can activate (activate a particular queue which has stopped or was dactivated) & unlock (unlock a locked queue: possibility to lock/unlock queues manually)
-3: the overview of specific queue-entries
--> here you can "process the LUW" or "debug the LUW".
The idea would be to go to level 2, where you can see the reason for the error, and then to level 3 to process the queue manually.
If the queue-entry disappeared when you processed it, it can mean that the problem that was stopping the queue has been solved, but it can also mean that a short-dump was triggered or .... Try to download the object again and see what happens. Also check the filters of the object.
Michael.

Strange Client Behavior after upgrading to 10g

Hello Friends !!!!
Here is my scenario:
Oracle Database 10g 10.2.0.3
Windows 2008 Server SP2
After upgrading from oracle 9.2.0.1.0 and Windows 2003 Server I'm facing a strange behavior.
Many times over the days some machines do not release some table resources even having their status "INACTIVE" and the wait event "SQL *Net message from client" and wait class "IDLE".
Therefore, i got a lot of locked sessions, and users complaining..... until I kill them
The client machine was as well switched to Oracle 10g client....
Have you guys got any tips about this scenario?
Tks for any advice.

About the lock queue:
1. blocking session has an exclusive table lock on VENDEDORES table; this is very rare in application because most of the time not needed: application code should try to avoid to take such kind of lock.
2. blocked sessions request a row share table lock: it looks like that VENDEDORES table is a child table linked to some parent table with a foreign key constraint and that an index on the child table foreign key is missing (this kind of lock is requested if you DELETE from parent table or update parent table primary key).
About the lock session: this is the blocking session that is waiting since 19 seconds on client: it is likely an application issue: you should try to investigate what the client (aservice.exe) is doing while holding an exclusive table lock.

Missing Messages by JMS Adapter

We are using JMS adapter to send the X12 messages to XI and we are having intermittent issues when the server load is high or server is given a restart.
Some of the messages from MQ are not processed by the adapter and are lost.
We have to resend the messages again.
has anyone face similar problems in prod. Solution for the problem would be awarded full points

Hi,
check the "Transactional JMS Session (Recommended)" check box.
Then no message loss will happen from MQ.If there is any messages loss, go and check the dead lock Queue.

Sun DS 5.2 SP4 patch upgrade - Cognos environment

We have Cognos v7.3MR2, using bundled Sun Dir. Server v5.2.
We are upgrading to Cognos v7.4, which bundles Sun Dir. Server v5.2 SP4. So, we wish to just patch the underlying Sun DS to v5.2 SP4, and avoid a complete export LAE >> uninstall >> install >> import LAE process.
I read part # 819-4461-10 Sun Java ES Upgrade Guide for MS Windows, and it says that the SP4 patch ZIP (121392-02.zip) is good to get you from SP3 to SP4.
All I know is that the build I have installed today (as part of Cognos v7.3 MR2) is build # 2003.143.0014 (taken from slapd.inf).
THE QUESTION: Can I apply the SP4 patch ZIP to upgrade from that build level of DS v5.2 and achieve SP4 nirvana?
Thanks ...
Tracy Slack

The pstack clearly indicates some contention on a RW Lock, deep in the processing of access controls (and there are only searches).
But it seems that the contention is not a reader / writer lock, but too much concurrent access on the lock queue.
I think you should call Sun support and have them investigate further the issue.
Ludovic.

Locking Queue

Similar Messages

Maybe you are looking for