sap refresh

SAP

Document Revision History

Date Version

Author Change Description

1.01.1

SAP Refresh Master Document of 72

Text Heading LegendSystem Colo

rECCBWCRMXISRMSCM

TEXT HEADING LEGEND.....................................................................................................2

SYSTEM................................................................................................................................2

COLOR..................................................................................................................................2

ECC....................................................................................................................................... 2

BW.........................................................................................................................................2

CRM.......................................................................................................................................2


XI........................................................................................................................................... 2

SRM.......................................................................................................................................2

SCM.......................................................................................................................................2

1. PRE-DATABASE/SAP REFRESH.................................................................................181.1 Post a System Message about Scheduled Downtime..........................................................................................191.2 Saplicense...............................................................................................................................................................19

Logon to as <sid>adm on Source System........................................................................................................................19Check your sap license.....................................................................................................................................................19saplicense –show..............................................................................................................................................................19Export the saplicense information to a file under <sid>adm home directory..................................................................19cd /home/<sidadm>..........................................................................................................................................................19saplicense –show > saplicense.SID.................................................................................................................................19

1.3 Confirm Passwords for Source/Target system with Security team.......................................................................19DDIC password in Client 000..........................................................................................................................................19DDIC and BASIS-BATCH in default client....................................................................................................................19

1.4 Stage Instance Specific Information before Volume Group is recreated..............................................................19Validate staging FS is available. This should return a valid FS entry.............................................................................19bdf /usr/sap/put_refresh....................................................................................................................................................19Copy the required directories to the staging Directory - /usr/sap/put_refresh.................................................................19cd /usr/sap/put_refrersh...................................................................................................................................................19mkdir -p oracle/T_SID....................................................................................................................................................19mkdir -p usr/sap/T_SID/DVEBMSxx...............................................................................................................................19mkdir -p sapmnt/T_SID..................................................................................................................................................19cd /oracle/<T_SID>.......................................................................................................................................................19tar -cvf /usr/sap/put_refresh/oracle/U11/102_64.tar 102_64....................................................................................19{Note: To check the tar file structure tar -tvf <filename>.tar}......................................................................................19cd /oracle/<T_SID>......................................................................................................................................................19tar –cvf /usr/sap/put_refresh/oracle/U11/dotastrik.tar .[a-z]*.................................................................................19cd /sapmnt/<T_SID>......................................................................................................................................................19tar -cvf /usr/sap/put_refresh/sapmnt/U11/profile.tar profile.......................................................................................19cd /usr/sap/<T_SID>/DVEBMGSxx.............................................................................................................................19tar -cvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar igs..................................................................................19cd /oracle.........................................................................................................................................................................19tar –cvf /usr/sap/put_refresh/oracle/client.tar client................................................................................................19tar -cvf /usr/sap/put_refresh/oracle/oraInventory.tar oraInventory..........................................................................20Team - Please add any other directories or files that you want to save off before the Volume Group is recopied with Target Volume Group......................................................................................................................................................20

1.5 Export User Master data...........................................................................................................................................20Log on to source client with SAP.....................................................................................................................................20Run Transaction SCC8...................................................................................................................................................20 Select profile SAP_USER.......................................................................................................................................20 Select target system.................................................................................................................................................20 start immediately.....................................................................................................................................................20Make note of the SIDKTxxxxx transport number from the pop-up screen. The data and cofiles will be created with this numbers............................................................................................................................................................................20Check the appropriate export log to validate if the export was successful......................................................................20SCC3 exports check for the current export logs..............................................................................................................20Always, logon as <sid>adm at the OS level and validate the recent creation of cofiles & data files..............................20cd /usr/sap/trans/cofiles..................................................................................................................................................20ls –ltr................................................................................................................................................................................20The KTxxxxx.SID file should have been created with recent time stamp.......................................................................20cd /usr/sap/trans/data......................................................................................................................................................20ls –ltr................................................................................................................................................................................20The RTxxxxx.SID file should have been created with recent time stamp.......................................................................20


1.6 Transport Printer Definitions..............................................................................................................................20Run Transaction SPAD..................................................................................................................................................20 Output Devices – Display........................................................................................................................................20 Go to Edit – transport – transport all.......................................................................................................................20 Note down the request number................................................................................................................................20 Release the Transport..............................................................................................................................................20

1.7 Transport RFC Definitions...................................................................................................................................20Create a workbench request in SE01.............................................................................................................................20Go to change mode of your request.................................................................................................................................20Include the following object Name with Program ID : R3TR Object Type : TABU.............................................20 RFCATTRIB...........................................................................................................................................................20 RFCDES..................................................................................................................................................................20 RFCDESSECU........................................................................................................................................................20 RFCDOC.................................................................................................................................................................20Now double click on each of your RFC table entry and it will open another screen and click on “Insert Row” button.20Give * as input (i.e. all the keys corresponding to that table are taken)..........................................................................20Now save the transport request........................................................................................................................................20Note down your request number......................................................................................................................................21Release your request.........................................................................................................................................................21

1.8 Logical System Definitions....................................................................................................................................21Run Transaction BD54..................................................................................................................................................21Take a screenshot of Logical Systems Definition............................................................................................................21

1.9 Partner Profile.......................................................................................................................................................21Run Transaction WE20..................................................................................................................................................21Take a screenshot of Partner Profile, specifically all Partner Type – Logical Systems...................................................21

1.10 IDOC Port Definitions..........................................................................................................................................21Run Transaction WE21..................................................................................................................................................21Drill Down on ‘Transactional RFC’, Take a screenshot of RFC Destination Port Assignment......................................21

1.11 Client Definitions...................................................................................................................................................21Run Transaction SCC4...................................................................................................................................................21Take a screenshot of client’s overview – to note the Client Description and settings.....................................................21

1.12 Trusted Systems.....................................................................................................................................................21Run Transaction SMT1..................................................................................................................................................21Take a screenshot of trusted systems – to note the Client Description............................................................................21This needs to be reconfigured during post refresh activities............................................................................................21

1.13 Trust Manager – Portals Certificates..................................................................................................................21Run Transaction STRUSTSSO2.................................................................................................................................21Check the existing public-key certificate of Portal Servers in component system's certificate list. This needs to be reconfigured during post refresh activities.......................................................................................................................21

1.14 Integration Engine Configuration........................................................................................................................21Run transaction SXMB_ADM......................................................................................................................................21Double Click on Integration engine configuration...........................................................................................................21Take screenshot of configuration data.............................................................................................................................21

1.15 Maintain SLD Access data....................................................................................................................................21Run transaction SLDAPICUST....................................................................................................................................21Take a snapshot or make note of the entries....................................................................................................................21

1.16 SLD Bridge Info – ABAP/JAVA..........................................................................................................................221.16.1 ABAP....................................................................................................................................................................22Run Transaction RZ70...................................................................................................................................................22Take screenshot or note the SLD Bridge Host and Service Info.....................................................................................221.16.2 Java......................................................................................................................................................................22Logon to Visual Admin....................................................................................................................................................22Go to services Select SLD Data Supplier Note SLD Data Collection Settings.....................................................22Note CIM Client Generation Settings..............................................................................................................................22

1.17 Port Maintenance IDOC Adapters......................................................................................................................22Run transaction IDX1.....................................................................................................................................................22Note all the ports and corresponding RFC destinations or take a screenshot of the same...............................................22This needs to be reconfigured during post refresh...........................................................................................................22

1.18 IDOC Adapter Metadata Overview.....................................................................................................................22Run transaction IDX2.....................................................................................................................................................22


Note all the ports and corresponding RFC destinations or take a screenshot of the same...............................................22This needs to be reconfigured during post refresh...........................................................................................................22

1.19 Distribution Model View.......................................................................................................................................22Run transaction BD64....................................................................................................................................................22Take a snapshot or make note of the entries....................................................................................................................22

1.20 Maintain CRM RFC Parameter..........................................................................................................................22This entry is maintained in table CRMRFCPAR in all sender/receiver systems (R3/BW etc).....................................22Verify the entries take a screenshot..................................................................................................................................22

1.21 Validate HP OMS entry in SPAD........................................................................................................................22Use transaction SPAD....................................................................................................................................................22 Select Full Administration button...........................................................................................................................22 Go to Output Management Systems tab..................................................................................................................22 Check Real Output Management Systems by clicking on Display.........................................................................22 Double click on HP-DAZEL and validate OMS Configuration info......................................................................22For Eg. QA2, it should be: “-N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]”..................................................22For Eg. U11, it should be: “-N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]”...................................................22Take a note or screenshot of the settings and if different add its entry on previous line for the specific SID.................23Please Add SBX specific info.........................................................................................................................................23

1.22 Display / Note Logon Group Definitions.............................................................................................................23Run Transaction SMLG..................................................................................................................................................23Take a screenshot of currently configured logon groups.................................................................................................23

1.23 Check operation modes.........................................................................................................................................23Run Transaction RZ04...................................................................................................................................................23Take a screenshot of currently defined OP modes...........................................................................................................23

1.24 Check for ITS.........................................................................................................................................................23Run transaction SM30...................................................................................................................................................23 Give the table name TWPURLSVR......................................................................................................................23 Click on Display......................................................................................................................................................23 Double click on your Logical system host name.....................................................................................................23Take a screen shot of that so that after the refresh we can reconfigure the same............................................................23

1.25 Verify DBA Planning Calendar...........................................................................................................................23Run transaction DB13....................................................................................................................................................23Note the scheduling period for DBA jobs or take screenshot..........................................................................................23

1.26 XI Specific Steps....................................................................................................................................................231.26.1 Export SLD Information..............................................................................................................................231.26.2 Export the Repository server information.......................................................................................................241.26.3 Export the Directory server information.........................................................................................................241.26.4 Configure CMS Setup........................................................................................................................................251.26.5 SLD DATA supplier and Bridge.......................................................................................................................251.26.6 SLD Business Systems........................................................................................................................................251.26.8 XI Message Archiving & Deletion....................................................................................................................25

1.27 BI Specific Steps....................................................................................................................................................261.27.1 Conversion of Logical System Names...............................................................................................................261.27.2 UDC Connection Container Settings..........................................................................................................27

1.28 SCM Specific Steps................................................................................................................................................271.28.1 Document connections to liveCache............................................................................................................271.28.2 Configure UDC (* same step as BI **)..............................................................................................................281.28.3 Document Business System Groups (BSG)......................................................................................................281.28.4 qRFC Monitor....................................................................................................................................................281.28.5 Stop/check CIF queue........................................................................................................................................291.28.6 LiveCache consistency.......................................................................................................................................291.28.7 Backup liveCache...............................................................................................................................................29Tushar Check and Verify..............................................................................................................................................29

1.29 SRM Specific..............................................................................................................................................................291.29.1 Copy the SRM IPC parameter file....................................................................................................................29Please Add this specific info for all the landscapes.....................................................................................................301.30 Display/Note Logical Ports...................................................................................................................................30

2 DATABASE BACKUP..................................................................................................31


2.1 Oracle Database Backup – Source System..........................................................................................................322.2 SCM maxDB liveCache Backup - Source System..............................................................................................32

3. ORACLE DATABASE RESTORE – TARGET SYSTEM...........................................333.1 Reproduce Source System environment on Target System...................................................................................333.2 Add Source system in /etc/hosts file.........................................................................................................................333.3 Start database as Source System..............................................................................................................................33

Logon the target system as ora<Source_system_sid>....................................................................................................33su – ora<s-sid>.................................................................................................................................................................33sqlplus “/ as sysdba”........................................................................................................................................................33startup;.............................................................................................................................................................................33exit....................................................................................................................................................................................33

3.4 Create Control File....................................................................................................................................................33Logon the target system as ora<source_system_sid>.....................................................................................................33su – ora<s-sid>.................................................................................................................................................................33sqlplus “/ as sysdba”........................................................................................................................................................33alter database backup controlfile to trace;......................................................................................................................33exit....................................................................................................................................................................................33cd /oracle/<Source_SID>/saptrace/usertrace.................................................................................................................33Get the latest file you just created through sqlplus command..........................................................................................33vi ` ls –ltr |tail -1|awk ‘{print $9}’ `.................................................................................................................................33Go to the end of the file and scroll up till you see the following text..............................................................................34STARTUP NOMOUNT.................................................................................................................................................34Scroll one line up and delete all the lines from the beginning of the file to the current line...........................................34:1,.d...................................................................................................................................................................................34Once you have deleted the lines, your first line should be...............................................................................................34STARTUP NOMOUNT.................................................................................................................................................34Now replace the Source_SID with Target_SID on all the lines by running the following..............................................34command..........................................................................................................................................................................34:%s,Source_SID,Target_SID,g.......................................................................................................................................34Now search the string CREATE in the file and replace the following line:....................................................................34/CREATE........................................................................................................................................................................34CREATE CONTROLFILE REUSE DATABASE "<Target_System_SID>" RESETLOGS ARCHIVELOG. .34With.................................................................................................................................................................................34CREATE CONTROLFILE SET DATABASE "<Target_System_SID>" RESETLOGS......................................34For editing the line do the following, On the following line go to end of the line..........................................................34CREATE CONTROLFILE REUSE DATABASE "<Target_System_SID>" RESETLOGS ARCHIVELOG. .34$........................................................................................................................................................................................34Move your cursor upto word ARCHIVELOG by using key h on your keyboard...........................................................34dw.....................................................................................................................................................................................34and move your cursor upto word REUSE and by using h on your keyboard.................................................................34dw.....................................................................................................................................................................................34now switch to insert mode i..............................................................................................................................................34Now write SET................................................................................................................................................................34Now your modified command looks like.........................................................................................................................34CREATE CONTROLFILE SET DATABASE "<Target_System_SID>" RESETLOGS......................................34Now search the string RECOVER in the file and replace the following line:................................................................34/RECOVER.....................................................................................................................................................................34RECOVER DATABASE USING BACKUP CONTROLFILE.................................................................................34With..................................................................................................................................................................................34RECOVER DATABASE USING BACKUP CONTROLFILE until cancel............................................................34For editing the line do the following................................................................................................................................34Go to end of the line and append as follows....................................................................................................................34$........................................................................................................................................................................................34a........................................................................................................................................................................................34until cancel......................................................................................................................................................................34Now your modified command looks like.........................................................................................................................34RECOVER DATABASE USING BACKUP CONTROLFILE until cancel............................................................34Now save the file as /tmp/rename.sql using the following command:.............................................................................34


