Copa vol 6

Copa vol 6

A 108 Step Example of a DMO Migration Runbook

•There are many repertory task you must do before the actual migration• In steps 1,2, and 3 we are reviewing the latest notes and setting up user and system access

In step 4.2 you must request a migration key

ID Task Page No.

1.0 Introduction 52.0 Reference documents 62.1 Reference SAP Notes Overview 62.2 Updated Tools Overview 63.0 Access & User ID's 73.1 Request OS access to source system 73.2 Access to OS with sidadm 73.3 Acess to OS with orasid 73.4 Oracle SYSTEM password 73.5 Oracle schema password 73.6 DDIC in client 000 on source system 73.7 Basis role access to SAP default business client 73.8 Access to HANA studio with SYSTEM 73.9 Access to HANA Linux servers with sidadm 7

3.10 Access to VM-Linux servers 73.11 Obtain target instance numbers 7

General Preparations 84.1 Check wether SSFS is configured on the Oracle system 84.2 Migration key for OS/DB migration 94.3 New SAP license for BW on HANA 94.4 Check disk space for SUM-DMO 94.5 Create MOPZ stack file for SUM-DMO 94.6 Request and/or download software & support packs 104.7 Download HANA client 104.8 Verify recent backup of Oracle system 104.9 Verify recent backup of HANA 10

4.10 Switch HANA archivelog mode to overwrite 104.11 Download updated exception tables according to OSS Note 996990 104.12 Install or upgrade existing SAPHOSTAGENT 104.13 Check SNOTE 104.14 Check and clear SPDD 104.15 Check and clear SPAU 104.16 Check table TBATG - transaction ICNV - 114.17 SAP notes related to BW-HANA Migration 114.18 Update SAP kernel to 720_EXT_REL patch 110 or higher 124.19 Update memory parameters for Linux app server 124.20 Update SPAM to version 51 or higher for SAP NetWeaver 7.01 124.21 Upgrade BR*Tools to latest verstion 124.22 Apply SP ST-PI 2008_1_710 SP7 in BW system 12

A 108 Step Example of a DMO Migration Runbook (cont.)• For those doing a Unicode conversion, there are

many additional steps. We first need to check what is already in-place. Thankfully, SAP provides programs to help you with these to check the config.

5.0 Unicode Preparations 135.1 Check consistency between DB & DD 13

5.2Create table CLU4 & VER_CLUSTR in the database for the sake of Unicode checks in DMO

13

5.3 Re-check consistency between DB & DD 145.4 Run report UCCHECK 145.5 Conversion of customer-defined code pages 155.6 Pre-conversion correction of table data BDCP* 165.7 Consistency check for cluster tables 175.8 Check installed langauges 185.9 Check tables TCPDB and TCP0I 18

5.10 Run Program TWTOOL01 to find Match Code IDs 185.11 Run report RSCPINST 19

5.12 Run report TERM_DELETE_INCORRECT_CHARSET SAP Note 1280494 19

5.13 Re-run report TERM_DELETE_INCORRECT_CHARSET 205.14 Check table DBTABLOG SAP Note 1255556 215.15 Delete the contents of ADR tables as described in OSS Note 673941 215.16 Remove temporary objects SAP note 449891 225.17 Delete QCM invalid temp tables 225.18 Run report RADNTLANG SAP Note 480671 235.19 Reset nametab buffer after RADNTLANG report 245.20 Database statistics update 245.21 Check Nametab 245.22 SPUMG 255.23 Upload newest exception tables according to OSS Note 996990 255.24 Start additional preparation steps 265.25 Continue with transaction SPUMG 275.26 Check language lists 275.27 Set global fall-back codepage 285.28 Initialise the worklist 285.29 Schedule Worker jobs 295.30 Check status of consistency check 305.31 Update worklist 305.32 Nametab Handling 315.33 Generate statistics for active nametab tables 315.34 Create the Unicode nametabs 315.35 Run UMG_SHOW_UCTABS 335.36 Generate statistics for active nametab tables 345.37 Run additional downtime steps 34

You can get this report by running the report UCCHECK and seeing the installed languages in the

source system by using the transaction SMLT

A 108 Step Example of a DMO Migration Runbook (cont.)

•The next major step is to extract the files needed for the migration. Here you will need the migration keys you obtained in step 4.2.

6.0 Software Update manager (SUM) and Direct Migration Option 356.1 Extract SUM-DMO 356.2 Create a softlink to HANA Client 356.3 Configure SAP Host Agent 356.4 Adjust DMO parameter file 356.5 Launch SUM-DMO 366.6 Extraction phase 376.7 Configuration phase 426.8 Check BW standard RFC 436.9 Check whether DMO created schema on HANA 47

6.10 Checks phase 526.11 Error with Partitioned DSOs at DB level 546.12 Error with inactive transfer rules in RSUPGRCHECK 586.13 Extend tablespaces 586.14 Extend PSAPTEMP 586.15 Post processing phase 606.16 Error with DB view ZCUST_SALES 626.17 Migration uptime phase 666.18 Prepare for downtime 706.19 Suspend batch jobs program BTCTRNS1 706.20 Check users in AL08 716.21 Check jobs running 716.22 Confirm backup 726.23 Confirm prepare completed 736.24 Starting migration 736.25 Error when RFC dedisnation for FINBASIS is not available 746.26 Error for D version update rules 766.27 Error during execution of RDDEXECL 776.28 ASCS Switch 826.29 Adapt soft links on the ASCS server 826.30 Switch logmode & backup HANA database 836.31 Errors reported when restarting SAP 856.32 Downtime finished message 856.33 PSA post processing has shortdump 866.34 DMO Post-processing 876.35 Restart RDA DAEMON 886.36 SPAU 886.37 Error in DB Check 896.38 Update finished 91


• If you are working with a BW system that is not heavily used, or one that has lots of processing capacity, you can minimize the downtime by using a “shadow system” during the upgrade

• If you use a shadow system (option 2/3), the system will be copied (not the data) and many of the upgrade tasks will happen on this “shadow’ system” while the real system is still running

•Only in the later stages is the system unavailable to the users while the configuration and data are moved to SAP HANA•This minimizes the downtime of the system




•Now we have to tell the DMO what system we are coming from and what system we want to migrate to




• It is now time to check inside SAP HANA Studio that the BW schema has been created by DMO. You find this under “users” in the HANA navigator.



• We also have to decide what support packages we want to include in the upgrade. Normally we pick the latest and ignore the equivalent SPs.


• In the check phase, you may get “soft warnings” or items that have to be fixed before progressing. Pay close attention to both and make sure you understand what each mean. 6.0 Software Update manager (SUM) and Direct Migration Option 35

6.1 Extract SUM-DMO 356.2 Create a softlink to HANA Client 356.3 Configure SAP Host Agent 356.4 Adjust DMO parameter file 356.5 Launch SUM-DMO 366.6 Extraction phase 376.7 Configuration phase 426.8 Check BW standard RFC 436.9 Check whether DMO created schema on HANA 47



•If you did not complete the in-depth cleanup tasks we recommended earlier, you can now do some basic system cleanup as well



Most of the cleanup tasks are better performed prior to starting this process


•Since the “shadow system” is created, no more changes to the configuration or settings in the existing BW system can occur after this stage•NOTE: Users can still access the system




• If we want to make changes to the shadow instance, we can do that by logging on as user DDIC and changing the system setting using the transaction code SE06.



We can now make changes directly using the transaction code SPDD

Documents

Copa vol 6