Status of queue in case of rollback

Hi All, Suppose in a distributed transaction which involve 1) receive 2) database interaction and 3) send. Now for any message msg1 received in step1 , step 2 that is database interection results in some exception which will result in overall rollback. So what wil be the status of message msg1. will be it still in queue. I think its should be as that will mean msg reliability:)...but i am not able to make it work. msg is never received by the application. I have tried it as a MDB and a java application. but same result.. I want the message to be recived again and it has to be a synchronous implementation that is Queue. Can anybody suggests what could be the problem in my code or how it can be implemented.
REgards Akhil Nagpla

Hi,
After the global transaction has aborted, msg1 have to be reinserted in its original queue. However, if the queue contains other messages the delivery of msg1 could be delayed but msg1 must be eventually redelivered. You said that you tried to run a client application program outside a MDB, I can have a look at your code if you want to email it to me.
Hope it helps.
Arnaud,
http://www.arjuna.com

Similar Messages

Business messages are not pushed back to the aq exception queue in case of errors

Hi,
I have the scenario, where I have configured the business events in ebs and implemented the soa interface which consumes the event message from wf_bpel_q.
SOA interface is able to pickup the messages succesfully and same message will be pushed back to the same queue with the status=READY in case of exceptions as well. Ideally as per default functionality of AQ, in case of errors, messages will be pushed to exception queue.
Please suggest why mesages are not pushed back to exception queue in case of errror scenarios with the status='Errored'. Please let me know what i have been missing here in the setup.
Regards,
Anjana

Hi Anjana,
I am not familiar with the SOA interface, so I can't help you in detail, but take a closer look to the following documents.
Doc ID 1374461.1 , Doc ID 1075611.1 , Doc ID 1356146.1
Maybe you hit a known bug ....
Hope that helps.

SMOHQUEUE - Status of Queue Demon on Hold

Hi Experts,
I'm not able to replicate the materials from R/3 to SRM,earlier i was successfull in performing this task,but after sometime there seems to be a problem,but when checked in the the transaction SMOHQUEUE ,system displays the message as Status of Queue Demon on Hold,even after releasing the queues still the same error being displayed,i've scheduled a job as per the note no 681516 but still the problem persists,please advice.
Thanks and Regards,
Sathya kumar.

Hi
What all error logs are coming in RZ20 and SLG1 Transactions in this case. ?
Please refer to following OSS notes as well.
895863 Realignment queue in HOLD status for no apparent reason
970292 MIP implementation, source code corrections and corrections
453882 Parallel processing of the R&R queues
1014410 MIP Queue framework conversion: Migration of queue entries
480543 CRM MW R&R queues in status STARTING (no processing)
1001051 New queue framework: Queues do not exist
1012140 Extract during activation of 'Initially Inactive' sites
1011874 Generation error in the realignment service
1005561 Lock reset with resource bottlenecks in MIP queues
752584 SMOHQUEUE: Retry with technical errors when setting locks
794569 Short dump with detail display in SMOHQUEUE
762261 Addition to Note 638617 and 638628
655417 EXTRACT queue hangs with reference on ST22
624921 Activities after a system start (R/3 or CRM)
Keep me posted.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Q.Status is "Queue stopped"

I am using ECC 6.0 and XI 7.0,
While testing messages in XI, in SXMB_MONI, I am getting "Q.Status" as Queue stopped for lot of messages. What could be the possible reason for this??
Thanks in advance

Hi,
In the SMB_MONI, goto the Column showing the queue name and drill down. If the queue is stopped due to errored out message you will be able to see the details.
you can take corrective actions accordingly.
1. If the queue is not registered then register it again.
2. try to reporcess the errored message
3. see if it's not critical to delete the message so that the rest of the message can get processed.
Regards
Vijaya

Agents getting kicked out of Talking status to ready status on Queue calls

Hello All,
We have an odd problem. Some of our agents are complaning that they are randomly getting kicked out of talking status and going into a ready state while on a queue call.
For example an agent will be on a queue call and talking and UCCX will put them into a ready state while having recieved a call from the queue and still on that queue call.
On the agent phone there are two extensions (7945 IP Phone). Extension 2110 which is the queue number and 2500 which is a extesnion that is shared on several diffrent phones by the agents. 2110 is set to 2 calls and set to 1 as a busy trigger. 2500 is set to 4 calls and busy trigger of 2. Both extesnions are not part off any hunt groups and 2500 is the only one that is on several diffrent phones.
The agents do use extension mobility to sign into the phones since they rotate desks. We are running the enhanced version of contact center express System version: 8.5.1.11003-32.
The agents are using the cisco desktop agent.
Thanks for any help or advice,
Dan

Hi Dan,
Unsupported Configurations for Agent Phones
The following configurations are not supported for agent phones:
•Two lines on an agent’s phone that have the same extension but exist in different partitions.
•A Unified CCX extension assigned to multiple devices.
•Configuring the same Unified CCX extension in more than one device profile, or configuring the same Unified CCX extension in any combination of device profiles and devices. (Configuring an Unified CCX extension in a single device profile is supported.)
•In the Unified CM Administration Directory Number Configuration web page for each Unified CCX line, setting Maximum Number of Calls to a value other than 2.
•In the Unified CM Administration Directory Number Configuration web page for each Unified CCX line, setting Busy Trigger to a value other than 1.
•Configuring a Cisco Unified IP Phone with Secure Real-Time Protocol (SRTP) for use in silent monitoring and recording.
•No Cisco Unified Communications Manager device can be forwarded to the Unified CCX extension of an agent.
•The Unified CCX extension of an agent cannot be configured to forward to a Cisco Unified CCX route point.
•Use of characters other than the numerals 0–9 in the Unified CCX extension of an agent.
•Configuring the Unified CM intercom feature.
•Configuring the hold reversion feature.
Agents are not moved to "Not Ready" state by "Dropped Event" in workflow in case the agent got reserved for next call.
Reference:
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/release/guide/uccx851rn.pdf
Hope this helps.
Anand
Please rate helpful posts !!

Message Status "Scheduled", Queue Status "Queue Stopped"

Hi friends,
My scenario is from Peoplesoft -> XI -> BI
Message has reached BI, but in SXMB_MONI, its showing Message Status as "Scheduled" and Queue Status "Queue Stopped".
How to proceed further ? How can I start that queue ?
Thanks ain advance,
Neena John

Hi Neena,
Go to SXMB_ADM -> Manage Queues -> Register Queues
More on queues
XI : How to Re-Process failed XI Messages Automatically
Run the report RSXMB_REGISTER_QUEUES and register the queues
Run the report RSXMB_RESTART_MESSAGES for restarting ur messages
Refer this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
Regards,
Vinod.

Status of message in case of file-xi-idoc scenario

In file2idoc scenario, i have 500 records, how to check the records reached or not (except SXMB_MONI & IDX5)?

palnati,
RWB run time workbench.
or
http://<yourserver>:<port>/MessagingSystem
Regards
Sreeram.G.Reddy

JMS adapter transaction. Rollback message to queue.

Hi all !
A have question about jms adapter transaction. My composite application has 3 steps : JMS adapter (listener), mediator, WS adapter. JMS adapter listen queue push message to mediator, mediator invoke web service. If ws not available (server down), mediator try recovery 5 times. After 5 times, reject message from queue. I wont rollback message to queue. I saw examples with JMS + BPEL, but it not help me. Anybody can help me.

Hi,
You don’t need to catch a mediator fault – you can let it rollback to the JMS Queue and let the Queue do the retries.
To get the retries working, log in to the weblogic console and navigate to JMS Modules -> Your Module -> Your Queue -> Configuration -> Delivery Failure
Here you will find options for Redelivery Limit. Set this to the number of retries you need.
Then navigate to the connection factory you want and set the redelivery delay.
This should get your desired behaviour, but once the message has failed it will be discarded. If you prefer to put it on an error queue you can create an error queue, and in the original queue’s, goto Delivery Failure, change the expireation policy and set the Error Destination to be your error queue.
Hope that helps!
Robert

