Sl No Activity List

1 Check the free space availability on /usr/sap/trans to accommodate

the patches
2 Sufficient space should be available in ORAARCH Filesystem
3
Check the space availability on Datbase and in SAPDATA Filesystems
4 Extend the tablespace if required
5 Get in touch with OS Team if sufficient space is not available in
/usr/sap/trans and SAPDATA Filesystems
6 Download the required support patches from SMP
7 Upload the support patches to the relevant system
8 Apply for the maintenance certificate if required
9 Check the Backup strategy of the Server (Disk/Tape)
10 Flash the message in SAP about the Downtime

11 Suspend the backup deletion CRONTABs if any

12 Raise the SR to DCO team to extend the retention of Tape, if there is

any tape backup
13 Schedule the Offline/Online Database Backup of the Server
14 Backup should be copied to the tape if required
15 Suspend the PR --> DR Sync before the activity starts
16 Suspend other DB/Arch Backups till the activity completes
17 Lock all the SAP users except service/communication/RFC
18 Suspend the Background Jobs
19 Upgrade the SPAM /SAINT to the latest
Start of Patching activity
ST PI ST API
20

21 SPAU/SPDD Adjustments
22 Release the Background Jobs
23 Run SGEN
24 Release the Locked Users

25 Reschedule the CRONTABs of backup and backup deletion

26 Start the PR --> DR Sync
27 Release for Functiona Testing
 PoA for Support Patch Upgrade
Action to be performed on system Team Responsible Downtime Status of the Activity
Preparation phase - Chicking prerequisites

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team

Service Market Place Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
Implementation phase - Activity phase
DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD WIPRO/ABG/DCO No
DEV/QA/PRD WIPRO/ABG/DCO
DEV/QA/PRD ABG/DCO No
PRD Wipro - Basis Team No
DEV/QA/PRD WIPRO/ABG/OS No
DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes

DEV/QA/PRD Wipro - Basis Team Yes

DEV/QA/PRD Wipro - ABAP Team Yes

DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes
Post Implementation phase
DEV/QA/PRD Wipro - Basis Team No
PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
or Support Patch Upgrade
Projected Duration (hrs) Actual Duration (hrs) Projected Start Date and Time
tion phase - Chicking prerequisites

0:30

1 day

0:30

mentation phase - Activity phase

0:20

0:15
0:15
0:15

0:15
20:00
0:20
ost Implementation phase
Projected End Date and Time Actual Start Date and Time Actual End Date and Time
Sl No Activity List

1 Check the space availability of Filesystem /usr/sap/trans in Quality and

Production
2 Run the report RSSPACECHECK to check the client size
3 Check the Database space availability in Quality server after the step-2
4 Check for Support Patch Levels on Source and Target Servers
5 Check and Enlist the open requests and the requests which are yet to be
transported to Production
6 Export of user master dump
7 Flash the message on Quality and Production servers

8 Scheduled backups should be suspended on Quality

9 Lock all the users to start the Export till the completion of the Export
10 Start of Export of Production client
11 Unlock the users in Production server post successful export
12 Transfer the Exported files from Production to Quality server
13 start Import process on Quality server
14 Start the Post-Processing
15 Import of Quality user master in Quality server
16 Post processing after the import of Quality user master
17 Reschedule the Backup of Quality server
 PoA for Client Copy
Action to be performed on system Team Responsible Downtime Status of the Activity
Preparation phase - Chicking prerequisites

Quality/Production Wipro - Basis Team No

Production Wipro - Basis Team No
Quality Wipro - Basis Team No
Quality/Production Wipro - Basis Team No

Quality Wipro - Functional Team No

Quality Wipro - Basis Team No
Quality/Production Wipro - Basis Team No
Implementation phase - Activity phase
Quality Wipro/DCO/OS No
Production Wipro - Basis Team Yes
Production Wipro - Basis Team Yes
Production Wipro - Basis Team Yes
Quality/Production Wipro - Basis Team No
Quality Wipro - Basis Team Yes
Quality Wipro - Basis Team Yes
Quality Wipro - Basis Team Yes
Quality Wipro - Basis Team Yes
Quality Wipro/DCO/OS No
A for Client Copy
Projected Duration (hrs) Actual Duration (hrs) Projected Start Date and Time
phase - Chicking prerequisites

