Inbound Worklist stuck in Waiting status

July 12, 2009 at 2:15 am

[] [] [] [] [] [] [] [] [] [] [] [] [] []

  1. Performance improvement for ‘Add’ Action in SynchronizationSymptom Middleware is taking a long time to send records for Add action during synchronization for any smartsync application. Other terms Smart Sync, Delta, Synchronization, Middleware, Application, Performance, Time, Data, Iteration, SyncBO,...
  2. Mobile component(s) getting deleted from Admin UISymptom Wrong mobile component(s) is getting deleted while unassigning device configuration. Context for a problem: - Device Configuration DC1 with a Mobile Component app1 - Device Configuration DC2 with a Mobile Component...
  3. Number field value of SyncBO is changed in middlewareSymptom If any record is created or changed from client, number field value of that SyncBO is getting changed by middleware before calling bapi wrapper. Other terms Display, User, Synchronization, Records, Deletion,...

Symptom

Inbound SyncBO’s continue to get ‘hung’ in ‘W’ on the MI server in
merep_mon. The only way to get them moving again is by selecting the
SyncBO stuck in ‘W’ status and click ‘trigger handler’ icon.
Other terms

MEREP_DISTRIBUTOR, Inbound, waiting, Worklist, MI 2.5, MI 7.0, MI 7.01,
Inbound Worklist, SyncBo, Synchronization, MEREP_RETRY_BP.
Reason and Prerequisites

Tho inbound worklist going to waiting status during synchronization is due to MEREP_DISTRIBUTOR job run at the same time
You are currently using SP20 or above for WebAS 6.40
Or
You are currently using SPS12 or above for WebAS 7.0
Or
You are currently using SPS01 or above for WebAS 7.01
Solution

For WebAS 6.40:
- Apply Support Package 25
or
- Apply this note via Note Assistant(SNOTE) if you are on SP20 to SP24.
For WebAS 7.0:
- Apply Support Package 20
or
- Apply this note via Note Assistant(SNOTE) if you are on SPS12 to SPS19
For WebAS 7.01:
- Apply Support Package 05

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment