Skip to Content

DEVICE data load terminating in background (EMIGALL)

Hello Conversion experts,

I come up with an exceptional issue which I never faced before.

While migrating DEVICE data through distributive import run in EMIGALL it terminates in the background after sometime. We have checked the active processes in SM66 and lock entries too and found some dialog WP on "Hold" status with RFC responses as description.

Lock entries also getting created on EQUI table, but we are not able to figure out the reason behind the termination happening in background.

Could anyone help us on this.

More details:

data count : 1,200,000 approx

File size: 6000 (data objects)

4 App Servers : using 8-10 WP out of 40 Background WP initially then increase accordingly.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Aug 01, 2016 at 07:33 AM

    Hi Davinder,

    Can you please share the ST22 Screenshot .

    Also just check in the system in which you are loading the data , if someone has reset the number range for Equipment No, resulting in Duplicate equipment no and thereby terminating the background job.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 16, 2016 at 01:39 PM

    Hi Chandandeep,

    Yes, it happens only with DEVICE and even BASIS has no clue yet.

    So right now load happens in 4-5 restart iterations after termination in background.

    We usually wait for all child jobs to complete ( in SM66) and then clear the lock entries (on EQUI) and restart the job with different split file names or by deleting the split files from AL11.

    Important things:

    1. Update work processes are getting fully utilized and ends up with "ON HOLD".

    2. RFC calls are being made through dialog work processes parallel to data load on background WP.



    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.