1:00
4:00
0:30
1:00

1:00
0:10
ation phase - Activity phase
0:30

0:30
1:00

1:00
1:00
0:30
Projected End Date and Time Actual Start Date and Time Actual End Date and Time
Sl No Activity List Action to be performed on system

1 The Quality and Production servers' SAP and Database

version should be same Quality
2 Take the snapshots of SCC4, RZ04, STMS, SM59, DB13 Quality
3 Export of Quality user master, RFCs, Printer config Quality
4 Check the space on Quality server Quality
5 Space should be increased on Quality server if required
after the step-4 Quality
6 Check and enlist the open transport requests which are yet
to be transported in Production Quality
7 Offline Backup of the Quality server Quality
8 Online/Offline Backup of the Production server Production
9 Take the control file backup on Production server Production

10 Mounting the Backup disk from Production to Quality for

restoration / Mount the tape to Quality server Production/Quality
11 Flash the message on Quality server Quality
12 Copy the Backup summary log and detailed log and control
file from Production to Quality Production/Quality

12 Suspend the scheduled backups on Quality server Quality

13 Suspend the Backup deletion CRONTABs if any in
Production and Quality server Production/Quality
14 Change the init<SID>.sap file accordingly Quality
15 Stop the SAP and DB on Quality server Quality
16 Start the restoration of Production backup on Quality using
brtools Quality
17 Alter the control file and generate the same on Quality
server Quality
18 Transfer the required archive logs for database recovery
from Production to Quality Quality
19 Start and open the Database Quality
20 Maintenance of Temp Tablespace Quality
21 Shutdown and restart the Database Quality
22 run commnads of ssfs in sid adm level to change SAPSR3
password Quality
23 Start the Oracle Listener Quality
24 Start the SAP Application Quality

25 Apply the SAP License Quality

26 Perform the post-database copy activities in SE06 Quality
27 Reconfigure the STMS Quality
28 Import the RFCs and Printer config Quality
29 Import the SAP Profiles in RZ10 Quality
30 Reshedule the Standard Jobs Quality
31 Run the BDLS Quality
32 Import the Qulaity server master Quality
33 Run the Database statics Quality
34 Perform the Health check before releasing for Functional
testing Quality
35 Reschedule the backup and CRONTABs if suspended in
step-12 & 13 Production/Quality
36 Release the system for Functional Testing
 PoA for Database (QA) Refresh
Team Responsible Downtime Status of the Activity Projected Duration (hrs)
Preparation phase - Chicking prerequisites

Wipro - Basis Team No

Wipro - Basis Team No 3:00
Wipro - Basis Team No
Wipro - Basis Team No

OS Team/ABG Team

Wipro - Functional Team No

Wipro/ABG/DCO Yes
Wipro/ABG/DCO
Wipro - Basis Team No 0:10

ABG/DCO/OS No
Wipro - Basis Team No 0:10

Wipro - Basis Team No 0:15

Implementation phase - Activity phase
Wipro/ABG/DCO No
0:30
Wipro/ABG/DCO No
Wipro - Basis Team No 0:30
Wipro - Basis Team No 0:30

Wipro - Basis Team Yes

Wipro - Basis Team Yes 0:20

Wipro - Basis Team Yes

Wipro - Basis Team Yes 0:30
Wipro - Basis Team Yes 0:30
Wipro - Basis Team Yes 0:30

Wipro - Basis Team Yes 0:30

Wipro - Basis Team Yes
Wipro - Basis Team Yes
Post Implementation phase
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team
Wipro - Basis Team

Wipro - Basis Team

Wipro - Basis Team

efresh
Actual Downtime (hrs) Projected Start Date and Time Projected End Date and Time
requisites

ty phase

ase
Actual Start Date and Time Actual End Date and Time
Sl No Activity List

1 Check the free space availability on /usr/sap/trans to accommodate

the patches
2 Sufficient space should be available in ORAARCH Filesystem
3
Check the space availability on Datbase and in SAPDATA Filesystems
4 Extend the tablespace if required
5 Get in touch with OS Team if sufficient space is not available in
/usr/sap/trans and SAPDATA Filesystems
6 Download the required support patches from SMP
7 Upload the support patches to the relevant system
8 Apply for the maintenance certificate if required
9 Check the Backup strategy of the Server (Disk/Tape)
10 Flash the message in SAP about the Downtime

