8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 1/18

SAP System Refresh Procedure Document for SAPR/3 on Windows/Oracle platform. 

This document outlines how to refresh an SAP R/3 4.6C system on Windows/Oracle

platform. 

The acronyms used in documents are 

PRM = Source System SIDPFM = Target System SID bp1tulap131 = Source System DB bp1tulap132 = Source System CI bp1tulap132 = Source System Application bp1tulap113 = Intermediate System for Export Storage. bp1tulap129 = Target CI bp1tulap130 = Target DB

Prerequisites: 

1. Windows login access on Host2. Checking OS level configuration i.e. <sid>adm, ora<sid> users, environment variable settings3. Checked /Create and map filesystem same as of Source System4. Downtime approval for Destination System copy process5. Verification of file systems6. Prepare SAP System for system copy-Prechecks7. Online database backup of Source System

8. Create backup control file of Source System9. Edit Control file with Target System10. Checked all required passwords (System, DDIC etc) of Source systems11. Taking backup of target system configuration12. Backup RFC Entries /SE0913. Export User Master /SE0914. Export Logical System Connections / SALE /SE0915. Save Logon Groups - SMLG16. Export STMS_QA worklist tables / SE0917. Save RFC Groups –  RZ1218. Take Screen Shot of BD54

19. WE20 / Partner Profile20. WE21/ Note Each tRFC21. SLICENSE /Installed licenses22. SCC4 /Client Details23. Offline Backup + File system backup of Target system

BASIS Prerequisites 

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 2/18

1. Start Online backup in PRM (Source System) Use transaction DB13 to scheduleSchedule at least 24 hrs before the planned PFM db roll forward time

2. Execute a user master export of PFM client 100. 

Go to transaction SCC8 (client export)Choose the following,

Profile: SAP_USERTarget System: PFMClick on ‘Start Immediately’ Take note of the request number.

If above method does not work do the following. 

TP pf=TP_DOMAIN_PSM.PFL export <transport#> client 100 UI