:w /oracle/<Source_SID>/rename.sql............................................................................................................................343.6 Copy back the pre-staged files from the staging Directory - /usr/sap/put_refresh............................................35

sudo su –...........................................................................................................................................................................35cd /oracle/<T_SID>.........................................................................................................................................................35rm –fr 102_64...................................................................................................................................................................35cd /oracle/<T_SID{Note: To check the tar file structure tar- tvf <filename>.tar}..................................................35tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/102_64.tar..............................................................................................35cd /oracle/<T_SID>.........................................................................................................................................................35tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/dotastrik.tar...........................................................................................35cd /sapmnt/<T_SID>.......................................................................................................................................................35tar -xvf /usr/sap/put_refresh/sapmnt/<T_SID>/profile.tar..............................................................................................35cd /usr/sap/<T_SID>/DVEBMGSxx................................................................................................................................35tar -xvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar.............................................................................................35cd /oracle..........................................................................................................................................................................35tar -xvf /usr/sap/put_refresh/oracle/client.tar..................................................................................................................35tar -xvf /usr/sap/put_refresh/oracle/oraInventory.tar......................................................................................................35

3.7 Change the ownership of all <T-SID> files to target system.................................................................................353.7.1 To change the ownership we need to be the root...............................................................................................353.7.2 Change the ownership.........................................................................................................................................353.7.3 Set the permission for the new kernel files.......................................................................................................353.7.4 Copy the files from /sapmnt/<SID>/exe to /usr/sap/<SID>/SYS/exe/run Directory....................................363.7.5 Now run the saproot.sh script............................................................................................................................363.7.6 Now copy the files from /usr/sap/<SID>/SYS/exe/run to /sapmnt/<SID>/exe...............................................36

3.8 Recover Database as Target System........................................................................................................................363.8.1 Recover the database on target system as ora<Target_sid>............................................................................363.8.2 Restart the database to make sure that DB starts correctly...........................................................................37shutdown immediate.........................................................................................................................................................37startup...............................................................................................................................................................................373.8.3 Create the ops$<Target_sid>adm users and grant permission......................................................................37create user ops$<Target_sid>adm identified externally.................................................................................................37default tablespace psapdatusr temporary tablespace psaptemp;....................................................................................37Grant dba,connect,resource to ops$<Target_sid>adm;.................................................................................................37create user ops$ora<Target_sid> identified externally..................................................................................................37default tablespace psapdatusr temporary tablespace psaptemp;....................................................................................37Grant dba,connect,resource to ops$ora<Target_sid>;...................................................................................................37create table ops$<Target_sid>adm.sapuser as select * from ops$<Source_sid>adm.sapuser;....................................37exit....................................................................................................................................................................................373.8.4 Test the connectivity to the database as user <Target_sid>adm....................................................................37su - <sid>adm..................................................................................................................................................................37R3trans –d........................................................................................................................................................................37This should give the return code of (0000) for successful logon to database..................................................................37If it was not able to connect /logon to database it will throw a return code 0008............................................................37

3.9 Create the Oracle Password File (OPTIONAL).....................................................................................................37Create the Oracle password file:......................................................................................................................................37$ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/dbs/orapw<SID> password=<system password> entries=100......................................................................................................................................................................37(Use password for system)...............................................................................................................................................37Logon to UNIX level as ora<sid>....................................................................................................................................37sqlplus “ / as sysdba.........................................................................................................................................................37create spfile from pfile;....................................................................................................................................................37startup...............................................................................................................................................................................37

4 DELETE TARGET JAVA INSTALLATION...............................................................384.1 **Delete the currently installed JAVA Installation**............................................................................................38

Make sure your Database is down for this step, which it should be since you did not start SAP as yet.......................384.2 Delete the following directories on Target DB server..........................................................................................38Su -<sid>adm...................................................................................................................................................................38cdD...................................................................................................................................................................................38rm –fr /usr/sap/<SAPSID>/DVEBMGS<xx>/SDM.........................................................................................................38


rm –fr /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee..........................................................................................................38rm –fr /usr/sap/<SAPSID>/SCS<xx>..............................................................................................................................38rm –fr /sapmnt/<SAPSID>/exeU (If it exists.).................................................................................................................38Note: - The directory exeU is only present in versions below 640..................................................................................384.3 Delete the following directories on each of the application server.....................................................................38/usr/sap/<SAPSID>/D<xx>/j2ee.....................................................................................................................................384.4 Delete the JAVA profile..........................................................................................................................................38cdpro.................................................................................................................................................................................38rm -f /sapmnt/<SAPSID>/profile/<SID>_SCSxx_hostname..........................................................................................38rm - f /sapmnt/<SAPSID>/profile/START_SCSxx_hostname.........................................................................................384.5 Drop your j2ee schema...........................................................................................................................................38Log on as user ora<Target_sid>.....................................................................................................................................38Start sqlplus and connect to the database.........................................................................................................................38sqlplus /nolog...................................................................................................................................................................38connect / as sysdba...........................................................................................................................................................38startup...............................................................................................................................................................................38Note:- when sqlplus /nolog is executed we get the error connected to an idle instance. This means the database is not connected. So at that time we need to start the database using startup command. Enter the following command to delete the database objects of the database schema:........................................................................................................38drop user SAP<Source_System_SID>DB cascade;........................................................................................................38Enter the following command to get the name of schema of the associated data files in the system.........................38select file_name from dba_data_files where tablespace_name = 'PSAP<Source_System_SID>DB';..........................384.6 Now drop the table spaces as they are empty....................................................................................................39Enter the following command to delete the tablespace of the database schema:.............................................................39drop tablespace PSAP<Source_System_SID>DB including contents;..........................................................................39Exit sqlplus:......................................................................................................................................................................39shutdown immediate.........................................................................................................................................................39exit....................................................................................................................................................................................394.7 Delete the data files of tablespace PSAP<Source_SID>DB from the system..................................................39rm –rf /oracle/<Source_SID>/sapdata4/<Source_SID>db_1........................................................................................39Now your java instance is completely deleted.............................................................................................................39

5.1 Install sap license........................................................................................................................................................40Logon as <sid>adm..........................................................................................................................................................40su – <sid>adm..................................................................................................................................................................40Browse to the directory where the license backup file is kept.........................................................................................40more <SID>.saplicense...................................................................................................................................................40saplicense –install............................................................................................................................................................40

5.2 Set Background Process as Zero...............................................................................................................................40Logon as <sid>adm..........................................................................................................................................................40su – <sid>adm..................................................................................................................................................................40cdpro.................................................................................................................................................................................40Edit SAP Instance Profile.................................................................................................................................................40vi <sid>_DVEBMGS<no>_<host>..................................................................................................................................40find parameter rdisp/wp_no_btc......................................................................................................................................40comment out # rdisp/wp_no_btc.....................................................................................................................................40append..............................................................................................................................................................................40rdisp/wp_no_btc = 0........................................................................................................................................................40To make background process = 0.....................................................................................................................................40

5.3 Cleanup /sapmnt/SID/global......................................................................................................................................40Before starting SAP remove the JOBLOG & SLOG files in the /sapmnt/SID/global/ directory on the target system.. .40cd /sapmnt/<Target_SID>/global...................................................................................................................................40rm –fr *JOBLG*...............................................................................................................................................................40rm –fr *SLOGJ*...............................................................................................................................................................40rm -fr WF_LOG*..............................................................................................................................................................40

5.4 STARTSAP.................................................................................................................................................................40startsap..............................................................................................................................................................................40Logon to your sap.............................................................................................................................................................40We see the default client of <Target System> which is configured in instance profile...................................................40Remove the <target system> default client number and type <source system > default client number..........................40Provide the logon information of <Source System>........................................................................................................40


5.5 Reinitialize TMS after DB copy...............................................................................................................................40logon to 000 as DDIC......................................................................................................................................................40Run transaction SE06 database copy or database migration....................................................................................40Reinstall CTS yes........................................................................................................................................................40change original <S_System <SID>>to <T_System <SID>> yes................................................................................40cts not configured ok...................................................................................................................................................41delete the TMS Configuration yes..............................................................................................................................41delete all versions of transports yes.............................................................................................................................41delete transport routs yes.............................................................................................................................................41

5.6 Delete Jobs..................................................................................................................................................................41** WARNING: MAKE SURE YOU ARE IN TARGET SYSTEM/CLIENT **..........................................................41Execute transaction SM37.............................................................................................................................................41Delete all released jobs from the system..........................................................................................................................41

5.7 Revert background processes to original................................................................................................................41Logon as <sid>adm..........................................................................................................................................................41su – <sid>adm..................................................................................................................................................................41cdpro.................................................................................................................................................................................415.7.1 Edit instance profile..........................................................................................................................................41vi <sid>_DVEBMGS<no>_<host>................................................................................................................................41Find parameter rdisp/wp_no_btc......................................................................................................................................41Reset to original values....................................................................................................................................................415.7.2 Stop SAP server...................................................................................................................................................415.7.3 Start SAP...........................................................................................................................................................41startsap..............................................................................................................................................................................41

5.8 Re-initialize Jobs........................................................................................................................................................41After the database restore has successfully completed, the import jobs used by the tp command may not work properly. Proceed as follows:..........................................................................................................................................41Logon to SAP in client 000 as DDIC and run transaction SE38...................................................................................41Execute program RDDNEWPP.......................................................................................................................................41Select Normal...................................................................................................................................................................41A message will show up in the status bar which indicates the job has been scheduled...................................................41

5.9 Schedule Standard Jobs..............................................................................................................................................41Go to transaction SM36 as BASIS-BATCH.................................................................................................................41Schedule all standard jobs................................................................................................................................................41

5.10 Configure SAP Profile Parameter Files.................................................................................................................42After the database restore, the active profiles listed in the SAP system will be from the old hostname. These profiles need to be deleted and the profiles from the OS need to be re-imported. Proceed as follows:.......................................42Run transaction RZ10....................................................................................................................................................42Delete source system profiles:..........................................................................................................................................42Click the Profile drop-down box and choose a profile (this process must be done for each profile)..............................42Select menu items: Profile -> Delete -> All versions of a profile....................................................................................42Click Yes to first prompt to update the database.............................................................................................................42Click No to delete the files from the Op. Sys. Level.......................................................................................................42Click green check on all versions deleted screen.............................................................................................................42Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list........................................................42Import all profiles from UNIX by selecting menu items: Utilities -> Import Profiles -> of active servers.....................42Green back arrow.............................................................................................................................................................42

5.11 Configure Op Modes................................................................................................................................................42After the database restore, the target system will contain Operation Modes from the old hostname. These Op Modes need to be deleted and the correct Op Modes need to be imported. Proceed as follows:...............................................42Run transaction RZ04....................................................................................................................................................42Select Instance/Opmodes.................................................................................................................................................42Select a server name and press SHIFT F2........................................................................................................................42Do this for each source system op mode listed................................................................................................................42Create the target system op mode configuration(s) by selecting the menu items Settings -> Based on Current Status -> New Instances -> Generate..............................................................................................................................................42Click the SAVE button.....................................................................................................................................................42

5.12 Check System Logs..................................................................................................................................................42Check the system logs to see if there were any unusual error messages generated while the SAP system was started back up. Proceed as follows:...........................................................................................................................................42


Execute transaction SM21.............................................................................................................................................42Select menu items System logs -> Choose -> All remote system logs............................................................................42Set the from date/time fields to the date and time just prior to starting the SAP system.................................................42Select the All messages radio button................................................................................................................................42Click the Reread system log button..................................................................................................................................42Review the system messages. Take action on any messages that may look suspicious.................................................42

5.13 Fix Logon Group Names.........................................................................................................................................43Run transaction SMLG...................................................................................................................................................43Add the newly added systems to existing LOGON groups.............................................................................................43Highlight the New Hostname Entries...............................................................................................................................43Click the Assign Group button and assign the Logon groups respectively.....................................................................43Highlight the Old Hostname Entries................................................................................................................................43Click the Delete button.....................................................................................................................................................43Save..................................................................................................................................................................................43Note: Do not delete the groups instead of that delete only instances assigned. If you delete..........................................43the groups both the groups and instances will be deleted................................................................................................43Re-execute transaction SMLG once again and validate the logon group configuration................................................43

5.14 Fix Server Group Names.........................................................................................................................................43Run transaction SM61...................................................................................................................................................43Click pencil for change mode, click cleanup list.............................................................................................................43Select Job-ServerGruppen................................................................................................................................................43Click Create Group...........................................................................................................................................................43Type GENERAL, click continue.....................................................................................................................................43Expand All Groups folder................................................................................................................................................43Highlight GENERAL, click on + assignment..................................................................................................................43Drop down instance name box, select only application servers.......................................................................................43Do this for each application server available, but if no app servers are configured for the instance, use the CI............43Once all the new entries are added. Delete the Source System Entries...........................................................................43

5.15 Import User Master Data........................................................................................................................................43Importing the previously exported Users from the Pre-Client Copy Steps......................................................................43Run T-Code: STMS.......................................................................................................................................................43Click on the transport button (Truck)...............................................................................................................................43Double click on the System name....................................................................................................................................43On the toolbar, goto ExtrasOtherAddAdd the transport request number.............................................................43Click on the transport button (Half Truck) after selecting the added request..................................................................43Provide target Client number and continue......................................................................................................................43

