Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
BW Migration to HANA
Part 2 of 3
SUM DMO Tool for SAP Upgrade & Migration
By OZSoft Consulting for ITConductor.com
Author:...
Introduction
• This is Part 2 of the series of publication which provides an
overview and explanation of major steps and c...
DMO, Guides
• SUM’s DMO (Database Migration Option) is the tool to update and
migrate anyDB (any Database) to HANA.
• HINT...
DMO (Database Migration Option)
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 4
(SOURCE) SID ABA
BASIS 750/02
S...
DMO uses memory pipe mode
The export and import occurs within the same server, so data
is passed through the same memory s...
DMO - more
DMO’s migration repetition for testing purposes of the downtime phase
See: 4.3.4 Using the Migration Repetition...
SLUIGUI – going around
The tab in the right hand side are Legend, More, Task List, Logs,
Breakpoints. Clicking on any tab ...
SLUIGUI - MORE
Under More,
SUM Guide – this will take you to SAP marketplace, right to SUM guide page
SUM Note – this will...
SLUIGI – Utilities and Task List
Utilities can also be viewed directly from the ‘extended viewer’ -
<server>:1128/lmsl/sum...
SLUIGUI – LOGS, BREAKPOINTS
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 10
V
Logs can be viewed without going...
Observer Mode
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 11
This feature allows monitoring for the
update pr...
Resetting DMO, source DB instance after migration
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 12
RESETing the...
DMO - Optimization
During the days of Combined Upgrade and Unicode
Conversion (CUUC) – downtime optimization was a challen...
Benchmarking tool
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 14
DMO’s ’benchmarking’ (migration) tool is
ava...
Migration Repetition/Optimizing downtime
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 15
DMO provides ‘migrati...
Preparations/Checks - 1
Migration Key - Generate the system migration key
License - Generate the license for the target mi...
Preparations/Checks - 2
SAP Host agent – install/update to the latest version
SPAM Update to the latest SPAM, or download ...
Preparations/Checks - 3
Deletion of some BW objects
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 18
In one of ...
Migration Steps/Screenshots - 1
Start DMO
http://sid-aba-aba:/1128/lmsl/sumabap/<SID>/doc/sluigui
Extracts from SAPupConso...
Migration Steps/Screenshots - 2
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 20
>> 2016/08/05 13:14:32 START O...
Migration Steps/Screenshots - 3
Author: Terry Kempis Editor: Linh
Nguyen
ITConductor.com 21
SAP HANA SCALE OUT
Are you run...
Migration Steps/Screenshots - 4
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 22
PREP_CONFIGURATION/SUBMOD_MIG_...
Migration Steps/Screenshots - 5
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 23
Enter the path of the SAP Lice...
Migration Steps/Screenshots - 6
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 24
=========== Parameters for BW-...
Migration Steps/Screenshots - 7
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 25
=========== Perform Scale Up (...
Migration Steps/Screenshots –
Export/Import/Downtime
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 26
Checks af...
Next – Post-processing on the New System
• Now that we have prepared the source BW system, and
• We have completed the SAP...
• Any Questions?
• Contact Info:
Linh Nguyen linh.nguyen@itconductor.com
Terry Kempis terry.kempis@itconductor.com
Let
itc...
Nächste SlideShare
Wird geladen in …5
×

BW Migration to HANA Part 2 - SUM DMO Tool for SAP Upgrade & Migration

8.360 Aufrufe

Veröffentlicht am

This series of publication intends to provide an overview and explanation of major steps and considerations for BW on HANA migrations from anyDB (any database). The complex procedure involves:
1) Preparatory work in the BW system
2) SUM DMO Upgrade and Actual migration
3) Post processing on the migrated systems
This first part focuses on the SUM DMO tool used for the migration, pre-requisites, optimization and the actual migration steps

By OZSoft Consulting for ITConductor.com
Author: Terry Kempis
Editor: Linh Nguyen

Veröffentlicht in: Software