(example of transport #: PFMKT00140, note T not 9)

3. Execute table export of PFM client 100. 

Map \\<<PRM HostName>>\e$ to Z: drive on <<PSM Host Name >> Ensure the scriptsexport_pfm_tables.cntl and import_pfm_tables.cntl Conatins all the client dependent and client-independent tables listed below.

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 3/18

To export the tables contents, execute the following from z:\usr\sap\trans\bin. (Or, the specify thedirectory locations of the control and log files. command>R3trans – w export_pfm_tables.logexport_pfm_tables.cntl

Check the log and verify whether the export completed successfully.

 Note : List of Client Independent Tables (tpfid,tpfba,tpfht,btcomset,btcomsdl,rzllitab,rzlliclass,tsp03,tsp03c,tsp03d,txcom,t000,tbdls,tbdlst,rfcdes,rfcdoc,edimsg,tbd21,tbd22,edipo,zzifc_pathmap)

List of Client Dependent Tables (TVARUVN,VARI,VARINUM,VARID,VARIT,tbd00,tbd00t,tbd03,tbd05,tbd06,tbda1,tbda2,tbd20,tbd62,tede5,ede5t,t242d,t242i,t242s,t242y,t242a,edpp1,edp13,edp21,edp12,edi poa,edipod,ediport ZZIFC_AR_DD_UNPD,ZZIFC_FILES,ZZIFC_TARGETS)

4. Create a system message Go to transaction SM02

5. Identify transports for post refresh Using STMS transport history, identify the transports imported into PFM, but not PRM.This transport list will be re-imported into PFM, post refresh.

6. Copy initPRM files from PRM Copy the following files from PRM E:\oracle\ora92\database directory to PFM(bptuldbb04)E:\oracle\ora92\database,initPRM.utlinitPRM.dbainitPRM.orainitPRM.sapinitPRM.bki

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 4/18

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 5/18

  Please remove datafiles from the new driv es NOTE: if control files are saved under sapdata, do not remove the cntrldirectories, but rename the CNTRL<SID>.DBF files

Remove origlog and mirrorlog files

Do not remove origlog* and mirrlog*diretcoriesGo to G:\ and H:\ to remove files

15. Rename directories Rename the <Drive>:\oracle\PFM to <Drive>:\oracle\PRM

Please do the same for all drives except E:\

16. Set the environment variables for the current session  Go to Command Prompt

Set Oracle_SID=PRMSet SAPDATA_HOME=F:\oracle\PRM

Set DSMI_CONFIG=e:\usr\sap\PFM\SYS\exe\run\dsm_opt\tsmsrv3.optSet SAPBACKUP=F:\oracle\PRM\sapbackupSet SAPARCH=F:\oracle\PRM\saparchSet SAPCHECK=F:\oracle\PRM\sapcheck Note:- Do not close the command prompt session

17. Regenerate BKI file Use the same command prompt session to execute the following commands,

 backint –  p e:\oracle\ora92\database\initPRM.utl – f password Note: - Please get the password from basis pool members

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 6/18

 

18. Restore the database 

Use the same command prompt session to execute the following commands brrestore -b <backuplog.anf> -d util_file -r e:\oracle\ora92\database\initPRM.utl -m full -l EVerify the restore completed successfully

19. Restore the archive logs Review the copied archive log (Step 2.1) to obtain the range of logs to restoreUse the same command prompt session to execute the following commands brrestore -a <start_log#>-<end_log#> -c -d util_file -re:\oracle\ora92\database\initPRM.utl

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 7/18

 

20. Start Oracle Service for PRM 

Start oracle service OracleServicePRM using computer management

21. Execute ‘Point in Time recovery Use the same command prompt session to execute the following commands

sqlplus /nologSQL> connect / as sysdbaSQL> startup mountSQL> recover database using backup controlfile until time '2004-03-19:18:00:00'(CHANGE DATE & TIME ACCORDINGLY)

ORA-00279: change 76403165 generated at 03/09/2004 19:56:02 needed for threadORA-00289: suggestion: /oracle/PRM/oraarch/PRMarch1_5435.dbf

ORA-00280: change 76403165 for thread 1 is in sequence #5435Specify log: {<RET>=suggested | filename | AUTO | CANCEL}AUTOVerify recovery finished successfully

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 8/18

 

22. Create trace file SQL> alter database open resetlogs;

Verify database opened successfullyPlease check the oracle alert log for more info.

SQL> alter system switch logfile; [execute 10 times ]

SQL> Alter database backup controlfile to trace resetlogs;SQL> shutdownClose the command prompt session.

23. Adjust the initPFM.ora file Compare the initPRM.ora with initPFM.ora and make changes accordingly. NOTE: careful adjusting all parameters (memory is not the same for source and target

servers)

24. Edit the trace file to create control.sql Copy the trace file from ‘usertrace’ directory to e:\renameRename the old control.sql from e:\oracleRename the new trace file to control.sqlEdit the control.sql

Remove all the lines before 'Create control file' lineChange 'REUSE' to 'SET'Replace all occurrences of 'PRM' with 'PFM'Remove the line 'alter database open'Remove the line 'RECOVER DATABASE USING BACKUP CONTROLFILE'

Save the control.sql

25. Stop Oracle Service for PRM Stop oracle service OracleServicePRM using computer managementChange the startup type for service OracleServicePRM to Disabled

26. Rename Directories Rename <Drive>:\oracle\PRM to <Drive>:\oracle\PFMPerform the above steps for all drives except E:\

27. Start Oracle Service for PFM 

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 9/18

  Start the following oracle services,OracleServicePFMOracleTNSlistenerOracleOraHome92Agent

28. Rename and start DB with new name Sqlplus /nologSQL>Connect / as sysdbaSQL>Startup nomountSQL>@e:\rename\control.sqlMake sure there are no errors

SQL>alter database open resetlogs

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 10/18

 

29. Execute oradbusr.sql Copy oradbusr.sql from installation directory to e:\rename

 For 4.6C system 

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 11/18

 Sqlplus /nolog @e:\rename\oradbusr.sql SAPR3 NT <DB server name> PFMSqlplus /nolog @e:\rename\oradbusr.sql SAPR3 NT bp1 PFM (since sapservicePFM isa domain user)

 For 620 system 

sqlplus /nolog @e:\rename\oradbusr.sql SAPDAT NT BPTULDBB04 PFMsqlplus /nolog @e:\rename\oradbusr.sql SAPDAT NT bp1 PFM

30. Start SAP Services (CI) Start the following SAP Services

SAPOSCOLSAPPFM_10

31. Start SAP(CI) without background and spool processes.  

Change number of process for background and spool to ‘0’ 

32. Install New SAP License (login as sap* and run tcode: slicense)  Installation Number: ??????????

System ID: PFMSystem Number:000000000310246581Hardware Key: ???????????License Key: D2NT2GOIJHFMEHLLOM7ACLTL

Valid to: 31.12.9999

33. Lock All users Using transaction su01, Mass changes to lock users. (all users or only selected users)

34. Set up the workbench organizer Login to client 000 as the user DDIC

Go to SE06Select Database Copy or Database MigrationClick on Perform Post-Installation ActionsDo you want to reinstall the CTS? YESSource System of database copy: PRMDelete TMS Configuration? YESDelete old versions of the transport routes? YESDo you want to delete the old versions of the transport routes? YES

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 12/18

 

35. Configure STMS 

 Note:- For PFM refresh,Transport domain controller = PSMTransport Route = PSM > PFM > PRM > GRM

 For PFM refresh,Login to PSM client 000 as user sap*

Go to STMSClick on systemsSelect PFMClick on DeleteDistribute and update the configuration

 Now login to PFM client 000 as user sap*Go to STMS

You will get a popup window.Confirm that transport domain is DOMAIN_PSM and domain controller is PSM Now click on Save

 Now Login to PSM client 000 as user sap*Go to STMSClick on systemsSelect PFMClick on ApproveDistribute and update the configuration

 Now click on Transport routesClick on ChangeClick on SaveDistribute and update the configuration

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 13/18

Post Refresh specific activities 

36. Regenerate BKI file Use command prompt session to execute the following commands, backint –  p e:\oracle\ora92\database\initPFM.utl – f password

 Note: - Please get the password from basis pool members

37. Start SAP(APP) Start SAP using SAP MMC in CI & APP

38. RFC Server Groups Call transaction RZ12

Delete all PRM Server groups.Double click on bp1tulap129_PFM_10

Enter ‘parallel_generators’ as server group 

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 14/18

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 15/18

  Enter PFM as logon group and click on copyDouble click on instance bp1tulap130_PFM_10

Enter PFM as logon group and click on copyClick on save

44. Modify Operation modes and instances (Verify only due to table export/import.)  Go to transaction RZ04

Click on Instances/Operation modes Now select the PRM CI and click on delete entry

Perform the same for PRM APPTo recreate as follows

Settings -> based on current status -> new instances -> generateEnter the following, (NOT needed)

Hostname: bptuldbb04SAP system number: 10Start profile name: START_DVEBMGS10_ BP1TULAP129Instance profile name: PFM_DVEBMGS10_ BP1TULAP129

Click on SaveEnter * as operation modeClick on Save

Assign WP distribution to other OP modes? NOClick on SavePerform the same for PFM APP (bp1tulap129)

45. BDLS converting logical systems 1. Convert PRMCLNT100 to PFMCLNT1002. Convert PRMCLNT200 to PFMCLNT2003. Convert BP_TP5_100 to BP_TI5_120

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 16/18

  4. Convert GP1_050 to GI1_050

46. SM59 adjustments or recreation of R/3 and TCP/IP (Verify only due to

table export/import.) 

a. Adjust as per the snap-shots of pre-refresh document (logical system names, userid/passwordused etc) b. Any Production related setting not adjusted should be disabled (example: GP1_050) or deleted(PRMCLNT100, PRMCLNT200)

47. WE20 adjustments or recreation of ports (Verify only due to table export/import.)  1. Adjust as per the snap-shots of pre-refresh document (we20 port definitions) (example

PRMCLNT100 to be converted to PFMCLNT100)

48. WE21 adjustments or recreation of partner type LS 1. Adjust as per the snap-shots of pre-refresh document (we21 partner definitions for logical

systems) (example PRM_100_IN to be converted to PFM_100_IN)

49. SP12 tempse consistency check  50. SPAD consistency check of spool database 

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 17/18

 

51. SPAD lock all the production printers

52. AL11 Adjust target server and target sid informationDATA_ftp \\<target server>\data\<target sid>\ftpDATA_inbound \\<target server>\data\<target sid>\inboundDATA_outbound \\<target server>\data\<target sid>\outboundDATA_tmp \\<target server>\data\<target sid>\tmp

DB02 adjust tablespaces by adding datafiles through SAPDBA if needed (any tablespace >95% full needs to be looked into)

52. Import the user export to PFM client 100. Use STMS to import the user export.Go to SCC7 to complete the user import

Select ‘Schedule as Background Job’ 

53. Perform Transports Re-transport all CASSIS transports as per the list received from the CASSIS team.

54. Set the system change option 

Using transaction SE06 set the system change option to ‘Not Modifiable’. 

8/11/2019 System Refresh With Screenshot

http://slidepdf.com/reader/full/system-refresh-with-screenshot 18/18

 

55. Set the client settings 

Go to transaction SCC4Click on ChangeDouble click on Client 100

Set Client-Specific Objects to ‘No changes allowed’ Set Cross-Client Object Changes to ‘No changes to cross-client Customizing objects’ Change the client role to ‘Production’ 

56. Run SM21, ST22 for sanity check. Verify that there are no errors and dump after refresh.

57. Start Online Backup Use DB13

Schedule immediate online backup58. Schedule Archive log backups and Online Backups (It should be scheduled as per the backup strategy based on data growth)Use DB13Schedule Archive log backupsSchedule Online Backups