5.16 Post user master import..........................................................................................................................................43Login into your target client.............................................................................................................................................43Run Transaction SCC7...................................................................................................................................................43From Menu options choose start immediately.................................................................................................................43SCC3 check your logs......................................................................................................................................................43

5.17 Import Printer, RFC Definitions............................................................................................................................44Run Transaction SPAD..................................................................................................................................................44Select menu items utilities for output devices delete all........................................................................................44Run Transaction STMS..................................................................................................................................................44Select menu items overview imports double click on target system.................................................................44Select your request. Import request give client no ok........................................................................................44Click refresh until your truck symbol is lost and the transport is successful...................................................................44Repeat this transaction for all the transports....................................................................................................................44Run transaction SPAD...................................................................................................................................................44Select menu items utilities for output devices assign server.............................................................................44Run transaction SM59...................................................................................................................................................44Validate RFC definitions..................................................................................................................................................44

5.18 Fix ITS Information................................................................................................................................................44Run transaction SM30...................................................................................................................................................44Edit the table TWPURLSVR by selecting the change option..........................................................................................44Change the hostname reflecting the new hostname.........................................................................................................44Save..................................................................................................................................................................................44

5.19 Delete Local CUA/Detach a Satellite Client..........................................................................................................44Delete the target hostname and system number under SM1 trusted connection entry....................................................44


Run transaction SE38....................................................................................................................................................44Execute the report RSDELCUA......................................................................................................................................44Select Child System -> <SID>CLNT500 and unselect Test -> execute..........................................................................44Use the Green back arrow to go to the previous screen...................................................................................................44Re-execute the last step to invalidate the CUA contents.................................................................................................44

5.20 Update HP OMS entry in SPAD............................................................................................................................44Use transaction SPAD....................................................................................................................................................44Select Full Administration button....................................................................................................................................44Go to Output Management Systems tab...........................................................................................................................44Check Real Output Management Systems by clicking on Display..................................................................................44Select change and update HP-DAZEL with the new OMS Configuration info...............................................................44For QA2, set it to: “-N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]”................................................................44For UA1, set it to: “-N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]”................................................................44Save..................................................................................................................................................................................44

5.21 Disconnect from previously connected P21............................................................................................................44(For all systems that are source systems of BW: ECC, SRM, CRM)..............................................................................44Run Transaction SE37...................................................................................................................................................44Enter RSAP_BIW_DISCONNECT.................................................................................................................................44Hit Test/Execute (F8).......................................................................................................................................................44Enter data into the following fields:.................................................................................................................................45I_BIW_LOGSYS: P21CLNT500...................................................................................................................................45I_OLTP_LOGSYS: <Logical system for your Production System>...............................................................................45I_FORCE_DELETE: X....................................................................................................................................................45Hit execute (F8)................................................................................................................................................................45

5.22 Converting Logical Systems....................................................................................................................................45Run transaction BDLS....................................................................................................................................................45Enter Old logical system name in the Old logical system name field..............................................................................45Enter New logical system name in the new Logical system Name field.........................................................................45Select Conversion of Client-Dependent and Client-Independent tables..........................................................................45Uncheck Test Run............................................................................................................................................................45Uncheck Existence of New Names in Tables..................................................................................................................45Execute.............................................................................................................................................................................45Press Return again, if any warnings are encountered.......................................................................................................45Rerun this transaction for all the Target Logical System entries.....................................................................................45Note: BDLS should be executed for each existing connection to other components in the respective clients. Example, if the logical system client says 110, BDLS should be executed in client 110 for each logical system connected to the system. This rule applies currently to ECC and SRM where there are multiple clients..................................................45Note: Check the logs in SLG1 for possible errors.........................................................................................................45BW Systems:...................................................................................................................................................................45

5.23 Logical System Names..............................................................................................................................................45Run Transaction BD54..................................................................................................................................................45Verify and Redefine the logical systems as per the screenshot during pre-refresh..........................................................45

5.24 IDOC Port Definitions.............................................................................................................................................45Run Transaction WE21..................................................................................................................................................45Adjust the port assignment / RFC Destinations as per the pre-refresh screenshot..........................................................45Note: During port creation, use the system provided port numbers.................................................................................45Remove any ports that were pointing to production........................................................................................................45

5.25 Partner Profile..........................................................................................................................................................45Create and adjust the Logical System/RFC Destinations as per the pre-refresh screenshot............................................45Activate the partner profiles if set to ‘I’ set it to ‘A’........................................................................................................45If a particular message type is not associated with the IDOC type, maintain the association.........................................45in WE82 transaction.........................................................................................................................................................45

5.26 Create Trusted System............................................................................................................................................46Run Transaction SMT1..................................................................................................................................................46Reconfigure the trusted systems as per the pre-refresh screenshot/description...............................................................46Delete the entries reflecting Source System entries.........................................................................................................46To create the Trusted systems you need to have access to the remote systems with proper authorization in the case of QA2 it was SA2 and SM1. SM1 system will be created by Kevin Flattery....................................................................46

5.27 Republish Services...................................................................................................................................................46Run Transaction SE38...................................................................................................................................................46


Enter Program name W3_PUBLISH_SERVICES..........................................................................................................46Execute and follow the screens to republish the services................................................................................................46Run transaction SICF.......................................................................................................................................................46Select the necessary services one at a time......................................................................................................................46Deactivate the Services....................................................................................................................................................46Activate the Services........................................................................................................................................................46Make sure that the SAP GUI service was enabled and working......................................................................................46

5.28 Trust Manager – Portals Certificates....................................................................................................................46Delete existing certificates and import portal certificates corresponding to target system..............................................46Run Transaction STRUSTSSO2.................................................................................................................................46Check the existing public-key certificate of Portal Servers in component system's certificate list.................................46Delete the Certificates......................................................................................................................................................46Reconfigure/Import the appropriate certificates in component system as during pre-refresh.........................................46Portals Certificates will be imported by Portal administrators........................................................................................46

5.29 Integration Engine Configuration..........................................................................................................................46Run transaction SXMB_ADM......................................................................................................................................46Double Click on Integration engine configuration...........................................................................................................46Reconfigure integration engine data as per the pre-refresh screenshot............................................................................46

5.30 Port Maintenance IDOC Adapters........................................................................................................................46Run transaction IDX1.....................................................................................................................................................46Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot............................................46

5.31 IDOC Adapter Metadata Overview.......................................................................................................................47Run transaction IDX2.....................................................................................................................................................47Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot............................................47

5.32 Verify Distribution Model View.............................................................................................................................47Run transaction BD64 and check pertinent model views..............................................................................................47Verify the same pre-refresh distribution model views existing after request import.......................................................47

5.33 Delete Workload Analysis Logs for Old Server....................................................................................................47Run Transaction ST03...................................................................................................................................................47Change your user mode to Expert Mode..........................................................................................................................47Collector and Performance DB Performance Database Monitoring Database contents...................................47Double click on contents..................................................................................................................................................47In the Host Column select the old host name Delete Server Confirm Delete........................................................47To make the changes effective save it after deleting the server. To view the changes go to the first screen and come back after saving the changes...........................................................................................................................................47

5.34 Reset the passwords for the following users..........................................................................................................47Run transaction SU01....................................................................................................................................................47Reset the password for the following users from the default client. These users will be recreated during the JAVA Install................................................................................................................................................................................47J2EE_ADMIN..................................................................................................................................................................47J2EE_GUEST...................................................................................................................................................................47SAPJSF.............................................................................................................................................................................47XI* (Only on XI systems)................................................................................................................................................47LD* ( Only on XI systems)..............................................................................................................................................47

5.35 Client Definition.......................................................................................................................................................47Run Transaction SCC4...................................................................................................................................................47Change the client description to reflect as per pre-refresh description............................................................................47

5.36 Maintain DBA Planning Calendar.........................................................................................................................47Run transaction DB13 as BASIS-BATCH....................................................................................................................47Setup DBA jobs as per the pre-refresh screenshot...........................................................................................................47

5.37 qRFC Monitor..........................................................................................................................................................47Run transaction SMQR & SMQS..................................................................................................................................47Delete old monitor and setup new monitor with correct system name. .(Registration Table-> Reorganise)..................47SMQ1, SMQ2 deleted the old queues and any old error entries .....................................................................................47

SLD Specific........................................................................................................................................................................485.38 Maintain SLD connection parameters............................................................................................................48Run transaction SLDAPICUST....................................................................................................................................48Change the connection parameters pointing to correct SLD source................................................................................48To change switch to editing mode and choose Insert Row. Specify the connection parameters (host name, port, user, and password) and set this SLD server as Primary. Only the entry marked as Primary is active....................................48


Save your entries..............................................................................................................................................................48Configure the SLD Data Supplier Service in the Visual Administrator.......................................................................48Logon as j2ee_admin/administrator in Visual Admin.....................................................................................................48Change and verify the connection parameters for SLD connection and CIM client generation settings in SLD Data supplier service.................................................................................................................................................................48Verify by triggering the SLD data load............................................................................................................................48Maintain the SLD connection in ABAP systems...........................................................................................................48Run transaction RZ70....................................................................................................................................................48Maintain SLD bridge host and gateway...........................................................................................................................48Validate SLD Connection/configuration..........................................................................................................................48Run transaction SLDCHECK........................................................................................................................................48Validate the all the checks are successful........................................................................................................................48

5.39 Schedule XML Messages Delete Jobs......................................................................................................................48Run Transaction SXMB_ADM as user DDIC.............................................................................................................48Go to SXMB_ADM Define Interfaces for Archiving and Retention Periods Retention periods.........................48Retention Periods for Asynchronous messages in the Database:.....................................................................................48XML Messages without Errors Awaiting Deletion: 30 Days.....................................................................................48XML Messages without Errors Awaiting Archiving: 7 Days.....................................................................................48Retention periods for Synchronous messages in the Database:.......................................................................................48XML Messages with Errors Awaiting Deletion: 7 Days.............................................................................................48XML Messages without Errors Awaiting Deletion: 0 Days.......................................................................................48Retention periods for History entries in the Database:....................................................................................................48History Entries for Deleted XML Messages: 35 Days...............................................................................................48Run Transaction SXMB_ADM as user DDIC.................................................................................................................48Schedule Delete Jobs........................................................................................................................................................48Check the settings and reconfigure as per the screenshot taken......................................................................................48Verify Parameters: Period of Days set to 1......................................................................................................................48Click on Job Overview (SM37) and verify the below jobs scheduled as pre-refresh......................................................48SAP_BC_XMB_DELETE_<client>................................................................................................................................48SAP_BC_XMB_HIST_DELETE_<client>.....................................................................................................................48

5.40 Attach a Satellite Client to CUA.............................................................................................................................49Logon to Satellite Client................................................................................................................................................49Run T-Code: SM59.......................................................................................................................................................49Validate entry for an ABAP system - SA2_SYSTEM.....................................................................................................49Validate entry for an ABAP system - SA2CLNT100......................................................................................................49Run T-Code: BD54........................................................................................................................................................49Select New Entry..............................................................................................................................................................49Define a new Logical System for CUA, e.g., SA2CLNT100..........................................................................................49Provide a description under Name...................................................................................................................................49Save..................................................................................................................................................................................49Create a new transport or use an existing transport.........................................................................................................49Run T-Code: SMT1........................................................................................................................................................49Select Create Button.........................................................................................................................................................49SA2CLNT100 in Destination field..................................................................................................................................49Login to CUA System.....................................................................................................................................................49Run T-Code: SM59.......................................................................................................................................................49Validate ebtry for the ABAP system – Q42CLNT500....................................................................................................49Run T-Code: BD54........................................................................................................................................................49Validate Logical System entry for Satellite System, e.g., Q42CLNT500.......................................................................49Create a new transport or use an existing transport.........................................................................................................49Run T-Code: SCUA........................................................................................................................................................49Enter the Satellite Instance Name, e.g., S11CLNT005 at the bottom of the list..............................................................49Select SAVE.....................................................................................................................................................................49You will have to enter DDIC user-id and password for the satellite system on the follow-up screen............................49Check the log file to validate that this command is completed successfully...................................................................49Logon to Satellite Client................................................................................................................................................49Run T-Code: WE20..........................................................................................................................................................49Validate that under LS, a Partner Profile for SA2CLNT100 is now defined and also SU01 has lesser number of available options...............................................................................................................................................................49


6. INSTALL J2EE AND APPLY JAVA PATCHES ON CI.................................................506.1 NW04S – Java Install................................................................................................................................................50

DVD/CD Name................................................................................................................................................................50Package Selection.............................................................................................................................................................50Installation........................................................................................................................................................................50KERNEL DVD................................................................................................................................................................50/sapcd/sap/install/unicode/crm50/kernel/kernel/KN_HPUX_IA64.................................................................................50SCS...................................................................................................................................................................................50/sapcd/sap/install/unicode/crm50/kernel_2/kernel2/KU_HPUX_IA64...........................................................................50SCS & CI..........................................................................................................................................................................50JAVA DVD......................................................................................................................................................................50NetWeaver........................................................................................................................................................................50/sapcd/sap/install/unicode/crm50/java_usage/java/J2EE_OSINDEP..............................................................................50DB & CI...........................................................................................................................................................................50/sapcd/sap/install/unicode/crm50/java_export/java_export.............................................................................................50DB....................................................................................................................................................................................50

6.2 NW04 Install(SRM/SCM Specific)...........................................................................................................................516.3 Java Patches on CI....................................................................................................................................................52

6.3.1 Update SDM..........................................................................................................................................................526.3.2 Update JSPM........................................................................................................................................................526.3.3 Apply Java Patch on CI.......................................................................................................................................536.3.4 Troubleshoot Errors while applying support package using JSPM................................................................536.3.5 For Target systems (Eg: SRM, SCM) which have J2EE 640 (Oracle 9i) install on Oracle 10.2 Database

53

7. POST SAP SYSTEM SPECIFIC STEPS:..................................................................547.1 XI Specific Steps........................................................................................................................................................54

