Skip to Content
avatar image
Former Member

Solman UPG in the phase TABIM_UPG (hanged)

Hi

I am facing a problem in the upgrading of Sol 3,2 to 4.0 ,in the phase TABIM_UPG ,thr is no related log and in the console monitor

i can see this

running C:\usr\sap\S01\SYS\exe\run\tp.exe pf=c:\usr\sap\put\bin\DEFAULT.TPP checkimpdp S01

running C:\usr\sap\S01\SYS\exe\run\tp.exe pf=c:\usr\sap\put\bin\TABIMUPG.TPP put S01

and in the SLOG700 it contains

Phase TABIM_UPG:

START put S01 20080318173742 s01adm SMTEST 200803181737420000f8

START SET STOPMARK S01 20080318173745 s01adm SMTEST 200803181737420000f8

STOP SET STOPMARK S01 20080318173745 s01adm SMTEST 200803181737420000f8

LIST put S01 ({I|

START tplock_eu S01 ( 20080318173745 s01adm SMTEST 200803181737420000f8

STOP tplock_eu S01 ( 20080318173745 s01adm SMTEST 200803181737420000f8

START locksysX S01 { 20080318173745 s01adm SMTEST 200803181737420000f8

STOP locksysX S01 { 20080318173745 s01adm SMTEST 200803181737420000f8

START MAIN IMPORT S01 I 20080318173745 s01adm SMTEST 200803181737420000f8

WARNING: c:\usr\sap\put\tmp\SAPKK-150GGINSTPL.S01 is already in use (10), I'm waiting 4 sec (20080318174033). My name: pid 248 on SMTEST (s01adm)

WARNING: c:\usr\sap\put\tmp\SAPKK-150GGINSTPL.S01 is already in use (20), I'm waiting 1 sec (20080318174057). My name: pid 248 on SMTEST (s01adm)

WARNING: c:\usr\sap\put\tmp\SAPKK-150GGINSTPL.S01 is already in use (30), I'm waiting 4 sec (20080318174122). My name: pid 248 on SMTEST (s01adm)

WARNING: c:\usr\sap\put\tmp\SAPKK-150GGINSTPL.S01 is already in use (40), I'm waiting 2 sec (20080318174153). My name: pid 248 on SMTEST (s01adm)

WARNING: c:\usr\sap\put\tmp\SAPKK-150GGINSTPL.S01 is already in use (50), I'm waiting 2 sec (20080318174228). My name: pid 248 on SMTEST (s01adm)

i guess tp is hanged some where please help me ASAP

Rgds

George

Edited by: George Varghese on Mar 18, 2008 1:48 PM

Edited by: George Varghese on Mar 18, 2008 1:49 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 19, 2008 at 09:00 AM

    still i'm facing the same problem ,even i upgraded the kernal

    thnk&regards

    George

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      George, Did you try renaming the tmp directory in DIR_PUT ?

      Then create a new directory with name tmp. Try this once and repeat the phase....Before renaming it stop the upgrade, kill the tp and R3trans processes.

      Hope this works...

      Regards,

      Suhas

  • Mar 18, 2008 at 11:57 PM

    cancel all TP and R3trans file, then, try again.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      George,

      I just referred my notes from one of the upgrades where i faced this problem. What happens is during the upgrade or also while transports when such error comes you need to stop the upgrade or transport, copy the SLOG*.SID file to the log directory in DIR_PUT and delete the file from tmp directory.

      Then kill all the processes for tp and R3trans whcih currently executing.

      Once you have done that then start SAP Upgrade again and then monitor.

      The reason is explained in the following SAPNote 12746 - WARN <file> is already in use (), I'm waiting 5 sec.

      I hope this should resolve your issue.

      Regards,

      Suhas

  • avatar image
    Former Member
    Mar 19, 2008 at 09:51 AM

    thanks I guess this solved my problem and I analysed that the tp and r3trans are processing in the backlground and also the the size of the temp directory is increasing ,could please tell me how long will take for this particular phase and rest of the process

    thanks alot

    Regards

    George

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      Great, even i was relieved to hear that this solved your problem as it had worked fine for me.

      Anyways well we cant say how much exact time it would take because it depends on the support packages that are to be applied on the target system. And of which some of the support packages are already applied before you came across this problem.

      Regards,

      Suhas