PFL (ECC 6.0) Refresh Procedure - UNIX

DOCUMEN NAME & LOCA-TION:

PFL Unix Refresh Procedure

VERSION: 1.0

DATE:

READERSHIP: Basis Team Members

SUMMARY: PFL(ECC 6.0) Refresh procedure

C O N T E N T S

1. PREPARATION.........................................................................................................4

1. BASIS PRE TASKS..................................................................................................4

2. Start Online backup in <SRC>PRL.......................................................................................4 3. Execute a user master export of <TGT>(EG:PFL) client 100...............................................5 4. Create a system message, Screen shots of existing Value (WE20, WE21….so on)..........5 5. Send email to appropriate team for approved transport list after refresh.............................5 6. Export Java schema from <PRL> (source system)..............................................................5 7. Copy init<SRC> files from <SRC>........................................................................................9 8. Copy the export directory from <SRC> (source system CI server) to <TGT>(EG:PFL) (tar-get system CI server)..................................................................................................................9 9. Copy backup and archive logs files from <SRC>.................................................................9

BEGIN REFRESH OF <TGT>(EG:PFL)........................................................................9

10. Stop SAP (CI & APP)..........................................................................................................9 11. <TGT>(EG:PFL) Installation/Import (CI & DB on different servers)...................................9 12. <TGT>(EG:PFL) Installation/Import (CI & DB on different servers).................................12 13. Create Soft Link ................................................................................................................20 14. Restore the database (PFL)..............................................................................................20 15. Execute ‘Point in Time recovery........................................................................................21 16. Adjust the init<TGT>(EG:PFL).ora file..............................................................................21 17. Copy CONTROL.SQL to SAP install directory on <TGT>(EG:PFL) DB server...............21 18. Resume SAPINST ............................................................................................................22 19. <TGT>(EG:PFL) Installation/Import (CI & DB on different servers).................................24 20. Start SAP (CI) without background and spool processes.................................................32 21. Start SAP Services (CI).....................................................................................................33

V 1.0 BP Internal Use Only - 1 -

22. Install New SAP License...................................................................................................33 23. Lock All users & Suspend Background Jobs....................................................................33 24. Set up the workbench organizer.......................................................................................34 25. Cancel Jobs in “Ready/Active” status: .............................................................................34 26. Verify within SAP all printers are disabled:.......................................................................34 27. Configure STMS- .............................................................................................................34 28. Open Client........................................................................................................................35 29. Check the tRfc and qRfc in R/3 and <TGT>(EG:RFO)- ( OPTIONAL )...........................35 30. Make sure no background jobs are running......................................................................35 31. Delete any outstanding update records (<TGT>(EG:PFL))..............................................35 32. Delete any outstanding Lock entries (<TGT>(EG:PFL))..................................................35 33. Change the number of background and spool processes to normal- ............................35 34. Import <TGT>(EG:PFL) specific tables from prior export.................................................36 35. Restart SAP (CI & App) ....................................................................................................36 36. Execute BDLS on <TGT>(EG:PFL)..................................................................................36 37. Check Partner profile in <TGT>(EG:PFL) ........................................................................37 38. RFC Server Groups ..........................................................................................................38 39. Delete the old_SID system statistics.................................................................................38 40. Delete the Old Profiles.......................................................................................................38 41. Import Profiles....................................................................................................................38 42. Modify logon groups..........................................................................................................39 43. Modify Operation modes and instances............................................................................39 44. Import the user export to <TGT>(EG:PFL) client 100......................................................39 45. Set the system change option...........................................................................................40 46. Set the client settings ( As required Appropriate as per the SIR ) ...................................41 Change the client role to ‘Quality Client’ ...........................................................................41 47. Unlock Users & Release Background Jobs ....................................................................42 48. SLD Configuration.............................................................................................................43 49. Update the Java Parameters and other Java related settings in configtool.....................48 50. Start Online Backup ..........................................................................................................48 51. Schedule Archive log backups and Online Backups........................................................48

APPENDIX..................................................................................................................49

V 1.0 2

This document outlines how to refresh an SAP ECC 6.0 system. The procedure uses <TGT>(PFL) as a target system and <SRC>(PRL) as the source system to perform the refresh. It is assumed that the database server and central instance server for <TGT>(EG:PFL) already exists and is set up.

VERY IMPORTANT – IF SOLUTION MANAGER IS CONNECTED BEFORE REFRESH,

Please check that Solution Manager

