#ATR (24) INFORMATIVE NOTE:
Created this blog to provide information on how to install ECC EHP8 System with Oracle 19c Database.Please visit Uninstalling SAP System and Reuse SAP Server for new installation #ATR to have an overview of how to setup VM/OS from scratch for SAP.Please visit QUICK CATCHUPS ON TOP-20-SWPM/SUM ERRORS – SAP INSTALLATION ON AIX – ORACLE #ATR to have an overview of SWPM/SUM Errors.
CHECK POINTS:
PART 1:
1) PREREQUISITE CHECK FOR INSTALLATION
2) STACK XML FILE GENERATION IN MAINTENANCE PLANNER
3) SWPM OPERATION [START] – INSTALLATION OF BASE PACK
Please refer link – END TO END INSTALLATION OF SAP EHP8 ERP SYSTEM WITH ORACLE DATABASE 19c ON RHEL 8.8 – PART 1 #ATR
PART 2:
4) ORACLE DATABASE INSTALLATION (IN MID OF SWPM)
5) ORACLE PATCH UPDATE WITH POST INSTALLATION SCRIPT (IN MID OF SWPM)
6) COMPLETION OF SWPM – INSTALLATION OF BASE PACK
Please refer link – END TO END INSTALLATION OF SAP EHP8 ERP SYSTEM WITH ORACLE DATABASE 19c ON RHEL 8.8 – PART 2 #ATR
PART 3:
7) SUM EXECUTION – EHP UPDATE WITH SAP NW
CHECK POINT 7: SUM EXECUTION – EHP UPDATE WITH SAP NW
Now, we are proceeding to perform SUM SP Update from EHP SP1 to SP9 with relevant updates of software components (includes ECC ERP, SAP NW as well).We can start SUM separately (manual) as well to complete EHP Update without need of SWPM since SWPM process completed. Make sure to provide same Stack file for SUM if started manually later for EHP & NW update.SWPM consider SUM Directory – /usr/sap/SID/SUM by default.We can also use other directory or make separate LVM for SUM path alone to delete and reclaim space once SUM Execution completed.In my case, I’m using /usr/sap FS itself since it’s test system and space will be increased accordingly.Logon SUM with SIDADM (EC0ADM) user.EX – https://servername:1129/lmsl/sumabap/EC0/doc/slui
Make sure to have atleast 55-65G free space in /usr/sap (includes trans/sumabap) directory to proceed update process.Also, provide full 777 access to downloaded Software files.
You can download and upload notes manually if you are planning to do post installation steps (SAP Note Download Connectivity, SAP Support Portal) once completion of SUM process.
All mentioned notes implemented in system. Repeat SUM failed process.
Configuration Checks completed successfully.
Checks completed successfully.
Lock Development Environment.
We can release our note implementation TR (changes) even if captured in Local Transport requests since STMS configuration – Transport Routes yet to be setup with corresponding SAP Systems/Virtual System to release TRs and get Data files &Co files.We can setup STMS Transport routes and includes this note changes (objects) later in the new TR/Transport of Copies which can be created with Target System (Corresponding SAP System/Virtual System- Relevant Transport Route) to get data files and co files.
Released TR – Local Change Transport requests – Without Data/Co Files.
Repeat SUM failed process.
Backup system based on your scenarios accordingly.
SUM will replace kernel files even if existing kernel have same version.
Importing entries into control tables take several hours to complete.Don’t cancel/kill SUM/OS level processes. Even if SUM stopped due to network connection issue, Wait for the completion of the OS level process.
We could see R3trans import process completed successfully.As of now, /usr/sap/trans occupied 19G for update and /usr/sap/SID occupied 33G for ABAP and SUM Files.
We can start/resume SUM process with “Check Status Again”.
SUM Execution step completed successfully.Final à SUM Dir occupied 38G and trans Dir occupied 19 G – Total – 57G
We won’t face issues mostly in Post Processing steps.
We are installing new EHP8 ECC System with no transport provided during SWPM operations.
SUM Procedure completed successfully.
Errors requiring revision – “Create statement view “ACMAUTE639F7F4D8” could not be generated” can be ignored as per Note 2700577 – https://me.sap.com/notes/0002700577
We have successfully completed SWPM and SUM Operations.We can cleanup SUM Directory since operations completed. Select “Cleanup” from Menu (Available near Breakpoints)
Post cleanup, SUM Dir file size reduced from 38G to <1GB. /usr/sap/trans occupied 20G
Since all operations completed, we can change TNS, Listener Ora Files Owner from Oracle OINSTALL to ORAEC0 DBA as well as restart database via Oraec0 user. PATH – /oracle/EC0/19/network/log/listener.logPATH – /oracle/EC0/19/network/admin/* (especially TNS, Listener, SQLNET)PATH – Listener Socket Files Access – /var/tmp/.oracle/*Start Listener/DB Instance via ORADBA user
ORAEC0 DBA user has default SAP/ORACLE DB ENV Variables to connect DB/ Restart Listener without setting Env Variables manually as like Oracle user.
Check Point 7: SUM EXECUTION – EHP UPDATE WITH SAP NW Completed.
SYS INFO:
WE HAVE SUCCESSFULLY INSTALLED ERP EHP8 SP09 WITH ORACLE 19c (19.24) ON RHEL 8.8
Thanks for visiting !!!
#ATR (24) INFORMATIVE NOTE:Created this blog to provide information on how to install ECC EHP8 System with Oracle 19c Database.Please visit Uninstalling SAP System and Reuse SAP Server for new installation #ATR to have an overview of how to setup VM/OS from scratch for SAP.Please visit QUICK CATCHUPS ON TOP-20-SWPM/SUM ERRORS – SAP INSTALLATION ON AIX – ORACLE #ATR to have an overview of SWPM/SUM Errors.CHECK POINTS:PART 1:1) PREREQUISITE CHECK FOR INSTALLATION2) STACK XML FILE GENERATION IN MAINTENANCE PLANNER3) SWPM OPERATION [START] – INSTALLATION OF BASE PACKPlease refer link – END TO END INSTALLATION OF SAP EHP8 ERP SYSTEM WITH ORACLE DATABASE 19c ON RHEL 8.8 – PART 1 #ATRPART 2:4) ORACLE DATABASE INSTALLATION (IN MID OF SWPM)5) ORACLE PATCH UPDATE WITH POST INSTALLATION SCRIPT (IN MID OF SWPM)6) COMPLETION OF SWPM – INSTALLATION OF BASE PACKPlease refer link – END TO END INSTALLATION OF SAP EHP8 ERP SYSTEM WITH ORACLE DATABASE 19c ON RHEL 8.8 – PART 2 #ATRPART 3:7) SUM EXECUTION – EHP UPDATE WITH SAP NWCHECK POINT 7: SUM EXECUTION – EHP UPDATE WITH SAP NWNow, we are proceeding to perform SUM SP Update from EHP SP1 to SP9 with relevant updates of software components (includes ECC ERP, SAP NW as well).We can start SUM separately (manual) as well to complete EHP Update without need of SWPM since SWPM process completed. Make sure to provide same Stack file for SUM if started manually later for EHP & NW update.SWPM consider SUM Directory – /usr/sap/SID/SUM by default.We can also use other directory or make separate LVM for SUM path alone to delete and reclaim space once SUM Execution completed.In my case, I’m using /usr/sap FS itself since it’s test system and space will be increased accordingly.Logon SUM with SIDADM (EC0ADM) user.EX – https://servername:1129/lmsl/sumabap/EC0/doc/sluiMake sure to have atleast 55-65G free space in /usr/sap (includes trans/sumabap) directory to proceed update process.Also, provide full 777 access to downloaded Software files.You can download and upload notes manually if you are planning to do post installation steps (SAP Note Download Connectivity, SAP Support Portal) once completion of SUM process.All mentioned notes implemented in system. Repeat SUM failed process.Configuration Checks completed successfully.Checks completed successfully.Lock Development Environment.We can release our note implementation TR (changes) even if captured in Local Transport requests since STMS configuration – Transport Routes yet to be setup with corresponding SAP Systems/Virtual System to release TRs and get Data files &Co files.We can setup STMS Transport routes and includes this note changes (objects) later in the new TR/Transport of Copies which can be created with Target System (Corresponding SAP System/Virtual System- Relevant Transport Route) to get data files and co files.Released TR – Local Change Transport requests – Without Data/Co Files.Repeat SUM failed process.Backup system based on your scenarios accordingly.SUM will replace kernel files even if existing kernel have same version.Importing entries into control tables take several hours to complete.Don’t cancel/kill SUM/OS level processes. Even if SUM stopped due to network connection issue, Wait for the completion of the OS level process.We could see R3trans import process completed successfully.As of now, /usr/sap/trans occupied 19G for update and /usr/sap/SID occupied 33G for ABAP and SUM Files.We can start/resume SUM process with “Check Status Again”.SUM Execution step completed successfully.Final à SUM Dir occupied 38G and trans Dir occupied 19 G – Total – 57GWe won’t face issues mostly in Post Processing steps.We are installing new EHP8 ECC System with no transport provided during SWPM operations.SUM Procedure completed successfully.Errors requiring revision – “Create statement view “ACMAUTE639F7F4D8” could not be generated” can be ignored as per Note 2700577 – https://me.sap.com/notes/0002700577 We have successfully completed SWPM and SUM Operations.We can cleanup SUM Directory since operations completed. Select “Cleanup” from Menu (Available near Breakpoints)Post cleanup, SUM Dir file size reduced from 38G to <1GB. /usr/sap/trans occupied 20GSince all operations completed, we can change TNS, Listener Ora Files Owner from Oracle OINSTALL to ORAEC0 DBA as well as restart database via Oraec0 user. PATH – /oracle/EC0/19/network/log/listener.logPATH – /oracle/EC0/19/network/admin/* (especially TNS, Listener, SQLNET)PATH – Listener Socket Files Access – /var/tmp/.oracle/*Start Listener/DB Instance via ORADBA userORAEC0 DBA user has default SAP/ORACLE DB ENV Variables to connect DB/ Restart Listener without setting Env Variables manually as like Oracle user.Check Point 7: SUM EXECUTION – EHP UPDATE WITH SAP NW Completed.SYS INFO: WE HAVE SUCCESSFULLY INSTALLED ERP EHP8 SP09 WITH ORACLE 19c (19.24) ON RHEL 8.8Thanks for visiting !!! Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
