Skip to Content

SUM reading wrong SCA files

Hi,


We are confronted by an issue with SUM in our solman development system

upgrade. This has resulted in a hault of our solman patch

upgrade.


What we are doing (or intend to do) -


We wanted to upgrade our Solman Java's J2EE Core componetns as per SAP

Note# 1893013 to the latest patch level available in market palce.

In other words, we wanted to upgrade following components as follows -


SAP-JEE 7.02 SP15 (1000.7.02.15.0.20141002164600) TO 7.02 SP15

(1000.7.02.15.5.20141002164600)

SAP-JEECOR 7.02 SP15 (1000.7.02.15.0.20160310055015) TO 7.02 SP15

(1000.7.02.15.24.20160310055015)

SAP_JTECHF 7.02 SP15 (1000.7.02.15.0.20160211045334) TO 7.02 SP15

(1000.7.02.15.16.20160211045334)

SAP_JTECHS 7.02 SP15 (1000.7.02.15.0.20160211045605) TO 7.02 SP15

(1000.7.02.15.21.20160211045605)



What we did -


We downloaded latest available SUM tool in market place -

SUM10SP17_4-20006543.SAR and started our upgrade (following guide for

example - running by root and using new command - ./STARTUP

confighostagent <SID> etc)

There we choose above mentioned 4 components and their target release

and continued. Not to say, we choose manual update in SUM



What SUM has done until now-

SUM is at step "Deploy Software Components" - 50% complete and now in

error. We see that all above 4 components have been upgraded to their

desired level in system status.



What is the issue we face now -

Unfortunately, EPS inbox had a lot of other patches in it from previous

upgrades of different systems which we didn't cleared. And now somehow

SUM has read the whole directory and stops with following error -


Jul 21, 2016 7:34:45 AM Info: Loading archive

'/usr/sap/trans/EPS/in/SECURITYEXT07P_5-10008748.SCA'

Jul 21, 2016 7:34:46 AM Error: This SDA has a software type assigned

that is not supported: CONTENT.

Jul 21, 2016 7:34:46 AM Error:

/usr/sap/S2D/DVEBMGS00/SDM/root/origin/sap.com/sc/security-ext/SAP

AG/0/7.3007.20120924153323.0000/sc~security-ext.sda: This SDA has a

software

type assigned that is not supported: CONTENT.


SUM is giving these errors for following components only (though we

surely have other unwanted patch files as well in inbox)-


'/usr/sap/trans/EPS/in/SAPCRMJAV04_149-20008034.SCA'

Loading archive '/usr/sap/trans/EPS/in/SAPCRMWEB04_149-20008033.SCA'

Loading archive '/usr/sap/trans/EPS/in/SAPSHRJAV04_149-20008031.SCA'

Loading archive '/usr/sap/trans/EPS/in/SAPSHRWEB04_149-20008032.SCA'

Loading archive '/usr/sap/trans/EPS/in/SAPXIESR07P_23-10008104.SCA'


What we have tried as of now -

I deleted these files from inbox as they are not needed but then SUM

said it couldn't find the files!

Actually SUM creates a file (like telnet does)

/usr/sap/S2D/SUM/sdt/tmp/deploy_list.txt and it makes entries for above

SCAs and search for them.


My Question -

Why SUM is looking for the components which we didn't selected in the

first place.


Why SUM is checking these components (that they are invalid) during

execution phase and not in "checks" phase ?


Most important question is ----- >>> Now what is the way to

tell SUM that we don't need these components and it can proceed without

them ?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jul 28, 2016 at 07:15 AM

    Here is what I found -

    We choose SUM manual upgrade and choose EPS inbox directory for patch files. This directory contained various other patch files from previous upgrades. Even though we choose only our four components (Java-core and we are sure because we double checked it and we were two people doing this); SUM in case of manual updates revise whole directory and sometimes (rarely) can pick other files as well for upgrade and then it gives a message in validation phase saying these wrong files will be rejected which was what, we off-course want. Now this message is very misleading and what it actually says here is that – These files seems invalid to me (SUM) but I will still try to update them and will surely fail in deployment phase so please cancel this upgrade, clean these files and try fresh!

    For further info - please read SAP KBA 2190432

    Though we could have tried to continue by jumping the step by SAP password or tried to re-run upgrade after cleaning the directory and completing all four ocmponents (not sure if that would have worked), but we went for a restore as it was only solman development system with a very small DB (hence restore period).

    So lesson learnt is always have only specific files to upgrade in EPS inbox or whichever directory you choose.

    Thanks

    Vivek

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.