upgrade is running! no import possible

[Former Member]

Hello All,

During Upgrade ECC5 to ECC6 EHP6 in PRD system, we are getting  "upgrade is running! no import possible" while trying to import a TR in PRD system due to some urgent requirement. In upgrade Preprocessing step completed, still didnot move to "Execution" Phase. In this time tried to unlock the system and import the TR.

we follow 1901463 - How to unlock the SAP system to perform correction(s) during an upgrade. to unlock the system.

• Original SAP system
  cd \<update directory>\abap\exe
  tp unlocksys <SAPSID> pf=..\var\DEFAULT.TPP
  tp unlock_eu <SAPSID> pf=..\var\DEFAULT.TPP

Please help. Thanks in advance.

[former_member264034 · Accepted solution]

Hello,

Transports can be performed at any point up to the REPACHK(2) phase, unless the repository has bee locked manually before then(in phase LOCKEU_PRE).
Before the repository is locked changes can safely be applied to the system.
If you make changes to the system after the repository lock you risk the whole upgrade.
The system will be inconsistent as this new data is not taken into consideration if manually imported while the system is locked.
If you would execute the tp UNLOCK_EU manually between REPACHK2 and MODPROF_TRANS(begin of downtime) the upgrade might get into trouble. If DDIC is imported or changed after the phase REPACHK2, the upgrade might fail, since the DDIC preparations on the shadow system may compute things wrong.

http://wiki.scn.sap.com/wiki/display/ERP6/How+to+handle+Transports+during+Upgrade+or+EHP+installatio...

Regards,
Aidan

[Former Member]

Thanks Aidan  . You are correct.

We got reply from SAP Like below.

Transport should be freeze after the REPACHK_CLONE phase. That is the reason, you encounter the error message: "system in upgrade, no import possible".

There will be inconsistent as new data is not taken into consideration. Changes to the repository will not be taken into account if imported after the REPACHK_CLONE phase and the upgrade will probably fail due to inconsistencies.

We did not move the TR.

Regards,

Rahul