SAP Knowledge Base Article - Preview

2438963 - Update stuck in "Started" status at SM13

Symptom

  • In transaction SM13 there are updates with status "Started" for a long time without any progress.

    STARTED.png
    Image 1. Example of transaction SM13 output with status "Started".


  • You see free update (UPD) work process at the server responsible to execute the update (update server).

    UPD_FREE.png
    Image 2. Checking work process table (SM50).

    The update server information could be collected from Update Header, follow steps below:
    1. Select an update entry at SM13;
    2. Open update header by clicking on "Top Hat" icon or press Crtl+Shift+F6;
    3. Check update server name.
  • Transaction SM12 has locks assign to SM13 stuck updates.

Read more...

Environment

  • SAP NetWeaver release independent.

Product

SAP NetWeaver all versions

Keywords

update in started, status, sm12, update locked, lock update, lock, locks, updates, updates stuck, updates lock, locked, started status, status started , KBA , crash , repeat update , v1 , v2 , v1 processed , BC-CST-UP , Update , BC-CST-EQ , Enqueue , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.