SAP Planning: Best Practices in Implementation Live

Checklist Cutover & Going

Basis Cutover Background Information

Leverage this checklist to cutover from the S15 (Staging) to the P20 (Production) system. At a high level the procedure involves a homogeneous system copy geared to ensure that all data (both development/master and customizing) are transferred to the production environment. It is assumed here that both Staging and Production are clustered in a W2KAS environment, running MSCS and Oracle Failsafe. Oracle 8.1.7 is assumed as well, with an SAP Basis release of 4.6C. Note that this cutover process requires data/configuration clean up after the system has been copied. At a high level, the process unfolds as follows: Prepare the S15 database for export Export the S15 database Import the P20 database from the exported files Clean up the P20 system after the data has been imported Copy the original S15-151 client to P20-020 Create the users in the P20-020 system Setup DBA and functional jobs. Proactive maintenance steps Check for any errors and open to core team members

Prepare the S15 database for export (2 hours)

1. 2. 3. 4. 5. 6. Post a system message on S15 using /nSM02, detailing the outage required for database export. Delete all pending or cancelled update requests using transaction SM13. Execute transaction SE16, view table contents of VBDATA, and verify that all updates were successfully deleted. Delete cancelled and finished background jobs using transaction SM37. Check TEMSE consistency and delete inconsistent objects using transaction SP12. Execute any special jobs related to data dependencies.

SAP Planning: Best Practices in Implementation Live

Export the S15 database (3 hours)
7. 8. Login to the S15 instance as S15ADM.

Checklist Cutover & Going

Using the cluster administrator, move all groups to S15 Database Server (Node A) for execution. Wait until all groups and resources are back online before continuing to the next step. Using the cluster administrator, take the SAP R/3 S15 resource offline. This does not include the disk or network resources within the SAP-R/3 S15 group. Wait until the SAP R/3 S15 resource status changes to offline.

9.

10. If any application servers are running in S15, these should be shutdown for the full duration of the export. 11. Copy the file DBEXPORT.R3S.ORIG to DBEXPORT.R3S. These files are located in the C:\users\S15adm\install directory. If the DBEXPORT.R3S.ORIG does not exist, it must be copied from the SAP R/3 KERNEL CD for release 4.6C SR2. 12. Execute the program R3SETUP.EXE from the C:\users\S15adm\install directory. 13. Select the DBEXPORT.R3S file to be used as the input parameter file. 14. The following parameters should be specified when prompted:

Parameter
SAP System Name Instance Number Directory for SAP System Domain Name of Central Instance Host Database system name Character Set Name of Oracle home Installation Style Operating System for target Database of target Directory for export files Update statistics Split STR and EXT files for R3LOAD Number of parallel processes Maximum size of export files

Value
S15 15 I: US_SAP S15cidb S15 WE8DEC S15817 Old Style I386 Oracle O:\Export Quick and Estimated NO 8 (assumes 8-CPU DB server) 2000

SAP Planning: Best Practices in Implementation Live

Checklist Cutover & Going

15. The database will now be exported. The anticipated run time is 2 hours from start to finish. Errors and warning can be viewed using the R3SETUP log window. The Windows task manager can be used to view activity on the system to ensure processes are still running. 16. When the export is completed, move the CLUSTER and SAP-R3 S15 group to S15 CI node (cluster node B) for execution. 17. Bring all groups online and verify that all resources are online. 18. Login to the S15 system using SAPLOGIN from any desktop computer and verify that system accordingly.

Import the P20 database from the exported files (6 hours)

19. Login to the P20CI system as P20ADM. 20. Using the cluster administrator, move all groups to P20 CI for execution. Wait until all groups and resources are back online before continuing to the next step. 21. Using the cluster administrator, take the SAP R/3 P20 resource offline. This does not include the disk or network resources within the SAP-R/3 P20 group. Wait until the SAP R/3 P20 resource status changes to offline. 22. Using the cluster administrator, take the OracleP20817TNSListenerFslP20ora and P20.WORLD resources offline. This does not include the disk or network resources within the OracleP20 group. Wait until both resource status changes to offline. 23. Copy the file DATABASE.R3S.ORIG to DATABASE.R3S. These files are located in the I:\users\P20adm\install directory. If the DATABASE.R3S.ORIG does not exist, it must be copied from the SAP R/3 KERNEL CD for release 4.6C SR2. 24. Modify the DATABASE.R3S file so that the STEP section between 200 and 300 looks as follows: (any additional steps should be removed) 190=R3DBSAPENVIRONMENT_NT_IND 200=R3DBUSERENVIRONMENT_NT_IND 230=DBINITORACREATE_NT_ORA 240=DBINITORAMODIFY_NT_ORA 250=DBLISTENERSTOP_NT_ORA 290=DBLISTENERSTART_NT_ORA 300=DBCONVTPLFILES_IND_ORA 25. Delete the following directories (including sub-directories) i. J:\Oracle ii. K:\Oracle iii. L:\Oracle