7.1.1 Configure the SLD Bridge (XI).........................................................................................................................547.1.2 Configure CMS Setup........................................................................................................................................547.1.3 Run transaction SXMB_IFR.............................................................................................................................547.1.4 Activate XI related services................................................................................................................................547.1.5 Refresh XI Cache...............................................................................................................................................547.1.6 XI Message Archiving & Deletion....................................................................................................................547.1.7 Configure JCo RFC provider using Visual Admin..........................................................................................55

7.2 BI Specific Steps..........................................................................................................................................................577.2.1 Restore the Logical system destinations............................................................................................................577.2.2 Restore the Table RSBKDTP entries to Target SID........................................................................................577.2.3 Restore Source System Connection..................................................................................................................587.2.4 Maintain IDOC Sender/Receiver Systems.......................................................................................................587.2.5 RSA1 Check........................................................................................................................................................587.2.6 BI Integration into the Portal............................................................................................................................587.2.7 Configure UDC...................................................................................................................................................597.2.8 Modify Logical System conversion Table........................................................................................................607.2.9 Change BIA (BI Accelerator) RFC Destination.............................................................................................60

7.3 SCM Specific Steps....................................................................................................................................................617.3.1 Delete connections to liveCache........................................................................................................................617.3.2 Setup Logical Systems........................................................................................................................................617.3.4 qRFC Monitor....................................................................................................................................................617.3.5 Start CIF queue.................................................................................................................................................617.3.6 liveCache Restore...............................................................................................................................................617.3.7 liveCache consistency.........................................................................................................................................62

7.4 ECC Specific Steps....................................................................................................................................................627.4.1 Update Custom tables...........................................................................................................................................627.4.2 ECC Adapter Ports...............................................................................................................................................62

7.5 SRM Specific Steps....................................................................................................................................................637.5.1 Update Custom table : ZPCARDENCRYPT.....................................................................................................637.5.2 Update Custom table : ZZRFCDES...................................................................................................................637.5.3 Synchronize Encryption for SRM.......................................................................................................................647.5.4 IPC Settings...........................................................................................................................................................64


7.6 CRM Specific Steps.....................................................................................................................................................65Maintain CRM RFC Parameter........................................................................................................................................65Update CRMC ICM RFC Parameter...............................................................................................................................657.7 Control-M Specific Steps............................................................................................................................................677.8 FireFighter Installation................................................................................................................................................68

8. BEFORE RELEASING SYSTEM TO BUSINESS – (POST CHECKOUTS).............698.1 General Check for All Systems..................................................................................................................................69

8.1.1 Valid license for PRD in DR-systems..................................................................................................................698.1.2 SAP access PRD Cl..............................................................................................................................................698.1.3 Oracle Alert Log...................................................................................................................................................698.1.4 DB12 – Backup Logs...........................................................................................................................................698.1.5 DB13 – DBA Planning Calendar.........................................................................................................................698.1.6 OS07.....................................................................................................................................................................698.1.7 RZ70 -> Ensure successful transmission of data to SLD.....................................................................................698.1.8 RZ03 -> No Configuration Alerts........................................................................................................................698.1.9 SICK – SAP Initial Consistency Check...............................................................................................................698.1.10 SMICM -- ICM Monitor.....................................................................................................................................698.1.11 SM12 – Check Lock Entries................................................................................................................................698.1.12 SM13 – Check Update Requests..........................................................................................................................698.1.13 SM21 – System Logs...........................................................................................................................................698.1.14 SM37 – Batch Jobs...............................................................................................................................................698.1.15 SM51 – Check SAP Servers.................................................................................................................................698.1.16 SM50 – Check Work Processes...........................................................................................................................698.1.17 SM59 -> ABAP Connections -> Check connectivity to other SAP system in the landscape..............................698.1.18 SMLG – Check SAP Logon Groups....................................................................................................................698.1.19 SPAD -> Print to any printer other than LOCL and validate successful printing using SP01.............................698.1.20 ST22 – Check SAP Dumps..................................................................................................................................698.1.21 SM58 – Check Transactional RFCs.....................................................................................................................698.1.22 SMQ1 – Monitor Outbound Queue......................................................................................................................698.1.23 SMQ2 – Monitor Inbound Queue........................................................................................................................698.1.24 http://hostname:5xx00 -> Check system Information -- Check System Information and Patch levels.............698.1.25 Tcode SICF..........................................................................................................................................................69

8.2 ECC Specific...............................................................................................................................................................698.2.2 SM59...................................................................................................................................................................698.2.3 KGS.....................................................................................................................................................................708.2.4 FAX......................................................................................................................................................................708.2.5 ITS Check............................................................................................................................................................70

8.3 BW Specific...............................................................................................................................................................718.3.1 RSA1 -> Source System -> Right Click individual system and select Check...........................................718.3.2 Check for BI UDC................................................................................................................................................71

8.4 SRM Specific.............................................................................................................................................................728.4.1 SM59 Tcode – Check for Live Auction.............................................................................................................728.4.2 SMOKE TEST for Live Auction..........................................................................................................................728.4.3 Check certificates................................................................................................................................................728.4.4 Check encryption.................................................................................................................................................72

8.5 XI Specific..................................................................................................................................................................738.5.1 SXMB_IFR........................................................................................................................................................738.5.2 SXMB_MONI...................................................................................................................................................738.5.3 TIBCO SXMB_IFR.......................................................................................................................................73

8.6 SCM Specific Checkouts..........................................................................................................................................748.6.1 LC10 - Check for LiveCache..............................................................................................................................748.6.2 JDBC Check..........................................................................................................................................................748.6.3 Analyse LiveCache & LCA Objects......................................................................................................................748.6.4 Optimizer Installation Tests..................................................................................................................................748.6.5 Check for BI UDC.................................................................................................................................................748.6.6 APO Consistency Check.......................................................................................................................................74


APPENDIX...........................................................................................................................75Steps to reset the SDM password......................................................................................................................................75

Logon to the system as <sid>adm....................................................................................................................................75cd /usr/sap/<SID>/DVEBMGSxx/SDM/program............................................................................................................75./sdm.sh jstartup sdmhome=”/usr/sap/<SID>/DVEBMGSxx/SDM/program” mode=standalone.................................75./sdm.sh changepassword sdmhome=”/usr/sap/<SID>/DVEBMGSxx/SDM/program newpassword=xxxxx................75./sdm.sh jstartup sdmhome=”/usr/sap/<SID>/DVEBMGSxx/SDM/program” mode=integrated..................................75

Steps to synchronize SDM Server.....................................................................................................................................75if required if your java patches doesn’t reflect in the system info after applying them with JSPM................................75Go to /usr/sap/DC2/DVEBMGS37/SDM/program..........................................................................................................75./StopServer.sh..................................................................................................................................................................75./sdm.sh SystemComponentState “mode=Sync”..............................................................................................................75./StartServer.sh.................................................................................................................................................................75Once Dev1 Instance is up and TMS is set in the Dev1 instance then run the following:................................................75Reset TMS........................................................................................................................................................................75Logon to SAP in client 000 as DDIC on the DEV Instance (TMS Domain Controller for system, i.e. D11 or D21, D41, D51)..................................................................................................................................................................................75Run transaction STMS.....................................................................................................................................................75Overview -> systems........................................................................................................................................................75CTRL F10 – Distribute and Activate TMS configuration...............................................................................................75Select Distribute configuration to all systems..................................................................................................................75You might be prompted to LOGON to Target system, just logon to client 000 with DDIC user/password...................75

To recreate PSAPTEMP table space................................................................................................................................75Logon to UNIX level as ora<sid>....................................................................................................................................75mkdir –p /oracle/Q41/sapdata3/temp2.............................................................................................................................75sqlplus “/ as sysdba”........................................................................................................................................................75create temporary tablespace psaptemp2 tempfile '/oracle/Q41/sapdata3/temp2/temp.data1' size 100m;......................75ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP2";...........................................................75drop tablespace PSAPTEMP including contents;............................................................................................................75create temporary tablespace psaptemp tempfile '/oracle/Q41/sapdata3/temp_1/temp.data1' size 1048584192 reuse autoextend off;..................................................................................................................................................................75ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP";.............................................................75drop tablespace PSAPTEMP2 including contents;..........................................................................................................75exit;...................................................................................................................................................................................75

Starting Java SDM server..................................................................................................................................................76Stopping Java SDM server:...............................................................................................................................................76


1. Pre-Database/SAP Refresh Most of the steps under this section will be performed at least One week prior to Refresh .

1.1 Post a System Message about Scheduled DowntimeUse SM02 T-code to Post a System Message and let users know about the scheduled downtime.

Example:IMPORTANT : <SAPSID> System will be unavailable from 10-Oct-2007 at 5pm CST to 15-Oct-2007 at 10am CST for a System Refresh. Please, plan your work accordingly.

1.2 SaplicenseLogon to as <sid>adm on Source System Check your sap license saplicense –show

Export the saplicense information to a file under <sid>adm home directory.cd /home/<sidadm>saplicense –show > saplicense.SID

1.3 Confirm Passwords for Source/Target system with Security teamDDIC password in Client 000DDIC and BASIS-BATCH in default client.


1.4 Stage Instance Specific Information before Volume Group is recreatedValidate staging File System is available. This should return a valid File System entry.

bdf /usr/sap/put_refresh

Copy the required directories to the staging Directory - /usr/sap/put_refreshcd /usr/sap/put_refrershmkdir -p oracle/T_SIDmkdir -p usr/sap/T_SID/DVEBMSxxmkdir -p sapmnt/T_SIDcd /oracle/<T_SID>tar -cvf /usr/sap/put_refresh/oracle/U11/102_64.tar 102_64{Note: To check the tar file structure tar -tvf <filename>.tar}

cd /oracle/<T_SID>tar –cvf /usr/sap/put_refresh/oracle/U11/dotastrik.tar .[a-z]*cd /sapmnt/<T_SID>tar -cvf /usr/sap/put_refresh/sapmnt/U11/profile.tar profilecd /usr/sap/<T_SID>/DVEBMGSxxtar -cvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar igscd /oracletar –cvf /usr/sap/put_refresh/oracle/client.tar clienttar -cvf /usr/sap/put_refresh/oracle/oraInventory.tar oraInventoryTeam - Please add any other directories or files that you want to save off before the Volume Group is recopied with Target Volume Group.

1.5 Export User Master dataLog on to source client with SAP Run Transaction SCC8.

Select profile SAP_USER Select target system start immediately

Make note of the SIDKTxxxxx transport number from the pop-up screen. The data and cofiles will be created with this numbers.

Check the appropriate export log to validate if the export was successful. SCC3 exports check for the current export logs

Always, logon as <sid>adm at the OS level and validate the recent creation of cofiles & data files. cd /usr/sap/trans/cofiles ls –ltr

The KTxxxxx.SID file should have been created with recent time stamp. cd /usr/sap/trans/data ls –ltr

The RTxxxxx.SID file should have been created with recent time stamp.


1.6 Transport Printer DefinitionsRun Transaction SPAD

Output Devices – Display Go to Edit – transport – transport all Note down the request number Release the Transport

1.7 Transport RFC DefinitionsCreate a workbench request in SE01Go to change mode of your requestInclude the following object Name with Program ID : R3TR Object Type : TABU

RFCATTRIB RFCDES RFCDESSECU RFCDOC

Now double click on each of your RFC table entry and it will open another screen and click on “Insert Row” button.Give * as input (i.e. all the keys corresponding to that table are taken)Now save the transport requestNote down your request numberRelease your request.

1.8 Logical System DefinitionsRun Transaction BD54

Take a screenshot of Logical Systems Definition

1.9 Partner Profile Run Transaction WE20

Take a screenshot of Partner Profile, specifically all Partner Type – Logical Systems

1.10 IDOC Port Definitions Run Transaction WE21

Drill Down on ‘Transactional RFC’, Take a screenshot of RFC Destination Port Assignment

1.11 Client Definitions Run Transaction SCC4.

Take a screenshot of client’s overview – to note the Client Description and settings.

1.12 Trusted Systems Run Transaction SMT1.


Take a screenshot of trusted systems – to note the Client Description. This needs to be reconfigured during post refresh activities.

1.13 Trust Manager – Portals CertificatesRun Transaction STRUSTSSO2.Check the existing public-key certificate of Portal Servers in component system's certificate list. This needs to be reconfigured during post refresh activities.

1.14 Integration Engine Configuration Run transaction SXMB_ADM

Double Click on Integration engine configurationTake screenshot of configuration data

1.15 Maintain SLD Access data Run transaction SLDAPICUST

Take a snapshot or make note of the entries.

1.16 SLD Bridge Info – ABAP/JAVA

1.16.1 ABAP Run Transaction RZ70

Take screenshot or note the SLD Bridge Host and Service Info.

1.16.2 Java Logon to Visual Admin Go to services Select SLD Data Supplier Note SLD Data Collection Settings Note CIM Client Generation Settings

1.17 Port Maintenance IDOC Adapters Run transaction IDX1

Note all the ports and corresponding RFC destinations or take a screenshot of the same. This needs to be reconfigured during post refresh.

1.18 IDOC Adapter Metadata Overview Run transaction IDX2

Note all the ports and corresponding RFC destinations or take a screenshot of the same. This needs to be reconfigured during post refresh.

1.19 Distribution Model ViewRun transaction BD64


Take a snapshot or make note of the entries.

1.20 Maintain CRM RFC Parameter This entry is maintained in table CRMRFCPAR in all sender/receiver systems (R3/BW etc) Verify the entries take a screenshot.

1.21 Validate HP OMS entry in SPAD Use transaction SPAD

Select Full Administration button Go to Output Management Systems tab Check Real Output Management Systems by clicking on Display Double click on HP-DAZEL and validate OMS Configuration info

For Eg. QA2, it should be: “-N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]”For Eg. U11, it should be: “-N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]”Take a note or screenshot of the settings and if different add its entry on previous line for the specific SID.

Please Add SBX specific info