Redelivery of messages to JMS queue

Hi,
          I am using weblogic 9.2 JMS and MDB for processing messages from queue. Only one instance of Container Managed MDB is running and the important point is that queue sequence should be maintained. I have a problem now. Each message will be picked by MDB and does some db lookups and it is sent over to another system. If there is any communication failure, the message has to be redelivered back to the front of the queue so that sequence is not lost. Even the same message is failing for more than one time, it should still be placed at the front of the queue becoz there is another mechanism that will pause the queue in case of communication exception.
          I tried with throwing Runtime exception but it is crashing the MDB and is getting deployed again which I think is not the right approach.
          I had set the transaction attribute as Required and tried to do setRollBackOnly on that for any exceptions but the message is not in the front of the queue. It is going to the back or somewhere in the queue.
          I also tried to put the message back with higher priority but did not seem to work.
          I have the redelivery delay as 0, I am not sure if I am missing any configuration settings. Pls let me know if there is a way to redeliver the message to the front of the queue for any exceptions in the message procesing by MDB.
          Thanks
          Srini

Srini,
          WebLogic JMS' Unit-of-Order (UOO) feature was very specifically designed to handle strictly ordered message processing. The feature ensures that messages with the same UOO name are processed strictly in order - regardless of the number of concurrent consumers, redelivery delays, rollbacks, etc.
          If the entire queue is to be processed single threaded, you can very simply configure a default UOO for the queue, otherwise there are a variety of other UOO options. A good place to start is the JMS developer guide's UOO chapter.
          And yes, "setRollbackOnly" is the best way to force a rollback of an MDB CMT.
          Tom

Case study: "Large?" labview programs flooded with different VIT's

