SUM Clean Module Password Required - Reset Java Upgrade

[Former Member]

Hi we were upgrading EP Java and went to the Preprocessing phase where patches were applied to shadow instance. We decided we want a different version/set of patches and needed to recalculate stack file. We went ahead and cancelled the upgrade. We proceeded as follows:

1. SUM - Update - Reset Update. Message showed it was reset. Not sure if it "actually" worked. This was done according to SUM guide. Exited out of SUM with no errors.

2. Checked DB table - found schema present SAP<SID>SH - dropped schema with content

3. Checked main schema SAPSR3DB - 565 tables starting with SHD found . Dropped all these tables with cascade and purge.

4. Restored the /usr/sap/SID directory

5. Rebooted Server

6. SAP Starts up fine and everything works fine as before

7. Deleted shadow instance services from registry

8. No profiles found related to shadow instance

9. Deleted old SUM folder. Extracted fresh SUM and started

(Unfortunately in Java there is no option of RSUPGRES/RSUPGREV - neither is there a UVERS table - also there is no DDIC user which is being asked for when I do a SAPup prepare reset)

How do we clean up and do a reset for Java ? Ther's gotta be a place where SUM is reading old entries from. We really dont want to restore the DB but they may be the only solution it seems

Below is the message I get. I have opened a ticket with SAP and already checked OSS Note:

2011380 - Previous SUM not finished properly and asking for CLEAN
MODULE PASSWORD

      SUM has detected leftover artifacts that originate from previous SUM
      execution that was left unfinished. This SUM instance can attempt to
      cleaup the leftover data. In order to proceed please open OSS message in
      BC-UPG-TLS-TLJ with the following information:
   
        1. Your execution code: 1978128322
     
        2. Explanation why the previous SUM run was not finished. If possible:
        In which step you have stopped it.
    

    After you open the message enter bellow the supplied password and choose

    Continue.

[Reagan · Accepted solution]

Stop SUM.

If there is a directory called oldSUM under /sapmnt/SID/global/security/data then remove or rename it.

Restart SUM.

[meiwang_melissa · Accepted solution]

thanks for Reagan Benjarmin,

your method is ok,

I have the same problem, and it is solved by your advice.

[jesus_torres2]

This worked like a Charm!

In our case we needed to move out all the following files from /sapmnt/SID/global/security/data

-rwxr--rwx 1 pxdadm sapsys 31 Sep 22 17:02 JUpgrade.key

-rwxr--rwx 1 pxdadm sapsys 1330 Sep 22 17:15 JUpgrade.properties

-rwxr--rwx 1 pxdadm sapsys 1330 Sep 22 17:15 JUpgrade.properties.back

-rwxr--rwx 1 pxdadm sapsys 528 Sep 22 17:13 sumExecutions.xml

[former_member624684]

Hello All,

We were facing below error, SUM was not allowing us to move forward.

**********************************************************************************************************

SUM has detected leftover artifacts that originate from previous SUM execution that has been entered downtime and was left unfinished.
Previous SUM execution has been started on03/19/2021from/usr/sap/SID/SUM/sdt. Last executed step wasDeploy Software Components.
In order to proceed please complete the previous SUM execution or revert the system.

********************************************************************************************************
We have tried above-suggested step by moving the upgrade/SUM files from /sapmnt/SID/global/security/data location. then started the SUM and it worked.

Thanks Benjamin!

Karthik Bura