1.22 Display / Note Logon Group Definitions Run Transaction SMLG Take a screenshot of currently configured logon groups

1.23 Check operation modes Run Transaction RZ04

Take a screenshot of currently defined OP modes

1.24 Check for ITS Run transaction SM30

Give the table name TWPURLSVR Click on Display Double click on your Logical system host name

Take a screen shot of that so that after the refresh we can reconfigure the same.

1.25 Verify DBA Planning Calendar Run transaction DB13.

Note the scheduling period for DBA jobs or take screenshot.


1.26 XI Specific Steps

1.26.1 Export SLD Information Logon to xi Run Transaction SLDCHECK

Select Administration Select contents Export All (in export line) save the file to your desktop.

1.26.2 Export the Repository server informationLogon to Windows terminal server

Logon to your Target system Run transaction SXMB_IFR Sap Exchange Infrastructure Page will be opened Select Integration builder Log on with xisuper Integration builder page will opened

In objects tab Here a list of software components will be present thereSelect the software component Go to toolsClick on Export Design ObjectsSelect the icon at the end of the software component version fieldA list of software components will be displayedExpand your software componentSelect your software component versionClick on ApplyClick on continue

Now select objects list field will be displayedExpand your object setSelect all objects of software component versionClick on Finish ButtonExport all your repository objects using the above procedure.The objects will be exported to /sapmnt/<SID>/global/xi/repository_server/exportAfter the export is completed move all the objects from export directory to a temporary directory to import them later after the JAVA install. At that point, move these files to the following directory to import – /sapmnt/<SID>/global/xi/repository_server/import


1.26.3 Export the Directory server informationNow go to your Sap Exchange Infrastructure PageClick on Integration Directory linkLogon with xisuperIntegration builder page will opened In the scenarios tab select your Configuration ScenarioGo to tools Select Export Configuration ObjectsSelect mode will be displayedSay continueSelect object set all objects of a ScenarioSelect your business scenarioSay okClick finishExport all your directory objects using the above procedure.The objects will be exported to /sapmnt/<SID>/global/xi/directory_server/exportAfter the export is completed move all the objects from export directory to a temporary directory to import them later after the JAVA install. At that point, move these files to the following directory to import - /sapmnt/<SID>/global/xi/directory_server/import

1.26.4 Configure CMS SetupVerify if the following parameters are set to true in Integration Builder section..

com.sap.aii.ibdir.core.cms.enableTransportWizardcom.sap.aii.ibdir.core.enable.TransportWizardcom.sap.aii.ibrep.core.cms.enableClTransportcom.sap.aii.ibrep.core.cms.enableTransportWizard

1.26.5 SLD DATA supplier and BridgeLog on to http://url:port/sld go to administration and select data supplier bridge.Note down the configured SLD bridges.

1.26.6 SLD Business SystemsLog on to http://url:port/sld go to Technical and then Business systemsNote all the Technical and Business Systems configured along with transport groups source and target. This needs to be reconfigured during post refresh.


1.26.8 XI Message Archiving & DeletionCheck Existence of physical directory at the operating system level for storing the archived XI messages at the following location.As always, make sure that the /interfaces directory and the FILEPORTS are correctly changed.

Path: interfaces/<sid>/client/out/ready/archiving/

Verify logical path in TCODE ‘FILE’ and take snapshots at the locations below:i) Logical File = ARCHIVE_XI_DATA_FILE double click Specify physical/logical file path based on pre-refresh screenshotTake snapshot * Validate Definition of variable: FILENAME and SYNTAX GROUP Definition** Validate Definition of variable “FILENAME” ** Validate Syntax group Definition Take snapshot in both the cases

ii) Transaction: SXMB_ADM Schedule Archiving Job Archive Administration Make sure the object is BC_XMB Click on Customizing. Go to Cross-Archiving Object Customizing Technical Settings [Take ScreenShot]

iii) Transaction SXMB_ADM Archiving Object – Specific Customizing Technical settings. Configure as per pre-refresh screenshot. * Make sure the Delete Jobs is set to “Start Automatically” and a logical File Name.

iv) Transaction : SXMB_ADM Define Interfaces for Archiving and Retention Periods [Take snapshot] Click on Retention periods[Take snapshot]


1.27 BI Specific Steps

1.27.1 Conversion of Logical System NamesLogon to BI Run Transaction RSA1Select Tools -> Conversion of Logical System NamesTake a screenshot of conversion Table to reinstate after refresh before transports are applied

1.27.2 UDC Connection Container SettingsTelnet to BI Central instance as <sid>adm using Reflection or Hummingbird X-Term session:

cdDcd j2eecd admin./go (make sure an x-client is used with DISPLAY variable set up)select the Central Instance Server in the left pane and open it upselect Services -> JDBC ConnectorNow select Connector Container in the left paneSelect the jdbc connector container, e.g., SDK_JDBC_TDSDK_JDBC_TD_ISCP

Go to tab “Managed Connection Factory” and then “Properties” for all the specified connector containers,

Note down the following for each of the Connectors Document the FixedSchema Find the password for Password field (Obtain Password Prior to refresh) and

document it for each landscap in this document for future refreshes. Document for URL Document for UserName

1.28 SCM Specific Steps

1.28.1 Document connections to liveCacheRun transaction LC10


Name of database connection: Type LCAPress Integration buttonSwitch to change mode <Shift+F1>Delete connection (Connection|Delete)Repeat 1-4 for remaining connections. Hit drop down on database connections to find all connections

1.28.2 Configure UDC (* same step as BI **)Telnet to SCM Central instance as <sid>adm using Reflection or Hummingbird X-Term session:

cdDcd j2eecd admin./go (make sure an x-client is used with DISPLAY variable set up)select the Central Instance Server in the left pane and open it upselect Services -> JDBC ConnectorNow select Connector Container in the left paneSelect the jdbc connector container, e.g., SDK_JDBC_TDSDK_JDBC_TD_ISCP

Go to tab “Managed Connection Factory” and then “Properties” for all the specified connector containers,

Note down the following for each of the Connectors Document the FixedSchema Find the password for Password field (Obtain Password Prior to refresh) and

document it for each landscap in this document for future refreshes. Document for URL Document for UserName

1.28.3 Document Business System Groups (BSG)Run transaction /SAPAPO/C1Hit new entriesBUS<SID><First 2 characters of client>Description Bus Sys Grp - <SID>CLNT<Client>document BSG to Logical System/SAPAPO/C2

1.28.4 qRFC MonitorRun transaction SMQRSMQ1 and SMQ2 and make sure there is no data.

1.28.5 Stop/check CIF queue/n/SAPAPO/OM17/nWE02 check the failed iDOC


1.28.6 LiveCache consistency/n/SAPAPO/OM13

1.28.7 Backup liveCacherun dbmgui > connect source system > make complete backup to the file system >validate the backup file from unix > rename the file to xx.orig

Check and Verify Launch MaxDB dbm GUI from your laptop/PC Click on backup Select complete data backup and click next. Connect to source LC instance

database server: FQDN of database server database name: <Source SID> username:control Password:control

Backup file will be created under default path /sapdb/<sid>/sapbackup/full.<source sid>_COM

FTP the source file (i.e. /sapdb/<sid>/sapbackup/full.<source sid>_COM ) to the target system to the following location

/sapdb/<T_sid>/sapbackup/

1.29 SRM Specific

1.29.1 Copy the SRM IPC parameter file cp /usr/sap/ipc/lib/properties/parameters.xml /usr/sap/put_refresh/srm_<S_SID>.parameter.xml


Please Add this specific info for all the landscapes

1.30 Display/Note Logical PortsRun transaction LPCONFIG to confirm the settings or take screenshot of the

logical port.Here – “Port for SmartMapper Lookup” double click and verify the parameter URL

path.Example -- http://PHGP0159:14810/XrefLookup_WS/Xref_Lookup.serviceagent/Xref_LookupEndpoint

This settings needs to be reconfigured during post refresh.


2 Database Backup

2.1 Oracle Database Backup – Source SystemBased on DB Refresh requirement, we will perform one of the following backups.

Disk_to_Disk_Copy Offline Backup Online Backup

2.2 SCM maxDB liveCache Backup - Source System

Rename file from /sapdb/<T_sid>/sapbackup/full.<sourcesid>_COM to /sapdb/<T_sid>/sapbackup/full.<targetsid>_COM ***** make sure to follow proper case while renaming file name.*****

Toggle source database to ADMIN mode - Connect to target LC instance(QL2,UL1,DL2 etc) from OS level and log in as <sid>adm - Connect to DBM client by typing the command


dbmcli –d <sid of LC instance> -u control,control

-You will be connected to dbm client on that instance. db_admin

Launch dbm gui again and connect to target LC instance -Click on recovery with initialization -restore a medium

-fullfile Click Start

Log on to SCM server and go to transaction LC10.

Click on Integration and change all settings corresponding to the target system, reset password for CONTROL and SAPQL2.

3. Oracle Database Restore – Target System

3.1 Reproduce Source System environment on Target SystemCreate soft link for Source Systemln –s /oracle/<T-SID> /oracle/<S-SID> Validate user exists on the target system.Change the ownership of all /oracle/<T-SID> files to source system ora<s-

sid>.To change the ownership we need to be the root. Now login as rootsudo su –Change the ownershipchown –R ora<target_sid>:dba /oracle/<Source_SID>

3.2 Add Source system in /etc/hosts fileWork with the OS team to make sure you have an entry for the source system in the target systems’ /etc/hosts file. This is needed to avoid affecting the source system during the re-build activities.


3.3 Start database as Source SystemLogon the target system as ora<Source_system_sid> su – ora<s-sid> sqlplus “/ as sysdba” startup; exit

3.4 Create Control FileLogon the target system as ora<source_system_sid>su – ora<s-sid>sqlplus “/ as sysdba”alter database backup controlfile to trace;exit

cd /oracle/<Source_SID>/saptrace/usertraceGet the latest file you just created through sqlplus command

vi ` ls –ltr |tail -1|awk ‘{print $9}’ `Go to the end of the file and scroll up till you see the following textSTARTUP NOMOUNTScroll one line up and delete all the lines from the beginning of the file to the current line.:1,.dOnce you have deleted the lines, your first line should beSTARTUP NOMOUNTNow replace the Source_SID with Target_SID on all the lines by running the following command. :%s,Source_SID,Target_SID,gNow search the string CREATE in the file and replace the following line:/CREATECREATE CONTROLFILE REUSE DATABASE "<Target_System_SID>" RESETLOGS ARCHIVELOGWithCREATE CONTROLFILE SET DATABASE "<Target_System_SID>" RESETLOGS

For editing the line do the following, On the following line go to end of the line CREATE CONTROLFILE REUSE DATABASE "<Target_System_SID>" RESETLOGS ARCHIVELOG$Move your cursor upto word ARCHIVELOG by using key h on your keyboarddwand move your cursor upto word REUSE and by using h on your keyboard dw


now switch to insert mode iNow write SETNow your modified command looks like CREATE CONTROLFILE SET DATABASE "<Target_System_SID>" RESETLOGSNow search the string RECOVER in the file and replace the following line:/RECOVERRECOVER DATABASE USING BACKUP CONTROLFILEWithRECOVER DATABASE USING BACKUP CONTROLFILE until cancelFor editing the line do the followingGo to end of the line and append as follows $auntil cancelNow your modified command looks like RECOVER DATABASE USING BACKUP CONTROLFILE until cancelNow save the file as /tmp/rename.sql using the following command::w /oracle/<Source_SID>/rename.sql

3.6 Copy back the pre-staged files from the staging Directory - /usr/sap/put_refreshsudo su –cd /oracle/<T_SID>rm –fr 102_64 cd /oracle/<T_SID{Note: To check the tar file structure tar- tvf <filename>.tar}tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/102_64.tar cd /oracle/<T_SID>tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/dotastrik.tar cd /sapmnt/<T_SID>tar -xvf /usr/sap/put_refresh/sapmnt/<T_SID>/profile.tar cd /usr/sap/<T_SID>/DVEBMGSxxtar -xvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar cd /oracletar -xvf /usr/sap/put_refresh/oracle/client.tar tar -xvf /usr/sap/put_refresh/oracle/oraInventory.tar

3.7 Change the ownership of all <T-SID> files to target system

3.7.1 To change the ownership we need to be the root Login as root sudo su –

Remove exe Directory from the Instance Directories. This will be recreated with the J2EE Install.cd /usr/sap/<SID>/SCSxxrm –fr exe


cd /usr/sap/<SID>/DVEBMGSxxrm –fr exeRemove and re-create /usr/sap/<SID>/SYS/exe/run Directory cd /usr/sap/<SID>/SYS/exe/rm –fr runmkdir run

3.7.2 Change the ownershipchown –R ora<target_sid>:dba /oracle/<Target_SID> chown –R <target_sid>adm:sapsys /usr/sap/<Target_SID> chown –R <target_sid>adm:sapsys /sapmnt/<Target_SID>

3.7.3 Set the permission for the new kernel filescd /sapmnt/<SID>/exechown –R <sid>adm:sapsys *chmod –R 755 *

3.7.4 Copy the files from /sapmnt/<SID>/exe to /usr/sap/<SID>/SYS/exe/run Directory

cd /sapmnt/<SID>/execp –rp * /usr/sap/<SID>/SYS/exe/run/.

3.7.5 Now run the saproot.sh script./saproot.sh <SID>Note: saproot.sh script file updates the ownership and permissions of files under the following path: /usr/sap/<SID>/SYS/exe/run

3.7.6 Now copy the files from /usr/sap/<SID>/SYS/exe/run to /sapmnt/<SID>/exe

cd /usr/sap/<SID>/SYS/exe/runcp –rp * /sapmnt/<SID>/exe/.

3.8 Recover Database as Target System

3.8.1 Recover the database on target system as ora<Target_sid> Check the Online Logs permission in /oracle/<T_SID>/oraarch directory. It should be set as:

Owner : ora<T_SID> Group : dba