Case study: "Large?" labview programs flooded
with different VIT's
Type of application:
Computer with loads of individual hardware connected or other software (either
onsite (different buses) or offsite (Satelite/GSM/GPRS/radio etc.).
Hardware
description: little data "RPM" but communications to all devices are intact.
More "RPM" when many VITs are involved.
Size: 1000+
VITS in memory (goal). Total software has been tested and simulated with 400.
I'm posting
this post after reading this thread (and actually I cant sleep and am bored as
hell).
Note: I do
not use LVOOP (but sure post OOP examples, am starting to learn more and more
by the day.)
Things I
will discuss are:
Case 1: Memory usage using a plugin
architecture
CASE 2: memory usage using VITs (!)
CASE 3: updating datastructures:
CASE 4: shutdown of the whole system
CASE 5: stability & heath monitoring
CASE 6: Inifiles
CASE 7: When the hardware is getting crappy
Total
application overview:
We have a
main application. This main application is mainly empty as hell, and only holds
a plugin functionality (to register and administer plugins) and holds an
architecture that holds the following items:
Queue state
machine for main application error handling
Queue state
machine for status messages
Queue state
machine for updating virtual variables
Event state
machine for GUI
Some other
stuff
Other
global functionality is:
User
logins, user configurations and unique access levels
Different
nice tools like the good old BootP and other juicy stuff
Supervision
of variables (like the NI tag engine, but here we have our own datastructures)
Generation
of virtual variables (so that the user can configure easy mathematical
functions and combining existing tags)
Licensing
of plugins (hell we free-lance programmers need some money to don't we?)
Handles
all communication between plugins themselves, or directly to a plugin or vice
versus.
And now we don't
talk about that (or marketing) the main application .
Message Edited by Corny on 01-20-2010 08:52 AM

CASE 3: updating datastructures:
As we do NOT use clusters here (that would
just be consuming) we only use an 1D array of data that needs to be updated in
different functional globals. If the the number of VITS exceeds so that the
updating of this datastructures becomes the bottleneck, this would cause
delays. And since in this example we use 250 serial interfaces (lol) we do not
want to disrupt that by any delays. When this happends, does anyone know a good
solution to transfer data?
A thought:
perhaps sending it down to the plugin and let the plugin handle it, this should
save some time, but then again if more VITs are added again this would become a
bottleneck and the queue would fill up after a while unable to process it fast
enough. Any opinions?
CASE 4: shutdown of the whole system
Lets say we
want to close it all down, but the VITs need perhaps to do some shutdown
procedure towards the hardware, that can be heavy.
If we ask
them to shutdown all together we can use an natofier or userevent to do this
job. Well, what happends next is that the CPU will jump to the roof, and well
that can only cause dataloss and trouble. The solution here was to let the
plugin shut them all down one by one, when one has been shutdown, begin at the
next. Pro; CPU will not jump to the moon. Con's: shutdown is going to take a
while. Be ready with a cup of coffee.
Also we
want the main application not to exit before we exit. The solution above solved
this as the plugin knows when all have been shut down, and can then shut itself
down. When all plugins are shutdown - the application ends.
Another
solution is to use rendovous (arg cant spell it) and only shut the system down
when all rendezvous have met.
CASE 5: stability & heath monitoring
This IS
using a lot of memory. How to get it down. And has anyone experienced any
difficulties with labview using A LOT of memory? I want to know if something
gets corrupt. The VITs send out error information in case, but what if
something weird happens, how can I surveillance all the VIT's in memory to know
one is malfunctioning in an effective way/code (as backup
solution so the application knows
something is wrong?
CASE 6: Inifiles
Well, we
all like them. Even if XML is perhaps more fahionally. Now Ive runned some
tests on large inifiles. And the labview Inifile functions use ages to parsing
all this information. Perhaps an own file structure in binary format or
something would be better? (and rather create an configuration program)?
CASE 7: When the hardware is getting crappy:
Now what if
the system is hitting the limit and gradually exceeds the hardware req. of the
software. What to do then (thinking mostly of memory usage)? Needing to install
it on more servers or something and splitting configurations? Is that the best
way to solve this? Any opinions?
Wow. Time for a coffee cup. Impressive if someone
actually read all of this. My goal is to reach the 1000 VIT mark.. someday.. so
any opinions, and just ask if something unclear or other stuff, Im open for all
stuff, since I see the software will hit a memory barrier someday if I want to
reach that 1000 mark hehe

EOIO Queues - Sysfail..

Hi,
I am getting messages from SRM to Int Server of XI directly using SAP Delivered BADI and in the BADI serialization is set so those Messages goes in to EOIO Queues.
Now all the Messages are stuck in different EOIO queues with Sysfail status of Queues Now so far there is two types of Sysfail errors:
1. XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION
(Only one message in this status though I have tested the configuration In XI IR and works successfully)
2. An exception occurred that was not caught (All toghather 5 messages)
Any suggestion what can be the Case?
Thanks,

Hi,
I have recreated all the config objects again so it solved the first problem but the second problem is still there and the queues are still getting stuck saying
An exception occurred that was not caught.
and when I click the queue it opens the ABAP code for function module SXMS_ASYNC_EXEC
Detailed analysis in SXMB_MONI:
the message processing is stuck at "Message Branch According to Receiver List" step. Also in the trace of the same step I can see following:
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Root-Exception from packaging: An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause</Trace>
<Trace level="1" type="T">Continue single processing</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
Any help resolving this will be appreciated.
Thanks.
-Adrean.
Message was edited by:
Adrean Hart

Rollback of Messages in OSB

I have a usecase as below -
jms.Q1 (nonxa) -- [ proxy service -- publish to a jms.Q2 (xa) -- raise an error ]
A proxy service receives request from non-xa queue (Q1) ,
then the proxy service publish that message to another queue (Q2) via XA enabled business service (i use connection factory as XA) ,
then i raise an error in the message flow.
What i need is, I want to rollback the message which i published to "Q2" once i raise an error in message flow.
Can anyone please help me out whether this is possible by using any of the routing option,etc..?
Regards
Sesha

Configure these:
1. Enable the option Same Transaction For Response in the Proxy Service configuration.
2. Use QoS as Exactly Once in the publish action which calls the JMS business service.
3. Use XA connection factory for connection between businsss service and target JMS Queue
4. Make sure that the error reaches System Error Handler. To ensure this you need to make sure that the flow does not encounter any Reply action after the Raise Error action you have configured in the message flow.
Once you configure like above:
1. Message will be deleted from source queue as soon as OSB Proxy picks up the message (since this is not XA enabled)
2. Message will be published to target JMS queue but not committed till the message flow is completed. So it can rollback in case there is an error after the publish action.
3. If based on a condition a Raise error action is executed (or any other error happens in the flow) message will be rolled back from target queue in case the error reaches the System Level error handler. So message will not be present in neither source queue nor the target queue.

Rollback after DB polling

Hi all,
I am using DB adapter to poll records from a table(changing a status flag to processed when the records are read) then write these records to a file, all is running fine but I need to handle rollback if any error occurs ,this means that I want the old status in the status flag instead of the current status(processed).
I already used rollback before and it works fine but I can't seem to rollback after polling, any ideas??

Hi,
To implement rollback scenario in BPEL, you need to use compensate activity and compensation Handler in your process.
Basically in compensate we define the scope which we want to compensate, and in compensation Handler we define the logic i.e in your case we will write the update statement in compensation Handler.
Hope I have answered to your doubt.
Cheers,
Abhi...

SMWMQUEUES - what does status "ready" mean

SMWMQUEUES lists all outbound queues by name in CRM. All my queues are in status NOSEND . They currently can not conntrans so I am wondering if this is some indication that their site is not correctly identified. Does anyone know why all the othere queues are in status NOSEND and this one is READY ?
Many thanks MM

Please have a look at the note below and reward points if it helps
Basically, if the initial load is not successful, you should analyze queues and restart them if required. It makes sense to restart the initial load of an individual object if the analysis did not result in problems. Always log on to the CRM/EBP server in English to see the error texts. For notes on the delta data supply from the R/3 Backend system into the CRM server and the other way round, see the attached notes.
Error Detection - Tool Monitoring in the Middleware Menu:
a) Transaction R3AM1: Initial load monitor: After a successful initial load, all traffic lights should be "green".
b) Transaction SMWP: 'Middleware Portal':Under 'Runtime Information' -> 'Adapter Status Information' -> 'Initial Load Status', you can investigate the inbound and outbound queues and branch to the qRFC transactions from there. Below, the error analyses with access via the CRM Middleware Portal are described.
c) Transaction SMW01: Analysis of errors in the BDoc flow, in particular CRM/EBP application Customizing errors during the initial load into the CRM Server.
d) Transaction SMWT: Middleware trace with trace environment 'I':Display of additional information for each data block transferred.
Analysis
1. Ensure that the highest available plug-in (PI) Support Package plus Core Support Package is installed in the R/3 back-end system. The same applies to the CRM/EBP Server.
2. Transaction SM30:In the R/3 Back-end System, the correct RFC destination must be entered in table CRMRFCPAR for CONSUMER CRM. For this, see the documentation on the CRM Adapter Framework.
3. Transaction SM59:Test RFC connection - 'Remote login' from CRM/EBP to R/3 Back end and vice versa.
4. Transaction SMOEAC (Administration Console): Check the sites for R/3 systems. Have the RFC destinations been entered correctly and do the additional attributes exist? For this, see the documentation on the CRM Adapter Framework.
5. Transaction SMWP:Menu item 'Runtime information' -> 'Adapter Status Information' -> 'Initial Load Status':The subitems for the monitoring of the different inbound and outbound queues must each be evaluated in a similar way:
Double-click a queue entry to display the status of a queue (for example, READY, RUNNING, SYSFAIL). If you double-click again, you can see the cause of the error from the status text in the case of an error (SYSFAIL). Note: In case of temporary errors, it often helps to restart the queue (F6).
In general, a short dump occurs for status SYSFAIL. For the outbound queues, this short dump exists in the target system and not in the system in which the queue is. For inbound queues, the short dump exists in the same system as the inbound queue. For the initial data transfer between CRM and CDB or CRM and XML/ALE sites, the source and the target system are the same.
a) Menu option 'Load from OLTP systems:Start outbound queues in the CRM server':Status SYSFAIL in these outbound queues displays that a program termination occurred during the selection or the sending of data from an R/3 source system.If the program termination occurs in programs SAPLCRM0, SAPLCXML, SAPLCXMP, SAPLCTRK, SAPLCRMD, SAPLCGEN, SAPLCGNR, SAPLCFIL, SAPLCRMR, SAPLCRMS, SAPLCRMC and if you cannot solve the problem with the help of this note, send a customer message to component CRM-MW-ADP.In all other cases, choose the corresponding application component.
b) Menu item 'Load from CRM: Start outbound queues in the CRM server': Status SYSFAIL displays that a program termination occurred during the selection of data from the CRM for the CDB or a different site (for example, XML). Apart from that, the same applies as under the previous point.
c) Menu item 'Outbound queues in OLTP-R/3 System(s)':In general, these queues are only temporary because they are converted into inbound queues on the CRM Server. Consequently, they only exist if network errors, incorrect RFC connection parameters or database problems occur on the CRM server. If a restart of the queue is not successful, a short dump has occurred on the receiving side, the cause of which you must first correct. If the status of the queue is 'NOSENDS', the sending of data was blocked by mistake. This should never be set during live operation. To solve the problem, ensure that the HOLD_DATA field is initial in the CRMRFCPAR table. You can use Transaction SM30 to check or change this. In this transaction, it is the entry for the 'Save data' text. You must trigger existing queues with the status 'NOSENDS' manually. Afterwards, the processing of the outbound queue will occur automatically again.
d) Menu item 'Inbound queues on CRM server': In these queues, you find the data from the initial data transfer from an R/3 System. A SYSFAIL is by far the most frequent item in these queues. The reasons for this can be manifold. Program terminations in the CRM application due to missing or incorrect Customizing are the most frequent reason. To see detailed information on the errors which occurred, call Transaction SMW01 for the corresponding BDoc type. This is also required if there is no queue with errors that you can use to determine and analyze errors in any type of data transport. Short dumps may also occur due to real program errors. In this case, there is a corresponding short dump on the same system. If the error occurs in the SAPLSMOUTIL, SAPLSMO0 or SAPLSMOXML programs and if you cannot correct the error yourself, create a message for component CRM-MW-ADP. In all other cases, create a message for the corresponding component.
A possible error text in the inbound queue is "Error in Mapping (Details: Transaction SMW01)" (SMOF078). To correct this error, proceed as follows: Analyze and correct the error which is displayed in Transaction SMW01 at the error segments. You can find the correct BDoc message with the aid of the date and the time of the entry in the queue as well as with the BDoc status which is 'F05'. After you have corrected this problem, restart the inbound queue in order to process the entry. You can request help for correcting the error displayed in Transaction SMW01 in the corresponding application component.
e) Menu item 'Inbound queue on CRM server from CRM': These queues contain the data from the initial data transfer from the CRM Server to the CDB or other linked sites (for example, XML). For the error analysis, the same applies as for the previous menu item.
6. Logical system maintained in the CRM/EBP Server and in the R/3 Back end?
7. Transaction SMW01: Incorrect settings in the CRM/EBP application.In the selection screen, restrict the relevant period and, if required, the BDoc type.In the result of the selection, select the incorrect message and choose 'Display errors/error segments'.Here, you find notes on CRM/EBP application Customizing problems.
8. Transaction ST22: Short dumps on OLTP CRM/EBP Server
9. Transaction SE80:Syntax check for generated functions in development class $SAP_MSAGEN, for example function group /1CRMG0/PRDCT_OBJECT for product master. If a function group has syntax errors, it is often useful to regenerate it by using Transaction SMOGGEN.
Typical error messages and their solution:
Error 1654, for example for table space PSAPBTABI: Solution: add SAPDBA to the table space.
Timeout in R/3 back-end system during the initial download: Solution:See Note 162956
General performance problems during the initial download:See Note 350176
Inbound queue (SMQ2) on the CRM/EBP Server has status 'READY', but it is not processed. Solution:Restart the queue and check the registration of R3A, CRI in Transaction SMQR
The outbound queue in the R/3 Back-end System has status 'SYSFAIL', the detailed message is: Solution:shut down the CRM/EBP Server and restart it.If other SYSFAIL messages occur, restart the queue and analyze the short dumps.
RSQL error 13 when accessing table SMOTCURR:you should convert the data exchange between the R/3 Back end and the CRM Server to the XML format (see Note 333008).Then delete the inbound queue (in SMQ2, for example, R3AI_DNL_CUST_CURREN) and restart the object.
The number of data records between an R/3 Back-end table or a CRM table and the corresponding CRM CDB table do not match. Solution:Check the following:
Was the initial load completed successfully?
Are filters set for the object?
Note:Filters that are defined in the CRM Server must be defined in the form in which the data is stored in the source system in the database. For example, the filter for date 20010215 corresponds to a filter for February 15, 2001 (format YYYYMMDD).Make sure that the filter criteria are entered with leading digits, for example 10-digit customer numbers, 18-digit material numbers with leading zeros.
Are there error messages in Transaction SMW01 indicating rejections by the CRM server application?
Is the table a child table and are the excessive records orphaned child records that are not selected as well?
Should this delta data only be in the Customizing tables after the compare?
After you start the initial load using Transaction R3AS, the started object remains in status WAIT in Transaction R3AM1, and the initial download is not started. This is not an error.
The following causes are possible:
Too many objects already have status RUNNING or too many requests have been started or too many DIMa instances have been started and not completed. The number of running initial loads plus the number of running requests is the total number of all running initial-like processes. Therefore, this object must wait for the initial load or request of a different object to be completed. After an object is completed, a different object in status 'WAIT' is started automatically. If the initial load/request of the other objects is not completed, you can use this note to analyze why these are not completed and trigger their processing. You can change the maximum number of parallel initial loads using the MAX_PARALLEL_PROCESSES parameter in the SMOFPARSFA table. The standard value in the 'Param. Value' field is 5.
The object has a parent object whose initial load was not completed successfully. You can see from flag 'P' in Transaction R3AM1 whether an object has a parent object. You can see from table SMOFOBJPAR which objects these are.
No entry exists in one of the queues, but the status in R3AM1 remains 'Running':
This is probably because after the data selection in the source system, no reply was sent to the CRM system. If this is the case for one adapter object but not for others, contact the respective application component, which can analyze why the source system does not send a reply and correct the problem.
If this system response occurs for all adapter objects, create a message for component CRM-MW-ADP.
During the start of the initial load, the system displays the message "No initial load if COMPARE is active" or "No Initial Load if data distribution is active. Use Synchron. Load" (SMOF162):
In this case, start a synchronization load for the respective Adapter Object.