SAP Planning: Best Practices in Implementation Live

iv. M:\Oracle v. N:\Oracle

Checklist Cutover & Going

26. Start the following services (NOT from the W2KAS Cluster Administrator) i. OracleServiceP20 ii. OracleP20817TNSListenerFslP20ora 27. Update the local host file, add the following entries: 179.165.221.12 179.165.221.11 179.165.221.10 P20cidb P20ora P20cluster

28. Map the network drive Y: to \\S15cidb\O$\Export. 29. Browse to the \DB\ORA directory and open the file DBSIZE.TPL (Backup original file first!) 30. Update the file DBSIZE.TPL as follows:
PSAPROLL=@SAPDATA1@;2000!@SAPDATA1@;2000 PSAPTEMP=@SAPDATA1@;2000 PSAPSTABI=@SAPDATA5@;2000!@SAPDATA5@;2000!@SAPDATA5@;2000!@SAPDATA5@;2000!@SAPDATA5@;2000 PSAPSTABD=@SAPDATA4@;2000!@SAPDATA4@;2000!@SAPDATA4@;2000!@SAPDATA4@;2000!@SAPDATA4@;2000 PSAPBTABI=@SAPDATA3@;2000!@SAPDATA3@;2000!@SAPDATA3@;2000!@SAPDATA3@;2000!@SAPDATA3@;2000! @SAPDATA3@;2000 PSAPBTABD=@SAPDATA2@;2000!@SAPDATA2@;2000!@SAPDATA2@;2000!@SAPDATA2@;2000!@SAPDATA2@;2000! @SAPDATA2@;2000 PSAPPOOLI=@SAPDATA1@;2000! @SAPDATA1@;2000 PSAPPOOLD=@SAPDATA5@;2000! @SAPDATA5@;2000 PSAPCLUI=@SAPDATA6@;2000!@SAPDATA6@;2000 PSAPCLUD=@SAPDATA6@;2000!@SAPDATA6@;2000 PSAPDDICI=@SAPDATA4@;2000! @SAPDATA4@;2000 PSAPDDICD=@SAPDATA5@;2000! @SAPDATA5@;2000 PSAPDOCUI=@SAPDATA6@;500 PSAPDOCUD=@SAPDATA4@;500 PSAPEL46BI=@SAPDATA6@;500 PSAPEL46BD=@SAPDATA5@;2000 PSAPLOADI=@SAPDATA5@;500 PSAPLOADD=@SAPDATA5@;500 PSAPPROTI=@SAPDATA4@;2000 PSAPPROTD=@SAPDATA4@;2000 PSAPES46BI=@SAPDATA6@;2000!@SAPDATA6@;2000 PSAPES46BD=@SAPDATA1@;2000!@SAPDATA1@;2000!@SAPDATA1@;2000 PSAPSOURCEI=@SAPDATA4@;1000 PSAPSOURCED=@SAPDATA6@;1000 PSAPUSER1I=@SAPDATA5@;1000 PSAPUSER1D=@SAPDATA5@;1000 SYSTEM=@SAPDATA1@;1000 [Z_ORACREATETSP_SUMSAPDATA] SAPDATA1 : 17000 SAPDATA2 : 12000 SAPDATA3 : 12000 SAPDATA4 : 19500 SAPDATA5 : 23500 SAPDATA6 : 13500

SAP Planning: Best Practices in Implementation Live

SUM : 97500

Checklist Cutover & Going

SAP Planning: Best Practices in Implementation Live

Checklist Cutover & Going

31. Select the DATABASE.R3S file to be used as the input parameter file. 32. The following parameters should be specified when prompted:

Parameter
SAP System Name Instance Number Domain Name of Central Instance Host Name of Central transport Host Database system name Character Set Default drive for Oracle directories

Value
P20 20 US_SAP P20cidb D15cidb P20 WE8DEC M: SAPARCH SAPBACKUP L J J K K M N M N M N J K K J

Database specific files

SAPCHECK SAPREORG SAPTRACE SAPDATA1 SAPDATA2 SAPDATA3 SAPDATA4 SAPDATA5 SAPDATA6

Oracle data files

Database Log Files

ORIGLOGA ORIGLOGB MIRRLOGA MIRRLOGB 2000 KERNEL EXPORT

Mirror Log Files Ram for SAP Location of CDs Passwords Create the Oracle Database Parallel processes Password for database user Exit for MNLS Enter DDICs password (x2)