BW Migration to HANA Part 2 - SUM DMO Tool for SAP Upgrade & Migration

  1. 1. BW Migration to HANA Part 2 of 3 SUM DMO Tool for SAP Upgrade & Migration By OZSoft Consulting for ITConductor.com Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 1 Any DB Migrate Upgrade
  2. 2. Introduction • This is Part 2 of the series of publication which provides an overview and explanation of major steps and considerations for BW on HANA migrations • Migrating a BW system from anyDB (any database) to HANA involves 1. Preparatory work in the BW system 2. SUM DMO Tool for SAP Upgrade and Migration 3. Post processing on the migrated systems • This part focuses on the tool used for the migration, pre- requisites, optimization and the actual migration steps. Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 2
  3. 3. DMO, Guides • SUM’s DMO (Database Migration Option) is the tool to update and migrate anyDB (any Database) to HANA. • HINT: It cannot be used for pure migration purposes only! If your current release/level already meet the HANA requirement and does not want to do go the latest release/level, then at least update other package (e.g. ST-PI) so that you will have stack xml which is needed by DMO. • Before embarking on doing migration using DMO, first go through the following • ‘SAP First Guidance - Using the DMO Option to Migrate BW on HANA, • ‘Database Migration Option (DMO) of SUM - Introduction’ - it provides a very good introduction of DMO and contains links to other related blog (e.g. optimization, technical background). • All notes in this document and the steps followed in this migration exercise were based on the cookbook, blogs and the references below. • The central note 2257362 for DMO with SUM 1.0 SP 17 • Update of SAP Systems using SUM 17 <— read this one to appreciate the SL Common UI, features, etc. • Database Migration Option of SUM SP17 - Target Database SAP HANA ITConductor.com 3 Author: Terry Kempis Editor: Linh Nguyen
  4. 4. DMO (Database Migration Option) Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 4 (SOURCE) SID ABA BASIS 750/02 SYBASE DB (TARGET) SID ABA BASIS 750/04 HANA DB KERNEL 745 patch 200 DMO needs two sets of kernel Target software release of the source DB – i.e. 745 patch 200 for SYBASE DB Target software release of the target DB – i.e. 745 patch 200 for HANA DB Target software release of the target DB – i.e. 745 patch 200 for HANA DB Source and Target System for this exercise DMO is an inplace-migration using SUM (Software Update Manager). The target PAS will replace the source PAS in the same host, using same ID, network configuration SOURCE PAS TARGET PAS
  5. 5. DMO uses memory pipe mode The export and import occurs within the same server, so data is passed through the same memory segment Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 5 SOURCE SYBASE DB TARGET HANA DB PP EXPORT Kernel : 745/200 SYBASE Import Kernel: 745/200 HANA Memory Reference: DMO: comparing pipe and file mode for R3load
  6. 6. DMO - more DMO’s migration repetition for testing purposes of the downtime phase See: 4.3.4 Using the Migration Repetition Option for Testing of the DMO Guide DMO supports MDC The target database in DMO can be a tenant database. DMO has option to create the target DB, if it does not exist yet. DMO Unicode conversion DMO can convert a non-Unicode system to Unicode – at the same downtime. Note that only single-code page is supported, not multi-code (MDMP). DMO SQL DDL generation DMO generates the DDL in one of its phase, so there is no need to manually run this. Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 6
  7. 7. SLUIGUI – going around The tab in the right hand side are Legend, More, Task List, Logs, Breakpoints. Clicking on any tab to expand, click again on the tab to hide. Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 7
  8. 8. SLUIGUI - MORE Under More, SUM Guide – this will take you to SAP marketplace, right to SUM guide page SUM Note – this will take you to the central note of the current SUM you are using SAP Help Portal – goes to https://help.sap.com Log Tail – this is the log ‘tail viewer’. You can choose any log file, e.g. SAPup.log Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 8
  9. 9. SLUIGI – Utilities and Task List Utilities can also be viewed directly from the ‘extended viewer’ - <server>:1128/lmsl/sumabap/<SID>/doc/sluigui_ext/ Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 9
  10. 10. SLUIGUI – LOGS, BREAKPOINTS Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 10 V Logs can be viewed without going to the OS Breakpoints can be set from here
  11. 11. Observer Mode Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 11 This feature allows monitoring for the update process from a mobile device or desktop. To use, 1. Prepare the observer mode (create new user <sid>obs, add a password, then add group SAPSYS to <sid>obs. 2. Start the observer monitor with the following URL, login with the <sid>obs user <server>:1128/lmsl/sumobserver/ABA/mo nitor/index.html
  12. 12. Resetting DMO, source DB instance after migration Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 12 RESETing the DMO After migration, the source database remains intact. It’s on the state before the shutdown. If for whatever reason, it can be used again after a reset which is provided by DMO. Note that the reset will delete data from the target HANA DB. Reference: DMO technical background Source database after migration After the migration testing, we installed another PAS pointing to the source database – so we ended up with two running systems: 1. A migrated system in HANA 2. The original source ASE system The normal steps in installing a Distributed system are: 1. ASCS instance 2. Database Instance 3. Primary Application System (PAS) But only step 1 and 3 are needed. Note that by skipping step 2, the profile parameter, environment (env.csh) and DB (dbenc.csh) variables may have some missing items. Fortunately, that DMO backup the source system versions, including the kernel for reference/re-use. This is handy for production copy sandbox – for comparison purposes, but not on production. Ensure that this is totally isolated from normal use.
  13. 13. DMO - Optimization During the days of Combined Upgrade and Unicode Conversion (CUUC) – downtime optimization was a challenge. You need to manually specify table split, which tables to do first, etc. With DMO, tools and features are available to reduce the downtime, including optimized table splitting • Benchmark Tool • Migration repetition Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 13
  14. 14. Benchmarking tool Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 14 DMO’s ’benchmarking’ (migration) tool is available to simulate the export and import process to check the migration rate/speed. It has repetition option to enable optimization by adjusting the process parameters (SQL uptime, SQL downtime, R3load uptime, R3load downtime). This should be done before the DMO and against a production copy which mirrors the production setting, (i.e. capacity, network, target HANA) HINT: benchmark both export and import to simulate production run For more details, refer to the following Optimizing DMO Performance
  15. 15. Migration Repetition/Optimizing downtime Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 15 DMO provides ‘migration repetition’ to help reduce the system downtime. For each DMO run, the following files are created • ‘MIGRATE_UT/DT_DUR.XML’ - contains statistics for each migrated table • UPGANA.XML These files can be use for subsequent DMO run to optimize and reduce the downtime. See DMO Guide Cookbook DMO UPGANA.XML MIGRATE_*_DUR.XML
  16. 16. Preparations/Checks - 1 Migration Key - Generate the system migration key License - Generate the license for the target migrated system (i.e. based on HANA DB). Time zone • Make sure both source system and the HANA severs have the same time zone settings and within SAP (transaction STZAC). DB Free space • As a shadow system is created, there should be at least 50Gb database free space, or more, depending on the existing components. SAPLOCALHOST/Hostname Make sure that the profile parameter SAPLOCALHOST matches the hostname in SM51. WARNING: Hostname 'XXXXXXXX' is different from hostname 'YYYYYYYY' system runs with! If you encounter the issue in the shadow instance, stop SAPup, stop the shadow instance, edit the parameter in the SHADOW profile directory, restart the shadow instance. Resume the process. Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 16
  17. 17. Preparations/Checks - 2 SAP Host agent – install/update to the latest version SPAM Update to the latest SPAM, or download and extract it into /trans/EPS/in SAPCAR download the latest SAPCAR for extraction HANA Client • Download and extract the HANA client • For LINUX PAS, the DMO will install it as part of the migration • For Windows PAS, install it manually before starting the DMO. DOWNLOAD/Stack.xml • The Maintenance Planner is now used to generate the stack.xml and download the target components, including the latest SUM, ACPs, and kernel (for all platforms) Target HANA DB log mode • Set the log_mode parameter to ‘overwrite’ Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 17
  18. 18. Preparations/Checks - 3 Deletion of some BW objects Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 18 In one of the dialog, you will enter values as per below. Discuss with your BW team. Delete temporary BW query bookmarks older than ... days:: 99 Delete sent BW query bookmarks older than ... days:: 9 Delete BW traces older than ... days:: 99 Delete BW statistics older than ... days:: 9 After extracting the SUM package, change owner to <sid>adm and the group to sapsys As root, register to host agent - cd <download directory>/SUM ./STARTUP confighostagent <SID> Normal upgrade preparations are not included in this document, e.g. pre-downtime tasks like queue processing, stopping jobs, locking users, etc. SUM
  19. 19. Migration Steps/Screenshots - 1 Start DMO http://sid-aba-aba:/1128/lmsl/sumabap/<SID>/doc/sluigui Extracts from SAPupConsole.log – note that only DMO-related phases are included here Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 19 ======= This is SAPup release lmt_008 V53.000 - all engines are running ======= =========== Welcome to Software Update Manager =========== Important information for this program is included in * SAP Note 2223738* and further SAP Notes mentioned therein. The keyword is included in the relevant product-specific SAP Note. Read the current version before you start preparing the procedure and check the SAP Note again for changes before you start the procedure.
  20. 20. Migration Steps/Screenshots - 2 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 20 >> 2016/08/05 13:14:32 START OF PHASE PREP_INPUT/MIG2NDDB_INI =========== Database Migration Option =========== Enter the target database type: 01) - No migration 02) * SAP HANA DATABASE TYPE: SAP HANA =========== Migration Parameters =========== Select tables for table comparison checks. 01) * Do not compare table contents 02) - Operate on all tables 3) - Operate on selected tables only Provide a valid migration key for installation number "0123456789". For a detailed description of generating the key, see SAP note *317096* . Migration Key: 1W5gdEM50D001eqtdQQ011e3
  21. 21. Migration Steps/Screenshots - 3 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 21 SAP HANA SCALE OUT Are you running a SAP HANA Scale Out Landscape as a target for this migration? *If so, you can enable the landscape reorganization during the preprocessing of the migration.* . 01) Execute Landscape Reorg Enter a number/range/"all" to change selection or "ok" or <ENTER> to complete Test cycle This option will stop the tool after the downtime migration phase, enabling a simple repetition of it to optimize the procedure by tuning the parameters (like R3load processes). You should in no case use this option for a productive run! 01) X Enable Migration Repetition Option Migration Repetition Choose an execution strategy for transaction SGEN. Select option ‘Do not start ABAP load generation during the update’. There is more flexibility when doing it as a post-task (e.g. use more servers) NOT for production
  22. 22. Migration Steps/Screenshots - 4 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 22 PREP_CONFIGURATION/SUBMOD_MIG_INSTCLIENT/HDB_INSTCLIENT =========== Target database client =========== The tool needs access to the target database client. Enter the following information: Path to "hdbinst" for client installation: (This is where the HANA DB Client will be installed in LINUX. For Windows, this should be installed before starting DMO) =========== Database Migration Initialization =========== You are going to migrate your system to a new database. Enter the following parameters of the target database: Target Hostname: xxxxxxxx Enter the SID and instance number of the target database instance (might be different from your SAP system): SID of the target database: A4H Target Instance Number: 00 Tenant DB name. If it does not exist yet, it will be created during the process. See next slide
  23. 23. Migration Steps/Screenshots - 5 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 23 Enter the path of the SAP License file for your migrated SAP system: Target System License: (License key based on HANA DB) *Additional Information:* Specify the database connectivity data of the target database to be used for the SAP system migration. In case you are using a SAP HANA multitenant database container, specify the connectivity data of the target database tenant. In case you are using a SAP HANA multitenant database container, and want to create a new database tenant, specify the connectivity data of the database tenant to be created. Enter password for target database user "SYSTEM". Enter password for target database SYSTEMDB superuser (MultiDB).
  24. 24. Migration Steps/Screenshots - 6 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 24 =========== Parameters for BW-Specific reports =========== Within the next phases certain BI housekeeping tasks will be performed. Please decide which data shall be deleted in the database. **Caution:* The data deleted during the next phases as specified in the fields below cannot be restored by resetting update process.* Enter the amount of data to be deleted: Delete temporary BW query bookmarks older than ... days:: 99 Delete sent BW query bookmarks older than ... days:: 9 Delete BW traces older than ... days:: 99 Delete BW statistics older than ... days:: 9 Values agreed with BW team
  25. 25. Migration Steps/Screenshots - 7 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 25 =========== Perform Scale Up (Single Node) Prerequisite on SAP HANA if necessary =========== *Action Required (if condition is met):* *You decided to NOT run the SAP HANA Landscape Reorganization. However, if you run an SAP HANA Single-Node system with scale-up, you must manually import a file with specific SQL-information to enable the optimal table partition. Carry out the following procedure:* 1. Download the appropriate file that is in the attachment of the following SAP Notes: * For SAP Business Warehouse on SAP HANA, see SAP Note 1908075. From the attachment TABLE_PLACEMENT_BW.zip, select the suitable SQL-file. * For SAP Business Suite on SAP HANA or SAP S/4HANA, see SAP Note 1899817. Choose the attachment: TABLE_PLACEMENT_ERP_* or TABLE_PLACEMENT_S4H_* according to the version and SP level of the target system. 2. Edit the downloaded file by replacing all occurrences of $$PLACEHOLDER with your SAP<sid>. 3. Import the edited files to SAP HANA using one of the following commands on OS level of the managed system: * */usr/sap/ABA/hdbclient/hdbsql -U SYSTEM -I <filename> -E 1* * */usr/sap/ABA/hdbclient/hdbsql -U SUPER -I <filename> -E 1* 4. After the import, continue with the migration procedure.
  26. 26. Migration Steps/Screenshots – Export/Import/Downtime Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 26 Checks after phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_ MIG_DT_RUN were negative! Last error code set: Found 12 failed export processes Found 64 failed import processes << 2016/08/10 18:35:33 END OF PHASE MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_ MIG_DT_RUN REPEAT – some errors due to export and import server capacity (e.g. memory) =========== Testcycle =========== Downtime migration finished successfully. 01) - Yes, initialize the downtime migration phase and repeat 02) * No, continue with next phase Do you want to repeat the downtime migration phase?: No, continue with next phase Downtime reached, migration repetition prompt
  27. 27. Next – Post-processing on the New System • Now that we have prepared the source BW system, and • We have completed the SAP SUM (Software Update Manager) upgrade & migration using DMO (Database Migration Option) for the BW system from anyDB to BW on HANA. • Stay tuned for the next section Post-processing on the Upgraded/Migrated System. Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 27
  28. 28. • Any Questions? • Contact Info: Linh Nguyen linh.nguyen@itconductor.com Terry Kempis terry.kempis@itconductor.com Let itconductor.com @itconductor 28

×