11 Suspend the backup deletion CRONTABs if any

12 Raise the SR to DCO team to extend the retention of Tape, if there is

any tape backup
13 Schedule the Offline/Online Database Backup of the Server
14 Backup should be copied to the tape if required
15 Suspend the PR --> DR Sync before the activity starts
16 Suspend other DB/Arch Backups till the activity completes
17 Lock all the SAP users except service/communication/RFC
18 Suspend the Background Jobs
19 Upgrade the SPAM to the latest
Start of Patching activity
BASIS, ABAP
SAP_APPL, SAP_AP
20

21 SPAU/SPDD Adjustments
22 Release the Background Jobs
23 Run SGEN
24 Release the Locked Users

25 Reschedule the CRONTABs of backup and backup deletion

26 Start the PR --> DR Sync
27 Release for Functiona Testing
 PoA for Support Patch Upgrade
Action to be performed on system Team Responsible Downtime Status of the Activity
Preparation phase - Chicking prerequisites

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD Wipro - Basis Team

Service Market Place Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
Implementation phase - Activity phase
DEV/QA/PRD Wipro - Basis Team No

DEV/QA/PRD WIPRO/ABG/DCO No
DEV/QA/PRD WIPRO/ABG/DCO
DEV/QA/PRD ABG/DCO No
PRD Wipro - Basis Team No
DEV/QA/PRD WIPRO/ABG/OS No
DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes

DEV/QA/PRD Wipro - Basis Team Yes

DEV/QA/PRD Wipro - ABAP Team Yes

DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes
DEV/QA/PRD Wipro - Basis Team Yes
Post Implementation phase
DEV/QA/PRD Wipro - Basis Team No
PRD Wipro - Basis Team No
DEV/QA/PRD Wipro - Basis Team No
or Support Patch Upgrade
Projected Duration (hrs) Actual Duration (hrs) Projected Start Date and Time
tion phase - Chicking prerequisites

0:30

1 day

0:30

mentation phase - Activity phase

0:20

0:15
0:15
0:15

0:15
20:00
0:20
ost Implementation phase
Projected End Date and Time Actual Start Date and Time Actual End Date and Time
Sl No Action to be
Activity List performed on system

1 Check all the Initialization Parameters on both DC & DR DC/DR

2 Verify the DR server DR
3 Verify the Managaed Recovery is running on the DR DR
4 Verify the DC --> DR sync process is on and ensure no archive gap DC/DR
5 Ensure to have a proper Database/Archive backup of DC DC
6
Oracle Listener is running on DC/DR, and both are able to ping vice versa DC/DR
7 Check to have successful backup of DC DC

8 Stop the cluster Fail-over mechanism DC

9 Lock the SAP users DC
10 Transaction verifiaction on DC prior to DC --> DR switch DC
11 Stop the SAP on Application servers/CI - Not DB DC
12 Ensure the DC --> DR is in Sync DC/DR

13 Check the Switchover status on DC DC

14 Start the Switcover process on DC - Make DC as Standby (DR) DC
15 Shutdown the Database and start in nomount DC
16 Alter the DC Databaes to Standby DC
17 Make the DC Database to Managed Recovery DC
18
Check Database Role of DC and enseure it is switched to Standby (DR) DC
19 Check the Database Role and Switchover status on DR DR
20 Check the Log sequence number on DC/DR DC/DR
21 Switch the DR to Primary (DC) DR
22 Open the Database on DR (Present DC) DR
23 Shutdown and startup the Database DR
24 Switch the logs on DR (Present DC) DR
25 Check the Sync after step-22 on both DC/DR DC/DR
26 Start the SAP Application on DR DR
27 Unlock the users DR

28 Lock the SAP users DR

29 Transaction verifiaction on DR prior to DR --> DC switch
30 Stop the SAP on Application servers/CI - Not DB DR
31 Ensure the DC --> DR is in Sync DC/DR
32 Check the Switchover status on DR (Present DC) DR
33 Start the Switcover process on DR - Make DR as Standby DR
34 Shutdown the Database and start in nomount DR
35 Alter the DR (Present DC) Databaes to Standby DR
 36 Make the DR (Present DC) Database to Managed Recovery DR
