Hi, you can use this roadmap I've made for upgrading to EHP1 from SP17 or lower. Please remark that its a prerquisite that Your java stack is on SP17 (solman SP17 = NW Java sps16). Also, You should include SP04/SP20 for Solman while upgrading via SAINT (ABAp Wise) and JSPM (JAVA wise).
BR Kurt
*Pre upgrade 1 *
Make a complete offline backup of Your whole system (DB + files)
Pre upgrade 2
release workbench/customizing request:
Pre upgrade 3
Lock all users exept from system users and exclusive users
- In TC=su10 click on "Authorization data"
- Scroll down and in "Additional selection criteria" check the "Locked users only" box
- Click on "Execute" (F8)
- Make at note of the locked users
- Go one step back, and click on "Authorization data" once again
- Scroll down and in "Additional selection criteria" check the "Unlocked users only" box
- Click on "Execute" (F8)
- Select all users by clicking the green icon in upper left corner
- Deselect the system users and own user:
- Click on "Transfer" in upper left corner
- Click on "Lock" icon
Pre upgrade 4
Check system (transport tool, ST22, SM21, SM13, SM50)
- In STMS run the check TP tool
- Look for ABAP dump in ST22
- Look for errors in SM21
- Look for update errors in SM13
Pre upgrade 5
- Extending datafiles/tablespace in database manually if needed
Pre upgrade 6
Setting all jobs to scheduled during the upgrade phase
In productive client , tc=SE38, run the program "BTCTRNS1".
This will take all currently Scheduled and Released jobs and move them into a "special" status
Upgrade part 1
Upgrade the Java stack + kernel to Solution Manager SPS17 (NW sps16) if not already upgraded.
- Logon to with OS user <sapsid>adm
- Open JSPM by db.clicking the go.bat file in the directory:
usr\sap\<SAPSID>\DVEBMGS<instance>\j2ee\JSPM
- Logon to JSPM (SDM) using the same password as J2EE_ADMIN
- Choose "deploy SPS stack"
- Follow the guidelines from JSPM
Remark:
First the JSPM application is updated, which requires restart of the JSPM
second: The kernel files is updated, which requires restart of the SAP system
Third: all other Java packages is deployed, which requires restart of the Java Engine cluster a couple of times during that phase - all controlled by the JSPM application + manual interaction via the Cluster administrator (stop/start of clusterressources).
During use of JSPM, refer to Note 891983 - JSPM: Central SAP Note SAP NetWeaver 2004s AS Java regarding troubleshooting if needed
Upgrade part 2
Upgrade SPAM to latest version 03x
- Login to client 000 with user (SAP_ALL, SAP_NEW) u2013 not SAP* and DDIC
- tc=SPAM
- Choose "Support Package", "Load packages", "from application server"
- Choose "Support package", "Import SPAM/SAINT_Update" and follow the guidelines
- Confirm after deploying the supportpackage
Upgrade part 3
Upgrade product definitions in Solution manager according to note 1169247
- tc=SE30
- Run the report: RS_SMSY_PPMS_XML_UP_DOWNLOAD
- Set checkmark with an uppercase "X" in option field: "Upload"
- Point to the downloaded .XML file
- Click "ok"
Upgrade part 4
Adding .DLL files to support NW7.01 use of Visual Studio 2005 Compiler According to note 684106
- on SAP servers execute downloaded vcredist_x64.exe file from directory:
- on SAP servers copy file: dbghelp.dll. to the directories:C:
windows\system32 and C:
windows\syswow64 on all SAP servers
Note, check before copying dbghelp.dll whether the relevant file exists in the directories \windows\system32 and \windows\syswow64, and replace the file only if the version that is made available here is more current than the version that is already available. You can use the Windows Explorer to determine the file version (right-click and choose "Properties -> Version").
Upgrade part 5
Upgrade to SAP kernel 7.01, kernel 55
- Logon to the SAP server
- Stop SAP instances via the MMC console
- Navigate to Kernel directory:
usr\sapmnt\<SAPSID>\SYS\exe\uc
- Make a copy of current kernel by copying the folder: NTAMD64
- Copy new kernelfiles (701_55 into the directory: :
usr\sapmnt\<SAPSID>\SYS\exe\uc \NTADM64
- Click "yes", when prompted to overwrite existing files
- Go to SAP MMC console and start the SAP system again
- make sure all instances goes into "green" status in SAP MMC console
- tc=Session_Manager, choose "system", "Status", press "Shift+F5" to show the kernel info
Upgrade part 2
Upgrade the ABAP stack to Solution Manager SPS20/EHP1 including supportpackages
- tc=SAINT
- Choose "Extras" --> "Settings" --> "Import queue" tab
- define 5 parallel R3trans processes
- click "Confirm" (green checkmark)
- Call transaction SAINT and choose "Start" and "Load".
- Choose the right pushbutton to load the stack configuration (SW-Center Stack-XML).
- Alternatively,the SAINT queue can be buildt manually.
Select the following components and choose "Continue".
PI_BASIS 701
SAP_ABA 701
SAP_BASIS 701
SAP_BW 701
BI_CONT 704
CRMUIF 500
ST-A/PI 01L_CRM570
ST-PI 2008_1_700
ST-SER 701_2008_2
If all necessary conditions for importing the add-ons are met,
the system will display the relevant queue. The queue consists
of installation packages, upgrade packages, Support Packages
and Conflict Resolution Transports (CRTs).
- To start the installation process, choose "Continue".
- The system prompts you to enter a password. This password is
provided below:
Before the installation, you will be asked to enter a password for
each component you selected. This password is (in bold):
Component Package name Password
CRMUIF 500 SAPK-500AGINCRMUIF D855FD497D
PI_BASIS 701 SAPK-701DHINPIBASIS 3DD62AEC78
SAP_ABA 701 SAPK-701DHINSAPABA 3DC721976A
SAP_BASIS 701 SAPK-701DHINSAPBASIS 3EC433FE19
SAP_BW 701 SAPK-701DHINSAPBW 3ED240976A
BI_CONT 704 SAPK-704DHINBICONT 14158187D7
BI_CONT 704 SAPK-704IHINBICONT 1415818AD7
Upgrade part 6
Implement notes after upgrade
- login to productive client
- tc=SNOTE
- Press "Download SAP Note" (CTRL+F8).
- Type notenumbers: 1250122, 1270420, 1256049, 1243425, 1236420 and 1269582 and press "Copy" (F8) and "Execute" (F8).
- Mark notenumber: 1250122 and press "Implement SAP Note" (CTRL+F1). REMARK: this note should be implemented in pair with note: 1270420.
- Mark notenumber: 1256049 and press "Implement SAP Note" (CTRL+F1). REMARK: this note should be implemented in pair with note: 1243425.
- Mark note 1236420 and press "Implement SAP Note" (CTRL+F1).
- Mark note 1269582 and press "Implement SAP Note" (CTRL+F1).
Upgrade part 7
Increase EventTimeout to avoid deployment errors in Java stack for SPS20/EHP1
- Log on to Server
- Open config Tool by clicking: config.bat in the directory:
- In the navigation area choose: Cluster-data --> Global server configuration --> Managers --> ServiceManager
- in the Global properties panel, set the Custom value of the EventTimeout property to 120
- choose "Save"
- Restart the Central Instance
Upgrade part 8
Upgrade the Java stack to Solution Manager SPS20/EHP1 including supportpackages
- Logon to SAP server
- Open JSPM by db.clicking the go.bat file in the directory:
usr\sap\<SAPSID>\DVEBMGS<instance>\j2ee\JSPM
- Logon to JSPM (SDM) using the same password as J2EE_ADMIN
- Choose "deploy SPS stack"
- Follow the guidelines from JSPM
Remark:
First the JSPM application is updated, which requires restart of the JSPM
Second: all other Java packages is deployed, which requires restart of the Java Engine cluster a couple of times during that phase - all controlled by the JSPM application + manual interaction via the Cluster administrator (stop/start of clusterressources).
During use of JSPM, refer to Note 891983 - JSPM: Central SAP Note SAP NetWeaver 2004s AS Java regarding troubleshooting if needed
Upgrade part 9
Update LM-SERVICE.SCA and LM-TOOLS.SCA to latest patch level
- Logon to SAP server
- Open JSPM by db.clicking the go.bat file in the directory:
usr\sap\<SAPSID>\DVEBMGS<instance>\j2ee\JSPM
- Logon to JSPM (SDM) using the same password as J2EE_ADMIN
- Copy the files to directory:
usr\sap\trans\EPS\in
- Choose "deploy single package"
- Follow the guidelines from JSPM
Post upgrade 1
Temporarely adjust the time out values for the HTTP service
- login to the productive client
- tc=SMICM
- navigate in the menu to GOTO -> SERVICES
- Set the checkmark for HTTP
- navigate in the menu to SERVICE -> CHANGE
- set the time out values for "Keep Alive" and "Max. Processing Time" to about 6000
Post upgrade 2
Restoring all jobs to the status before the upgrade phase
- In productive client, tc=SE38, run the program "BTCTRNS2".
This will restore all jobs to their previous status
Post upgrade 3
- Logon to productive client via SAPGUI
- TC= SOLMAN_SETUP
- Follow the setup wizard. If You allready have done configuration in Your system, do not use "Initial Setup"
Post upgrade 4
Generation of objects
- tc=SGEN
- Mark "Generate all objects of selected software components" and click "Continue"
- Click on "Select all components" and click "Continue"
- Click on "Select all" applications servers and click "Continue"
- Click on "Start job directly (in background)"
Post upgrade 5
Checking diverse tc/functionality
- Login to productive client
- tc=DSWP
- Choose "Operation", "Change management", "Maintenance optimizer". Is it posible to create new maintenance transaction?
- Choose "Solution landscape". Is it possible to browse the landscape?
- tc=ST22. Is there any dumps?
- tc=SM21. Any error in log?
- tc= SOLUTION_SETUP. Does it work?
Post upgrade 6
Unlock all users exept from already locked user preupgrade
- In TC=su10 click on "Authorization data"
- Scroll down and in "Additional selection criteria" check the "Locked users only" box
- Click on "Execute" (F8)
- Click on "Transfer" in upper left corner
- Click on "Unlock" icon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.