Steps to deactivate the system monitoring in Solution Manager:

Login to SR0 >> Go to RZ21Technical Infrastructure>>Availability Monitoring>>Configure CCMSPIMG availability Monitoring

This will show you the list of the systems which are monitored by solution Manager

Select the system >> Right Click>De-activate system Monitoring

Then the system you deactivated will come under unmonitored system’s list.

On OS level of CI Server , make the startup –type of service SAPCCM4X service as dis-abled.

Steps to activate the system monitoring in Solution Manager:

Login to SR0 >> Go to RZ21Technical Infrastructure>>Availability Monitoring>>Configure CCMSPIMG availability Monitoring

The system will be in unmonitored system’s list.

Right Click >> Activate System monitoring

On OS level of CI Server, make the startup –type of service SAPCCM4X service as en-able and make sure that it is started.

V 1.0 3

1. Preparation

Please check the following with the customer1. If there are multiple clients in the system which user masters should be retained. ( Sometimes we make the assumption to only take the export of one client however they may have needed another clients user master, this has happened before)

Please have this check performed early before starting the refresh2. Take current screen shots of tables RSBASIDOC, RSLOGSYSDEST,STMS , CIFR-FCDES,WE20,SCC4,SM59,SE06,SLDAPICUST,RZ70,SXMB_ADM,SM51,AL11,SMLG,RZ04, . Also retain the profiles, kernel, nit.* files (dbs folder)so they can be replaced after the refresh.3. If it is unix system in EMDC make sure if the id is working and we have access to root access with su. Make sure this is communicated well in advance4. If we have to transfer files from one data center to other datacenter . Please make sure that the file is always pulled to the destination data center. This option is 3-10 times faster than the push. I don’t have an explanation as to why this happens( Many times pushing is the easier option . However I have found repeatedly that in the end we spend more time to push and finally end up with the pull.)5. Make sure there is space to import the data or in other words make sure the sap-data’s have enough space 6. Make sure the CD directories are known or can be accessed through NAS7. Never mount any CD or export directory from another data center even if it is possi-ble and start the sapinst pointing the location to the cds or export cd to that location ( This has resulted in very weird behavior in the past ) 8. The R3trans export script is documented in the appendix. However make sure that this precise script is used for export. Also make sure to check the export log. (We have other variations of this script and that also takes the tbtcp table and other batch related tables . This will retain the batch jobs of the current system , they want the batch jobs from the newly refreshed system )

1. Basis Pre tasks

On Target server <TGT>(EG:PFL)

Run the export<TGT>(eg:PFL)100tables.sh to export the tables related to RFC, Part-ner profiles etc. The script is attached in the Appendix section

Execute the command: R3trans -w <exportlog file> <cntl file>

2. Start Online backup in <SRC>PRL

In the Crontab of user oraprl, DISK backup is going on. If you want to take the backup manually you can also execute this manually V 1.0 4

/usr/sap/PRL/SYS/exe/run/brbackup -p initPRL_DISK.sap -d disk -t online_cons -m all -k yes -e 0 -l E –U

After the backup is complete, copy over the Backup files and Archive log files to the Target DB server PFL.

Alter database backup controlfile to trace;

3. Execute a user master export of <TGT>(EG:PFL) client 100.

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

Profile: SAP_USERTarget System: <TGT>(EG:PFL)

Click on ‘Start Immediately’Take note of the request number.

4. Create a system message, Screen shots of existing Value (WE20, WE21….so on)

• Go to transaction SM02- Put Appropriate MessageTake screenshots of WE20 ,WE21 , RSA1 , SLICENSE , STMS , STMS-Transport routes ,SM59 ( Take Screen shots of all RFC’s –Check authorization test also),SCC4,SE06,SCOT,SLDAPICUST,RZ70,SXMB_ADM,SLDCHECK,Configtool pa-rameters.SLDDATASUPPLIER in Visual admin,AL11,Rz04,SALE)

5. Send email to appropriate team for approved transport list after refresh

6. Export Java schema from <PRL> (source system)

Create a directory on source system (ex: /usr/sap/PRL/JAVA_EXP_150510)

Run SAPinst from SR2 Installation Master CD (on CI system)

Command should look like this (V V IMP)

<path_to_sapinst>/sapinst SAPINST_USE_HOSTNAME=saprlpas

On the Welcome screen (for Distributed system CI & DB on different servers)

