SRM Upgrade

[Former Member]

Hi,

I am in middle of SAP upgrade.

Existing - SRM 7.01 sp12 on NW 7.02 sp15

UPGRADE to - SRM 7.0 Ehp 4 on NW 7.5 sp1

Current Phase - MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSGEN is running since 6 hours.

The upgrade logs are also not getting updated and the phase is stuck.

I went through the log files like RSGEN.LOG and SAPup.log

1) RSGEN.LOG

4 ETQ263 Batchjob "RSGEN_GENER8_SHADOW" finished successfully

2 ETQ399 Phase RUN_RSGEN is now finalizing...

1 ETQ124 Scanned file 'log\RSGEN.SRT' from offset 114 to 292702 for errors.

2 ETQ399 Phase RUN_RSGEN: Finalize OK

1 ETQ207 Executing post-phase DB specific actions 0/1.

4 ETQ010 Date & Time: 20160325151446

1 ETQ202 Upgrade phase "RUN_RSGEN" completed successfully ("20160325151446")

2) SAPup.log

CURRENTPHASE MAIN_DTTRANS/DOWNCONF_DTTRANS

...started at 20160325152605

# Using phase log file 'DOWNCONF.LOG'.

...begin dialog at 20160325152605

3) DOWNCONF.LOG

1 ETQ201 Entering upgrade-phase "MAIN_DTTRANS/DOWNCONF_DTTRANS" ("20160325152605")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '10', GwService = 'sapgw10' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399  dbs_mss_schema=srt 1 ETQ206 Executing pre-phase DB specific actions 0/1.

1 ETQ200 Executing actual phase 'MAIN_DTTRANS/DOWNCONF_DTTRANS'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'START_DOWNTIME'

1 ETQ399 SYSTEM MANAGER: Initializing.

4 ETQ399 Starting dialog 'DownConf' at 20160325152605.

There are no log updations after this since 6 hours and the upgrade screen shows Current Phase - MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSGEN

The shadow instance is deleted by SUM and no longer exists.

However, the main SAP instance is up and running and not yet shutdown.

Please suggest and appreciate your help.

Thanks,

Sameer

Message was edited by: Sameer M

[Reagan · Accepted solution]

>>1 ETQ200 Executing actual phase 'MAIN_DTTRANS/DOWNCONF_DTTRANS'.<<

In the logs you have supplied I can see the phase has been completed successfully. It has started the downtime phase. Most likely the GUI is stuck. Are there any logs that contain some information in the <Upgrade Directory>/SUM/abap/tmp location?

Can you list the latest 10 logs from the upgrade log location please?

Consider restarting the SUM tool and see what it says and if nothing helps a complete restart of the SAP system.

[Former Member · Accepted solution]

Thanks for your reply Regan

I checked the location - /SUM/abap/tmp

In this found the SAPupDialog.txt -

###  Dialog on screen  ###

=========== Preparations for Downtime ===========

The procedure has reached the end of the "Preprocessing" step.

Perform the following actions: 

* Stop all production activities now 

* Ensure that no scheduled batch jobs can start anymore and await regular completion of currently running jobs 

* Make sure that all users have logged out 

* Isolate the central instance (primary application server instance) as described in the guide

When you confirm "Actions completed", the system will be stopped and you will be prompted to perform a complete backup.

01)  *  Actions completed

02)  -  Exit program

: Actions completed

The 10 logs as you mentioned from the upgrade log directory are

> DOWNCONF.LOG

> ALOG750

> CHECKS.LOG

> SAPup.LOG

> SAPupConsole.LOG

> SLOG750

> ULOG16_1

> CHECK_SLT_TRIGGER_PH.LOG

> SAPupStat.log

> DMPSPC_MPT.LOG

I have 2 questions

My SUM upgrade screen is in a hang state and no logs are getting updated since last 24hours+.

The shadow instance, it's services are all deleted by SUM and my original instance is GREEN and up and running when I checked the MMC. So I guess I have completed the preprocessing stage and now in Downtime phase. NOT SURE THOUGH.

Q1) Can I only STOP SAP in MMC and see if SUM proceeds to the next stage?

Q2) Can I restart the SUM tool and NOT reset SUM? I don't want to reset at this point of time.

I am not aware of RESTARTING the SUM tool as this is the first time I am using SUM.

Which of the above two ways help me enhance my upgrade?

Thanks,

Sameer

[Reagan · Accepted solution]

1 - You do not need to stop the SAP from MMC. As you are doing an EHP update you just need to keep the central instance up and running and stop only the App servers. Check the SUM on how to start the downtime phase.

2 - Restarting the SUM tool will not reset the upgrade/update process. In your case the option would be to restart the SUM tool as there appears to be an issue with the tool.

[former_member182657]

Hi,

Could you share DOWNCONF.LOG from the system ?

My SUM upgrade screen is in a hang state and no logs are getting updated since last 24hours+.

Suggest you to stop the SAP system & restart the system once along with SUM tool to execute the process again from the point where it get stucked .

Can I restart the SUM tool and NOT reset SUM?

You could restart the SUM tool & avoid to reset the SUM process at this stage.

I am not aware of RESTARTING the SUM tool as this is the first time I am using SUM

SUM restarts similar as like when you started it first time,SUM will starts from the same step from where we closed it by providing Administrator password ( User which you used during start of SUM).

Regards,

[Former Member]

DOWNCONF.LOG

1 ETQ201 Entering upgrade-phase "MAIN_DTTRANS/DOWNCONF_DTTRANS" ("20160325152605")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '10', GwService = 'sapgw10' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399  dbs_mss_schema=srt

1 ETQ206 Executing pre-phase DB specific actions 0/1.

1 ETQ200 Executing actual phase 'MAIN_DTTRANS/DOWNCONF_DTTRANS'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'START_DOWNTIME'

1 ETQ399 SYSTEM MANAGER: Initializing.

4 ETQ399 Starting dialog 'DownConf' at 20160325152605.

Thanks,

Sameer