Sqlplus “/ as sysdba”@rename.sql


This might ask for multiple Online logs to recover; so, just keeps “ENTER” and watch carefully the screen.cancelNote:- here it will ask us for CANCEL option at the end of command execution. Say CANCELalter database open resetlogs;

Open another telnet session to tail the rename.sql file and run the last sql command from the rename.sql file to create the PSAPTEMP tablespace. Here is the example of the command you need to run:

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/<Target_SID>/sapdata3/temp_1/temp.data1' SIZE 629145600 REUSE AUTOEXTEND OFF;

3.8.2 Restart the database to make sure that DB starts correctlyshutdown immediatestartup

3.8.3 Create the ops$<Target_sid>adm users and grant permissioncreate user ops$<Target_sid>adm identified externally default tablespace psapdatusr temporary tablespace psaptemp;Grant dba,connect,resource to ops$<Target_sid>adm;create user ops$ora<Target_sid> identified externally default tablespace psapdatusr temporary tablespace psaptemp;Grant dba,connect,resource to ops$ora<Target_sid>;create table ops$<Target_sid>adm.sapuser as select * from ops$<Source_sid>adm.sapuser;exit

3.8.4 Test the connectivity to the database as user <Target_sid>admsu - <sid>admR3trans –dThis should give the return code of (0000) for successful logon to database.If it was not able to connect /logon to database it will throw a return code 0008.

3.9 Create the Oracle Password File (OPTIONAL)Logon to UNIX level as ora<sid>sqlplus / as sysdbacreate pfile from spfile;shutdown immediate;


Using vi add the following entry"remote_login_passwordfile = exclusive"Create the Oracle password file:$ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/dbs/orapw<SID> password=<system password> entries=100(Use password for system)Logon to UNIX level as ora<sid>sqlplus “ / as sysdbacreate spfile from pfile;startup

4 Delete Target Java Installation4.1 **Delete the currently installed JAVA Installation**

Make sure your Database is down for this step, which it should be since you did not start SAP as yet.

4.2 Delete the following directories on Target DB serverSu -<sid>admcdDrm –fr /usr/sap/<SAPSID>/DVEBMGS<xx>/SDMrm –fr /usr/sap/<SAPSID>/DVEBMGS<xx>/j2eerm –fr /usr/sap/<SAPSID>/SCS<xx>rm –fr /sapmnt/<SAPSID>/exeU (If it exists.)Note: - The directory exeU is only present in versions below 640.

4.3 Delete the following directories on each of the application server/usr/sap/<SAPSID>/D<xx>/j2ee

4.4 Delete the JAVA profilecdprorm -f /sapmnt/<SAPSID>/profile/<SID>_SCSxx_hostname rm - f /sapmnt/<SAPSID>/profile/START_SCSxx_hostname

4.5 Drop your j2ee schemaLog on as user ora<Target_sid>Start sqlplus and connect to the database. sqlplus /nologconnect / as sysdba


startupNote:- when sqlplus /nolog is executed we get the error connected to an idle instance. This means the database is not connected. So at that time we need to start the database using startup command. Enter the following command to delete the database objects of the database schema:drop user SAP<Source_System_SID>DB cascade;Enter the following command to get the name of schema of the associated data

files in the systemselect file_name from dba_data_files where tablespace_name = 'PSAP<Source_System_SID>DB';

4.6 Now drop the table spaces as they are emptyEnter the following command to delete the tablespace of the database schema:drop tablespace PSAP<Source_System_SID>DB including contents;Exit sqlplus:shutdown immediateexit

4.7 Delete the data files of tablespace PSAP<Source_SID>DB from the system rm –rf /oracle/<Source_SID>/sapdata4/<Source_SID>db_1

Now your java instance is completely deleted.


5 Post SAP Refresh5.1 Install sap license

Logon as <sid>admsu – <sid>admBrowse to the directory where the license backup file is keptmore <SID>.saplicensesaplicense –install

5.2 Set Background Process as Zero Logon as <sid>admsu – <sid>admcdproEdit SAP Instance Profilevi <sid>_DVEBMGS<no>_<host>find parameter rdisp/wp_no_btccomment out # rdisp/wp_no_btcappend rdisp/wp_no_btc = 0To make background process = 0

5.3 Cleanup /sapmnt/SID/globalBefore starting SAP remove the JOBLOG & SLOG files in the /sapmnt/SID/global/ directory on the target system. cd /sapmnt/<Target_SID>/globalrm –fr *JOBLG* rm –fr *SLOGJ*rm -fr WF_LOG*

5.4 STARTSAP startsapLogon to your sapWe see the default client of <Target System> which is configured in instance profile Remove the <target system> default client number and type <source system > default client number.Provide the logon information of <Source System>

5.5 Reinitialize TMS after DB copylogon to 000 as DDICRun transaction SE06 database copy or database migrationReinstall CTS yeschange original <S_System <SID>>to <T_System <SID>> yescts not configured okdelete the TMS Configuration yesdelete all versions of transports yes


delete transport routs yes

5.6 Delete Jobs ** WARNING: MAKE SURE YOU ARE IN TARGET SYSTEM/CLIENT **Execute transaction SM37Delete all released jobs from the system

5.7 Revert background processes to originalLogon as <sid>admsu – <sid>admcdpro

5.7.1 Edit instance profilevi <sid>_DVEBMGS<no>_<host>Find parameter rdisp/wp_no_btcReset to original values

5.7.2 Stop SAP server stopsap

5.7.3 Start SAPstartsap

5.8 Re-initialize JobsAfter the database restore has successfully completed, the import jobs used by the tp command may not work properly. Proceed as follows:Logon to SAP in client 000 as DDIC and run transaction SE38Execute program RDDNEWPPSelect NormalA message will show up in the status bar which indicates the job has been scheduled.

5.9 Schedule Standard JobsGo to transaction SM36 as BASIS-BATCH.Schedule all standard jobs

5.10 Configure SAP Profile Parameter Files After the database restore, the active profiles listed in the SAP system will be from the old hostname. These profiles need to be deleted and the profiles from the OS need to be re-imported. Proceed as follows:Run transaction RZ10


Delete source system profiles:Click the Profile drop-down box and choose a profile (this process must be done for each profile).Select menu items: Profile -> Delete -> All versions of a profile.Click Yes to first prompt to update the databaseClick No to delete the files from the Op. Sys. LevelClick green check on all versions deleted screenRepeat steps 1-3 for all source system profiles listed in the Profile drop-down list.Import all profiles from UNIX by selecting menu items: Utilities -> Import Profiles -> of active servers.Green back arrow.

5.11 Configure Op Modes After the database restore, the target system will contain Operation Modes from the old hostname. These Op Modes need to be deleted and the correct Op Modes need to be imported. Proceed as follows:

Run transaction RZ04Select Instance/Opmodes Select a server name and press SHIFT F2.Do this for each source system op mode listed.Create the target system op mode configuration(s) by selecting the menu items Settings -> Based on Current Status -> New Instances -> GenerateClick the SAVE button.

5.12 Check System LogsCheck the system logs to see if there were any unusual error messages generated while the SAP system was started back up. Proceed as follows:Execute transaction SM21

Select menu items System logs -> Choose -> All remote system logs.Set the from date/time fields to the date and time just prior to starting the

SAP system.Select the All messages radio button.Click the Reread system log button.Review the system messages. Take action on any messages that may look

suspicious.

5.13 Fix Logon Group NamesRun transaction SMLGAdd the newly added systems to existing LOGON groups.Highlight the New Hostname Entries.Click the Assign Group button and assign the Logon groups respectively.Highlight the Old Hostname Entries.Click the Delete button.Save. Note: Do not delete the groups instead of that delete only instances assigned. If you delete the groups both the groups and instances will be deleted.Re-execute transaction SMLG once again and validate the logon group


configuration.

5.14 Fix Server Group NamesRun transaction SM61Click pencil for change mode, click cleanup list.Select Job-ServerGruppenClick Create GroupType GENERAL, click continueExpand All Groups folderHighlight GENERAL, click on + assignmentDrop down instance name box, select only application serversDo this for each application server available, but if no app servers are configured for the instance, use the CI.Once all the new entries are added. Delete the Source System Entries.

5.15 Import User Master DataImporting the previously exported Users from the Pre-Client Copy StepsRun T-Code: STMSClick on the transport button (Truck)Double click on the System nameOn the toolbar, goto ExtrasOtherAddAdd the transport request number.Click on the transport button (Half Truck) after selecting the added request.Provide target Client number and continue.

5.16 Post user master importLogin into your target client Run Transaction SCC7 From Menu options choose start immediately.SCC3 check your logs

5.17 Import Printer, RFC DefinitionsRun Transaction SPAD Select menu items utilities for output devices delete all.Run Transaction STMS Select menu items overview imports double click on target system Select your request. Import request give client no okClick refresh until your truck symbol is lost and the transport is successful.Repeat this transaction for all the transportsRun transaction SPADSelect menu items utilities for output devices assign server.Run transaction SM59 Validate RFC definitions.

5.18 Fix ITS InformationRun transaction SM30


Edit the table TWPURLSVR by selecting the change option.Change the hostname reflecting the new hostname.Save

5.19 Delete Local CUA/Detach a Satellite ClientDelete the target hostname and system number under SM1 trusted connection entry. Run transaction SE38 Execute the report RSDELCUA. Select Child System -> <SID>CLNT500 and unselect Test -> execute.Use the Green back arrow to go to the previous screenRe-execute the last step to invalidate the CUA contents.

5.20 Update HP OMS entry in SPAD Use transaction SPADSelect Full Administration buttonGo to Output Management Systems tabCheck Real Output Management Systems by clicking on DisplaySelect change and update HP-DAZEL with the new OMS Configuration infoFor QA2, set it to: “-N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]”For UA1, set it to: “-N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]”Save

5.21 Disconnect from previously connected P21 (For all systems that are source systems of BW: ECC, SRM, CRM)

Run Transaction SE37Enter RSAP_BIW_DISCONNECTHit Test/Execute (F8)Enter data into the following fields:I_BIW_LOGSYS: P21CLNT500I_OLTP_LOGSYS: <Logical system for your Production System>I_FORCE_DELETE: XHit execute (F8)

5.22 Converting Logical SystemsRun transaction BDLSEnter Old logical system name in the Old logical system name fieldEnter New logical system name in the new Logical system Name fieldSelect Conversion of Client-Dependent and Client-Independent tables. Uncheck Test RunUncheck Existence of New Names in Tables. ExecutePress Return again, if any warnings are encountered.Rerun this transaction for all the Target Logical System entries. Note: BDLS should be executed for each existing connection to other components in the respective clients. Example, if the logical system client says 110, BDLS should be executed in client 110 for each logical system connected to the system. This rule applies currently to ECC and SRM where there are multiple


clients.Note: Check the logs in SLG1 for possible errors.

BW Systems: Execute RSBKDTP_BDLS via SE38 for each source system in RSA1.

Old Logical System Name: (ex. P11CLNT500, P31CLNT500, etc…)New Logical System Name (ex. Q11CLNT500, Q31CLNT500, etc…)

5.23 Logical System NamesRun Transaction BD54Verify and Redefine the logical systems as per the screenshot during pre-refresh.

5.24 IDOC Port DefinitionsRun Transaction WE21Adjust the port assignment / RFC Destinations as per the pre-refresh screenshot. Note: During port creation, use the system provided port numbers.Remove any ports that were pointing to production.

5.25 Partner ProfileCreate and adjust the Logical System/RFC Destinations as per the pre-refresh screenshotActivate the partner profiles if set to ‘I’ set it to ‘A’If a particular message type is not associated with the IDOC type, maintain the

association in WE82 transaction.

5.26 Create Trusted System Run Transaction SMT1Reconfigure the trusted systems as per the pre-refresh screenshot/description.Delete the entries reflecting Source System entries.To create the Trusted systems you need to have access to the remote systems with proper authorization in the case of QA2 it was SA2 and SM1. SM1 system will be created by Kevin Flattery.

5.27 Republish ServicesRun Transaction SE38

Enter Program name W3_PUBLISH_SERVICES.Execute and follow the screens to republish the services.

Run transaction SICFSelect the necessary services one at a timeDeactivate the ServicesActivate the Services.Make sure that the SAP GUI service was enabled and working.


5.28 Trust Manager – Portals CertificatesDelete existing certificates and import portal certificates corresponding to target system. Run Transaction STRUSTSSO2Check the existing public-key certificate of Portal Servers in component system's certificate list.Delete the Certificates. Reconfigure/Import the appropriate certificates in component system as during pre-refreshPortals Certificates will be imported by Portal administrators.

5.29 Integration Engine ConfigurationRun transaction SXMB_ADMDouble Click on Integration engine configurationReconfigure integration engine data as per the pre-refresh screenshot.

5.30 Port Maintenance IDOC AdaptersRun transaction IDX1Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot.

5.31 IDOC Adapter Metadata OverviewRun transaction IDX2Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot.

5.32 Verify Distribution Model ViewRun transaction BD64 and check pertinent model views. Verify the same pre-refresh distribution model views existing after request import.

5.33 Delete Workload Analysis Logs for Old ServerRun Transaction ST03Change your user mode to Expert Mode.Collector and Performance DB Performance Database Monitoring Database contentsDouble click on contents.In the Host Column select the old host name Delete Server Confirm Delete.To make the changes effective save it after deleting the server. To view the changes go to the first screen and come back after saving the changes.

5.34 Reset the passwords for the following users Run transaction SU01Reset the password for the following users from the default client. These users


will be recreated during the JAVA Install.J2EE_ADMINJ2EE_GUESTSAPJSFXI* (Only on XI systems)LD* ( Only on XI systems)

5.35 Client Definition Run Transaction SCC4Change the client description to reflect as per pre-refresh description.

5.36 Maintain DBA Planning CalendarRun transaction DB13 as BASIS-BATCH.Setup DBA jobs as per the pre-refresh screenshot.