Choose SAP Netweaver 2004S support release 2-> Additional Software Life-Cycle Tasks-> System Copy->Oracle->Source System-> Distributed System -> Based on AS ABAP and Java -> Central Instance Export. NOTE: you do not need the Database export (as we are using the Oracle backup/re-covery)

V 1.0 5

Choose Next

Select Custom option

V 1.0 6

Enter the profile directory of the SAP system

Profile Directory: /sapmnt/PFL/profile

Choose Next

SAP System User Domain

Domain Model -> Choose Local Installation

Choose Next

SAP System > OS User Passwords

Enter the <SRC>ADM password

V 1.0 7

Choose Next

System Copy

Choose Database Specific Tools (v important)

Choose Next

SAP System > Database Export

Enter the directory of Export Location

Export Location: Choose /usr/sap/PRL/JAVA_EXP_150510Uncheck stop running system (v important)

Choose Next

Parameter Summary

Review Summary and Click Start

Monitor the export and Check the logs

Note: Mark the time the Java export is created, the roll forward time for <TGT>(EG:PFL) system should be the time after this is created

FTP this Java export JAVA_EXP_150510 to PFL CI server

FOLLOWING STEPS SHOULD BE PERFORMED ONLY AFTER THE PRE BACKUP IS COMPLETED.

V 1.0 8

7. Copy init<SRC> files from <SRC>

Copy the following files from PRL <Oracle_Home>\database directory to PFL <Or-acle_home\database:

initPRL*.utlinitPRL*.dbainitPRL*.orainitPRL*.sap

8. Copy the export directory from <SRC> (source system CI server) to <TGT>(EG:PFL) (target system CI server)

FTP this Java export JAVA_EXP_150510 from PRL CI server to PFL CI server

( Here The file system is already mounted from source(PRL) to Target (PFL))

9. Copy backup and archive logs files from <SRC>

Also check the File is correct by checking the last lines of the Files & Status code to be ‘0’Eg: If *.and file is copied before the last line is written < terminated successfully> while restoring it will give problem Similarly if back<src>.log shows for the particular *.and file status is 9 ( In progress) , it has to be changed to ‘0’ status before going ahead.

Identify the required backup log file to restore from <SRC>Copy the required .and file from PRL (/oracle/PRL/sapbackup) to PFL (/oracle/PFL/sapbackup)Copy the backPRL.log from PRL (/oracle/PRL/sapbackup) to PFL (/oracle/PFL/sapbackup)Copy the archPRL.log from PRL (oracle/PRL/saparch) to PFL (oracle/PFL/saparch)

Begin Refresh of <TGT>(EG:PFL)

10. Stop SAP (CI & APP)

Stop SAP CI Shutdown Oracle

11. <TGT>(EG:PFL) Installation/Import (CI & DB on different servers)

Installation of SCS

V 1.0 9

Create directory for Inst Logs ex: /usr/sap/PFL/sapinst_scs

Run SAPinst from SR3 on CI system as below

Installation master SR3 = sudo /sapnas1/BS2005_SR3 _Installation_ Master_Solaris_X64/IM_SOLARIS_X86_64/sapinst

On the Welcome screen

Choose SAP ERP 6.0 support release 3-> Additional Software Life-Cycle Tasks-> Sys-tem Copy->Oracle->Target System-> Distributed System -> Based on AS ABAP and Java -> Central Services Instance.

Choose Next

V 1.0 10

Click on OK

SAP system -> general parameters

SAP system id (SAPSID) <TGT>(EG:PFL)

SAP System Mount Directory : /sapmntCheck the box: Unicode system recommended

Choose Next

SAP system > SCS Instance

Scs Instance Number: 11

Internal SCS Message server port : 3911

SAP System > OS USer Passwords

V 1.0 11

Enter the passwords for operating system users

SAP System Administrator

<CI host name>\<TGT>(EG:PFL)adm: XXXXX

SAP System Service User

<CI host name>\SAPservice<TGT>(EG:PFL): XXXXX

Choose Next

Media Browser > Software Packages

For Kernel select as below

Choose ok

Parameter Summary

Review the Summary and Click Start

12. <TGT>(EG:PFL) Installation/Import (CI & DB on different servers)

DB Installation

Run SAPinst from SR3 Installation Master CD (on DB system)

Created a directory for Installation logs in DB host(reuxgbuz415:pfladm)ex:. /usr/sap/PFL/sapinst_db

On the Welcome screen

V 1.0 12

