****** Not Applicable in Sumitomo ******
T-Code: /n/SAPAPO/OPT09
4 Start Uptime 4.1 Uptime PART I
4.1.1 Manual Activities
4.1.1.1 Check/Configure Operation Mode (RZ04)
Call transaction RZ04 to check the definition of your operation modes. Delete the invalid operation modes in case if it exists. If operation mode contains names of servers other than those belonging to the system, problems may arise in the background interface in some phases.
The jobs may be released, but not set as active (in theory, this affects all jobs scheduled to start on a specific server and triggered by an event).
If the SAP instance on which you want to update EHP2 is not entered in an operation mode, create the operation mode for the installation as follows:
Call transaction RZ04 -> Choose Operation mode Create -> Enter a name for the operation mode, for example:
“EHP2” -> enter a short description and then save the operation mode.
Make sure that the instance required for the installation has been started up. Position the cursor on the new operation mode and choose Operation mode Maintain instances -> Instances/OP modes -> Choose Settings based on act. Status New Instances Create. This displays all instances and their current configuration -> Choose Save.
Call transaction SM63 to enter the operation mode you have defined as an active operation mode for 24hours (select Normal operation (24 hours)).
T-Code: RZ04
T-Code: SM63
4.1.1.2 Check Additional SAP Notes
SAP Note 1843966 - Oracle: Add. Information – Software Update Manager 1.0 SP08
Apply all recommended parameters
Sumitomo, we are on Oracle 11.2.0.3.0, we didn’t find any issue and necessity to apply the Patch Set.
4.1.1.3 Verify No Entry in Table TBATG (SE16)
Please check and ensure that there is no entry in table TBATG. The TBATG table should be empty to ensure that there is no error during DB conversion. If there are entries in the table, please ensure that they are rectified or processed.
4.1.1.4 Verify Clean Up Activities Status
If any outdated entries output from the below transaction code will have to be sent to Functional Team for their verification.
T-Code: SM12
T-Code: SM13
T-Code: SMQ1
T-Code: SMQ2
4.1.1.5 Starting SUM Tool
The installation tool was already extracted and tested in preparation phase and now you will need to execute the tool before starting the Uptime.
To start the installation program (in background), login as <SID>adm i.e., S2Padm and enter the command Command:
su – s2padm
cd /<SUM_DIRECTORY>/SUM i.e., cd /usr/sap/S2P/SUM ./STARTUP &
4.1.1.6 Starting the Installation GUI
To start the installation GUI, login as <SID>adm to a VNC session or xwindows software i.e., Xmanager.
Command:
su – s2padm
cd <SUM_DIRECTORY>/sdt/exe ./DSUGui
4.1.2 Initialization Phase
Name = administrator
Password = ****** [Mentioned in the Secure File]
Phone or Email = [email protected]
Browse to the XML file for Upgrade purpose.
Click NEXT to continue with the Extraction Phase
**** Initialization Phase Completed Successfully ****
4.1.3 Extraction Phase
Passwords stored in secure file and maintained separately and not part of this cookbook.
Provide the Password for - DDIC & SYSTEM [Password Maintained in the Secure File]
As the existing SPAM version is lower it is mandatory to comply with the latest SPAM level requirement to avoid any unwanted errors during upgrade phases.
As the SPAM Patch level 50 is already extracted and placed in the /usr/sap/trans/EPS/in, select the Import Spam Version 50 and Continue.
Provide the DVD Mount points as below:
/misc/UpgradeDump/51041986_SLCONT700/Kernel_7.20_EXT_AIX_z_OS_OS400_LNXz_
Click Continue
At the end of the extraction phase, the brconnect [DBAtools] is quite old in version, please update with the latest patch level of dbatools.
Login to a new putty session and execute the below steps to correct the above error:- Commands:
At the end of the extraction phase, the required R3trans exe is quite old in version, please update with the latest patch level file of R3trans in the Upgrade Directory path /usr/sap/S2P/SUM/abap/exe
Click NEXT
Close the Pop-up
Click NEXT to continue with Configuration Phase
***** Extraction Phase Completed Successfully *****
4.1.4 Configuration Phase
If you choose the option Switch expert mode on, you can adapt additional tool configuration options during the update.
If the option is chosen, the Software Update Manager always displays a Support Package overview in phase BIND_PATCH, even if manual adjustment is not necessary. You can overrule the Support Package level, which is derived from the stack configuration file (stack.xml).
You can change the automatically generated instance number for the shadow instance.
You can use a remote shadow instance.
You can remove installed languages or their components, for which the Software Update Manager does not find an appropriate DVD.
The Software Update Manager asks you if you want to use saved profiles from a previous update for the shadow system.
Continue
Continue without adding CD’s
Check if newer versions
Continue
Incase of Dev & QA there was no SPDD & SPAU Transports from Trail upgrade, Both SPDD & SPAU were created locally in the system due to difference in SPDD & SPAU of DEV & Quality
Note:-
For Production Upgrade, SPDD will be carried from Quality system created SPDD TR i.e., [ SC7K900024 IBM_ABAP SCM Upgrade: SPDD Adjustments ] or can be created locally in Production Shadow Instance.
For Production Upgrade, SPAU will be Transported immediately after Upgrade and the SPAU Transport of quality will be used [ SC7K900026 ANTHONY SCM Upgrade: SPAU Adjustments ].
ABAP Shadow Instance Details :-
Continue
Close
Click NEXT to continue with Checks Phase
***** Configuration Phase Completed Successfully *****
4.1.5 Check Phase
Carryout the Section A of the Program /SAPAPO/OM_LC_UPGRADE_70 This Program is mandatory for Live Cache Upgrade Preparation.
4.1.5.1 Live Cache Upgrade Preparation
Login to Client 800
SE38 /SAPAPO/OM_LC_UPGRADE_70
A).
Logs or data from previous upgrades that is still contained in the download table can cause problems. It is therefore recommended that you delete this data.
Click Yes
B).
To minimize the upgrade time, you should ensure that only essential data is transferred.
Therefore, delete unnecessary planning versions. Make sure that you check all liveCache-relevant clients.
Check with Functional which planning we can delete
Delete all other planning versions except 000 / 001 & 002. Please consult with the SCM Functional team on deletion of other planning version and with their consent.
Execute
Execute
Execute
Execute
Execute
Execute
C).
If you upload inconsistent transaction data from the database following an upgrade, this can lead to various problems.
You should therefore perform a consistency check before the upgrade using transaction /SAPAPO/OM17. This check compares the liveCache data with the data in the database. If necessary, correct the inconsistent data.
You do not have to perform the consistency check immediately before the upgrade, but the closer you run this check to the time of the upgrade, the more current the results will be.
Make sure that you perform the consistency check in each liveCache-relevant client for all planning versions.
All planning versions selected
In-case there is Inconsistency resulted as below please follow the steps mentioned:-
Note 1825133 - An error /SAPAPO/OM_SYNC001 in liveCache consistency check
D).
Due to a program error in some older COM or liveCache builds, you may have faulty APS data in your dataset. (APS = Advanced Planning & Scheduling. This means data belonging to the applications SNP, PP/DS, ATP, and TP/VS).
If you do not correct this data, you will encounter errors when uploading the liveCache data.
You can use the program /SAPAPO/OM_CHECK_LIVECACHEDATA to check whether you have faulty data in the system.
You should delete any faulty orders and then use the connected systems to import them again after the upgrade, if required.
To delete orders in older releases, select the field "Delete Using DELETE Command" on the selection screen. If the report finds faulty orders, select the orders that you want to delete and enter DELETE in the command field.
One by One
E).
You need to analyze the SAP liveCache and the LCA builds well before the upgrade as well as directly after the upgrade. To do this, you can use transaction the /SAPAPO/OM13, which is called when you choose the button for this step. Pay special attention to whether red lights are displayed. An information pushbutton next to the red lights explains how you can eliminate them.
Since only a limited number of partial checks are performed in the overview, a green light is never displayed.
F).
Not Applicable in Sumitomo’s Case
The time that elapses between this check and section B of the report should be as short as possible. Once this step has been executed successfully, you must no longer make changes to planning areas (for example, changes to initialization horizons of planning areas, changes to initialization horizons of key figures, or changes to planning object structures). If you make changes to planning areas after performing this step, you must execute this step again.
Execute program /SAPAPO/TS_LCM_REORG in repair mode for each planning version. The program checks the consistency of the Demand Planning data stored in liveCache in comparison with the Demand Planning data in the SAP APO database.
One of the main tasks of the program is to check whether each object in liveCache has a corresponding object in the
Repeat for all planning versions
Execute program /SAPAPO/TS_LCM_REORG_SNP in repair mode for each initialized planning area. Note that planning areas can be initialized for multiple planning versions.
Repeat for each planning
The program /SAPAPO/TS_LCM_CONS_CHECK_ALL performs various checks on the integrity of the Demand Planning and Supply Network Planning data stored in the SAP APO database. It also checks the consistency of the corresponding data in liveCache. If it reports inconsistencies, you must use program /SAPAPO/TS_LCM_CONS_CHECK to manually rectify them for the relevant planning areas.
/n/SAPAPO/TR32
/n/SAPAPO/MSDP_ADMIN
The program /SAPAPO/OM_TS_LCCONS checks whether the objects in liveCache have the correct networking and it also checks for logical consistency and for the consistency of the time series data.
Execute the program in check mode with all three types of consistency check for all existing planning versions. Here can you can use parallel processing for each planning version.
If the program reports errors, stop the entire process and open an OSS message under the component BC-DB-LCA-DP.
G).
Not Applicable in Sumitomo’s Case
If a resource time stream was incorrect before the upgrade, the dates/times of the activities that consume a resource can change after the upgrade.
An incorrect time stream might occur if a user changes the factory calendar in Customizing that the resource uses.
This step ensures that the program /SAPAPO/OM_UPGR_TSTR_CHECK is executed automatically in the background.
For this, one background job is created per planning version in each liveCache-relevant client. This job checks and corrects the time streams.
You can also perform partial checks by calling the program directly and making a relevant selection.
You can display the log in the application log with object APO, subobject = UPGRADE.
Refresh
Continue once the Section A is completed for all Clients.
Select Yes and continue
S2PK901809 BC-ASHISH Upg:tcode /ASU/Upgrade Note 875986-ChecksPhase Do Not Trspt
Continue after Transport is Import in further QA & Prd upgrade
Software Update Manager has flagged that a new tablespace (for shadow instance) needs to be created with the storage size. Please note that this storage size will varies according to the current system database size.
Create Oracle Tablespace PSAPSR3731
Increase the Tablespace PSAPSR3731 as below with oraS2P
Click Next
Click Next to continue with the Pre-processing Phase
***** Checks Phase Completed Successfully *****
4.1.6 Pre-processing Phase Part I
******** TAKE NOTE SPECICIALLY IN DEVELOPMENT SYSTEM *********
T-Code: SE10
Release all the above listed transports
Check Again Continue
If the above screens appear like above, please check with SCA & IBM Functional team if there are transports related to them as they will have to release the transports.
Locked transport requests should not appear in Productive System.
Lock Now and Continue [This Step will Lock the Development]
We have reached the sub-phase MAIN_SHDRUN/ACT_UPG and we will generate the SPDD list and pass them to ABAP to make the adjustment.
Before ABAPer can make the adjustment, we will need to setup the environment access in the shadow instance.
Login to Shadow Instance and Create an ABAP User ID – IBM_ABAP
After setting up the access environment, proceed to next activity in Section 4.3 SPDD adjustment.
4.1.6.1 End Uptime PART I
4.1.6.2 SPDD Adjustment
SPDD list is generated and handed to ABAP to perform the adjustment.
Once ABAP Team has confirmed that the SPDD adjustment has completed, we will proceed to the next activity in Section 4.4 Start Uptime Part II
4.1.6.3 Start Uptime Part II
We will continue from the Pre-processing phase after ABAP Team has confirmed SPDD adjustment.
4.1.7 Pre-processing Phase Part II
We have reached the end of uptime at sub-phase MAIN_DTTRANS/SUBMOD_DOWNTRANS/DOWNCONF_DTTRANS.
DO not click on ‘Actions completed’ button
Before we proceed further, we will have to perform the next activities before we start the downtime. Please refer to Section Start Downtime.
4.1.7.1 End Uptime Part II
5 End Uptime
This is the phase where we have completed our uptime activities and most of the pre-processing phase. At this stage, we are ready to go to downtime phase. Before we start the downtime, we will need to perform the next step of isolating the systems. Please refer to the Project Plan.
6 Verify Backup
Before we proceed with the downtime phase, ensure that the scheduled online and archive log backup are completed successfully and we are able to perform a point-in-time database recovery when necessary.
If database is not completed successfully, please run the backup again before entering downtime phase. This is to ensure that the database can be recovered till this point in time.
Please also ensure that the successful backup is stored separately and is not overwritten.
7 Start Downtime
7.1 Start External Isolation
This step will be performed by IBM. The steps involve will include the below:-
1) To ensure that external scheduled job is completed successfully before the downtime and stop external jobs which will run across the downtime period.
2) The other is to stop business communication channel to and from ERP & other External System viz., LES 3) IBM Basis Team will disable below RFC for APO and ECC with guidance from the isolation team (SCM).
NOTE: Please refer to project plan for the activity.
7.2 End External Isolation
7.3 Start Internal Isolation
Internal Isolation activities will be performed by IBM. During this time, there may be activities that need to be performed on OS or SAP level. Please refer to the project plan for the activity.
7.3.1 Suspend Batch Jobs (Program: BTCTRNS1)
T-Code: SE38 execute report BTCTRNS1
T-Code: SM37
NOTE: Check for any active jobs, please refer to project plan for the sequence task to review and kill them.
7.3.2 Lock All SAP Users (refer to Project Plan)
This procedure will be performed by BASIS. Please refer to Project Plan. User should be locked in all client in case of Production only one client.
Client 800
7.3.3 Stop Active Users’ Session (refer to Project Plan)
This procedure is to stop users’ session which are still active and logon before Basis locked all users. This is to prevent users from updating the system.
7.3.4 Disable RFC Destinations
Sumitomo’s case we didn’t executed this step
To disable all the RFC destinations, a script is executed at the database level (login as oraS2P and run sqlplus). Syntax of the SQL script is as follows:
Command:
su – oras2p sqlplus /nolog connect / as sysdba;
update sapsr3.rfcdes set rfcoptions=replace (rfcdes.rfcoptions, 'H=', 'H=SCM_Trial.') where rfcoptions like '%H=%' and rfcoptions not like '%H=dumm%' and RFCDEST not like '%SAP%' and RFCDEST not like '%TMS%';
commit;
The below screen shows the before and after results of the target host of one RFC Execute /$sync
7.3.5 Disable SMTP Node and FAX (SCOT)
This step is to disable the sending of email from SAP system. Uncheck the Node in use button.
Carry out this setting in all relevant clients of the upgrading system.
7.3.6 Disable Outbound Queue (Program: RSTRFCQ1)
7.3.7 Disable Inbound Queue (Program: RSTRFCI1)
7.3.8 Stop CCMS
To stop the CCMS, execute below steps:
Command:
su – s2padm
sapccm4x -stop pf=/sapmnt/S2P /profileS2P_DVEBMGS00_scap02
7.3.9 Stop Solution Manager Agent
To stop the Solution Manager Agent, execute the command (logon as smdadm):
Command:
cd /usr/sap/SMD/<SID>/
./smdstop.sh
7.3.10 Check and Stop All Active Batch Jobs (SM37/SM66)
This step is to check and stop all active batch jobs which are still running.
7.3.11 Check and Clear Update Requests (SM13)
You will need to clear the queue because the SUM tool will stop and will not proceed further until you have cleared them.
7.3.12 Check and Clear Lock Entries (SM12)
You will need to clear the queue because the SUM tool will stop and will not proceed further until you have cleared them.
7.3.13 Check and Clear Mass Processing (SE14)
7.3.14 Check and Clear Outbound Queue (SMQ1)
You will need to clear the queue because the SUM tool will stop and will not proceed further until you have cleared them.
For SAP system with more than 1clients, please logon to the client and delete all queues.
7.3.15 Check and Clear Inbound Queue (SMQ2)
You will need to clear the queue because the SUM tool will stop and will not proceed further until you have cleared them.
7.3.16 Check for unprocessed logistics extraction data (Program: RMCEXCHK)
We will need to clear the structure if the above screen appears by executing program RMCSBWSETUPDELETE for each of the structure number highlighted in the list. Go to SE38 and execute
Program: RMCSBWSETUPDELETE
Run the program RMCEXCHK again to ensure that all status is green.
7.3.17 Check and Stop Active User Session (AL08/SM04)
This step is to check and stop any active user (not authorized users) still logged into the system.
7.3.18 Disable Database Backup Job
Disable regular backup Schedule by informing SCA IT team
7.3.19 Shutdown SAP Application Servers (stopsap)
This procedure is executed for production system if any additional App servers.
Logon to all dialog instances as <SID>adm and shutdown the instance including the saposcol and sapstartsrv. Ensure that there is no sap processes running by executing ps –ef|grep sap.
Command:
stopsap D<nr>
saposcol –k (DO not execute this command the kernel is 720)
sapcontrol –prot NI_HTTP –nr <instance number> -function StopService
7.3.20 High Availability
We will use the ASCS standalone enqueue server during upgrade.
7.3.21 High Availability (Disable HA Clustering Process)
This procedure is executed by SCA UNIX administrator.
The setup of the clustering is based on HACMP script which will monitor the heartbeat of the 2 clustered nodes (Node A and Node B) and failover will only take place when the first node (Node A) is down (where ASCS00, CI and Database is running).
The HACMP script does not monitor critical processes (example ASCS and oracle pmon) and will not failover if we
The HACMP script does not monitor critical processes (example ASCS and oracle pmon) and will not failover if we