5.37 qRFC MonitorRun transaction SMQR & SMQSDelete old monitor and setup new monitor with correct system name. .(Registration Table-> Reorganise)SMQ1, SMQ2 deleted the old queues and any old error entries .

SLD Specific

5.38 Maintain SLD connection parametersRun transaction SLDAPICUSTChange the connection parameters pointing to correct SLD source. To change switch to editing mode and choose Insert Row. Specify the connection parameters (host name, port, user, and password) and set this SLD server as Primary. Only the entry marked as Primary is active. Save your entries.

Configure the SLD Data Supplier Service in the Visual AdministratorLogon as j2ee_admin/administrator in Visual Admin.Change and verify the connection parameters for SLD connection and CIM client generation settings in SLD Data supplier service.Verify by triggering the SLD data load.

Maintain the SLD connection in ABAP systemsRun transaction RZ70Maintain SLD bridge host and gateway.Validate SLD Connection/configurationRun transaction SLDCHECKValidate the all the checks are successful.

5.39 Schedule XML Messages Delete JobsRun Transaction SXMB_ADM as user DDIC


Go to SXMB_ADM Define Interfaces for Archiving and Retention Periods Retention periods Retention Periods for Asynchronous messages in the Database:XML Messages without Errors Awaiting Deletion: 30 DaysXML Messages without Errors Awaiting Archiving: 7 DaysRetention periods for Synchronous messages in the Database:XML Messages with Errors Awaiting Deletion: 7 Days XML Messages without Errors Awaiting Deletion: 0 DaysRetention periods for History entries in the Database:History Entries for Deleted XML Messages: 35 DaysRun Transaction SXMB_ADM as user DDIC Schedule Delete Jobs Check the settings and reconfigure as per the screenshot takenVerify Parameters: Period of Days set to 1.Click on Job Overview (SM37) and verify the below jobs scheduled as pre-refresh.SAP_BC_XMB_DELETE_<client>SAP_BC_XMB_HIST_DELETE_<client>.

5.40 Attach a Satellite Client to CUALogon to Satellite ClientRun T-Code: SM59Validate entry for an ABAP system - SA2_SYSTEM.Validate entry for an ABAP system - SA2CLNT100.

Run T-Code: BD54Select New EntryDefine a new Logical System for CUA, e.g., SA2CLNT100Provide a description under NameSaveCreate a new transport or use an existing transport.

Run T-Code: SMT1Select Create ButtonSA2CLNT100 in Destination field.

Login to CUA SystemRun T-Code: SM59Validate ebtry for the ABAP system – Q42CLNT500

Run T-Code: BD54Validate Logical System entry for Satellite System, e.g., Q42CLNT500Create a new transport or use an existing transport

Run T-Code: SCUA Enter the Satellite Instance Name, e.g., S11CLNT005 at the bottom of the listSelect SAVEYou will have to enter DDIC user-id and password for the satellite system on the follow-up screenCheck the log file to validate that this command is completed successfully.


Logon to Satellite ClientRun T-Code: WE20 Validate that under LS, a Partner Profile for SA2CLNT100 is now defined and also SU01 has lesser number of available options.

6. Install J2EE and Apply Java Patches on CIPlease use the reset passwords, during the J2EE Installation

Important: This section activity should be performed on available Pepsico Windows Terminal Server(WTS); because if your PC/laptop lost connection then there will be incosistency or might have to restart the process.

6.1 NW04S – Java Install Logon to available WTS Run ProgramsReflection and open X-term to UNIX server where you are installing

J2EE. Check X-Windows xclock

This will display Clock Window; then you can proceed, otherwise you need to export DISPLAY.

Run SAPINST to install Java ADD-in as belowSAPINST_USE_HOSTNAME=<hostname>cd /install/<SID>/xx

/sapcd/sap/install/unicode/crm50/master/master/IM_HPUX_IA64/sapinst

On Initial Screen SelectionUsage Type ParameterECC SAP ERP 2005BI SAP NetWeaver 2004sCRM SAP CRM 2005XI SAP NetWeaver 2004s

sapcd selection :DVD/CD Name Package Selection Installation

KERNEL DVD /sapcd/sap/install/unicode/crm50/kernel/kernel/KN_HPUX_IA64 SCS/sapcd/sap/install/unicode/crm50/kernel_2/kernel2/KU_HPUX_IA64SCS & CI

JAVA DVDNetWeaver

/sapcd/sap/install/unicode/crm50/java_usage/java/J2EE_OSINDEP DB & CI/sapcd/sap/install/unicode/crm50/java_export/java_export DB

SAPCD Software Units Selection (Central Instance Java Add In for ABAP)


Usage Type Software UnitsECC NoneBI NoneCRM CRM-APP

JCRMXI PI

SLD Configuration Selection (Central Instance Java Add In for ABAP)Usage Type No SLD Destination Configure Local SLD Register in Existing SLDECC YES*BI YES*CRM YES*XI YES

Select “No SLD Destination” if XI SLD is not yet configured.

6.2 NW04 Install(SRM/SCM Specific)Run SAPINST to install Java ADD-in as belowcd /install/<SID>/xx/sapcd/sap/install/unicode/crm50/nw04sr1/hpux/ia64/master/DVD_NW_04_SR1_Installation_Master/IM07_HPUX_IA64/SAPINST/UNIX/HPIA64sapinst SAPINST_USE_HOSTNAME=<hostname>On Initial Screen Selection

Usage TypeDescriptionSRM SAP Netweaver 2004 Support Release 1 Java Add In for

ABAPOracle Central System Java system Finalization

SCM SAP Netweaver 2004 Support Release 1 Java Add In for ABAPOracle Central System Java system Finalization

SAPCD SelectionDVD/CD Name Package Selection

JAVA DVD

/sapcd/sap/install/unicode/nw04sr1/hpux/ia64/java_osind/DVD_NW_04_SR1_ SAP_Web_AS_JAVA/J2EE_OSINDEP

If the above directory doesn’t work then please try the below:/sapcd/sap/install/unicode/nw04sr1/hpux/ia64/java_scs/DVD_NW_04_SR1_SAP_Web_AS_JAVA/SCS_HPIA64/SCS

Export /sapcd/sap/install/unicode/nw04sr1/hpux/ia64/export

SLD Configuration Selection (Java Add In for ABAP)


Usage Type No SLD Destination Configure Local SLD Register in Existing SLDSRM YES*SCM YES*

* Select “No SLD Destination” if XI SLD is not yet configured.* Port should be 39XX(XX is instance number).*Use ABAP system for users only.

6.3 Java Patches on CIBefore applying JAVA Patches we need to Update SDM (Software Deployment Manager) and JSPM (JAVA Support Patch Manager) to the Patch level we going to apply.E.g.: Applying JAVA SP11 on Q12 system.

6.3.1 Update SDMUpdate SDM to SP11 from OS Level. Login as <SID>adm cd /sapcd/sap/patches/nw04s/SP11/JAVA cp * /usr/sap/ecctrans/EPS/in mkdir /usr/sap/<SID>/DVEBMGS<xx>/SDM/test cd /usr/sap/<SID>/DVEBMGS<xx>/SDM/test jar –xvf /usr/sap/ecctrans/EPS/in/*.JAR cdmod +x * cd /usr/sap/<SID>/DVEBMGS<xx>/SDM/program ./StopServer.sh ./sdm.sh jstartup mode=standalone ./update.csh (update SDM from test directory. Make sure SDM is not running while

executing this command ) While updating it asks for SDM installation directory. Give the installation directory as /usr/sap/<SID>/DVEBMGS<xx>/SDM/program

After the SDM update is successful again go to cd ../program ./sdm.sh jstartup mode=integrated

./StartServer.sh./RemoteGui.sh

6.3.2 Update JSPMLogin as <SID>adm ./RemoteGui.sh Enter SDM Password Click on Deployment tab in SDM. Browse to /usr/sap/<System_Name>trans/EPS/in System_Name like ecc bw srm Select JSPM<xx>_<x>-xxxxxxxx.SCA file Eg. JSPM12_0-10003470.SCA Select the JSPM package and Deploy


6.3.3 Apply Java Patch on CILogin <SID>adm cd /usr/sap/<SID>/DVEBMGS<xx>/j2ee/JSPM ./go Enter SDM administrator password. Now, Select the following on this screen Select a package type to apply

◙ Single support packages (advanced use) NWDI Control ◙ No NWDI control

Click Next Click Next Check Queue and Deploy Queue to apply

6.3.4 Troubleshoot Errors while applying support package using JSPM

If there is error while applying support package using JSPM, we need to identify the package which got error.

Login to SDM and go to Undeployment tab. Select the error package and undeploy completely. Now apply the Error package using SDM tool from Deployment tab. Make sure all the packages are deployed completely from URL

http://qa2q12.corp.pep.pvt:51200 Select the system information and check for successfully applied Support packs.

6.3.5 For Target systems (Eg: SRM, SCM) which have J2EE 640 (Oracle 9i) install on Oracle 10.2 DatabaseReview the Oracle Upgrade document and update the location of classes12.jar file under J2EE Specific entries from Post Steps.


http://qa2q12.corp.pep.pvt:51200/

7. Post SAP System Specific steps:

7.1 XI Specific Steps

7.1.1 Configure the SLD Bridge (XI) As per prerefresh screenshot

7.1.2 Configure CMS SetupBased on pre-refresh steps, add the following parameters and set to true in Exchange Profile.com.sap.aii.ibdir.core.cms.enableTransportWizardcom.sap.aii.ibdir.core.enable.TransportWizardcom.sap.aii.ibrep.core.cms.enableClTransportcom.sap.aii.ibrep.core.cms.enableTransportWizard

7.1.3 Run transaction SXMB_IFRVerify link for repository, runtime workbench etc.This should point to http://host: (icm http port)/rwb

7.1.4 Activate XI related services Run transaction SE38RSXMB_ACTIVATE_ICF_SERVICES Execute

7.1.5 Refresh XI CacheRun transaction SXI_CACHE.Select GotoSelect Adapter Engine CacheSelect line item under Adapter Engine Connection Data Cache sectionDelete

7.1.6 XI Message Archiving & DeletionCheck Existence of physical directory at the operating system level for storing the archived XI messages. Path: interfaces/sid/client/out/ready/archiving/Verify logical path in TCODE ‘FILE’Logical File = ARCHIVE_XI_DATA_FILE double clickSpecify physical/logical file path based on pre-refresh screenshotValidate Definition of variable “FILENAME” Use TCode: FILE, Create as per the screenshot from pre-refreshValidate Syntax group Definition create syntax group for operating


systems with the same syntax for file names and paths from pre-refresh screenshot. Check assignment of syntax group to operating system as per the screenshot.Go to SXMB_ADM Schedule Archiving Job Archive Administration Make sure the object is BC_XMB Click on Customizing. Go to Cross-Archiving Object Customizing Technical Settings Configure as per pre-refresh screenshotGo to Archiving Object – Specific Customizing Technical settings. Configure as per pre-refresh screenshot. Make sure the Delete Jobs is set to “Start Automatically” and a logical File Name./* Go to SXMB_ADM Define Interfaces for Archiving and Retention Periods Select the interfaces for Archiving using the Multiple selection button and click on “Flag interface for Archiving”. */Note: The following database tables are key tables in archiving and

Deletion process: SXMSPMAST & SXMSPHISTGo to SXMB_ADM as DDIC Schedule Archiving Job assign the Start Date, Period & Spool Parameter data as per the pre-refresh screenshot.Activate Archive infostructure, Go to SXMB_ADM Schedule archiving jobs Archive Management Information System Customizing Choose Archive Infostructure for object SAP_BC_XMB Activate.

7.1.7 Configure JCo RFC provider using Visual AdminRun Transaction SM59 and verify the below RFC connections in TCP/IP ConnectionsLCRSAPRFCSAPSLDAPIAI_RUNTIMEAI_DIRECTORCreate following Destinations in Visual Admin Server Services JCo RFC provider


7.2 BI Specific Steps

7.2.1 Restore the Logical system destinationsGo to Tcode SE16 RSLOGSYSDEST select each LOGSYS and change the Destination to the target logical system name.Ex: LOGSYS DESTINATIONOriginal Value U51CLNT500 P51CLNT500New Value U51CLNT500 U51CLNT500In the Java side add the JCO RFC connection Go to Visual admin server services JCo RFC Provider.Add BW_J2EE.

7.2.2 Restore the Table RSBKDTP entries to Target SID Go to Tcode SE16 RSLOGSYSDEST select the entry and change the value of field RSBKDTP:SRC from <S_SID>CLNT<CLIENTNo:> to <T_SID>CLNT<CLIENTNo:>

Go to Tcode SE38 RSBKDTP_BDLS and Execute.


7.2.3 Restore Source System ConnectionNOTE: In case the Source Systems have also been refreshed, make sure all the refresh activities have been completed before you restore the connection. Should not perform the restore for UD Connect Systems but can do the checks.

Verify the RFC Destination/Aleremote using Tcode SM59 Open the client using TCode SCC4. Change System settings to modifiable in SE06 Tcode. Go to TCode RSA1 Source System

Restore all systems one by one, starting with BW System (Myself) Specify the ALEREMOTE passwords for source and receiver

systems when prompted.Restoring all source systems may take some time to complete depending on number of extract structures/Data sources to be replicated.

Rename the logical system name in RSA1 to maintain consistency. Right click on the source system Select Rename

Change the name to appropriate value.

7.2.4 Maintain IDOC Sender/Receiver Systems Table RSBASIDOC should have sender and receiver source systems rightly configured. Verify in SE16 appropriate entries for all sender and receiver systems.

7.2.5 RSA1 Check In RSA1 perform source system check by right click the source system check Recommended Perform simple master data load from source to target to confirm the extraction to be okay.

In RSA1 InfoSources select some Master data attribute. For example (0VENDOR_ATTR or 0BUSSYS or 0COMPCODE etc) select the the infopackage and trigger the load.Verify the successful completion of the load in transaction RSMON. This helps in rectifying any ALE specific issues if still existing.