Choose SAP ERP 6.0 support release 3-> Additional Software Life-Cycle Tasks-> Sys-tem Copy->Oracle->Target System-> Distributed System -> Based on AS ABAP and Java -> Database Instance.

Choose Next

Select Custom

Choose Next

V 1.0 13

Click on OK

Media Browser > Software Package Request

JAVA Component SR3 = /sapnas1/SAPCD/NWSR3JAVACOMP

Choose next

Enter the profile directory of the SAP system

Profile Directory: /sapmnt/PFL/profile

V 1.0 14

Choose Next

SAP System > Master Password

Password for all Users of this SAP System : XXXXXXXConfirm : XXXXXXX

Choose Next

SAP System > Database

Database Installation - (v important- Choose Proper Method)

Installation Method:Standard System Copy / Migration ( Load-based ) – Followed in this Case ( RFO) Choose Homogeneous System Copy ( Backup/Restore)

V 1.0 15

Choose Next

SAP System > Database Parameters

Database ID: Enter <TGT>(EG:RFO)Database Host: Enter HOST NAME

Choose Next

Optional – The below error are being observed during ECC 6.0 Refresh using BACKUP/Restore Method ( WINDOWS / SOLARIS-Unix )

V 1.0 16

Solution:

Modify control.xml as per sap note and Restart SAPINST again OSS NOTE – 970518

SolutionEdit the control.xml in the installation directory:Search for "update ORACHECK_PAR" and delete the row "row.createDb = false;" underneath.

Oracle > Database System as below

Choose Next

V 1.0 17

Password remains same as master passwordChoose Next

Check for existing listener port number and make sure both match

V 1.0 18

Password remains same as master password

Media Browser > Software Packages as below

Click Next

Parameter Summary

Review the Summary and Click Start

V 1.0 19

SAPinst stops at Backup/Restore database Step.

Note : Proceed with the backup/restore process as given below (do not exit, just minimize)

13. Create Soft Link

ln -s /oracle/PFL /oracle/PRL

14. Restore the database (PFL)

Use the same command prompt session to execute the following commands

brrestore -b xxxxxxx.and -d disk -r /oracle/PFL /102_64/dbs/initPFL_disk.sap -m full -l E

Verify the restore completed successfully

14. 1 Delete from all CONTROLPRL.DBF sapdata1

V 1.0 20

Delete from all CONTROLPRL.DBF oralogB

@CONTROL.SQLGenerated control fileSet RESETChange PRL to PFLULT8

15. Execute ‘Point in Time recovery

Use the same command prompt session to execute the following commandssqlplus /nologSQL> connect / as sysdbaSQL> startup mount

SQL> recover database using backup controlfile until time '2010-05-17:18:00:00' (CHANGE DATE & TIME ACCORDINGLY, time should be after the CONTROL.SQL generated on DB server and Java Export on CI server)

ORA-00279: change 76403165 generated at 17/059/2010 19:56:02 needed for thread ORA-00289: suggestion: /oracle/PRL /oraarch/PRLarch1_5435.dbfORA-00280: change 76403165 for thread 1 is in sequence #5435Specify log: {<RET>=suggested | filename | AUTO | CANCEL}AUTOVerify recovery finished successfully

SQL> alter database open resetlogs; Verify database opened successfully Please check the oracle alert log for more infoSQL> alter system switch logfile; (execute about 10 times)SQL> shutdown;SQL> startup (to make sure PRL database is recovered properly)SQL> shutdown;SQL> exit Close the command prompt session.

16. Adjust the init<TGT>(EG:PFL).ora file

Compare the init<SRC>.ora with init<TGT>(EG:PFL).ora and make changes accordingly.

17. Copy CONTROL.SQL to SAP install directory on <TGT>(EG:PFL) DB server

alter profile default limit COMPOSITE_LIMIT unlimited;alter profile default_new limit FAILED_LOGIN_ATTEMPTS unlimited;

V 1.0 21

alter profile default_new limit SESSIONS_PER_USER unlimited;alter profile default_new limit PASSWORD_LIFE_TIME unlimited;alter profile default_new limit COMPOSITE_LIMIT unlimited;alter profile default_new limit CPU_PER_SESSION unlimited;alter profile default_new limit PASSWORD_REUSE_TIME unlimited;alter profile default_new limit CPU_PER_CALL unlimited;alter profile default_new limit PASSWORD_REUSE_MAX unlimited;alter profile default_new limit LOGICAL_READS_PER_SESSION unlimited;alter profile default_new limit PASSWORD_VERIFY_FUNCTION NULL;alter profile default_new limit LOGICAL_READS_PER_CALL unlimited;alter profile default_new limit PASSWORD_LOCK_TIME unlimited;alter profile default_new limit IDLE_TIME unlimited;alter profile default_new limit PASSWORD_GRACE_TIME unlimited;alter profile default_new limit CONNECT_TIME unlimited;alter profile default_new limit PRIVATE_SGA unlimited;

