on 04-01-2016 5:04 PM
Trying to upgrade an SCM5.0 APO (+LC) System to SCM7.0 EHP3
Old System:
OpSys: Linux SLES 64bit
Kernel: NW7.0
DB: MaxDB 7.7
LiveCache: LCAPPS2005
Upgrade Target
OpSys: Linux SLEX64bit
Kernel: NW7.3
DB: MaxDB (??)
LiveCache: LC10
Sorry, but I don't know the target stack MaxDB release.
In any case, the stack calculation was done via SolMan MOPz, and the CIM & CR-Delta catalog was updated to the most recent level.
System verifications were run three times over, and everything went w/o a hitch.
But as soon as I try to launch SUM 1.0 SP16 the problems start.
It keeps peskering me for a user ID and password, and no matter what I try it won't take (including <sid>adm login info).
I had to start SUM SP16 as root to make it work with saphostagent(!)
Now I was able to start SUM SP11 as <sid>adm, but that one throws me the error
"You cannot use SUM to update your system from SAP SCM 5.0 to SAP SCM 7.0" as soon as it is done analyzing the stack XML file.
I could not locate the (in)famous SUM SP14 on SWDC.
What am I doing wrong here, and why do my old notes (regarding SCM upgrades) mention something about an "Upgrade Master DVD" (instead of SUM), that I seem unable to locate *anywhere* in the SWDC???
I am in a tight pickle here folks, and yes "this used to work" two years ago with our other APO Systems.
Any help in locating the correct installation media (or in pointing out to me that I am missing something else completely here) is truly appreciated.
Regards
Donald
Thx to all who chipped into this thread, yet in the end the solution was a simple as it was flabbergasting.
For one, I could start the upgrade engine simply by changing the URL to call it.
ABAP only: http://<Host-IP>:1128/lmsl/sumabap/APP/doc/index.html
And second, once I downloaded the latest SUMSP16 version (March 2016) I found out that:
A) You call it via <SID>ADM (again) from /usr/sap/<SID>/SUM
B) The old upgrade engine is still in there and fully functional.
You can launch it via: http://<Host-ID>:4239/sdtdsu.jnlp
Now I am damn sure that 'B' is not supported by SAP, and might be switched off at any future release date. But I am truly miffed here that SAP keeps introducing new software releases, that work less reliably and are more difficult to use than their predeccessors - instead the other way around.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After setting up SAPHOSTAGENT completely from scratch - including tripple checking/correcting all file and dir permissions, and setting up the PSE, I am finally able to connect as <sid>adm.
Only to get the same "Document not found" error as I did via sapadm.
Thx SAP, that was a late Saturday night well spend (not) 😞
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I went and reinstalled SAPHOSTAGENT from scratch via Software Provisioning Manager.
That still did not do the trick.
But now I know which user/password combo "works" - sort of.
When I use sapadm with he Pwd I used during installation, I get passed the password popup dialog.
But then the browser presents me with an empty window, and the only text being displayed is:
"Document can not be found"
I can *not* log on as <sid>adm, no matter what I try.
Can someone here please at least confirm to me that:
1) SUM SP16+ needs to be started from /usr/sap/<SID>/SUM?
2) It needs to be started as user "root" (Linux)?
If I can't find another upgrade engine (is there really no "Upgrade Master DVD" for SCM5.0 -> SCM7 EHP3 ???),
and nobody helps me to get this dreaded new SUM running, then I need to open up a ticket with SAP - just to get SUM to start up right.
This is ludicrous, I already disliked the move to SUM in the first place, and now SAP requires dozens of other components to be configured/running, just to start the damn upgrade - not even to finish it successfully.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Donaldo,
Not sure if you have gone through SUM guide but please check it. See Preparation section from SUM Guide relevant for Linux with Maxdb. Below is the link for that guide, please see if you are able to access it:
https://websmp207.sap-ag.de/~sapidb/011000358700000783522011E
Also 5.3 Registering SUM in SAP Host Agent section for preparing Host Agent (Use of SSL or without SSL) and then running SUM tool using root user (screenshot attached).
Thanks,
MPS
This is not directed against you, but I already performed that nonsense agent registration step.
Nonsense because it should not be neccessary in the first place - and it didn't change a thing.
Its a single use server & system and all this makes just getting the install engine up & running utterly complicated, w/o any added benefit.
I don't get it why SAP keeps changing *everything*: the Marketplace, the way basic tools work and where to locate essential stuff.
Is like a big whooping fashion show with them, and as a result Basis Admins end up wasting weeks with things that should be done and over with in under 5 days 😞
Give me a good old fashioned "Upgrade Master DVD", so I can spend the weekend with my girl friend instead of this dumbf* terminal 😞
SUM SP16, once started as "root" (trying to start it as <sid>adm produced nothing but error messages with hostagent), simply terminates and there are no log files for the failed login attempts.
But saphostagent writes this log file under its "work" directory:
---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 1, release: "721"
---------------------------------------------------
pid 24944
[Thr 140604392695680] Fri Apr 1 22:00:09 2016
[Thr 140604392695680] MtxInit: -2 0 0
CCMS agent initialization for instance type HOST: return code 0.
[Thr 140604392695680] CCMS: Initialized monitoring segment of size 40000000.
[Thr 140604392695680] CCMS: Initialized CCMS Headers in the shared monitoring segment.
[Thr 140604392695680] CCMS: Checking Downtime Configuration of Monitoring Segment.
[Thr 140604392695680] *** ERROR => SemRel: Inv. Operation. Units 1. Key=1004 [semux0_mt.c 1393]
[Thr 140604392695680] CCMS: AlMsUpload called by wp 1998.
[Thr 140604392695680] CCMS: AlMsUpload successful for /usr/sap/hostctrl/work/ALMTTREE (124 MTEs).
CCMS agent start: return code 0.
Initializing SAPHostControl Webservice
[Thr 140604392695680] =================================================
[Thr 140604392695680] = SSL Initialization platform tag=(linuxx86_64_gcc41)
[Thr 140604392695680] = (721_REL,Mar 19 2016,mt,ascii,SAP_UC/size_t/void* = 8/64/64)
[Thr 140604392695680] profile param "ssl/ssl_lib" = "/usr/sap/hostctrl/exe/libsapcrypto.so"
[Thr 140604392695680] resulting Filename = "/usr/sap/hostctrl/exe/libsapcrypto.so"
[Thr 140604392695680] = disabled FIPS 140-2 crypto kernel
[Thr 140604392695680] = found CommonCryptoLib 8.4.49 (Mar 4 2016) [AES-NI,CLMUL,SSE3,SSSE3]
[Thr 140604392695680] = current UserID: "sapadm", env-var USER="sapadm"
[Thr 140604392695680] = using SECUDIR=/usr/sap/hostctrl/exe/sec
[Thr 140604392695680] *** ERROR => secudessl_Create_SSL_CTX(): PSE "/usr/sap/hostctrl/exe/sec/SAPSSLS.pse": File not found! [ssslsecu_mt. 1796]
[Thr 140604392695680] secudessl_Create_SSL_CTX: SSL_CTX_set_default_pse_by_name() failed --
[Thr 140604392695680] secude_error 4129 (0x00001021) = "The PSE file does not exist."
[Thr 140604392695680] >> ---------- Begin of Secude-SSL Errorstack ---------- >>
[Thr 140604392695680] 0x00001021 | SAPCRYPTOLIB | SSL_CTX_set_default_pse_by_name
[Thr 140604392695680] SAPCRYPTO API error
[Thr 140604392695680] The PSE file does not exist.
[Thr 140604392695680] 0xa1d50108 | TOKEN_TOKPSE | sec_SSL_CTX_set_asc
[Thr 140604392695680] Token application not existing
[Thr 140604392695680] << ---------- End of Secude-SSL Errorstack ----------
[Thr 140604392695680] *** ERROR => SapISSLAddCredential(): Error SSSLERR_PSE_ERROR trying to create SERVER Credential
for "/usr/sap/hostctrl/exe/sec/SAPSSLS.pse" [ssslxxi_mt.c 2422]
[Thr 140604392695680] *** ERROR => Initialization of SSL library failed -- NO SSL available!
[Thr 140604392695680] =================================================
[Thr 140604392695680]
[Thr 140604392695680] <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_PSE_ERROR
SapSSLInit failed => https support disabled
Starting WebService thread
Webservice thread started, listening on port 1128
Trusted http connect via Unix domain socket '/tmp/.sapstream1128' enabled.
[Thr 140604342195968] CCMS: Initialized monitoring segment of size 40000000.
[Thr 140604342195968] CCMS: Initialized CCMS Headers in the shared monitoring segment.
[Thr 140604342195968] CCMS: Checking Downtime Configuration of Monitoring Segment.
[Thr 140604342195968] *** ERROR => SemRel: Inv. Operation. Units 1. Key=1004 [semux0_mt.c 1393]
[Thr 140604342195968] CCMS: AlMsUpload called by wp 1998.
[Thr 140604342195968] CCMS: AlMsUpload successful for /usr/sap/hostctrl/work/ALMTTREE (124 MTEs).
[Thr 140604293416704] Fri Apr 1 22:01:11 2016
[Thr 140604293416704] *** ERROR => GSOAPHTTPRequest::Parse failed [saphostcontr 418]
[Thr 140604293416704] HTTPHandlerManager : HTTP Handler found for /lmsl/sumabap/APP/doc/sluigui.html
[Thr 140604293416704] Fri Apr 1 22:01:28 2016
[Thr 140604293416704] HTTPHandlerManager : HTTP Handler found for /lmsl/sumabap/APP/doc/sluigui.html
[Thr 140604293416704] Fri Apr 1 22:01:42 2016
[Thr 140604293416704] HTTPHandlerManager : HTTP Handler found for /lmsl/sumabap/APP/doc/sluigui.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, my mistake. In order to eliminate an error in the stack, I had calculated a 2nd stack that went to the bare minimum in Solution Manager.
This (misleading) screenshot only shows that SUM SP11 also doesn't do the trick when I only go for the bare minimum of upgrades.
This is not from the stack I had originally calculated, which went for the latest and greatest in all components.
I believe you are upgrading the SCM system to SCM 7.0 EHP3 and if yes the target kernel will 7.4x based. Have you checked PAM for the supported OS and DB versions for the target release?
Check this SAP note 1951491 - Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08 as it clearly states the MaxDB requirement. As you are doing a release upgrade of the SCM system you will need the upgrade DVD's. Look for the upgrade export media 51049225
Not really sure what that password error is all about. Some logs?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Donald,
As per PAM target MaxDB might be 7.9. Also please go through Upgrade Guide to review pre-requisites for upgrading to EHP3 for SCM 7.0.
Also please go through below SAP Note for your upgrade.
1737723 - EHP3 for SAP SCM 7.0 SP Stacks - Release & Information Note
It is advisable to use latest SUM patch level for upgrade activity, could you please provide the log or error screenshot when you are trying to use SUM 1.0 SP16.
Thanks,
MPS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check below SAP Note:
2294832 - User and password are repeatedly asked when starting SUM (SL Common UI)
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.