Page tree
Skip to end of metadata
Go to start of metadata

Always verify the most up-to-date procedures by checking the SUM guide. Always have it on hand while performing the upgrade.


This page provides symptoms and solutions during SPS updates/EHP installations/Release upgrade using Software Update manager (SUM) in the  phase MAIN_INIT/REPACHK_CLONE or MAIN_INIT/REPACHK_TRANS



This step is relevant if you perform an enhancement package installation or an SPS update.
If you have chosen preconfiguration mode standard or advanced, the Software Update Manager asked you in this phase to confirm the locking of the ABAP Workbench on all SAP instances. In contrast to the release upgrade, the Software Update Manager requires the lock in this phase only.
This lock prevents development objects (for example, ABAP reports, table definitions, and so on) from being changed during the update since these modifications would be lost.
You can continue to use your SAP system in production operation, even if you confirm that the ABAP Workbench can be locked. However, after you have confirmed the ABAP Workbench lock, no more transports can be made into or out of the SAP system. Some further actions might be blocked that either check for this lock as well or for the running update. This is especially known in the area of Business Intelligence and SAP Solution Manager.
This phase displays all the repairs that are still in open transport requests. They are also written to the REPACHK2.LOG file.
Release these transport requests so that you can continue; otherwise, the objects contained in these repairs are locked.Note
SUM checks in this phase also for inactive development objects.


During this check, it can occur that SUM reports inactive objects, which cannot be found in the SAP system. For information about removing these inconsistencies, see SAP Note 538167.




Troubleshooting tips



Symptoms and solutions

SUM displayed error or Error in log file
Log file
Last error code * is: RFC error system SID nr 00 function

Time limit exceeded

1EETQ203 Upgrade phase "REPACHK_CLONE" aborted with errors

<update directory>/log/


Increase the parameter value rdisp/max_wprun_time on all servers in transaction RZ11  (e.g. to 3600) , it is dynamically switchable, not server restart is needed.Repeat the SUM phase afterwards.

Inactive objects found.

Error sample:

4 ETG010 "612 inactive objects found" " " " " " "
4 ETG010 "329 inactive SAP objects" "colliding with 
import queue
4 ETG010 "Please contact the development team" "to either activate or
discard the inactive object." " " " "
2EETG010 "The following objects are inactive" 
"in the system:"

<update directory>/log/

  1. Go to transaction SE80, in the leftside menu, select "Repository Browser"(which is selected by default) and then select "Inactive Objects", input "*" in the next line to search all users, click the Display(eyeglass) button. All inactive objects in the system will be displayed in the list.
  2. Find out the objects in the upgrade error, then double click to check the Attributes tab. If you cannot see the inactive information, click "Active <-> Inactive"(Shift+F8) button to display the inactive version. You should be able to see who and when changed this object.
  3. You can either now activates this inactive version, or use option 'Utilities -> Versions -> Return to active version' for removing the inactive version.
    REMARK! Usually we would not recommend to change the SAP standard definition of the SAP objects, but the decision is on your side based on what was the changed for.
  4. Find out the transport request via version management containing the object. Check, if the tr.request contains SAP notes. If yes, execute report SCWB_NOTE_ACTIVATE for all involved SAP notes.

REMARK! If you cannot find the inactive object listed in the log, please follow the SAP note 538167.

Locked SAP objects have been found in open repairs, corrections,
or transport orders. If these orders are not released, you will not be
able to adjust these objects if necessary.The development environment
has been unlocked now. Release the repairs and transport

orders to ensure that you can adjust the contained objects, if necessary.

Sample log:
Transport Request|User |Date |Repair |User |Date
K01K900002 |SOLMAN_ADMIN|20150423|K01K900003|SOLMAN_ADMIN|20150423

<update directory>/log/

Go to transaction SE01 and release the mentioned Transport Requests.

After all these, you can repeat SUM phase and it will check whether any inactive objects or Open repairs left. If nothing found, it will move on.

For BW and after phase REPACHK_CLONE:

  • You cannot load data during the BW system upgrade before the downtime. 
  • When you try to change the filters for the selection of a Infopackage
    to start a load request,the system issues following errors:
    Upgrade running (phase xxx) - you can only make limited changes
    to objects (RSO 861)
    Object xxx cannot be edited during the upgrade (phase xxx) (RSO 862)

transaction RSA1

Follow the SAP KBA  1730554 Infopackage Object cannot be Edited during BW Upgrade

Checks after phase MAIN_INIT/REPACHK_CLONE were negative!

Last error code set: RFC error system SID nr 00 function 'SUBST_GET_OPEN_SAPOBJ_TAS_REPS'
failed with code 3 key RAISE_EXCEPTION: Exception condition &quot;CANNOT_CHECK_LOCKS&quot; raised.

<update directory>/log/
Follow the SAP KBA 1972035 - Upgrade or EHP install breaks down at REPACHK phase with CANNOT_CHECK_LOCKS dump

FAQ (Frequently asked questions) 


Related documents

REPACHK2 phase

Related SAP notes/KBAs

SAP note 538167 - Active objects are displayed as inactive

SAP KBA 1943694 - Perform transport import during pre-processing phase

SAP KBA 2177563 REPACHK_CLONE: Inactive objects and Open repairs found

SAP KBA 1730554 Infopackage Object cannot be Edited during BW Upgrade

SAP KBA 1972035  - Upgrade or EHP install breaks down at REPACHK phase with CANNOT_CHECK_LOCKS dump