Also check the DEFAULT profile and if needed do the above thing for DEFAULT profile

Then create a file CONTROL.SQL with the following content and copy it to to sapinst-dir of PFL DB server

Connect / as sysdbastartup;exit;

Recovery has been completed.

18. Resume SAPINST Sidadm in DBHOSTGive full permission to SAPINSTRestart SAPINST by Clicking OK (for DB installation to complete)

V 1.0 22

Now Click on OK button.

When prompted: Enter Database schema users that you want to drop1. OPS$<SRC>ADM2. OPS$SAPSERVICE<SRC>3. OPS$DATADM4. OPS$<SRC>

V 1.0 23

19. <TGT>(EG:PFL) Installation/Import (CI & DB on different servers)

Installation of CI Create a directory on CI server(reuxgbuz416:pfladm) as below./usr/sap/PFL/sapinst_ci

Run SAPinst from SR3 Installation Master CD (on CI server)

Installation master SR3 = sudo /sapnas1/BS2005_SR3 _Installation_ Master_Solaris_X64/IM_SOLARIS_X86_64/sapinst

On the Welcome screen

Choose SAP ERP 6.0 support release 2-> Additional Software Life-Cycle Tasks-> Sys-tem Copy->Oracle->Target System-> Distributed System -> Based on AS ABAP and Java -> Central Instance.

V 1.0 24

Choose Next

Parameter Mode > Default Settings Options – Typical or Custom Select Custom

Chose Next

Click on OK

V 1.0 25

Choose ok

Chose Next

Enter the profile directory of the SAP system

Choose Next

V 1.0 26

: Enter the master password

Click on Cancel

Choose Next

V 1.0 27

SAP System – Central Instance Central Instance Number - < 10>

Choose Next

Choose Next

Choose next

Choose OK

SAP system > Secure Store Information

Specify User J2EE_ADMIN and password of Production System ( PRL)

Choose next

V 1.0 28

SAP System > SDMPassword of SDM - <……….>Confirm <……….>

Choose Next

Choose next

Click OK

Parameter Summary

V 1.0 29

V 1.0 30

Review the Summary and Click Start

V 1.0 31

Click Continue

Click OK to complete CI Installation

NOTE: ERROR- Sometimes during Perform post-steps for Java Applications , you might en-counter the following error in runJMT.log – PSAPTEMP – empty –Solution - Increase / Add Datafile to PSAPTEMP & continue

Also, set the DEFAULT and DEFAULT_NEW DBA profiles like it was set before the REFRESH

20. Start SAP (CI) without background and spool processes.Change number of process for background and spool to ‘0’

V 1.0 32

Cleanipc <00,10 and 01> remove

21. Start SAP Services (CI)

Startsap

POST-REFRESH-ACTIVITIES

22. Install New SAP License

Login into SAP client 000 using SAP*Tcode: SLICENSE – New License – Import Installation Number: XXXXXXXXXSystem ID: <TGT>(EG:PFL)System Number: <xxxxxxxxxxxxxxxxxxxx>

Hardware Key: <xxxxxxxxxxxxxxxxxxxx>

License Key: <xxxxxxxxxxxxxxxxxxxx>

Valid to: 31.12.9999

Also license file will have J2EE license as well (see the last section)

NOTE: If SAP* entry was deleted from usr02 table.Login to each client with SAP* / PASS Tcode: SU01Create user SAP* and give the right authorizations and initial password

Reset DDIC password if necessary. Login to each client with SAP* and adjust with right password

Login to each client with DDIC and adjust with right password Update the password spread sheet with the changed passwords for each client

Note:- You can download license from Market place.No need apply for new

License.

license_script.txt

23. Lock All users & Suspend Background Jobs

Login into client 100Trx- SU10-, Mass changes to lock users (except basis group, ddic, sap*, own id etc)

V 1.0 33

Trx- SE38 – BTCTRNS1 ( To suspend all background jobs ) Tcode: sm50 -- make sure no BTC and SPO process are seen

