Post migration script gets stopped - Showing status as 'in-progress' (V12)

SUGGESTED

Hi,

We are doing sage x3 migration from V7 to V12. We have successfully imported and validated the folder in to V12 before validation we truncate the APLLCK table. Then created the Plan from sequencing monitor to launch the script, the plan goes smoothly till the code “UUMGTRTPURO6” and after that it stopped working and displayed all the codes in pending status. Also, even after re-launching the same, the plan is not proceed further and we suspended that plan and created new one. But in the new plan the module which are already succeeded in previous plan are completed with error and some of the module like “Normal Order His.”, “Purchase Request” and “Normal Order” are still showing in process status even though the record of those module/screen is already been fetched in tables in previous plan and now the script is got stuck and not going further.

Kindly suggest what we can do further. We have also validate the folder second time.

  • 0

    Hi @,

    Thanks for reaching out. Did you ever find a resolution to this issue? If you are still looking for guidance, please let us know and we can try to point you in the right direction or suggest some resources or next steps.

    Warm Regards,
    Erzsi

     

  • 0
    SUGGESTED

    Hello,

    First time round, did “UUMGTRTPURO6” complete or was it at "in progress" status ?   There are some cases whereby certain processes can take a LONG time to complete (measured in days rather than hours), albeit only for large data sets (contact Sage Support if this is happening, as the workaround needs a change to UTIMAJMAXUPDTRS.adx)

    I am not sure creating a new plan is a good recovery strategy, it is better to identify the root cause and fix it before then restarting the processing where it left off (with the same plan)    In this case I would have to say restoring the folder data and re-running from scratch is the best option (once you understand root cause)

    If you need further help identifying root cause, may be best to talk to Sage Support as probably need to look at log files and data in the migration tables to understand the issue further

    regards

    Mike