Upgrade Solution Manager 7.0 to 7.1

[Former Member]

Hello, TechSupport!

I am upgrading SAP Solution Manager from 7.0 up to 7.1. Phase MAIN_SHDRUN/ACT_UPG is running for 7 days.

It is ok ? How can I find that SUM is hungs up or upgrade is running good ?

TP is running:

There is no running jobs in SM37

Phasexe.trc:

20131231104800:PHASEXE:0:WARNING: Unused exec status 4 for phase 'MAIN_SHDRUN/JOB_RBCA_FSP_UPG_WRITE' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/RUN_RSINCGEN_SHD1' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SETSYNC_SHD_STARTED' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/RFCDEST_CREATE_S2O' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_DIFFEXP/DIFFEXPDDIC_IP' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_SHDPREPEXP/ADDTOHEAP_SFW' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_DIFFEXP/RUN_RDDIT006' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_DIFFEXP/DIFFEXP_TMPSAP' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/RUNASYN_RSGENLOAD' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 4 for phase 'MAIN_SHDRUN/SUBMOD_DIFFEXP/JOB_SRM_PRE_CHECKS_2' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 4 for phase 'MAIN_SHDRUN/RUN_RUTPREDEPVIEWS4DEL' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/BUFFEROP_ACTUPG' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_SHDPREPEXP/JOB_DL4TA_UPG' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_DIFFEXP/JOB_RDDSAVTE' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/DDIC_UPG' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/SUBMOD_DIFFEXP/SQLDB_WCONT2UPP1' - ignored!

20131231104800:PHASEXE:0:WARNING: Unused exec status 2 for phase 'MAIN_SHDRUN/START_SHDI_FIRST' - ignored!

ALOG702:

### Phase MAIN_SHDRUN/SUBMOD_SHDPREPEXP/NTACT_DELPRE:

ALL                  SM1.ALL \ 0000 20131226201131              sm1adm       sap_server 20131226201112004e38

ALL                  SM1.ALL \ 0000 20131226201140              sm1adm       sap_server 20131226201112005d18

ALL                  SM1.ALL \ 0000 20131226201146              sm1adm       sap_server 201312262011120058fc

ALL                  SM1.ALL \ 0000 20131226201147              sm1adm       sap_server 201312262011120059d0

ALL                  SM1.ALL \ 0000 20131226201148              sm1adm       sap_server 20131226201112005b60

ALL                  SM1.ALL \ 0000 20131226201211              sm1adm       sap_server 20131226201112005cb0

ALL                  SM1.ALL \ 0000 20131226201234              sm1adm       sap_server 20131226201112005a44

ALL                  SM1.ALL \ 0000 20131226201255              sm1adm       sap_server 2013122620111200588c

### Phase MAIN_SHDRUN/SUBMOD_SHDPREPEXP/JOB_SFW_UPG:

### Phase MAIN_SHDRUN/SUBMOD_SHDPREPEXP/ADDTOHEAP_SFW:

### Phase MAIN_SHDRUN/JOB_UMOD20_UPG:

### Phase MAIN_SHDRUN/RUN_RADTBUCACT:

### Phase MAIN_SHDRUN/RUN_RUTPREDEPVIEWS4DEL:

### Phase MAIN_SHDRUN/DB6_ACTIONS:

### Phase MAIN_SHDRUN/BUFFEROP_ACTUPG:

### Phase MAIN_SHDRUN/SQLDB_SET_TIMESTAMP_E070SHD:

### Phase MAIN_SHDRUN/ACT_UPG:

ALL                  SM1.ALL a 0000 20131226201441              sm1adm       sap_server 20131226201441005cc8

ALL                  SM1.ALL ( 0000 20131226201441              sm1adm       sap_server 20131226201441005cc8

ALL                  SM1.ALL ) 0000 20131231104735              sm1adm       sap_server 201312311047340044e4