24. Set up the workbench organizer

Login to client 000 as the user DDICGo to SE06

Select Database Copy or Database MigrationClick on Perform Post-Installation ActionsDo you want to reinstall the CTS? YESSource System of database copy: <SRC>Delete TMS Configuration? YESDelete old versions of the transport routes? NODo you want to delete the old versions of the transport routes? YES

25. Cancel Jobs in “Ready/Active” status:

Start transaction SM37 and display all jobs that are in a status of ‘Ready/Active’.

Cancel any jobs that show up as active or ready. (Remember to change the date range)

Highlight the job and choose ->Job ->Check Status. When prompted, cancel the job.

26. Verify within SAP all printers are disabled:

Using transaction SPAD, verify that the printers are showing up as locked and have been assigned to the dummy spool server.

If necessary, reset all SAP buffers using /$SYNC, and re-check SPAD if they are not showing up as locked.

27. Configure STMS-

Login to domain controller (eg:PSL) client 000 for <TGT>(EG:PFL) system Stms -> systems overviewDelete Target system entry (<TGT>(EG:PFL)Activate and distribute the configuration

Login into to <TGT>(EG:PFL) system client 000 Stms -> choose the right transport domain

Login to domain controller (PSL) client 000 for <TGT> (EG: PFL) system Stms -> system overview -> approve the new system -> distribute the configu-ration. Adjust the target system information (transport directory, groups etc)

NOTE:If it is a single system landscape, create a dummy system and configure the same in two systems landscape.

V 1.0 34

Transport routes>>Distribute and activate

Make sure that STMS is setup in the same way it was setup before the REFRESH

28. Open Client

Call transaction SE06

Click on system change option

Select ‘Modifiable’ from the drop down list box

Now click on Edit

Click on ‘Software Components Modifiable’ and click on ‘Namespaces Modifiable’

Click on ‘Client Settings’

Click on Change

Double click on Client 100

Set Client-Specific Objects to ‘Changes without automatic recording’

Set Cross-Client Object Changes to ‘Changes to repository and cross-client Customizing allowed’

Change client role to ‘Customizing’

Click on Save

29. Check the tRfc and qRfc in R/3 and <TGT>(EG:RFO)- ( OPTIONAL )

Use SMQ1 & SMQ2 & SM58 – Delete the old queue & cancelled LUW

30. Make sure no background jobs are running

Use SM50 and SM37

31. Delete any outstanding update records (<TGT>(EG:PFL))

Execute transaction SM13 delete all update records.

32. Delete any outstanding Lock entries (<TGT>(EG:PFL))

Execute transaction SM12 delete any outstanding lock entries.

33. Change the number of background and spool processes to normal-

Un-Comment out batch and spool processes from SAP CI and APP profilesrdisp/wp_no_btcrdisp/wp_no_spologin/min_password_lng

V 1.0 35

login/min_password_digits

34. Import <TGT>(EG:PFL) specific tables from prior export

<TGT>(EG:PFL)/100 table import Step:

Execute the command: R3trans -w <importlog file> <cntl file of import>

35. Restart SAP (CI & App)

Startsap

36. Execute BDLS on <TGT>(EG:PFL)

Run Tx BDLS

First Run

Old Logical System Name: <SRC>CLNT100

New Logical System Name: <TGT>(EG:PFL)CLNT100

De-Select 'TEST' and ‘Check Existence of New names in Tables’

Second Run: CRLCLNT100 to CFLCLNT100

Third Run: PRLCLNT100 to PFLCLNT100

Fourth Run: WRLCLNT100 to WFLCLNT100

Fifth Run: --WRTCLNT100 to WFTCLNT100

Execute in Background.

Note:- BDLS ran successfully with out any issues.

Check in Following tables whether logical system names has been changed properly or

Not?

V 1.0 36

SE16 RSLOGSYSDEST

SE16 CIFRFCDES

37. Check Partner profile in <TGT>(EG:PFL)

After Import of Tables all entries should be existing as present Earlier Go to WE20Select partner '<TGT>(EG:PFL)CLNT100'Change the RFC destination for port to '<TGT>(EG:PFL)CLNT100'Check all the outbound and inbound parameters

V 1.0 37

Activate the partner profile (if required)

38. RFC Server Groups

Call transaction RZ12Delete all <SRC> Server groups.

Double click on reuxgbuzXXX_<TGT>(EG:PFL)_10 Enter ‘parallel_generators’ as server groupClick on Save

39. Delete the old_SID system statistics

Using transaction ST03 delete all of the old system statistics relating to old_SID.Go to transaction ST03

Choose ->Expert mode -> Collector and performance DB -> Performance database -> Contents of DB, from the menu path.Press the ‘Delete data group’ pushbutton.

Choose ->Expert mode -> Collector and performance DB -> Performance database -> Reorganization (make sure the retention times are 30 days,

26 weeks 12 months)

40. Delete the Old Profiles

Go to RZ10

Select the old (source <SRC>) Instance profile

Click on Profile -> Delete -> All Versions -> Of a Profile

Select YES to confirm

Select YES to delete from the operating system

Perform the same steps to delete the old START profile

MAKE SURE THAT PROFILE PARAMETERS are same as what they were before the refresh

41. Import Profiles

Go to RZ10

Select Utilities > Import profiles > Active servers

V 1.0 38

Also, please make sure all the SAP parameters are same as before re-fresh.

42. Modify logon groups

Go to transaction SMLG

Delete logon group <SRC>

Double click on instance bp1tulapXXX_<TGT>(EG:PFL)_10

Click on save

43. Modify Operation modes and instances

Go to transaction RZ04Click on Instances/Operation modes

Now select the <SRC> and click on delete entry

To create new entries: Settings -> based on current status -> New instances -> generate

Adjust the Op mode time and WP distribution

44. Import the user export to <TGT>(EG:PFL) client 100.

Use the Transport request Exported earlier during the Pre-requisite checksEnsure -RDDIMPDP in 100 & 000 via DDIC. Is running ( OR ) Schedule SE38-RDDNEWP

V 1.0 39

Use STMS to import the user export.Go to SCC7 to complete the user import

Select ‘Schedule as Background Job’ Execute Tcode: PFUD

Note: If USER master import ended with return code 8, do the following steps,Delete the user master transport from the <TGT>(EG:PFL) STMS listRun RDDIMPDP in 100 & 000 via DDIC.

Also run RDDPUTPP in 000 and RDDNEWPP in 000 & 100 via DDIC Add the user master transport to the STMS list and import the transport.

Also delete all the STANDARD SAP jobs which are scheduled through sm36 and reschedule all the standard SAP jobs through SM36

45. Set the system change option

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

V 1.0 40

46. Set the client settings ( As required Appropriate as per the SIR )

Go to transaction SCC4Click on Change

Double click on Client 100

Set Client-Specific Objects to ‘No changes allowed’ Set Cross-Client Object Changes to ‘No changes to cross-client customiz-ing objects’

Change the client role to ‘Quality Client’

V 1.0 41

47. Unlock Users & Release Background Jobs

SU10 – Unlock All users which were locked earlier SE38 – BTCTRNS2 - Release all background Jobs

Optional - Import Transports Request. As per the SIR

V 1.0 42

48. SLD Configuration

Maintain in SLDAPICUST with Target System (PFL) details.

PFL is pointing to DSV System i.e. SLD-Development System

Maintain SLD Development System (DSV) details in RZ70

Maintain Same SLD details in Visual Administrator

V 1.0 43

Here it should be sapdsv.bpweb.bp.com

Port number as 50100

User Name is SLDAPI_PFL Password Labrad0r

Now check SLDCHECK is working fine.

V 1.0 44

V 1.0 45

V 1.0 46

49. STRUSTSSO2 .

1) Create local certificate of PFL