Z: Y:

Enter P20ADM and SAPServiceP20 passwords when prompted DO NOT ENTER ANY VALUE 8 (may need to be reduced to fewer) pass Continue installation pass

SAP Planning: Best Practices in Implementation Live

33. The following errors were encountered and resolved:

Checklist Cutover & Going

Parameter
DBR3LOADEXEC_NT_ORA All Loads Fail Immediately

Value
Syntax error in the DDLORA.TPL file. Remove all trailing spaces from the STO: sections (x2). The spaces have to be removed after each line and MAXEXTENT. See OSS note 383887. Also copy the DDLORA.TPL file from Y:\DB to I:\Users\P20adm\install.

DBR3LOADEXEC_NT_ORA SAPDBA_ROLE Initialize the Workbench Organizer

ORA-0430 Out of process memory reduced the total number of parallel load processes to 4 from 8. Restarted the load. Edit DATABASE.R3S set step to OK. Start the SAP R/3 system from the cluster administrator.

34. When R3SETUP completes, bring the OracleP20 group online in the cluster administrator. 35. Start the Oracle Fail Safe Manager and verify the Oracle cluster. Ensure that the cluster verifies completely with no errors. 36. Next, fail the Oracle group to the P20 DB server and ensure the resources come online. 37. Next, fail all the groups over to the P20 DB server and ensure the resources come online. Verify that you can logon to SAP R/3 after all the resources are brought online. 38. Next, move the SAP R/3 and Cluster groups to the P20 CI server for execution. 39. This section is now complete continue to Section D - Clean Up Operations.

Clean up the P20 system after import (3 hours)

40. Logon as P20ADM on the P20 CI host. 41. Using the cluster administrator move all groups to S15CI for execution. 42. Stop the SAP R/3 P20 cluster resource using the cluster administrator. Do not stop any other resource within the cluster group. 43. Stop the Oracle P20 cluster resource using the cluster administrator. Do not stop any other resource within the cluster group. 44. Start the OracleP20 service using the computer manager service utility. 45. Start SAPDBA and toggle the database archive mode. (PS: Remember that this is only temporary toggle that MUST be reset before any database loading is executed by the Functional Teams) 46. Start the OracleP20 group with the cluster administrator once the databases archive mode has been toggled. 47. Open CMD and change directory to c:\temp\PostBuildScripts

SAP Planning: Best Practices in Implementation Live

48. Execute the clean-up script cleanP20.cmd

Checklist Cutover & Going

i. The SQL commands executed correctly (make sure no errors occur at this step) ii. Verify that the P20 license (x2) has been installed correctly 49. Start the SAP R/3 P20 cluster resource using the cluster administrator. 50. Move the OracleP20 group back to P20DB for execution.

Initialize the new SAP Instance (3 hours)

51. Logon as D15adm on the D15 CI server. 52. Start the SAPLOGON from the desktop icon. 53. Select Production and click logon. 54. Logon to client 000 as SAP* 55. Execute transaction SICK to ensure there are no errors.

SAP Planning: Best Practices in Implementation Live

Checklist Cutover & Going

Execute transaction SE06, select Database copy and click Post-installation Processing button as shown:

56. Answer the interview questions and prompts as follows: i. Do you want to reinstall the CTO YES ii. Source of DB copy S15 iii. Change originals from S15 to P20 NO iv. Delete the TMS configuration YES (click GREEN CHECK at next screen) v. Delete the TMS configuration YES vi. Delete the old transport routes YES (click GREEN CHECK at next screen) vii. Delete the old transport routes YES 57. Execute transaction RZ04, double-click on the Normal line.

SAP Planning: Best Practices in Implementation Live

58. Select each server line and delete the entry. 59. Generate a new entry for the server as shown:

Checklist Cutover & Going

60. Save the data just created. 61. Execute transaction RZ10 and upload the profiles as shown: (click the back arrow when the summary screen is shown)

Execute transaction SMLG (maintain logon groups), delete the S15 servers from the ALL group and add the P20as system:

62. Save the data just created. 63. Close the GUI on (D15) and logoff.

SAP Planning: Best Practices in Implementation Live

Checklist Cutover & Going

64. Reassign default spool server for printers by executing transaction SPAD as shown below. Click on CHANGE ICON and then OUTPUT DEVICES button.