ALL                  SM1.ALL ( 0000 20131231104759              sm1adm       sap_server 20131231104758005dd0

### Phase MAIN_SHDRUN/ACT_UPG:

ALL                  SM1.ALL d 0000 20131231104803              sm1adm       sap_server 20131231104803005b40

ALL                  SM1.ALL a 0000 20131231104804              sm1adm       sap_server 201312311048030058b8

ALL                  SM1.ALL ( 0000 20131231104804              sm1adm       sap_server 201312311048030058b8

SAPup.ECO:

### Phase MAIN_SHDRUN/ACT_UPG:

SAPup> Starting subprocess in phase 'ACT_UPG' at 20131231104803

    ENV: DBMS_TYPE=ora

    ENV: JAVA_HOME=c:\j2sdk1.4.2_22-x64

    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

    ENV: ORACLE_HOME=D:\oracle\SM1\11203

    ENV: ORACLE_SID=SM1

    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

    ENV: PATH=D:\sum\SUM\abap\exe;D:\oracle\SM1\11203\bin;D:\oracle\SM1\102\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\usr\sap\SM1\SYS\exe\uc\NTAMD64

    ENV: SAPDATA_HOME=D:\oracle\SM1

    ENV: SAPSYSTEMNAME=SM1

    ENV: auth_shadow_upgrade=1

    ENV: dbs_ora_schema=SAPSR3

    ENV: dbs_ora_tnsname=SM1

EXECUTING D:\sum\SUM\abap\exe\tp.EXE  "pf=D:\sum\SUM\abap\var\ACTUPG.TPP" put SM1

This is D:\sum\SUM\abap\exe\tp.EXE version 380.08.41 (release 720, unicode enabled)

Looking for effective putsteps ... ... ready (looking for putsteps)

SLOG702:

### Phase MAIN_SHDRUN/ACT_UPG:

START REMOVE STOPMARK      ALL        20131226201436              sm1adm       sap_server 20131226201436005cdc

STOP  REMOVE STOPMARK      ALL        20131226201436              sm1adm       sap_server 20131226201436005cdc

START REMOVE STOPMARK      SM1        20131226201441              sm1adm       sap_server 20131226201441005c70

STOP  REMOVE STOPMARK      SM1        20131226201441              sm1adm       sap_server 20131226201441005c70

START put                  SM1        20131226201441              sm1adm       sap_server 20131226201441005cc8

START SET STOPMARK         SM1        20131226201441              sm1adm       sap_server 20131226201441005cc8

INFO: Buffer saved as D:\sum\SUM\abap\buffer\SM1SAV.

STOP  SET STOPMARK         SM1        20131226201441              sm1adm       sap_server 20131226201441005cc8

LIST  put                  SM1 (A{|

START tplock_eu            SM1 (      20131226201441              sm1adm       sap_server 20131226201441005cc8

STOP  tplock_eu            SM1 (      20131226201441              sm1adm       sap_server 20131226201441005cc8

START DD ACTIVATION        SM1 A      20131226201442              sm1adm       sap_server 20131226201441005cc8

START tp_getprots          SM1 J      20131226201442              sm1adm       sap_server 20131226201441005cc8

START tpunlock_eu          SM1        20131231104734              sm1adm       sap_server 201312311047340044e4

STOP  tpunlock_eu          SM1        20131231104735              sm1adm       sap_server 201312311047340044e4

START tplock_eu            SM1        20131231104758              sm1adm       sap_server 20131231104758005dd0

STOP  tplock_eu            SM1        20131231104759              sm1adm       sap_server 20131231104758005dd0

### Phase MAIN_SHDRUN/ACT_UPG:

START REMOVE STOPMARK      SM1        20131231104803              sm1adm       sap_server 20131231104803005b40

STOP  REMOVE STOPMARK      SM1        20131231104803              sm1adm       sap_server 20131231104803005b40

START put                  SM1        20131231104803              sm1adm       sap_server 201312311048030058b8

START SET STOPMARK         SM1        20131231104804              sm1adm       sap_server 201312311048030058b8

INFO: Buffer saved as D:\sum\SUM\abap\buffer\SM1SAV.

STOP  SET STOPMARK         SM1        20131231104804              sm1adm       sap_server 201312311048030058b8

LIST  put                  SM1 (A{|

START tplock_eu            SM1 (      20131231104804              sm1adm       sap_server 201312311048030058b8

STOP  tplock_eu            SM1 (      20131231104804              sm1adm       sap_server 201312311048030058b8

START tp_getprots          SM1 J      20131231104804              sm1adm       sap_server 201312311048030058b8

sap_server

PHASES.LOG:

1 ETQ201 Entering upgrade-phase "MAIN_SHDRUN/ACT_UPG" ("20131231104800")

4 ETQ399 Set database connect to shadow.

4 ETQ399 Set environment for shadow connect:

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '12', GwService = 'sapgw12' Client = '000'

4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"

4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ399 Requirement for tp maps to 'exe'

4 ETQ383 translates to path "D:\sum\SUM\abap\exe"

4 ETQ399 Set tool parameters for shadow connect:

4 ETQ399   default TPPARAM: SHADOW.TPP

2 ETQ366 Connect variables are set for shadow instance access

4 ETQ399 System-nr = '12', GwService = 'sapgw12' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_ora_schema=SAPSR3

4 ETQ399   auth_shadow_upgrade=<null>

1 ETQ200 Executing actual phase 'MAIN_SHDRUN/ACT_UPG'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'ACTUPG.BUF'

2 ETQ399 Arg[1] = 'ACTUPG.TP0'

2 ETQ399 Arg[2] = 'SHDINCIMP.BUF'

2 ETQ399 Arg[3] = ''

1 ETQ399 Using error summary log 'ACTUPG.ELG'.

1 ETQ399 Executing putsteps '{|(A'.

3 ETQ399 20131231104803: PID 23360 execute 'D:\sum\SUM\abap\exe\tp "pf=D:\sum\SUM\abap\var\SHADOW.TPP" delstopmark "buffer=SM1"' , output written to 'D:\sum\SUM\abap\log\TP.ECO'.

3 ETQ399 20131231104803: PID 23360 exited with status 0 (time 0.000 real)

3 ETQ399 20131231104803: PID 22712 execute 'D:\sum\SUM\abap\exe\tp "pf=D:\sum\SUM\abap\var\ACTUPG.TPP" put SM1' in background, output written to 'D:\sum\SUM\abap\log\SAPup.ECO'.

TP.ECO:

SAPup> Starting subprocess in phase 'ACT_UPG' at 20131231104803

    ENV: DBMS_TYPE=ora

    ENV: JAVA_HOME=c:\j2sdk1.4.2_22-x64

    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

    ENV: ORACLE_HOME=D:\oracle\SM1\11203

    ENV: ORACLE_SID=SM1

    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

    ENV: PATH=D:\sum\SUM\abap\exe;D:\oracle\SM1\11203\bin;D:\oracle\SM1\102\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\usr\sap\SM1\SYS\exe\uc\NTAMD64

    ENV: SAPDATA_HOME=D:\oracle\SM1

    ENV: SAPSYSTEMNAME=SM1

    ENV: auth_shadow_upgrade=1

    ENV: dbs_ora_schema=SAPSR3

    ENV: dbs_ora_tnsname=SM1

EXECUTING D:\sum\SUM\abap\exe\tp.EXE  "pf=D:\sum\SUM\abap\var\SHADOW.TPP" delstopmark "buffer=SM1"

This is D:\sum\SUM\abap\exe\tp.EXE version 380.08.41 (release 720, unicode enabled)

tp finished with return code: 0

meaning:

  Everything OK

tp=>sapparam(1c): No Profile used.

tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

TP.SAV:

#--------------------------------------------------------------

#---- MASKING file TP.ECO from D:\sum\SUM\abap\log

#---- TIME: 20131231104803  PHASE: MAIN_SHDRUN/ACT_UPG

#--------------------------------------------------------------

SAPup> Starting subprocess at 20131231104759

    ENV: DBMS_TYPE=ora

    ENV: JAVA_HOME=c:\j2sdk1.4.2_22-x64

    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

    ENV: ORACLE_HOME=D:\oracle\SM1\11203

    ENV: ORACLE_SID=SM1

    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

    ENV: PATH=D:\sum\SUM\abap\exe;D:\oracle\SM1\11203\bin;D:\oracle\SM1\102\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\usr\sap\SM1\SYS\exe\uc\NTAMD64

    ENV: SAPDATA_HOME=D:\oracle\SM1

    ENV: SAPSYSTEMNAME=SM1

    ENV: auth_shadow_upgrade=1

    ENV: dbs_ora_schema=SAPSR3

    ENV: dbs_ora_tnsname=SM1

EXECUTING D:\sum\SUM\abap\exe\tp.EXE  "pf=D:\sum\SUM\abap\var\SHADOW.TPP" locksys SM1

This is D:\sum\SUM\abap\exe\tp.EXE version 380.08.41 (release 720, unicode enabled)

tp finished with return code: 0

meaning:

  Everything OK

tp=>sapparam(1c): No Profile used.

tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

[Reagan · Accepted solution]

Hello

This is not normal. The ACT_UPG shouldn't run for 7 days.

Are the logs at D:\sum\SUM\abap\tmp getting updated ?

Regards

RB

[Former Member · Accepted solution]

Hello, Reagan

I reboot server today and start upgrade again from phase main_shdrun/act_upg.

I see a new log file in tmp directory.

LM1A000059.SM1.txt.zip

[Reagan · Accepted solution]

Hello Igor

Are the logs getting updated ?

As you are on Oracle you must be hitting the issue mentioned in this note.

1635605 - CLIENT HANGS ON INSERT INTO TABLE WITH SECUREFILE LOB

Set the parameter "_use_zero_copy_io=false" and restart the database.

Regards

RB

[Former Member · Accepted solution]

I dont think that this note is valid as the oracle is 11.2.03 and there is no bug in windows.......

ORACLE_HOME=D:\oracle\SM1\11203

Thanks

Rishi abrol

[Reagan · Accepted solution]

I dont think that this note is valid as the oracle is 11.2.03 and there is no bug in windows.......

You may read the solution part of the note I have pointed out

Regards

RB

[Former Member · Accepted solution]

I think i read it correctly why the workaround is there fro the release that have issues...

Thanks

Rishi Abrol

[Former Member · Accepted solution]

I altered parameter _use_zero_copy_io=false and run SUM again

Upgrade is on same step - main_shdrun/act_upg

[Reagan · Accepted solution]

Connect to the shadow system and check the status of the activation job.

Consider doing a check status for the job in Tx SM37

Regards

RB

[Former Member · Accepted solution]

Yes, log LM1A000059.SM1 is updating

[Former Member · Accepted solution]

Also oracle.exe runs for 30% of CPU

[Reagan · Accepted solution]

I suggest you to wait for a while.

By the way did you set the Oracle parameter _use_zero_copy_io=false after restarting the server today?

Regards

RB

[Former Member · Accepted solution]

Yes, I set parameter _use_zero_copy_io=false and restart the server today.

I hope that upgrade is working. I will be wait..

[Former Member · Accepted solution]

Yes, parameter _use_zero_copy_io=false and restarting server was helpfull for me!

Thanks a lot for all !

[sunny_pahuja2]

Hello,

This is not normal. This phase does not take so much time. Could you please check if some background job is failed and check if there is any dump in the system? Also, you can try by stopping the upgrade and start the tool again.

Thanks,

Sunny

[Former Member]

Hello, Sunny!

I have some dumps:

And canceled jobs:

I stoped, reboot server and started upgrade again. But I think that it will be the same problem.

[Former Member]

Hi Igor

Currently what is the status of the upgrade - when the phase is reached , please check if there are any processes running / background jobs running in the system..

Thanks

Rishi

[Former Member]

Hi,

Can you please post the latest logs in the /<sum>/abap/log directory.

Also check the below note relate to this phase.

1919276 - Performance issues when running a SAP Upgrade

1674812 - Performance improvement for ACT_UPG

1918279 - performance analysis for ACT_UPG phase

These note are just guidance . Once we get the exact details of the logs can comment more.

We dont need all the old jobs but if any failed for the current phase .

I think currently would be this job. RDDMASGL

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

Current phase: main_shdrun/act_upg (Activates ABAP Dictionary customer objects)

There is no active jobs running:

And there is no busy processes:

[Former Member]

Hi, Rishi

ALOG702.txt.zip

ENVDUMP.SAV.txt.zip

ENVDUMP.LOG.txt.zip

[Former Member]

more logs

TP.ECO.txt.zip

SLOG702.txt.zip

ULOG14_1.txt.zip

[Former Member]

and more

TP.SAV.txt.zip

SAPupConsole.log.txt.zip

PHASES.SAV.txt.zip

[Former Member]

more

SAPup.ECO.txt.zip

SAPup.log.txt.zip

SAPupStat.log.txt.zip

[Reagan]

Hello

You are checking the wrong logs.

There is no need to provide so much of logs. You need to provide the relevant ones for each phase.

You are in the activation phase. The logs are initially created in the D:\sum\SUM\abap\tmp diurectory and once the phase has been completed the upgrade tool will will move the logs to the D:\sum\SUM\abap\log directory.

There will be individual activation logs for each package.

So first check the directory I have pointed out.

Regards

RB

[Former Member]

Hi,

If you check that the logs...

-------------------------------------------------------------------------------------------------------

>> 2013/12/26 20:14:32  START OF PHASE MAIN_SHDRUN/ACT_UPG

Collecting adjustments ...

Collection done - creating cofile ...

Running D:\sum\SUM\abap\exe\tp pf=D:\sum\SUM\abap\var\SHADOW.TPP checkimpdp SM1

Running D:\sum\SUM\abap\exe\tp pf=D:\sum\SUM\abap\var\ACTUPG.TPP put SM1

Analyzing result of tp call ...

<< 2013/12/31 10:47:24  END OF PHASE   MAIN_SHDRUN/ACT_UPG

INFO: shadow instance unlocked.

Synchronizing buffers via 'UPG_BUFFER_SYNC'...

-----------------------------------------------------------------------------------------------------------

So this Phase has already failed on 31/12/2013.....

Did you check what was the cause of the error that time ....

And then the phase was repeated again..

Thanks

Rishi Abrol

[Former Member]

Hello Rishi

Yes, I made this error when I restart system upgrading on 31.12.2013. Before this 7 days SolMan upgrages 3 days. Then I restart SUM and it starts to upgrade for 7 days.

[former_member45419]

Hi Igor,

Pls refer below thread,

http://scn.sap.com/thread/3248769

http://service.sap.com/solutionmanager

Regards

Nayeem