2) Get the EFV file from portal team and apply in PFL using strustsso2.

V 1.0 47

49. Update the Java Parameters and other Java related settings in configtool.

• Adjust the JVM

Configtool.sh ( config editor )

Go to cluster_data --> instance_IDXXXX --> server_IDXXXX

In the Java parameters change the values to following for the variables

-XX:NewSize=320m-XX:MaxNewSize=320m-XX:MaxPermSize=512m-XX:PermSize=512m-Xms2048m-Xmx2048m

Also, change the following 2 variables to point to PFL

Go to cluster_data --> instance_IDXXXX --> server_IDXXXX & Go to cluster_data --> instance_IDXXXX --> dispatcher_IDXXXX

-Drdbms.driverLocation=/sapmnt/PFL/SYS/exe/run/classes12.jar-Dsys.global.dir=/sapmnt/PFL/SYS//SYS/global/

• Apply License (Login to Visual Administrator go.sh)

Go to CLUSTER --> SERVER --> SERVICES --> LICENSING ADAPTER --> Install from file

50. Start Online Backup

Make sure that Gateway is started on PFL DB server

Use DB13Schedule immediate online backup

51. Schedule Archive log backups and Online Backups

Make sure that CRON is setup for Online backups and archivelogs

V 1.0 48

APPENDIX

