on 2016 Sep 22 9:31 AM
Hello Group,
We are in phase MAIN_UPTRANS/STARTSAP_PUPG after downtime from an ECC EHP4 upgrade to EHP7 on SAP on iseries.
However, the upgrade has stopped when trying to start the SAP system for the final time. We are receiving the following error so seems to be an issue with journals ahead of starting the SAP system.
Last error code set: SAPupdbdb4.c:1014: Error message MCH3602 running 'CALL PGM(SAPDV6UPG/R3UPCHGJRN) PARM('R3DV6DATA' 'QSQJRN' 'R3DV6JRN' 'QSQJRN0004' '*NO')'.
I can see from searches MCH3602 means "Pointer not valid for requested operation" but this is not helping resolve.
Has anyone come across this before ? Any help would be much appreciated. We have raised SAP message 329643 for those with access, but I thought
I would try this group as well.
Best regards,
Steven
Hello Group,
Just to follow up that SAP helped move past the upgrade issue with journals, but we do not have an explanation why this did not work. Below is the response from SAP
I could not catch the reason for the MCH3602 error since it simply did not occurred when the debug version was used. I will try to recreate it with an SAP in house system by using the SUM SP17 you currently have with the same upgrade path. It's not the first time I found that debug program versions hide pointer issues somehow... Fixing such issues is time consuming but possible.
Best regards,
Steven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
71 | |
10 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.