How to Get One MQ Message at a time from MQ Queue

Hi,
Before posting my query here is the configuration I am using:_
Weblogic Server 10.3.3
Soa Server 11.1.1.3.0
Oracle JDeveloper 11.1.1.3.0
Till now I have done the following things:_
1) created an MQ Queue
2) Producing MQ Messages in the Queue with the help of an Asynchronous BPEL process.
I can see the message put in the Queue:
What is my requirement?_
1) I want to read (Get) only one of the above created MQ Messages in the main BPEL process(Synchronous), then needs to process it
And based on my Business condition I have to write that message in the Database.
After successful completion of this instance only my main process should go to consume the next message in the MQ queue.
What is the problem I am facing?_
1) The main BPEL process is not reading one message at a time. I.e. if there are 10 messages in the queue, then as soon as the main bpel process gets deployed, 10 instances created automatically, all in running status and Queue gets empty
2) And if I explicitly test the process, the processes always go in running mode. I.e. Waiting for the messages at the receive activity (this receive is attached to the MQ adapter through operation Get in the main BPEl process)
I just want to know how I can read the MQ messages one by one, though there may be n number of messages in the MQ queue
And only after the completion of the first instance (of Reading First MQ message from queue) it would go to initiate the next instance and so on
Would anyone please help me in this issue?
Thanks
Sunil

Is the MQ Queue local or remote?

Status of queue in case of rollback

Similar Messages

Maybe you are looking for