Scripts to update tables for WE20, WE21, BD64, SM59

Bat file: export<TGT>(eg:PFL)100tables.shR3trans –w export<TGT>(eg:PFL)100tables.log export<TGT>(eg:RFO)100ta-

bles.cntl

Control file: export<TGT>(eg:PFL)100tables.cntlexportfile = 'clone.export.RFO.data'select * from ediposelect * from rfcdesselect * from rfcdocselect * from btcomsetselect * from btcomsdlselect * from btcevtjobselect * from tsp03select * from tsp03cselect * from tsp03dselect * from txcomselect * from rzllitabselect * from rzlliclassselect * from tbtcaselect * from tbtcbselect * from tbtccntxtselect * from tbtcctxttselect * from tbtcctxttpselect * from tbtciselect * from tbtcjstepselect * from tbtcoselect * from tbtcpselect * from tbtcrselect * from tbtcsselect * from btcevtjob

exportclient = 100file = 'clone.export.RFO.100.data'select * from edpp1select * from edp13select * from edp21select * from edp12select * from tbd00select * from tbd00tselect * from tbd03select * from tbd05select * from tbd06select * from tbda1select * from tbda2select * from tbd20select * from tbd62select * from edipoa

V 1.0 49

select * from edipodselect * from ediport

Bat file: import<TGT>(eg:PFL)100tables.shR3trans -w import<TGT>(eg:PFL)100tables.log -uimport<TGT>(eg:RFO)100ta-

bles.cntl

Control file: import<TGT>(eg:PFL)100tables.cntlremoveselect * from ediposelect * from rfcdesselect * from rfcdocselect * from btcomsetselect * from btcomsdlselect * from btcevtjobselect * from tsp03select * from tsp03cselect * from tsp03dselect * from txcomselect * from rzllitabselect * from rzlliclassselect * from tbtcaselect * from tbtcbselect * from tbtccntxtselect * from tbtcctxttselect * from tbtcctxttpselect * from tbtciselect * from tbtcjstepselect * from tbtcoselect * from tbtcpselect * from tbtcrselect * from tbtcsselect * from btcevtjob

removeclient = 100

select * from edpp1select * from edp13select * from edp21select * from edp12select * from tbd00select * from tbd00tselect * from tbd03select * from tbd05select * from tbd06select * from tbda1select * from tbda2select * from tbd20select * from tbd62select * from edipoaselect * from edipodselect * from ediport

importfile = 'clone.export.PFL.data'buffersync = yes

V 1.0 50

importclient = 100file = 'clone.export.PFL.100.data'buffersync = yes

Issue:-

Our colleague Jan Roelans is having a problem running Interface tests, follow-ing the PFL refresh.

This is because the logical file destinations in PFL have not been corrected as part of the refresh procedure.

Can you please fix this now?

It will require PFE to be opened temporarily for changes whilst you make the change in client 100.

- Transaction FILE

- Locate logical filepath ZZIFC_INBOUND_IDOCS, and change the destina-tion from value /interface/inbound/PRL/<FILENAME> to value /interface/in-bound/PFL/<FILENAME>

- Locate logical filepath ZZIFC_ARCHIVE_IDOCS, and change the destina-tion from value /interface/inbound/PRL/archive/<FILENAME> to value /inter-face/inbound/PFL/archive/<FILENAME>

Please also modify your refresh documentation, so that this step is completed as part of the Refresh in future.

Solution:-

Once you enter the FILE transaction.

V 1.0 51

Select ZUTC_FILES using position button.

Select left side “Assignment of Physical Paths to Logical Path

V 1.0 52

Select UNIX and click on Magnifying glass.

V 1.0 53

Then the FILEPATH would be displayed.

We have changed the below from PRL to PFL.

- Locate logical filepath ZZIFC_INBOUND_IDOCS, and change the destination from value /interface/inbound/PRL/<FILENAME> to value /interface/in-bound/PFL/<FILENAME>

V 1.0 54

- Locate logical filepath ZZIFC_ARCHIVE_IDOCS, and change the destination from value /interface/inbound/PRL/archive/<FILENAME> to value /interface/in-bound/PFL/archive/<FILENAME

V 1.0 55