37 Check Database Role of DR (Present DC) and enseure it is switched to
Standby (DR) DC
38
Check the Database Role and Switchover status on DC (Present DR) DC
39 Check the Log sequence number on DC/DR DC/DR
40 Switch DC (Present DR) to Primary (DC) DC
41 Open the Database on DC (Present DR) DC
42 Shutdown and startup the Database DC
43 Switch the logs on DC (Present DR) DC
44 Check the Sync after step-40 on both DC/DR DC/DR
45 Start the SAP Application on DC DC
46 Unlock the users DC
Release the DC to users and Functional Tesing
 PoA for DR Drill

Status of the Projected Actual Duration

Team Responsible Downtime Activity Duration (hrs) (hrs)
Preparation phase - Chicking prerequisites
Wipro - Basis Team No
Wipro - Basis Team No
Wipro - Basis Team No
Wipro - Basis Team No
4:00
Wipro - Basis Team No

Wipro - Basis Team No

Wipro - Basis Team No
Implementation phase - Activity phase
Cluster/OS Team No
Wipro - Basis Team Yes 0:15
Business Yes 0:15
Wipro - Basis Team Yes 0:30
Wipro - Basis Team Yes 0:15
Implementation phase - Switchover DC to DR
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes

Wipro - Basis Team Yes

0:30
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes 0:30
Wipro - Basis Team Yes 0:15
Implementation phase - Switchback DR to DC
Wipro - Basis Team Yes 0:15

Wipro - Basis Team Yes 0:30

Wipro - Basis Team Yes 0:15
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes

0:30
Wipro - Basis Team Yes

Wipro - Basis Team Yes

0:30
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes
Wipro - Basis Team Yes 0:30
Wipro - Basis Team Yes 0:15
 Projected Start Date and Time Projected End Date and Time Actual Start Date and Time

DC
Actual End Date and Time
 Kernel Version Upgrade from 700 to 720
SNO Activity Action to Be Performed on
1 Check the File System Space DEV
2 Indentify the Target Kernel Release According to OS (HPUX) DEV
3 Check Any OS (HPUX) kernel Dependecies DEV
Check If Any OS Patches,Kernel,file Sets requied Contact with OS team
4 need to Finish before start the Activty (Optional) DEV
5 Add all required patches in Download baset Service Market Place
6 Download and Copy the same to Target Server DEV
7 Take Backup of existing kernel DEV
8 Stop SAP DEV
8 Start Kernel Upgrade DEV
9 Finalize Kernel upgrade at OS level & SAP level DEV
10 Run Szen (Shedule at Less Business hours) DEV
database (SAP, table SVERS) 700

operating system
HP-UX B.11
de from 700 to 720
Team Responsible Downtime Status of the Activity Projected Duration (hrs)
Wipro No Completed 1 Hr
Wipro No WIP 2 Hrs
Wipro No WIP 6 Hrs

Wipro/Binani Yes WIP

Wipro NO WIP 30 Min
Binani NO
Wipro NO 2 Hrs
Wipro Yes
Wipro Yes 4 Hrs
Wipro Yes
Wipro Yes 15 Hrs
 Sl No
Preparation phase - Chicking prerequisites
1
2
3
6
7
Implementation phase - Activity phase
8
9
10
11
12
Activity List

Check the space availability of Filesystem /usr/sap/trans

Run the report RSSPACECHECK to check the client size
Check the Database space availability in Quality server after the step-2
Export of user master dump
Flash the message on quality system or development

Scheduled backups should be suspended on Quality

Login as target client to perform client copy
Make sure two BG jobs are available
Make sure Oraarch is below 80 %
Check scc3 sm37 sm50 for client copy monitoring
Action to be performed on system Team Responsible DowntimeStatus of t Actual Dura
Projected

Quality Wipro - Basis Team No

Quality Wipro - Basis Team No
Quality Wipro - Basis Team No
Quality Wipro - Basis Team No
Quality Wipro - Basis Team No
Quality
Quality Wipro/DCO/OS No
Quality Wipro - Basis Team Yes
Quality Wipro - Basis Team Yes
Quality Wipro - Basis Team Yes
Projected Actual Sta Actual End Date and Time