65. At the next screen choose UTILITIES FOR OUTPUT DEVICES ASSIGN SERVER. 66. At the next screen leave the defaults and click on DISPLAY LIST. 67. At the next screen click on CONVERT and all the printers will be converted to T14 for spooling. 68. Next, delete cancelled and finished background jobs using transaction SM37. 69. Next, check TEMSE consistency and delete inconsistent objects using transaction SP12. 70. Execute program RDDNEWPP from client 014. 71. Start the SAPLOGON from your LOCAL PC desktop icon. If you get a GUI error wait 5 minutes and try again. If the SAP login window does not appear, then SMLG has not been configured correctly, go back to Step 1 in Section F and verify all settings are correct. 72. Select the Production and click logon. 73. Logon to client 000 as SAP* 74. Execute transaction STMS; enter the description and press SAVE. 75. Start the SAPLOGON from your LOCAL PC desktop icon. 76. Select the Dev D15 item and click logon.

SAP Planning: Best Practices in Implementation Live

77. Logon to client 015 as SAP*

Checklist Cutover & Going

78. Execute transaction STMS and press SHIFT-F6 to open the transport routes screen.

79. At the next screen distribute the configuration by pressing F8 as shown below: 80. At the prompts that follow perform the following actions: i. Distribute and active across all systems YES ii. Enter the SAP* password to all systems as requested 81. Execute transaction STMS again from D15 and ensure that no errors or warnings are reported on the first screen again. NOTE: warnings are reported on the front screen below the information message

Copy the original S15-151 client to P20-020 (2 hours)

82. Start the SAPLOGON from your LOCAL PC desktop icon. 83. Select the Production item and click logon. 84. Logon to client 020 as SAP* 85. Execute transaction SCC4 and set clients. 86. Save the settings when done and continue to the next step. 87. Execute transaction SCC5 and select the settings as shown below:

SAP Planning: Best Practices in Implementation Live

Checklist Cutover & Going

88. ENSURE THAT YOU ARE IN THE CORRECT SYSTEM AND CLIENT. 89. Click on Background button to start the job in the background. 90. Click on Schedule Job on the next screen. 91. Click on Continue at the information dialog box. 92. Click on Immediate and then the SAVE button. 93. Select the LOCL output device and click the green check at the bottom of the screen. 94. The job can be monitored from transaction SCC3. 95. Login to P20 client 020 and repeat steps 33 through 40.

SAP Planning: Best Practices in Implementation Live

96. After the client deletes have been completed continue with step 43. 97. Create new entry for client 015 i. Execute transaction SCC4 ii. Click on the CHANGE icon iii. Click on the NEW ENTRIES button iv. Enter the values as shown in the following screen:

Checklist Cutover & Going

SAP Planning: Best Practices in Implementation Live

98. Start the SAPLOGON from your LOCAL PC desktop icon. 99. Select Production again, and click logon. 100. Logon to client 015 as SAP*

Checklist Cutover & Going

101. Execute transaction SCUA and click on the DELETE then SAVE icon. 102. Execute transaction SCCL to start the client copy procedure. 103. Start the job in the background and monitor it periodically using transaction SCC3.

Create users in P20-020 (2 hours)

104. Start the SAPLOGON from your LOCAL PC desktop icon.

105. Select the Dev D15 item and click logon. 106. Logon to client 015 as SAP* 107. Execute transaction BD64, click on the Central User Administration then EDIT Model View Distribute 108. Next, execute transaction SCUA and click on the SAVE icon. 109. Start the SAPLOGON from your LOCAL PC desktop icon.

110. Select the Production item and click logon. 111. Logon to client 015 as SAP* 112. Execute transaction BD64, click on the Central User Administration then ENVIRONMENT GENERATE PARTNER PROFILES. Click on the execute icon. 113. Switch back to the D15 logon. 114. Next, execute transaction SUCOMP, make a non-intrusive change to the company address (e.g. remove or add a period). Click on the SAVE icon when done. 115. Next, execute transaction SU10. 116. Select all User-IDs and add P20MAND015 as the destination system. Execute the request. 117. Transaction SCUL can be checked for any errors. 118. Switch back to the P20 logon. 119. Create the User Groups in P20 using transaction SUGR.

SAP Planning: Best Practices in Implementation Live

Proactive maintenance steps (2 hours)
120.

Checklist Cutover & Going

Start the SAPLOGON from your LOCAL PC desktop icon.

121. Select the Production item and click logon. 122. Logon to client 015 as SAP* 123. Execute transaction DB02. 124. Click on DETAILED ANALYSIS for TABLES and INDEXES. 125. Input 50 for maximum extents. 126. Note all objects that belong to owner SAPR3. 127. Next, stop the R/3 system (no other resources) and move the cluster groups onto the P20CI node. 128. Use SAPDBA to reorganize each object. 129. Implement any parameter changes that are required. The following changes have already been implemented: i. Latest SAP Kernel Patch (1098) ii. Early Watch SAP parameters iii. Early Watch Oracle parameters