7.2.6 BI Integration into the PortalCall transaction SPRO and choose SAP NetWeaver->Business Intelligence->Reporting- >relevant Settings->BEx Web->Integration into the Portal.Follow the instructions for the following steps:Create RFC Destination in J2EE EngineImport BI Certificate to the PortalMaintain Portal Server Settings for the PortalCreate RFC Destination for the PortalImport Portal Certificate to BI System

7.2.7 Configure UDCLogon to available WTS


Run ProgramsReflection and open X-term to UNIX server where you are installing J2EE.

Check X-Windows xclock

This will display Clock Window; then you can proceed, otherwise you need to export DISPLAY.

Telnet to BI Central instance as <sid>adm.cdDcd j2eecd admin./go (make sure an x-client is used with DISPLAY variable set up)select the central instance server in the left pane and open it up.select services -> JDBC ConnectorIn the middle pane select Driver and click on “Create New Driver or

DataSource”For Driver Name enter “teradata”When asked to pick a Jar file for the driver go to /home/<sid>adm/TeraJDBC_304 and select the following 3 files: tdgssconfig.jar, tdgssjava.jar, terajdbc4.jarNow select Connector Container in the left paneOpen the jdbc connector container

Select SDK_JDBC and hit the Clone buttonEnter the name SDK_JDBC_TDHit Save Select SDK_JDBC_TD and go to the Resource Adapter tabClick the “add” button and enter: “library:teradataSave

Go to tab “Managed Connection Factory” and then “Properties”Enter the following configuration properties:com.ncr.teradata.TeraDriver for DriverNameQTG_S for FixedSchema???? for Password (Obtain Password Prior to refresh)jdbc:teradata://td4.corp.pep.pvt for URLRQ2250TD4 for UserNameHit Save

Select SDK_JDBC_TD and hit the Clone buttonEnter the name SDK_JDBC_TD_ISCPHit Save

Select SDK_JDBC_TD_ISCP Go to tab “Managed Connection Factory” and then “Properties”Enter or verify the following configuration properties:com.ncr.teradata.TeraDriver for DriverNameQTG_S_ISCP for FixedSchema???? for Password (Obtain Password Prior to refresh)jdbc:teradata://td4.corp.pep.pvt for URLRQ2250TD4 for UserNameHit Save

Exit Visual Administrator


7.2.8 Modify Logical System conversion TableLogon to BI Run Transaction RSA1Select Tools -> Conversion of Logical System NamesModify entries based on the screenshot taken before the refresh.

7.2.9 Change BIA (BI Accelerator) RFC DestinationRun Transaction RSCUSTASwitch to change mode.Use chart below to determine the entry for RFC BI Accelerator

Target BI System RFC BI Accelerator EntryQ21 BIA_QE1U21 BIA_UE1P21 BIA_PE1All Others Should be blank, delete entry if there is

one.


7.3 SCM Specific Steps

7.3.1 Delete connections to liveCacheRun transaction LC10.Name of database connection: Type LCAPress Integration buttonSwitch to change mode <Shift+F1>Delete connection (Connection|Delete)Repeat 1-4 for remaining connections. Hit drop down on database connections to find all connections

7.3.2 Setup Logical SystemsRun transaction SALEBasic Settings|Logical Systems|Define Logical SystemMake sure all required logical systems exist after BDLS. Add any additional

onesBasic Settings|Logical Systems|Assign Logical System to ClientMake sure correct logical system is assigned to correct client.

7.3.4 qRFC MonitorRun transaction SMQRSMQ1 and SMQ2 and make sure there is no data.

7.3.5 Start CIF queue/n/SAPAPO/OM17

7.3.6 liveCache Restorerun dbmgui > connect target system > make complete backup to the file


system > validate the backup file from unixftp the file to the source system > rename the file to the source system backup

filedbmgui > select recovery > recovery with initialization > check and make one more backup as abovedbmgui > menu instance > configuration > database user > validate the sap user name sapSID from /nLC10 > button integratin > change the user name and password of "standard liveCache user" as sapSID/nWE02 > check the failed iDOC

7.3.7 liveCache consistency /n/SAPAPO/OM13

7.4 ECC Specific Steps

7.4.1 Update Custom tablesTransaction SM30 to table ZRFCECCSRM and add corresponding Sid and Logical system entries for ECC and SRM

7.4.2 ECC Adapter Ports Check the attached Adapter ports confiuration file.


7.5 SRM Specific Steps

7.5.1 Update Custom table : ZPCARDENCRYPTTransaction SM30 to table ZPCARDENCRYPT and change corresponding SID and directory specs to destination system settings.

7.5.2 Update Custom table : ZZRFCDESTransaction SM30 to table ZZRFCDES and adjust entries to match destination SIDs in both Client 500 and 530.

7.5.3 Synchronize Encryption for SRMStep 1: Logon to each of the application servers at the Unix level and ftp files SAP*.pse files from the CI to the application server directory. The directory is


/usr/sap/<SID>/D<##>/sec.Step 2: Then login to STRUSTSSO2, right click on System PSE and select distribute, and all lights should go to green. Step should not be performed until step 1 has been completed.

7.5.4 IPC SettingsChange the correct settings for IPC

Logon <sid>adm sudo su –su – ipcadm

Edit the parameters file under /usr/sap/ipc/lib/propertiesvi /usr/sap/ipc/lib/properties/parameters.xml Now serch for 500 Old Values:<Database Alias="P51" IsBasisSystem="true" IsR3System="false" IsServerConnection="true" ApplicationServer="prdp51.corp.pep.pvt" SystemNo="55" DatabaseActive="true"> <Client ClientNo="500" User="IPCUSER" Password="BEkERBEdRVkFUFVVARATMQ==
" ClientActive="true" ClientEnabled="true">

Change the values in RED to your settings.

Smoke Test


7.6 CRM Specific Steps

Maintain CRM RFC Parameter This entry is maintained in table CRMRFCPAR in all sender/receiver systems (R3/BW etc)SM30 CRMRFCPAR Maintain Delete the existing entry for CRMCreate a new one with the previous values.

Update CRMC ICM RFC Parameter

Update table CRMC_ICM_RFCDEST to reflect the new environment. The ECC and BW RFC destinations should reflect the ECC & BW systems in the refreshed environment.

SM30 for table CRMC_ICM_RFCDEST.

Select customizing.Continue w/out specifying Project

Under Incentive and Commission Management --> BW-ICM Transfer of BW Data to ICMExecute the Set up RFC Destinations for ICM Engine and BW System


The ECC and BW RFC destinations should reflect the ECC & BW systems in the refreshed environment.


7.7 Control-M Specific Steps Check the below document for all Control-M specific steps. Please, check all SAP systems i.e. ECC, BI, CRM, SCM, SRM.

7.8 FireFighter InstallationCheck the attached document for FireFighter Installation and configuration.


8. Before Releasing System to Business – (Post Checkouts)


8.1 General Check for All Systems8.1.1 Valid license for PRD in DR-systems8.1.2 SAP access PRD Cl8.1.3 Oracle Alert Log8.1.4 DB12 – Backup Logs8.1.5 DB13 – DBA Planning Calendar8.1.6 OS078.1.7 RZ70 -> Ensure successful transmission of data to SLD8.1.8 RZ03 -> No Configuration Alerts8.1.9 SICK – SAP Initial Consistency Check8.1.10 SMICM -- ICM Monitor8.1.11 SM12 – Check Lock Entries8.1.12 SM13 – Check Update Requests8.1.13 SM21 – System Logs8.1.14 SM37 – Batch Jobs8.1.15 SM51 – Check SAP Servers8.1.16 SM50 – Check Work Processes8.1.17 SM59 -> ABAP Connections -> Check connectivity to other SAP system in the landscape8.1.18 SMLG – Check SAP Logon Groups8.1.19 SPAD -> Print to any printer other than LOCL and validate successful printing using SP01.8.1.20 ST22 – Check SAP Dumps8.1.21 SM58 – Check Transactional RFCs8.1.22 SMQ1 – Monitor Outbound Queue8.1.23 SMQ2 – Monitor Inbound Queue8.1.24 http://hostname:5xx00 -> Check system Information -- Check System

Information and Patch levels8.1.25 Tcode SICF -> execute -> default host -> sap -> bc -> gui -> sap -> its

-> webgui -> Test Service -> WebGui Logon Page8.1.26 TCode SLDCHECK

8.2 ECC Specific

8.2.2 SM59TCP/IP Connections ->

IGS_RFC_DEST HPOM_RFC_DESTINATION SLD_UC TIBCO_P11 TIB_QTG1_P11 VERTEX


8.2.3 KGSOAAD -> Technical Search ->

Business Object: BUS0815Client: 500

Archive:-> Press Enter for the next pop-up window -> Select any of the two documents-> Display PDF file

8.2.4 FAXSBWP -> New Message ->

Title: TestRecipient: US3128217756Recip. Type: FAX-> Send

SCOT -> At least 1 entry should be there under Waiting for FAXP11 queue-> Start Send Process(CNTRL + F7)-> The count for (In transit) followed by (Completed) should inccrease by 1.

8.2.5 ITS CheckTcode : SITSPMON

8.3 BW Specific

8.3.1 RSA1 -> Source System -> Right Click individual system and select Check

8.3.2 Check for BI UDChttp://<SID_hostname>.corp.pep.pvt:5<SID Instance#>00/BI_UDC/servlet/GrmgServlet


8.4 SRM Specific

8.4.1 SM59 Tcode – Check for Live Auction

8.4.2 SMOKE TEST for Live Auction http://prdp51.corp.pep.pvt:55500/srm/la/smoketest.jsp

8.4.3 Check certificatesSTRUSTSSO2 -> Select (System PSE)/(SNC)/(SSL Server)/(SSl Client)

-> Ensure that all the line items for each system is GREEN.

8.4.4 Check encryption TCode SE38 -> SSF01 -> use variant Z_PCARD_TEST


http://prdp51.corp.pep.pvt:55500/srm/la/smoketest.jsp

8.5 XI Specific

8.5.1 SXMB_IFR -> On the web page select all the components to ensure proper connectivity

8.5.2 SXMB_MONI - Check for any Red Flag Messages

8.5.3 TIBCO SXMB_IFR -> On the web page select (Runtime Workbench) -> Login as XISUPER -> -> Select (Component Monitoring) -> Click on Display -> Adapter Engine prdp41 -> Adapter Monitoring -> login as XISUPER ->

-> Select the arrow on http://sap.com/xi/XI/System -> Select JMS -> Ensure the status is Green for all the four line items under JMS section.

8.6 SCM Specific Checkouts


8.6.1 LC10 - Check for LiveCache

8.6.2 JDBC Check http://prdp61.corp.pep.pvt:56500/TestJDBC_Web/TestJDBCPage.jsp http://prdp61.corp.pep.pvt:56500/TestJDBC_Web/TestJDBCPage2.jsp?sys_jdbc=SDK_JDBC_ISCP

8.6.3 Analyse LiveCache & LCA Objects TCode : /sapapo/om13

8.6.4 Optimizer Installation Tests TCode : /sapapo/opt_inst

8.6.5 Check for BI UDC http://prdp61.corp.pep.pvt:56500/BI_UDC/servlet/GrmgServlet

8.6.6 APO Consistency Check se38 -> /SAPAPO/TS_LCM_CONS_CHECK_ALL

APPENDIX

Steps to reset the SDM password.Logon to the system as <sid>adm.cd /usr/sap/<SID>/DVEBMGSxx/SDM/program./sdm.sh jstartup sdmhome=”/usr/sap/<SID>/DVEBMGSxx/SDM/program” mode=standalone./sdm.sh changepassword sdmhome=”/usr/sap/<SID>/DVEBMGSxx/SDM/program newpassword=xxxxx


http://prdp61.corp.pep.pvt:56500/BI_UDC/servlet/GrmgServlet

http://prdp61.corp.pep.pvt:56500/TestJDBC_Web/TestJDBCPage2.jsp?sys_jdbc=SDK_JDBC_ISCP

http://prdp61.corp.pep.pvt:56500/TestJDBC_Web/TestJDBCPage.jsp

./sdm.sh jstartup sdmhome=”/usr/sap/<SID>/DVEBMGSxx/SDM/program” mode=integrated

Steps to synchronize SDM Server if required if your java patches doesn’t reflect in the system info after applying them with JSPM.Go to /usr/sap/DC2/DVEBMGS37/SDM/program./StopServer.sh./sdm.sh SystemComponentState “mode=Sync”./StartServer.shOnce Dev1 Instance is up and TMS is set in the Dev1 instance then run the following:Reset TMSLogon to SAP in client 000 as DDIC on the DEV Instance (TMS Domain Controller for system, i.e. D11 or D21, D41, D51).Run transaction STMSOverview -> systemsCTRL F10 – Distribute and Activate TMS configurationSelect Distribute configuration to all systems.You might be prompted to LOGON to Target system, just logon to client 000 with DDIC user/password.

To recreate PSAPTEMP table spaceLogon to UNIX level as ora<sid>mkdir –p /oracle/Q41/sapdata3/temp2sqlplus “/ as sysdba”create temporary tablespace psaptemp2 tempfile '/oracle/Q41/sapdata3/temp2/temp.data1' size 100m; ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP2";drop tablespace PSAPTEMP including contents;create temporary tablespace psaptemp tempfile '/oracle/Q41/sapdata3/temp_1/temp.data1' size 1048584192 reuse autoextend off;ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP";drop tablespace PSAPTEMP2 including contents;exit;

Starting Java SDM serverLogin <SID>adm/usr/sap/<SID>/DVEBMGS<xx>/SDM/program./StartServer.sh

Stopping Java SDM server:Login <SID>adm/usr/sap/<SID>/DVEBMGS<xx>/SDM/program./StopServer.sh


sap refresh

Documents