SAP First Guidance - Using the DMO Option to Migrate BW on HANA

May 17, 2018 | Author: Santosh Sarkale | Category: Ibm System I, Databases, Ibm Db2, Computer Engineering, Computer Data
Share
Report this link


Comments



Description

SAP First GuidanceSAP BW 7.3x/7.4 SAP Realtime Database Platform SAP First Guidance - migrate BW on HANA with the database migration option (DMO) Applicable Releases: SAP NetWeaver BW 7.0x SP27/SP10 SAP NetWeaver BW 7.3x SP07/SP03 SAP NetWeaver BW 7.40 SP02 and higher DMO is an option of SUM for combined update and migration including unicode conversion: update an existing SAP system to a higher software release and migrate to SAP HANA database including UC migration. As the technical SUM steps are the same, this “SAP First Guidance” document should make all customer-specific documentation obsolete. It is the complementary documentation to the existing Notes and SUM/DMO Upgrade Guides. The document is “work in progress” and it not intended to be exhaustive, although it does contain everything you need to successfully migrate your existing BW System Release 7.0x running on any DB to BW on HANA 7.31 or higher, using the database migration option (DMO) as part of the software update manager (SUM) provided by the SL toolset. For more Information please contact [email protected] SAP First Guidance SAP BW 7.3x/7.4 SAP Realtime Database Platform Version 1.58 September 2014 © Copyright 2014 SAP AG. All rights reserved. All other product and service names mentioned are the trademarks of No part of this publication may be reproduced or transmitted in any form their respective companies. Data contained in this document serves or for any purpose without the express permission of SAP AG. The informational purposes only. National product specifications may vary. information contained herein may be changed without prior notice. The information in this document is proprietary to SAP. No part of this Some software products marketed by SAP AG and its distributors document may be reproduced, copied, or transmitted in any form or for contain proprietary software components of other software vendors. any purpose without the express prior written permission of SAP AG. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered This document is a preliminary version and not subject to your license trademarks of Microsoft Corporation. agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® IBM, DB2, DB2 Universal Database, System i, System i5, System p, product and is not intended to be binding upon SAP to any particular System p5, System x, System z, System z10, System z9, z10, z9, iSeries, course of business, product strategy, and/or development. Please note pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, that this document is subject to change and may be changed by SAP at OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power any time without notice. Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, SAP assumes no responsibility for errors or omissions in this document. HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, SAP does not warrant the accuracy or completeness of the information, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and text, graphics, links, or other items contained within this material. This Informix are trademarks or registered trademarks of IBM Corporation. document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of Linux is the registered trademark of Linus Torvalds in the U.S. and other merchantability, fitness for a particular purpose, or non-infringement. countries. SAP shall have no liability for damages of any kind including without Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either limitation direct, special, indirect, or consequential damages that may trademarks or registered trademarks of Adobe Systems Incorporated in result from the use of these materials. This limitation shall not apply in the United States and/or other countries. cases of intent or gross negligence. Oracle is a registered trademark of Oracle Corporation. The statutory liability for personal injury and defective products is not UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open affected. SAP has no control over the information that you may access Group. through the use of hot links contained in these materials and does not Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, endorse your use of third-party Web pages nor provide any warranty and MultiWin are trademarks or registered trademarks of Citrix Systems, whatsoever relating to third-party Web pages. Inc. SAP “How-to” Guides are intended to simplify the product implement- HTML, XML, XHTML and W3C are trademarks or registered trademarks tation. While specific product features and procedures typically are of W3C®, World Wide Web Consortium, Massachusetts Institute of explained in a practical business context, it is not implied that those Technology. features and procedures are the only approach in solving a specific Java is a registered trademark of Sun Microsystems, Inc. business problem using SAP NetWeaver. Should you wish to receive JavaScript is a registered trademark of Sun Microsystems, Inc., used additional information, clarification or support, please refer to SAP under license for technology invented and implemented by Netscape. Consulting. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Any software coding and/or code lines / strings (“Code”) included in this BusinessObjects Explorer, StreamWork, and other SAP products and documentation are only examples and are not intended to be used in a services mentioned herein as well as their respective logos are productive system environment. The Code is only intended better explain trademarks or registered trademarks of SAP AG in Germany and other and visualize the syntax and phrasing rules of certain coding. SAP does countries. not warrant the correctness and completeness of the Code given herein, Business Objects and the Business Objects logo, BusinessObjects, and SAP shall not be liable for errors or damages caused by the usage of Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other the Code, except if such damages were caused by SAP intentionally or Business Objects products and services mentioned herein as well as their grossly negligent. respective logos are trademarks or registered trademarks of Business Disclaimer Objects Software Ltd. Business Objects is an SAP company. Some components of this product are based on Java™. Any code change Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, in these components may cause unpredictable and severe malfunctions and other Sybase products and services mentioned herein as well as their and is therefore expressively prohibited, as is any decompilation of these respective logos are trademarks or registered trademarks of Sybase, Inc. components. Sybase is an SAP company. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. SL Monitor App.58 Adding HANA Post Steps after DMO.40 DMO SP09 update.31 SPUMG. corrections 1. guide splitted. further additions/corrections 1.30 First external release including DMO and Basis/BW-PCA 1. SP11 Hostagent adaption 1. corrections 1. corrections 1.30 switch upgrade.42 Further Updates.40 SP07 as Target.WNABWH/WDEUMH Workshops 1. Additions for Pre/Post Migration Steps for DMO 1.43 Additions/Updates. split off ASCS.51 Including 7.WDEUMH Workshop 1.40 SP06 as Target. further additions/corrections 1. MSSQL for DMO. further additions/corrections 1.00 First internal release (only SUM run) 1. further additions/corrections 1. Updating ABAP Post Steps .2014 additions/corrections .57 iOS7 App removed.52 Corrections March 2014 .56 06.2014 BW 7.20 enablement.20 Further Improvements SUM/DMO.10 SAPHostAgent 7. further additions/corrections 1.50 BW 7.55 05.Document History Document Version Description 1. updates. SP10 usage. for example.Typographic Conventions Icons Type Style Description Icon Description Example Text Words or characters quoted from the screen. Angle text> brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. . source text. messages. upgrade and database tools. and table titles Example text File and directory names and their paths. Recommendation or Tip Cross-references to other documentation Example text Emphasized words or phrases in body text. Example and menu options. F2 or ENTER. menu paths. EXAMPLE TEXT Keys on the keyboard. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example Variable user entry. names of variables and parameters. and names of installation. graphic titles. Example text User entry texts. menu names. screen Note or Important titles. pushbuttons labels. These Caution include field names. ...............................2 Unicode preparations for the DMO Procedure .................... 13 3...................................... 6 2.............................................4........................ 12 3............1 Prerequisites .........................1 Activate new HANA server functions ..6 BW Phases in the Overall DMO Process ......................................................5....5............3......... for SAP HANA .............................1 Split off ASCS Instance from Existing Server ...................... 71 3....3 BW Upgrade Task List with DMO Procedure ..................... 12 3......................1....................... 10 2........... 11 3................1.......... 70 3...............3....... 27 3........1..........2....................1 Application Specific Preparation Steps..........1..........2.......5 1...... 75 3......................................... 8 2..............................5 DMO Procedure: In-Place Upgrade and Migration..................3. 10 2......................... 44 3................................2 Phase Configuration (2)....2................. 80 October 2014 3 ....... 75 3...2 Install Application Function Library (AFL)........................................................ Step by Step – DMO Option............5.... 9 2..................1 Phase Extraction (1) ...........1 Interaction ASU Toolbox with DMO Procedure ........ 19 3.........................3................................1...2 HANA Specific Post Steps ................................................................................................SAP First Guidance … database migration option (DMO) – BW on HANA Table of Contents 1................ 71 3.......................................................1..........79 3..2 DMO in Interaction with BW-PCA .............. 14 3.5 Post Activities after the main DMO Procedure ......................1......................................76 3....... 75 3.Conceptional Overview ................Comparison Standard and New Process .......................................................... 11 2..............2.............5.............................................................1................. 41 3......... 60 3.........5.........7 DMO ............... 16 3.................................... Database migration option (DMO)....... 64 3.....................53 3.1.................1 Details of the export/import process ........................................................54 3.... 8 2.4 Phase Preprocessing (4) ..........................................3................ 19 3.2 Result from the parallel export/import process...4.5........3 Phase Checks (3)....................3 The DMO Procedure in Detail .......................................3.............................................4 Report UMG_ADD_PREP_STEP.....5 Phase Execution (5) .1 DMO in a Nutshell .............................................................................5........................... 17 3...... DMO ...................................2.......................3 DMO in Interaction with the New SAPHostAgent ................................1.............3 Install the smart data access (SDA) drivers ........2.......................76 3....................3...................... 9 2..................................6 Phase Postprocessing (6) ................................................................................4 Software Update Manager Evaluation ........................3.............5 Mass Maintenance of DBMS User .................... 12 3...........................4 DMO Milestones during the Procedure ..............5......2 Notes for the BW-Specific Upgrade Phases .......6 Transaction RS2HANA_CHECK/ADMIN..4 Configuring DBMS User Man....1................................... ..3.............5.....................6 List of manual Interactions with the DMO procedure .......87 3.5....... 85 3....6 Migrate existing BW Workspaces........... 81 3.................2 Application check ....3........................5 Correct missing views for selected Master Data ......... 89 3.4 Check consistency for all external HANA views .9 Check the updates for SNOTE corrections ............5...SAP First Guidance … database migration option (DMO) – BW on HANA 3..3 Repair inconsistent PSA tables . 85 3...5............RSDU_TABLE_CONSISTENCY 83 3.......3...3....3 BW Specific Post Steps .3.5.5.......8 Convert InfoCubes into in-memory optimized .................. 86 3..... 88 3.....5....3.... 81 3...3....1 Check HANA DB with transaction DBACOCKPIT .......3.5.......7 BW Migration Post Task List with DMO procedure .. 89 3..3...5.................5..... 91 October 2014 4 .. com/sltoolset  Documentation If you not on the current SP level for your source system released in Q1/2014 the following Notes must be reviewed/considered: Note 940679 .com/~sapidb/011000358700000950402013E/ The official SUM/DMO Documentation for SP10.Using DMO of SUM for SAP BW systems The current Version with SUM 1.com/~sapidb/011000358700000950402013E/SUM_SP11_DMO_RTC_13.Number range inconsistency after system setup Note 1983758 .DMO error in Phase MAIN_POSTP/RUN_CUBE_INDEX_ADJUST Note 1656582 .Query terminations .pdf The official SUM/DMO Documentation for SP11.0 SP10 and higher is now generally available! The usage of the DMO procedure including UC migration is now RTC (released to customer). master data in HANA DB Note 1695112 .sap.InfoCubes.SAP First Guidance … database migration option (DMO) – BW on HANA 1. please consult this first! https://service.BW client is incorrectly set in prepare phase of upgrade October 2014 5 .sap. https://service.sap.Activities in BW after migrating to the SAP HANA database Note 1937899 .Database migration option (DMO) for Software Update Manager Note 1799545 . go to the original location of the official DMO/SUM guide: http://service. Database migration option (DMO) Note 1813548 . DSOs. please consult this first! If the URL isn’t working. BAT Username: $[SID:#required#tolower]adm Workdir: D:\usr\sap\$[SID:#required]\SUM\abap ResultConverter: flat  Optional: Enable SSL for the SAPHostAgent (Port 1129). sapgenpse seclogin -p SAPSSLS.Central Note . http://help. D:\usr\sap\N4S\SUM\abap> C:\Program Files\SAP\hostctrl\exe\operations.conf Name:SUMStart Authorization:$[SID:#required#tolower]adm Command:D:\usr\sap\$[SID:#required]\SUM\abap\SUMSTART.sapevents.pse -x <password> -O sapadm 5.SAP First Guidance … database migration option (DMO) – BW on HANA 1. October 2014 6 .Software Update Manager 1.exe -upgrade -archive D:\_install\download\SAPHOSTAGENT176_178-20005735.sap.com/saphelp_nw73ehp1/helpdata/en/f9/50aeeb64604e818b24626d287b63b0/fr ameset. C=DE" 4.d\sumstart. Creation of file C:\Program Files\SAP\hostctrl\exe\operations.dll before upgrade)  run saphostexec. O=<OrgUnit>.d\sumstart.<domain>.0 SP10 [lmt_006] (password 1743651) Note 1926261 . Take the response file *.Central Note .BAT confighostagent Base Dir: D:\usr\sap\N4S\SUM\abap SID: N4S Modified Base Dir: D:\usr\sap\$[SID:#required]\SUM\abap Registering SUM in SAP Host Agent. sapgenpse gen_pse -p SAPSSLS.pse -x <password> -r <server>-csr.p10 and send the certificate signing request to an appropriate CA.0 SP11 [lmt_007] (password 1747235) Note 1981278 .conf in (SAPHOSTAGENT ≥ 189) D:\usr\sap\N4S\SUM\abap>SUMSTART.p10 "CN=<server>.conf Registering SUM in SAP Host Agent finished. %PROGRAMFILES%\SAP\hostctrl\exe> mkdir sec 2..1 Prerequisites Prepare the SAPHostAgent and DMO according to the following Notes: Note 1799545 .exe -install from the extracted SAP Agent 7.htm 1.Conditions for using database migration option of SUM Note 1878193 .20 source directory. add parameter to the file C:\Program Files\SAP\hostctrl\exe\host_profile service/admin_users = <server>\SAPServiceDAS <server>\SAPService<SID>  run this option when you upgrade to an newer Version (at least ≥ 148): C:\Program Files\SAP\hostctrl\exe>saphostexec..<ext>. %PROGRAMFILES%\SAP\hostctrl\exe> set SECUDIR=%PROGRAMFILES%\SAP\hostctrl\exe\sec 3.dll in DIR_CT_RUN is locked (rename sapevents.Software Update Manager 1.Software Update Manager 1.0 SP12 [lmt_008] (password 1750819) You also need to do the following:  Note 1556113 .SAR  Run the command /usr/sap/<SID>/SUM/abap/SUMSTART confighostagent to create the file sumstart.Central Note . October 2014 7 . sapgenpse import_own_cert -c <server>.<ext>:1128/lmsl/upgrade/<SID>/set/procpar http://<hostname>.<domain>.  Restart the SAPHostAgent C:\Program Files\SAP\hostctrl\exe> saphostexec.<domain>.<ext>:1129/lmsl/upgrade/<SID>/doc/gui with DMO 1.<ext>:1129/lmsl/sumabap/<SID>/doc/gui  To reset or check the DMO procedure./SAPup reset prepare delete the directory /usr/sap/<SID>/SUM/ and start from scratch with the SUM sar file unpack.BEGIN CERTIFICATE ----" and "---.and paste it into a text file. Copy the signed certificate from the output area . for example <server>.par like: /clonepar/imp/procenv = HDB_MASSIMPORT=YES /clonepar/indexcreation = after_load /clone/clonedurations = MIGRATION_DT_DUR.<ext>:1128/lmsl/sumabap/<SID>/set/procpar  Additional DMO/SUM options can be maintained in the file SAPup_add.BAT confighostagent again) http://<server>.LST Please refer to the official DMO/SUM guide for details.SAP First Guidance … database migration option (DMO) – BW on HANA 6. [Exit]: 01  To reset the Upgrade/DMO process run (replaces the old ABAP Report upgreset) Note 1790486 .pse -x <password> -v 9.pse -x <password> 8.<domain>./SAPup <option> gt=scroll (httpserver0/allowjump/set allpwd/set procpar) 2) Choose the option “Back” Back Exit Cleanup and start fresh.p7b 7.0 SP11 the URL and the SAPHostAgent Registration changes: (please Note that you have to run SUMSTART. Now you have enabled the SAPHostAgent for HTTPS on Port 1129 (if available)  As Alternative copy the files from D:\usr\sap\<SID>\DVEBMGS<nr>\sec as fallback. sapgenpse get_my_name -p SAPSSLS.including the "---.SAP_ABA is in an undefined state that is not safe to be upgraded cd /usr/sap/<SID>/SUM/abap/bin . use the following step-by-step procedure: o Start SAPup in scroll mode cd /usr/sap/<SID>/SUM/abap/bin .<domain>.<ext>:1128/lmsl/sumabap/<SID>/doc/gui https://<server>.p7b -p SAPSSLS.<ext>:1128/lmsl/upgrade/<SID>/doc/gui https://<server>.  Changing Process Parameters during runtime using UI browser access: http://<hostname>.<domain>.END CERTIFICATE ----" lines .exe -restart  Start the DMO Frontend with the following URL – (HTTP/HTTPS) http://<server>.<domain>. and database migration are combined in one tool  Business downtime is reduced  The source database remains consistent.30 to 7. DMO .com/community/it-management/alm/software-logistics/blog/2014/03/20/dmo-comparing- pipe-and-file-mode-for-r3load October 2014 8 . which means application specific pre/post upgrade steps maintained by the Upgrade task lists and/or the ASU toolbox.com/community/it-management/alm/software-logistics/blog/2014/03/10/dmo-technical- procedure DMO: comparing pipe and file mode for R3load http://scn.sap. it combines SAP upgrade and database migration to SAP HANA in one tool! Benefits:  Migration steps are simplified  System update. so a fast fallback is possible DMO general introduction  http://scn.com/docs/DOC-49580 SUM/DMO technical runtime consideration Depending on the Start and Target Release.sap. DMO technical background http://scn.1 DMO in a Nutshell Scenario:  You want to migrate your existing SAP ABAP system to the SAP HANA database  Your SAP release needs to be upgraded prior to migration Use the database migration option (DMO) of the Software Update Manager (SUM). the release change from 7. which not be seen during the so called “switch upgrade” to 7.Conceptional Overview 2. While the release change from 7.SAP First Guidance … database migration option (DMO) – BW on HANA 2.0x to 7. from a SAP BW application stand point everything is counted as an upgrade.1.sap.40 is a technical upgrade (as type of an exchange upgrade). Unicode Conversion.40 Despite the technical upgrade procedure. the technical procedure for the upgrade part is partly different.40 is and EHP installation/upgrade which includes much more packages and intensive and time consuming additional phases. 3 DMO in Interaction with the New SAPHostAgent October 2014 9 .1.1.2 DMO in Interaction with BW-PCA 2.SAP First Guidance … database migration option (DMO) – BW on HANA 2. 1.5 DMO Procedure: In-Place Upgrade and Migration October 2014 10 .4 DMO Milestones during the Procedure 2.1.SAP First Guidance … database migration option (DMO) – BW on HANA 2. 6 BW Phases in the Overall DMO Process 2.SAP First Guidance … database migration option (DMO) – BW on HANA 2.7 DMO .1.1.Comparison Standard and New Process October 2014 11 . SAP First Guidance … database migration option (DMO) – BW on HANA 3. Step by Step – DMO Option 3.1. Start transaction /ASU/START and opload the XML file and create a new task list. The reminder for the ASU toolbox appears in the extraction phase. download the latest XML file from the attachment section of the SAP Note.1 Interaction ASU Toolbox with DMO Procedure To save time.ASU Toolbox 2008 To use the ASU toolbox. you can already start working with the Application-Specific Upgrade (ASU) toolbox in the original system. Create a new Task List and Jump to Task List 0-ASU000xx October 2014 12 .1 Application Specific Preparation Steps 3. Check for the latest XML file in SAP Note 1000009 . Add.731.Automated Configuration scripts for HANA Landscape (contains HDB script for reorg) Note 1720495 .01 SP14 an higher) Note 1941711 . transport errors Note 1908075 . info about the upgrade to SAP NetWeaver 7.Dump in report RSPRGCTWM during upgrade Note 1983758 .BW objects cannot be processed (upgrade is running) Note 337950 .Dump: INSERT_PROGRAM_NAME_BLANK during After-Import processing of SXCI / SXSD Note 1954122 .Queries (and other objects) cannot be edited October 2014 13 .Error: Retcode 1024: SQL-error "288-cannot use duplicate table name Note 1981718 .you are not able to change objects Note 458024 . 3.Upgrade already running .3 EHP1 Note 912369 .R3load: support for CDS views and some fixes Note 1994569 .Pre-upgrade measures for upgrade/update to 7. This will save time during the runtime of the DMO procedure.Invalid deimplementation of obsolete notes by SNOTE tool Note 1668882 . after import failures.740 (check after the Upgrade) Note 1867494 .Upgrading application server ABAP running on an SAP HANA DB Note 1879618 .1.SAP First Guidance … database migration option (DMO) – BW on HANA Check and execute the tasks before the technical DMO procedure starts.BW client is incorrectly set in prepare phase of upgrade Note 1990326 .BW on SAP HANA SP6: Landscape redistribution (at least Rev. Note 851449 .FINB_TR_DEST.Note Assistant: Important notes for SAP_BASIS 730. Note 1609441 .Error during conversion of pooled table or cluster table (if you start release is 7.4 (included in 7.Changeability of BW objects during the upgrade Note 780710 .40 SP07) These Notes are still valid for the changeability of BW objects during upgrade. ≥ 60 for HANA needed) Note 1891393 .2 Notes for the BW-Specific Upgrade Phases These Notes must/should be checked before the DMO process for BW based systems is started. 3 BW Upgrade Task List with DMO Procedure Together with the BW Housekeeping Task List which is described in detail in the Document - http://scn.1. This is due to the enablement of this new Task List as part of the BW Housekeeping Tasks Lists. Execute the Task List in advance. Implement the following SAP Note to enable usage of task list SAP_BW_BEFORE_UPGRADE via transaction STC01.com/docs/DOC-46433. October 2014 14 . Note 1734333 .sap. and NO automated steps applied with SNOTE) You might now find overlapping tasks in the ASU toolbox and in the SAP_BW_BEFORE_UPGRADE Task List.BW Pre and Post Upgrade and Migration Tasks (contains manual report ZNOTE_1734333_PRE_70x/ZNOTE_1734333_PRE_73x. this will save time during the runtime of the DMO procedure. and allows you to use one Interface for all necessary upgrade pre and post steps. there are also additional Task Lists available to simplify preparation of the application-specific part.SAP First Guidance … database migration option (DMO) – BW on HANA 3. In advance check with Transaction SU01 the correct password.DTP: Error msg RSO851 during upgrade or Content installation Note 1701115 . After this use the Transaction FINB_TR_DEST to create RFC Destinations for Transport Methods. Transaction SPRO  F5  Business Intelligence  Transport Settings  Create Destination for … Furthermore make sure that the password you choose here is the correct one.Error in phase XPRA_* during support packs update: Job RDDEXECL fails with SYNTAX_ERROR Note 1801400 . At the end of the DMO procedure the program RS_UPG_TOOL_HMW is also using this destination.SAP HANA adj. In order to enable the usage of the tasks lists during the SUM/DMO procedure you have to setup in transaction RSTPRFC the RFC destinations for the BW clients for import post processing. for BW Workspaces: Inactive CompositeProviders Note 1861585 .Time-critical processes in BW upgrade/Support Package import Note 1668456 .Upgrade terminates with error RS0 871 or RS0 876 Note 1975065 . This will prevent additional errors in the Phase MAIN_NEWBAS/XPRAS_AIMMRG.Error in XPRAS_AIMMRG phase during EHP installation for BADI Multiple active implementations Note 1894463 .DMO Abbruch in der Phase MAIN_POSTP/RUN_CUBE_INDEX_ADJUST To create the user for BW backend processing use transaction RSBWREMOTE to create the user bwremote.Error FINB_TR 032 during upgrade in phase XPRAS_AIMMRG Note 1813468 .SAP First Guidance … database migration option (DMO) – BW on HANA Additional Notes to apply: Note 1845061 . The password of BWREMOTE must be correct.Web Dynpro: Conversion for non-printable chars (NON-UNICODE) Note 1835882 .Background user has no authorization for scheduling Note 1860274 . Additional Notes for optimizing the phase MAIN_NEWBAS/XPRAS_AIMMRG: Note 1649901 .Termination in XRPA RS_TCO_ACTIVATION_XPRA in non-SAP-BW systems October 2014 15 .RSUMOD20/func sumo_is_adjust: handling for cluster table Note 1940679 . It performs additional checks and makes repairs that help to ensure consistency prior to the Upgrade.4 Report UMG_ADD_PREP_STEP This additional report was originally used with UC migrations (which also is valid for the DMO process). Report RSSPAM_PREPARE_UC is started by preparation report UMG_ADD_PREP_STEP and its only action is to delete the contents of table OCSCMPLOBJ. October 2014 16 .1.SAP First Guidance … database migration option (DMO) – BW on HANA 3. that existing data must be prepared for the conversion while the new data which comes with the upgrade process must be merged within the DMO process to enable the UC conversion during the parallel export and import phase with R3load.0X Note 1457258 .3x Note 1051576 .40 and 7. The Reason for this is the fact.SAP First Guidance … database migration option (DMO) – BW on HANA 3.3x must run the Transaction SPUMG first to prepare the existing data for the unicode conversion.20.20 and onwards. In all other Systems based on NetWeaver BW 7.0x and 7. For these Systems the complete and successful preparation with SPUMG is a mandatory step.0x and BW 7.Conversion of Single Code Page Systems to Unicode check for corrections of SPUMG and additional preparation steps Note 662215 . 6. The Transaction SPUMG is a complete set of preparation modules which can run independently from the other preparation steps.SPUMG and SUMG in Basis Release 6.Unicode Collection Note In addition check with Transaction I18N the RSCPINST settings October 2014 17 . The following Note contains the detailed Guide for the usage of SPUMG for every NetWeaver Release based on 7. NetWeaver BW contains only on Code page and also almost of the ABAP coding (might include customer coding) is already UC enabled since NetWeaver Release 6.2 Unicode preparations for the DMO Procedure If your Source System based on NetWeaver BW is already on unicode (UC) you can skip this Chapter.Correction instruction for the Additional Preparation Steps Note 1319517 . RADCUCNT in Unicode Conversion: Collective Note Note 932779 .SAP First Guidance … database migration option (DMO) – BW on HANA Starting Transaction SPUMG the first time (follow the first steps) SPUMG after running the pre checks Additional troubleshooting Notes Note 837173 .analysis of nametab problems October 2014 18 .Unicode conversion . can be found for the following phases. specify the correct stack. support packages. you must specify this in the Instance Parameter DIR_PUT and restart the server.3 The DMO Procedure in Detail 3. The stack.xml file. Please note: the following directories are selected by default.xml is resided including all additional needed files during the SUM/DMO process.SAR Start the SUM/DMO UI with the following URL: http://<server>. Unpack the SUM 1.SUM root directory: \\sapmnt\<SID>\SUM . . etc.1 Phase Extraction (1) After you start the Software Update Manager (SUM). The Download Directory is the location where the stack. Otherwise the Parameter will be set automatically.xxx.xml /usr/sap/CIH/download/SMSDXML_CIH_20140416094540. On Win64 based systems remain to the default download directory to avoid ACL errors in the phase EHP_INCLUSION.0 SP10 or higher file as follows: /usr/sap/<SID>/SAPCAR -xvf SUM10SP10_0-20006676. where all necessary files.xml you define the download directory.795.Download directory: \\sapmnt\<SID>\download If you want to use a different location for the SUM directory.<ext>:1128/lmsl/upgrade/<SID>/doc/gui Phase: 1 0. updates.3. October 2014 19 .xml cannot be loaded from a local destination.SAP First Guidance … database migration option (DMO) – BW on HANA 3.<domain>.xml (path valid also for Win64) By selecting the stack.0% select STACK CONFIGURATION FILE Location of the stack.xml file: /usr/sap/<SID>/download/SMSDXML_<SID>_<date><time>. If you already have executed several SUM/DMO runs you can place the existing UPGANA. especially the comparison between long and short runtimes Phases (e. TABIM_UPG vs.4% PREP_PRE_CHECKPROFREAD For a better overview you can always open the “CURRENT PHASELIST” on the right side of the UI. October 2014 20 . This allows the DMO process to calculate the different Phases more precisely.g. xyz) So you will see different timings on the following screenshot’s due to updates between SP08-10 and more accurate runtimes of the specific phases.SAP First Guidance … database migration option (DMO) – BW on HANA In addition provide any updated files here as well. In this phase the download directory must be already available.g. as all needed files are extracted to /usr/sap/trans/EPS/in Phase: 2 0. Kernel.xml. ST-A/PI. which are not collected by the stack. SAPCryptoLib. etc. e.xml files into the download directory as well. 7% PREP_PRE_CHECK/SPAMCHK_INI In case you didn’t applied the latest SAPM update. that the MOPz process only selects only the delta files after the availability of the NetWeaver 7.2% PREP_INPUT/READDATA_EXP If there is NetWeaver 7.40 SR1 export DVD must be available in the download location. Please Note.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 3 0. yet you will be asking to install the latest Version for your NetWeaver Release. October 2014 21 . The created stack. the NetWeaver 7. Current Version is 0053.xml file will recognize this correctly.30 as Start for the DMO procedure. Phase: 4 1.40 SR1. SAR packages to the directory. if your source kernel is higher than in the scan directory. The SUM/DMO process will always recognize the latest file and also. if you are running on a single HANA node. October 2014 22 . You can also copy newer *.6% PREP_INPUT/SCANDIR_EXTRACT In this phase the download directory is checked for the Kernel archives.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 5 1. Note 1134948 .LOG to make sure your database is supported for the DMO procedure.ABAP Migration Key for special installation numbers Migration key 1G5fdEM50DwSq3egt6h]pGhK for instance number SAP-INTERN lasts until 2014/12/31 Leave the Option Execute Landscape Reorg unticked.9% PREP_INPUT/MIG2NDDB_INI Check the log MIG2NDDB_INI. Phase: 6 1. otherwise allow DMO to prepare the Landscape reorg. LOG can be checked by clicking the Star on the left side of the UI. October 2014 23 .log appears as a red flag. when you have the following Pop-Up due to inactivity of the screen. An error in the file CHECKS. setting break points or additional settings can be accessed by clicking on UTILITIES. This is also suitable.SAP First Guidance … database migration option (DMO) – BW on HANA The CHECKS. By pressing refresh in the Browser the overlaying CHECKS window will disappear and you are back in the COCKPIT monitor. Log Files. log constantly updated). automatically you will see the overall rumtime estimate of the DMO procedure (file SAPupStat. INFO: The upgrade strategy for the addon FSAPPL is described in note 983007. October 2014 24 . INFO: The upgrade strategy for the addon FSPOT is described in note 632429.SAP First Guidance … database migration option (DMO) – BW on HANA Setting explicit Breakpoints can be optimized by clicking into the column header and use the search. INFO: The upgrade strategy for the addon BI_CONT_XT is described in note 632429. INFO: The upgrade strategy for the addon FSCM_CCD is described in note 632429. INFO: The upgrade strategy for the addon CTS_PLUG is described in note 632429. INFO: The upgrade strategy for the addon FINBASIS is described in note 438520. INFO: The upgrade strategy for the addon DMIS is described in note 1231203. By hoover the Mouse Pointer over the Phase Bar. PREP_INIT/ADDON_INFO TEXT INFO: The upgrade strategy for the addon BI_CONT is described in note 1000822. INFO: The upgrade strategy for the addon CPMBPC is described in note 1142913. INFO: The upgrade strategy for the addon SAP_ABA is described in note 632429. October 2014 25 . INFO: The upgrade strategy for the addon SAP_GWFND is described in note 632429. INFO: The upgrade strategy for the addon SAP_UI is described in note 632429. INFO: The upgrade strategy for the addon MDG_FND is described in note 632429. INFO: The upgrade strategy for the addon PCAI_ENT is described in note 632429. INFO: The upgrade strategy for the addon SAP_BS_FND is described in note 632429. INFO: The upgrade strategy for the addon ST-PI is described in note 539977. INFO: The upgrade strategy for the addon PI_BASIS is described in note 555060. INFO: The upgrade strategy for the addon SEM-BW is described in note 186299. INFO: The upgrade strategy for the addon POASBC is described in note 1511393. INFO: The upgrade strategy for the addon SAP_BW is described in note 632429. INFO: The upgrade strategy for the addon SAP_BASIS is described in note 632429. INFO: The upgrade strategy for the addon ST-A/PI is described in note 69455. INFO: The upgrade strategy for the addon WEBCUIF is described in note 632429.SAP First Guidance … database migration option (DMO) – BW on HANA INFO: The upgrade strategy for the addon HANABPC is described in note 632429. 1714734. 1860274.END (1) October 2014 26 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 7 7. 1689526. 1667685. 1910464 Phase: 8 7. 1388287.1% PREP_PARSEETUP/CHECK4NOTES_TOOL 1142427.1% PREP_CONFIGURATION/INITSUBST . tool configuration It is now possible to reallocate the ABAP CI to the HANA appliance. This allows you to increase dramatically the performance overall due to massive parallelization.2 Phase Configuration (2) Phase: 9 6.SAP First Guidance … database migration option (DMO) – BW on HANA 3.9% PREP_CONFIGURATION/INITSUBST .3. October 2014 27 . Please Note that the Parameters have a massive influence of the time consuming phase during the SUM/DMO procedure. So the Advanced/Standard strategy is the right choice. the “Downtime-minimized” strategy is not from concern here. As with a BW upgrade the “downtime” is not really relevant. However the selected option (Advanced and Switch expert mode on) is the most effective way to get the maximum on the available resources for the Upgrade/DMO process.6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG October 2014 28 . You may want to change the suggested value for the used SGEN processes. So the seen values might not fit to your environment (increase them accordantly).SAP First Guidance … database migration option (DMO) – BW on HANA Even if you try to change the settings in the next screen. it will go back to these settings. Phase: 10 7. 02.SAP First Guidance … database migration option (DMO) – BW on HANA SAP HANA 1.0 ODBC Client \\<server>.ABAP Migration Key for special installation numbers Phase: 11 7.<ext>\sapmnt\<SID>\download\SAP_HANA_CLIENT d:\usr\sap\CIH\download\SAP_HANA_CLIENT Get a migration key for anyDB to HDB .6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG See the Details to examine the correct license (7.40 .<domain>.<domain>.txt d:\usr\sap\CIH\download\CIH_Standard_17.2015.txt SAP HANA 1.BW on HANA) on the target system and the details for the used HANA appliance Phase: 12 License Key Request (Internal View) October 2014 29 .<ext>\sapmnt\<SID>\download\<SID>_multiple.31 or 7.0 License \\<server>.see internal Note (SAP Employees) Note 1134948 . Lifecycle Management Phase: 14 SAP HANA Studio .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 13 SAP HANA Studio .HDB Connection Phase: 15 7. October 2014 30 . you will not see this input window anymore.7% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/INSTHDBCLI If the HANA client is already installed (at the correct place) or already available and accessible in the Download folder. Installation of current SAP HANA client with SWPM Unpack the archive.SAR Generate the file LABEL. In addition see Note 1943235. for example to /tmp SAPCAR -R /tmp -xvf IMDB_CLIENT100_72-10009664.ASC The DMO procedure looks for the correct LABEL.ASC file in the Directory.SAP First Guidance … database migration option (DMO) – BW on HANA Note 1825053 . echo HDB_CLIENT:10xxx:RDBMS:*:*:* > /tmp/SAP_HANA_CLIENT/LABEL.7% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/HDB_PREPARE October 2014 31 . Phase: 16 SAP HANA Client Installation Phase: 17 7.ASC in the directory SAP_HANA_CLIENT. The language files will also be extracted by default to the DVD 51047454. October 2014 32 . the language DVD must also be present in the download directory.BW client is incorrectly set in prepare phase of upgrade Phase: 19 8. To avoid this screen. Note 1983758 . You can deinstall additional languages in this phase. but not the default languages which are DE and EN.4% PREP_CONFIGURATION/LANG_SELECT If you have additional languages installed in your system.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 18 7.8% PREP_CONFIGURATIONS/SUBMOD_MIG_CONFIG/DETBWMODE This input window is not seen on a correctly installed and configured NetWeaver BW system. check for correct settings in the table RSADMINA for an active client.0% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/MIG2NDDB_AUX_PRE Phase: 20 8. Furthermore check the RFC destination <SID>CLNT<client> for correctness. 4% PREP_CONFIGURATION/LANG_SELECT If you run the DMO process on a system based on copy. October 2014 33 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 21 8. make sure you applied a valid license. otherwise an error will occur in this phase. 2 % PREP_EXTENSION/IS_INST Phase: 24 11.7 % PREP_EXTENSION/UPLOAD_REQUEST Phase: 23 10. On Win64 based system make sure.0% PREP_EXTENSION/EHP_INCLUSION Depending on the amount of available files in the download directory this can be a time consuming phase. October 2014 34 .<ext>\sapmnt\<SID>\SUM is read/write accessible from the <sid>adm and SAPService<SID> to prevent errors and switch off the virus scanner during this phase. that the directory \\<server>.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 22 9.<domain>. 7% PREP_EXTENSIONS/IS_SELECT .Upgrade behavior of Addon ST-A/PI Furthermore also the current SAPCryptoLib package SAPCRYPTOLIBP_8xxx-200xxxxx.xml is provided) manually.2 Please Note that the MOPZ process is not reflecting the existence of the ST-A/PI Add-On when the stack.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 25 11.xml is created. you should deinstall this Add-On to avoid follow up errors.SAR must be added to the download directory (where the stack. October 2014 35 .SAR (Installation instead of Exchange-Upgrade) Note 1083365 .4% PREP_EXTENSIONS/IS_SELECT Phase: 26 11. D:\usr\sap\<SID>\download\KITAB9J. As the PCAI_ENT Add-On (BW-PCA “License”) also has a deinstallation option. Copy the necessary file to the download directory. 3 Phase: 28 11.Upgrade to DMIS_CNT 2011_1 in the system switch upgrade Password (SUM/DMO): 6855059 Note 1807738 . October 2014 36 .Upgrade behavior of Addon ST-A/PI Password Vendor Key KEEP (SUM/DMO): 2902571 Note 1678780 . 5156796 Note 1577503 .Business function / set DATA_PROVIDER_DUN_BRADSTREET This Note becomes obsolete.47 is included in the DMO process.Installation/Upgrade for the ABAP Add-On BI_CONT / BI_CONT_XT 757 Password (SUM/DMO): 3821837.6% PREP_EXTENSIONS/IS_SELECT .Upgrade to DMIS 2011_1 in the system switch upgrade Password (SUM/DMO): 4690407 Note 1577504 .Installation or upgrade of BI_CONT/BI_CONT_XT 7x7 Password (SUM/DMO): 3668936 Note 1943931 . as SP04 for BC 7.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 27 11.8% PREP_EXTENSION/ADDONKEY_CHECK Note 1083365 . Phase: 30 12.SPAM update October 2014 37 .0% PREP_EXTENSIONS/BIND_PATCH .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 29 11.g. ST-PI 2008_1_700/710 you should take over the calculated level.9% PREP_EXTENSIONS/BIND_PATCH In case of additional Support Packages. This will include the additional updates. e. October 2014 38 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 31 12.Note 1788379 .2% PREP_EXTENSIONS/BIND_PATCH . instead of having this interaction screen. See more details here .8% PREP_EXTENSIONS/CONFLICT_CHECK .0% PREP_EXTENSIONS/ADDON_LANGINC . This table is used by the Support Package Manager and by the Add-On Installation Tool to save formatted object lists for add-on conflict verification during the import of Support Packages. the Report RSSPAM_PREPARE_UC is started by preparation report UMG_ADD_PREP_STEP and its only action is to delete the contents of table OCSCMPLOBJ.DMIS Add-On decision Phase: 33 12. Since the contents of the table depend on the type of character encoding used (UNICODE. the contents must be deleted prior to a UNICODE conversion.Note 889596 If errors occur. non-UNICODE).Transport of SAP NOTES Phase: 32 12.include change request The Report SCWN_TRANSPORT_NOTES allows you to add SAP Notes as transports. SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 34 13.1% PREP_INTERACTION/ADJUSTTPRP If you prepare the file \\server\sapmnt\trans\bin\umodauto.lst then you have to provide the entries in the following format before you enter the phase. SPDD/SPAU 740 trcorr, for example SPAU 740 CIHK900031 If the transport was created for a different SP, you have to tick the option box in addition. Phase: 35 14.2% PREP_INSTALL/INITSHD - advanced option Phase: 36 14.3% PREP_INSTALL/SHD INST_CPY October 2014 39 SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 37 15.9% PREP_INSTALL/JOB_FILL_TPF_CHK_PHASES - END (2) October 2014 40 SAP First Guidance … database migration option (DMO) – BW on HANA 3.3.3 Phase Checks (3) Phase: 38 18.5% PREP_GENCHECKS/JOB_TS_UGR41 - report RSUGRCHECK Phase: 39 20.5% PREP_PREPROC/SAVE_VAR_CHK - save variants Furthermore in this Phase and in the next Phases additional cleaning Tasks are running, which are part of the pre migration task list - SAP_BW_BEFORE_MIGRATION Phase: 40 20.7% PREP_PREPPROC/SUBMOD_MIG_BI_TASKS_PREP/MIG2NDDB_HANA_BW_PARAMS October 2014 41 Later in the process the correct entry TPBWMANDTRFC to logon on will be used as well.SAP First Guidance … database migration option (DMO) – BW on HANA Check that the table RSADMINA (transaction SE16) the entry BEX REQUEST is removed. Phase: 41 Edit table RSADMINA .select BEX REQUEST to delete October 2014 42 . 4% MAIN_INIT/BEGIN .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 42 21.END (3) October 2014 43 .3% PREP_PREPPROC/REQ_ASU_RUN .start ASU toolbox Transaction /ASU/UPGRADE (Note 1000009) Phase: 43 Transaction /ASU/UPGRADE Phase: 44 21. check open transports Phase: 46 24.3. from now on you cannot maintain any BW objects anymore. October 2014 44 .lock development environment Despite what Information you might have from other sources.5% MAIN_INIT/REPACHK1 .SAP First Guidance … database migration option (DMO) – BW on HANA 3.4 Phase Preprocessing (4) Phase: 45 22.0% MAIN_INIT/LOCKEU_PRE . long running phase Phase: 48 37.4% MAIN_SHDCRE/SHADOW_IMPORT_UPG1 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 47 27.4% MAIN_SHDRUN/SUBMOD_DIFFEXP/ADJUSTCHK_UPG Phase: 49 39.9% MAIN_SHDRUN/ACT_UPG .8% MAIN_SHDRUN/DDIC_UPG .long and intensive runtime phase Phase: 50 40.use DDIC/000/SHD October 2014 45 . continue with procedure Phase: 52 41.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 51 40.long and intensive runtime phase October 2014 46 .0% MAIN_SHDRUN/ACT_UPG .adjustments made.9% MAIN_SHDRUN/ACT_UPG . Phase: 54 42. to avoid additional errors here.3% MAIN_SHDRUN/PARDIST_UPG Phase: 56 48.3% MAIN_SHDRUN/RUN_INDC_UPG Phase: 55 42.0% MAIN_SHDRUN/ACT_UPG .accept non-severe errors and repeat phase ACTUP.ELG Repair of InfoObjects was not performed.1% MAIN_SHDIMP/PARMVNT_SHD Phase: 58 51. (DDIC is not allowed to activate customer objects.1% MAIN_SHDIMP/SUBMOD_CP2SHD/TP_ACTION_CP2STAB October 2014 47 .5% MAIN_SHDIMP/NTACT_PREMV Phase: 57 49.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 53 41.0% MAIN_SHDIMP/SUBMOD_CP2SHD/SUBMOD_DIFFCP2SHD/DIFFEXPABAP_CIGPR Phase: 59 51. create code or activate BEx standard transports) In the Preparation phase the repair of InfoObjects must run. 4% MAIN_SHDIMP/SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE October 2014 48 .7% MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_UPG2 .long runtime phase Phase: 62 52.4% MAIN_SHDIMP/SUBMOD_SHD2_RUN/TABIM_POST_SHD Phase: 65 54.8% MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC .0% MAIN_SHDIMP/SUBMODE_SHDIMP/TABIM_REDUCE Phase: 63 52.5% MAIN_SHDIMP/SUBMOD_SHD2_RUN/NTACT_ALTNT Phase: 64 53.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 60 51.language import Phase: 61 51. 5% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_UT .0% MAIN_SHDIMP/SUBMOD_MIG_UPTIME_PRP/RUN_SMIGR_CREATE_DDL October 2014 49 .intensive Phase (CPU) Phase: 67 58.3% MAIN_SHDIMP/SUBMODE_SHD2_RUN/RUN_RSGEN .1% MAIN_SHDIMP/SUBMOD_FATESTS/RUN_RSDB02CK_MOD Phase: 68 59.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 66 56.start uptime migration Phase: 69 62. 0% MAIN_SHDIMP/SUBMOD_MIG_BI_TASKS_PREDTT/RUN_WORKSPACE_BACKUP_CREATE To avoid errors in this phase make sure that you have a working connection to a BWA server. as the backup program check the existence. you can use the following option for it. Report RSL_WSP_CALL_PROGRAMS October 2014 50 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 70 63. If there are BW Workspaces which either not used anymore or can be deleted for various reasons. 387329 SQLDBC 1.c#7 $ SAP D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.02.02.h): (0.00.LST opened (SQL) INFO: Searching for SQL file APPL0.69.EXE: START OF LOG: 20140127135355 D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.h): (0.SQL (SQL) INFO: APPL0. (Enviromnent Variable HDB_MASSIMPORT=YES).69.EXE -decluster -i D:\usr\sap\N4S\SUM\abap\migrate_ut\MIGRATE_UT_00045_IMP.1" (GSI) INFO: version = "7601 Service Pack 1" (GSI) INFO: machine = "4x AMD64 Level 15 (Mod 65 Step 3)" (RTF) ########## WARNING ########### Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases (IMP) INFO: import of E071~ completed (2830673 rows) #20140127135451 (DB) INFO: E071~ merged #20140127135455 (SQL) INFO: Searching for SQL file SQLFiles.LST (SQL) INFO: SQLFiles.017) R3load conversion of REPOTEXT (note 1925533) DBSL patchinfo (patches.EXE: version R7.EXE: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.017) Datatype NCLOB missing in tablesize calculation (note 1952609) --------------------.SQL opened October 2014 51 .SQL (SQL) INFO: found APPL0.LST (SQL) INFO: found SQLFiles.LST (SQL) INFO: Trying to open SQLFiles.8 [UNICODE] Compiled Jan 19 2014 18:14:03 D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.LOG (Example Import Log from MSS to HDB) D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.Start of patch information ------------------------ patchinfo (patches. (DB) INFO SUPPORT: support infos for R3load on NewDB is in internal Note 1651927 (GSI) INFO: dbname = "N4S/04 " (GSI) INFO: vname = "HDB " (GSI) INFO: hostname = "lt5007 " (GSI) INFO: sysname = "Windows NT" (GSI) INFO: nodename = "IWDF4366" (GSI) INFO: release = "6. (DB) INFO: NewDB Kernel version 1.LOG -loadprocedure fast -table_suffix ~ -k 1G5fdEM50DwSq3egt6h]pGhK -------------------.SAP First Guidance … database migration option (DMO) – BW on HANA Transaction RSWSP (RSWSPW) MIGRATE_UT_00045_IMP.41/V1.00.SQL (SQL) INFO: Trying to open APPL0.CMD -dbcodepage 4103 -l D:\usr\sap\N4S\SUM\abap\migrate_ut\MIGRATE_UT_00045_IMP.End of patch information ------------------------- process id 23108 (DB) INFO: connected to DB (DB) INFO: Loading Data with mass import for lobs.0387329 (DB) INFO SUPPORT: mass import for table with lobs should be active. SAP First Guidance … database migration option (DMO) – BW on HANA (DB) INFO: E071^HW5 created #20140127135456 (DB) INFO: E071~ unloaded #20140127135456 (IMP) INFO: import of WVOBJTYPES_SCOPE completed (27 rows) #20140127135456 (DB) INFO: WVOBJTYPES_SCOPE merged #20140127135456 (DB) INFO: WVOBJTYPES_SCOPE unloaded #20140127135456 (IMP) INFO: import of SEOSUBCO completed (1391041 rows) #20140127135516 (DB) INFO: SEOSUBCO merged #20140127135520 (DB) INFO: SEOSUBCO unloaded #20140127135520 <<< >>> (IMP) INFO: import of VBCD_VO completed (13 rows) #20140127135740 (DB) INFO: VBCD_VO merged #20140127135740 (DB) INFO: VBCD_VO unloaded #20140127135740 (DB) INFO: disconnected from DB D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.EXE: job completed D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.EXE: END OF LOG: 20140127135741 October 2014 52 . LST You can specify this file within SAPup_add. it is not possible with a Breakpoint to stop between this phases.SAP First Guidance … database migration option (DMO) – BW on HANA 3. This will restart the migration process from the beginning.4.0 SP10 onwards dynamically change the main load parameters during the phase for optimization. To completely initialize the uptime/downtime migration process you have to remove all the mentioned directories. There is a new file created during the DMO run called MIGRATION_DT_DUR.LST Both files are located in the /usr/sap/<SID>/SUM/abap/bin directory and allow to keep you own settings in separate files while you can exchange the existing files by a newer SAR file of the same SUM Support Package. October 2014 53 . The command SAPup set procpar gt=scroll allows you from SUM 1.3.1 Details of the export/import process During the main phases for the uptime and downtime migration there are several directories created which you can link to the following phases: EU_CLONE_UP_PRP  creates the directory migrate_ut_create “R3ldctl” phase EU_CLONE_UP_RUN  creates the directory migrate_ut “R3load” phase EU_CLONE_DT_PRP  creates the directory migrate_dt_create “R3ldctl” phase EU_CLONE_DT_RUN  creates the directory migrate_dt “R3load” phase migrate_dt_cp2shd migrate_dt_repair If you want to optimize the different phases.par as follows: /clone/clonedurations = MIGRATION_DT_DUR. LOG October 2014 54 .LOG EUMIGRATEDTRUN.3.2 Result from the parallel export/import process EUMIGRATEUTRUN.4.SAP First Guidance … database migration option (DMO) – BW on HANA 3. SAP First Guidance … database migration option (DMO) – BW on HANA Size of MSS DB before Export (two examples . of tables: 1575 | | ABAP Size Column Store: 5.4 GB. No. of tables: 31960 ============================================================== HANA DB size 20.3 GB.transaction DBACOCKPIT) Result from Report /SDF/HANA_BW_SIZING SUMMARY |======= | | ABAP Size Row Store: 14. 33725 October 2014 55 .9 GB. No. So you have to repartition the objects accordantly beforehand.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 71 62. Furthermore there are the following Repair Reports available: Report DDIF_OBJECT_DELETE to clean database entries and nametab Report RSDU_REPART_UI to check inconsistencies with shadow indexes October 2014 56 .4% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_DT_CREATE In this Case check the existence of any additional inconsistencies with shadow indexes which were left from unsuccessful BW Table Repartitioning Note 1741015 .Repartitioning of BW tables (contains Report RSDU_REPART_UI) Please Note that currently DSO objects with a partition number higher than 1000 are not supported by HANA. SAP First Guidance … database migration option (DMO) – BW on HANA Optional: if you encounter any import problems which are not critical.BW on HANA SP6: Landscape Redistribution Note 1908073 . so please inform yourself about the correct procedure.sap. at least HANA 1. Note 1815547 . the quickest approach is to use the guidance from the following note: Note 885441 . 68 or higher is needed. For a correct Landscape Reorg.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape- redistribution-with-sp6 October 2014 57 .Automated Configuration scripts for HANA Landscape (contains HDB script for reorg) For more details see also the following Blog: http://scn.Common Migration Errors Phase: 72 62.0 Rev.Row/ColumnStore check without rowstorelist.SMIGR: Rowstore Tables Without file access needed Note 1908075 .8% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/REQ_LANDSCAPE_REORG This Phase is very important.BW on HANA Scale Out: Tabellenverteilung / -partitionierung Note 1891393 .txt Note 1883487 . backup request October 2014 58 .preparations for downtime Phase: 74 66.0% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK .0% MAIN_DTTRANS/DOWNCONF_DTTRANS .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 73 65. 0% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK .disable archive mode Phase: 76 66.END (4) October 2014 59 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 75 66.1% MAIN_DTTRANS/SETSYNC_PREUP_DT_CONFIRM . Now you can reconnect to the URL. delete/kill the SAPup/SAPuptool processes and restart the SAP Host Agent.8% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/EU_CLONE_MIG_DT_RUN Optional: if you encounter any import problems which are not critical.5 Phase Execution (5) In case the message of the UI shows “the tool is not running”.3. Phase: 77 67.Common Migration Errors These Recommendations doesn’t fit to the DMO procedure rather than to the heterogeneous system copy. If you encounter critical or invalid tables you can do the following workaround: October 2014 60 .SAP First Guidance … database migration option (DMO) – BW on HANA 3. the quickest approach is to use the guidance from the following note: Note 885441 . tmp will not work. rename to sapvents_old.dll before upgrade) Rename to sapevents.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 78 68.dll.dll With SUM 1.0 SP10 the error should not occur anymore. October 2014 61 . Phase: 79 72.5% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/SUBMOD_SWITCH_KERNEL/KX_SWITCH Note 1556113 .dll in DIR_CT_RUN is locked (rename sapevents.0% MAIN_SWITCH/PARMVNT_XCNV In case of duplicated Indexes/Tables use the SAP HANA Studio and remove the affected objects in the SAP<SID> Schema.sapevents. Time-critical processes in BW upgrade/Support Package import PSEUDO_D_AFTER_IMPORT_D = ' ' REPL_D_AFTER_IMPORT_D = X Note 1543092 .long runtime phase 4 Settings in table RSADMIN to optimize runtime in Phase XPRAS_AIMMRG: Note 1629923 .Upgrade of BP_BIADMIN 1. Make sure the parameter mentioned above is removed from table RSADMIN before executing the XPRA.SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 80 79.1% MAIN_NEWBAS/TABIM_UPG . Phase: 81 81.Skip BW technical content objects activation during upgrade SKIP_TCO_ACTIVATION_XPRA = X You can run the XPRA RS_TCO_ACTIVATION_XPRA after the technical upgrade has finished.RSADMIN table parameter October 2014 62 .0 to BP_BIADMIN 3.1% MAIN_NEWBAS/XPRAS_AIMMRG . Note 1649901 .0(BP BW ADMINISTRATION) Run the transaction RSTCT_INST_BIAC when the upgrade has finished. SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 82 89.5% MAIN_UPTRANS/MAIN_POSTP .9% MAIN_UPTRANS/UPCONF .9% MAIN_UPTRANS/STARTSAP_PUPG .end of downtime Phase: 84 90.END (5) October 2014 63 .2nd backup request Phase: 83 89. 6 Phase Postprocessing (6) Phase: 85 91.7% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_PSA_VERSION_CREATE Phase: 87 91.SAP First Guidance … database migration option (DMO) – BW on HANA 3.8% MAIN_POSTP/SETUPGPAR_UPG_POST Phase: 86 91.7% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE October 2014 64 .0.3. 1% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_TIMESTAMP_RESET October 2014 65 .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 88 92. 4% MAIN_POSTP/RUN_CUBE_INDEX_ADJUST Phase: 90 97.2% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP2_REQRSRDA .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 89 92.restart RDA daemons October 2014 66 . 2% MAIN_POSTP/SPAUINFO October 2014 67 .SAP First Guidance … database migration option (DMO) – BW on HANA Command to analyze the R3load runtimes after the migration: D:\usr\sap\<SID>\SUM\abap\bin\SAPup.LOG Command to analyze the R3load runtimes constantly as graphic: D:\usr\sap\<SID>\SUM\abap\bin\SAPup.exe r3load logstat D:\usr\sap\<SID>\SUM\abap\log\migrate_dt\*.exe r3load logstat D:\usr\sap\<SID>\SUM\abap\log\MIGRATE_DT_RUN.log Phase: 91 98. Phase: 92 98.repair with RSDU_TABLE_CONSISTENCY October 2014 68 .7% MAIN_POSTP/RUN_RSDB02CHK_END . If you have registered a SPAU transport. Such a transport is needed to perform automatic adjustments in subsequent SAP systems. it will be exported when choosing "Continue" below. In that case. exit the program now and continue after SPAU has been finished. All SPAU activities can be performed without object registration key (SSCR) for a period of 14 days after you first entered this phase.SAP First Guidance … database migration option (DMO) – BW on HANA You can call transactions SPAU and SPAU_ENH and check for any open adjustments. END (6) October 2014 69 .9% MAIN_POSTP/SAVELOGS Phase: 94 100% YOUR UPGRADE IS COMPLETE .SAP First Guidance … database migration option (DMO) – BW on HANA Phase: 93 99. SAP First Guidance … database migration option (DMO) – BW on HANA 3.<domain>.html http://<server>.XML October 2014 70 .<ext>:1128/lmsl/upgrade/<SID>/doc/eval/index.4 Software Update Manager Evaluation http://<server>.<ext>:1128/lmsl/upgrade/<SID>/doc/UPGANA.<domain>. com/patches or http://service. This can be done via a software provisioning manager (SWPM) option.sap.0 UC): Furthermore you have to Split off ASCS Instance from the Primary Application Server Instance to follow the new Guideline from 7.30 onwards.Upgrade to new instance-specific directory on UNIX The following graphic illustrates the new structure (since NetWeaver 7. See the following pages for details.1 Split off ASCS Instance from Existing Server In case the Source System was based on non-unicode (NUC) or was already upgraded from a previous release.5.5 Post Activities after the main DMO Procedure 3. The software provisioning manager can be downloaded either from http://service.Upgrade to the New Instance-Specific Directory Structure UNIX  Note 1104735 . See the following Notes for details: Windows  Note 919046 . you have to check the file structure of your SAP Instance manually.sap.com/sltoolset October 2014 71 .SAP First Guidance … database migration option (DMO) – BW on HANA 3. SAP First Guidance … database migration option (DMO) – BW on HANA October 2014 72 . SAP First Guidance … database migration option (DMO) – BW on HANA October 2014 73 . SAP First Guidance … database migration option (DMO) – BW on HANA October 2014 74 . SAP First Guidance .SAP First Guidance … database migration option (DMO) – BW on HANA 3.2. Refer to the SAP First Guidance Document .40 Functionality together with SAP HANA 1. Therefore you have to import the correct Version of the AFL assign to your HANA Revision.SAP HANA Database: Starting the Script Server Note 1917938 . 71 Note 1925684 .2 Install Application Function Library (AFL) The HANA Analysis Process (HAP) uses the AFL content for SAP HANA. October 2014 75 .5.2 HANA Specific Post Steps 3.2. you have to activate the following components on your HANA server.1 Activate new HANA server functions To work with the new SAP BW 7.0 SP07 and above.ABAP adjustments for SAP HANA SPS 7 3.Business Warehouse on SAP HANA Installation for more Details. Note 1650957 . You can use the HANA Lifecycle Management via the HANA Studio.5. If you are Updating HANA with AFL content applied.5.Migration des Statistics Server mit dem Upgrade auf SPS 7  Rev. you have to update the AFL content first. or apply a complete HANA stack. 4 Configuring DBMS User Man. you can assign the user in the Transaction SU01 via an additional Tab Strip as follows: October 2014 76 . you have to map the existing ABAP User to an existing HANA User.5. 3.2. With the Transaction DBCO create a connection with the SAP<SID> to the underlying HANA database and assign this connection in the User DBMS System View (SM30  Table USR_DBMS_SYSTEM).SAP First Guidance … database migration option (DMO) – BW on HANA 3.5. After this.3 Install the smart data access (SDA) drivers The SDA drivers can be applied with the same tool (HLM) as mentioned above. for SAP HANA To enable the usage of the Analysis Capabilities together with SAP BW and HANA.2. October 2014 77 .SAP First Guidance … database migration option (DMO) – BW on HANA It is suitable to use a similar notation as for the creation of logical source systems as known for SAP BW. htm ?frameset=/en/74/3ef0e24417493a8bf2b50fb0199d64/frameset. or Not enough rights to open view (HDB 02074).0 .htm&current_toc=/en/06/371640b 7b6dd5fe10000000a155106/plain. Additional Information can also be found in the SAP Help Portal: http://help.External SAP HANA view: Assignment of SAP HANA authorizations without roles October 2014 78 .SAP First Guidance … database migration option (DMO) – BW on HANA The Assignment of the Analytical Privilege _SYS_BI_CP_ALL is helpful as well. of BW authorizations for a specific BW user Note 2040167 .Prerequisite SAP Note for SAP Note 2038865 Note 2038865 .SAP Lumira 1. See also Note 1956963 .htm&node_id=217&show_children=false Transaction RS2HANA_VIEW The activation of the relevant BI Content (InfoObjects and InfoProvider 0TCA*) is necessary as well.Replication of CP * authorizations and correction in the key of BW filter tables If you are not yet on SAP BW Support Package Stack 08. these SAP Notes are also relevant: Note 2038892 .Error "User has no authorization" after rep.com/saphelp_nw74/helpdata/en/74/3ef0e24417493a8bf2b50fb0199d64/content.Insufficient rights: Unable to connect to HANA server. Note 2057532 .sap.Access privileges required for SAP Lumira from SAP HANA Note 1823771 .Creating roles from BW in SAP HANA not possible Note 1881935 . Furthermore the additional SAP Notes corrections have to be applied. 2.SAP First Guidance … database migration option (DMO) – BW on HANA 3.5 Mass Maintenance of DBMS User For the Mass Maintenance of the DBMS Users you can use the Program RSUSR_DBMS_USERS: October 2014 79 .5. Mass DBMS User Management Note 1836006 . 3.htm?f rameset=/en/82/25d779272c40b2867137374af77017/frameset.Transaktionen RS2HANA_ADMIN and RS2HANA_CHECK October 2014 80 . The Functionality will be final delivered with 7.sap.SAP First Guidance … database migration option (DMO) – BW on HANA Details about the usage can be found in the following Notes: Note 1927767 .5.6 Transaction RS2HANA_CHECK/ADMIN With the Transactions RS2HANA_ADMIN and RS2HANA_CHECK you can maintain the correct creation of the external HANA Views. so apply the following Note 2031522 .40 SP09.Requirements for DBMS User for DB connection Additional Information can also be found in the SAP Help Portal: http://help.com/saphelp_nw74/helpdata/en/69/faccbf575c4f79b61e1b38af757a2c/content.htm&node_id=223 Tip: Create with SE93 a Transaction to call the program RSUSR_DBMS_USERS directly.htm&current_toc=/en/06/371640b7b 6dd5fe10000000a155106/plain.2. October 2014 81 .31/7.3.5.40 is complete.5.3 BW Specific Post Steps 3.4.1 Check HANA DB with transaction DBACOCKPIT From the technical perspective your database migration process including the upgrade to NetWeaver BW 7.4. 3.5.SAP First Guidance … database migration option (DMO) – BW on HANA The mentioned RSRV Check points to the RSRV check mentioned in Chapter 3. The usage of the ASU toolbox is already mentioned before. Optionally it might be necessary to re-run certain steps in interaction with the program RSDU_TABLE_CONSISTENCY. There is no need to run the Report RS_BW_POST_MIGRATION separately. This depends on the skipped phases in the DMP procedure beforehand. like the recreation of the calc views.SAP First Guidance … database migration option (DMO) – BW on HANA You have to manually create the DBCON entry for the HDB connection with the user DBACOCKPIT. Please Note that the DMO process includes also all post activity steps after the Upgrade and Migration as well. October 2014 82 . RSDU_TABLE_CONSISTENCY NW 7.RSHDB: RSDU_TABLE_CONSISTENCY NW7.30 SP12 Note 1953984 .SAP First Guidance … database migration option (DMO) – BW on HANA 3.RSHDB: Dev.SHDB: Tool classes for NW 7.SHDB: misleading security error in class cl_shdb_ddl Note 1908854 .Consistency check .30 SP13 Note 1953493 .SAP HANA: CHECK_TABLE_CONSISTENCY on Extended Storage tables may lead to crash Before you run the Report RSDU_TABLE_CONSISTENCY make sure the following corrections are applied: Note 1937062 .2 Application check .RSHDB: Hash partition keys of PSA tables without PARTNO October 2014 83 .30 SP11 Note 1889467 .SHDB: Development tool classes NW 7.RSHDB: RSDU_TABLE_CONSISTENCY NW7.Usage of RSDU_TABLE_CONSISTENCY (apply in sequence 1953984 and 1953493) Note 2025241 .SHDB: Development Tool-Classes NW7.3.Technical Consistency Checks for SAP HANA Databases Note 1908075 .30 SP13 Note 2025271 .30 SP11 Note 1892492 .reading pdim adjustment Note 1937166 .5.Group name of table classification is missing for change log tables of a DSO Note 1939413 .BW on HANA: Table Placement und Landscape Redistribution Note 2052419 .RSDU_TABLE_CONSISTENCY Note 1977584 .30 SP12 Note 1888511 . Go back to the main entry screen and start the “Repair” option with “Execute in Background” October 2014 84 .SAP First Guidance … database migration option (DMO) – BW on HANA After the first run (either for or background) with option „Store issues“ you will an additional operation mode “Repair” and the section “Issues from previous checks” DoubleClick on the selected Line in the Log list (1) Press the Save Button (2) Continue with these Steps (1-2) for the other entries in the Log List as well. SAP First Guidance … database migration option (DMO) – BW on HANA The Repair Job is now running as background job. Check either with SM50 or SM37. 3.5.3.3 Repair inconsistent PSA tables Note 1979867 - Program for repairing inconsistent partitioning of PSA tables The Note contains the program RSDU_PSA_PARTNO_CHECK. The usage of the program is identical with the program RSDU_TABLE_CONSISTENCY. 3.5.3.4 Check consistency for all external HANA views Note 1967624 - External SAP HANA view: SAPKW74007 corrections Note 1955345 - RS2HANA: Generation of authorizations before and after SAP HANA Revision 70/71 October 2014 85 SAP First Guidance … database migration option (DMO) – BW on HANA 3.5.3.5 Correct missing views for selected Master Data Implement the manual report attached to the following Note (ZRSDMD_CHECK_CHA_VIEWS) Note 1892819 - Improved performance when loading master data and run the Repair Mode Option. Note 1656582 - Query terminations - InfoCubes, DSOs, master data in HANA DB Note 1898395 - Secondary Index on InfoObject master data tables Note 1860274 - SAP HANA adj. for BW Workspaces: Inactive CompositeProviders Note 1891981 - HANADB: Performance - missing views when updating master data October 2014 86 SAP First Guidance … database migration option (DMO) – BW on HANA 3.5.3.6 Migrate existing BW Workspaces Report RS_BW_POST_MIGRATION If you had a BWA in use, and also with BW 7.30 the new BW workspaces you can now also adjust these areas for the usage on BW on HANA. After the note 2060342 has been implemented with the latest version, please execute step 12 of the post migration report (RS_BW_POST_MIGRATION) which also adjusts the xmls of the CompositeProviders. Afterwards please execute report SET_COPR4REPAIR_MPRO Note 2060342 - BW Workspace - local CompositeProvider with MultiProvider mapping - post-migration to SAP HANA Note 1953480 - Column view generation after upgrade to SAP BW 7.40 SP5 or above Note 2064791 - "Migration" of BW Workspaces from BW7.3 with BWA to BW 7.4 on HANA Note 2055364 - Workspaces: Recovery creates local provider with column width 1 In Advance implement the following UDO Reports first: Note 2060342 - BW Workspace - local CompositeProvider with MultiProvider mapping - post-migration to SAP HANA Note 2059888 - Workspaces: Collective corrections for 7.40 SP8 – Part 1of 2 Note 2037805 - BW Workspaces: Local prov: Reloading with appends and other improvements - Part 1 Note 2048446 - BW Workspace: Local characteristic: Corrections 740 SP08: Part 1 Note 2047705 - UDO Report for SAP Note 2033948 "General Enchantments for SAP BW 7.40 SP8” Note 2047471 - UDO report for SAP Note 2043430 ("Enhancement of the InfoProvider Properties Maintenance") Note 2061288 - BW-MT: Sammelhinweis, NW 7.40 SP07 10/1, SP08 6/1 - UDO Report zweimal ausführen Note 2061289 - BW-MT: Sammelhinweis, NW 7.40 SP07 10/2, SP08 6/2 October 2014 87 However this Task List is implemented with the DMO procedure as well.7 BW Migration Post Task List with DMO procedure The call of the Post Migration Task List is optional in case not all steps are runned successfully with the DMO procedure. October 2014 88 .3.5.SAP First Guidance … database migration option (DMO) – BW on HANA Report RSL_WSP_ADJUSTMENT_AINX Report RSL_WSP_ADJUSTMENT_COMPLETE Report RSL_WSP_REPAIR_COPR (SET_COPR4REPAIR_MPRO) 3. SAP HANA DB: Check for correct InfoCube migration Note 1925571 .BW on SAP HANA: Conversion of an InfoCube terminates Note 1926112 .3.8 Convert InfoCubes into in-memory optimized Use Transaction RSMIGRHANADB to convert InfoCubes on demand.BW on SAP HANA: Merge after InfoCube compression Note 1952076 . DSO objects remains unchanged.SAP First Guidance … database migration option (DMO) – BW on HANA 3.740 October 2014 89 .5.Note Assistant: Important notes for SAP_BASIS 730.Report BW_POST_MIGRATION causes ABAP memory shortage 3. Note 1731569 .5.3.9 Check the updates for SNOTE corrections Note 1668882 .731. 40 SP5 Note 1984935 .NW BW 7.30 SP10 SAPKW73011 InfoCube Example: find all HANA InfoCube related SAP Note corrections after NetWeaver 7.BW modeling tools: Composite SAP Note for SAP NetWeaver 7.31 now.40 (SP07) .RSMRT: Korrekturen für SAP BW 7.40 SP07 Nr.Important SAP Notes for SAP BW 7.SAP First Guidance … database migration option (DMO) – BW on HANA If you have inconsistencies with the BW-PCA or the BW Housekeeping Task Lists.HANA Analysis Processes and HANA Transformations .Tables of BW objects are not compressed Note 1969720 .com/notes with the keywords like: Example: find all HANA DSO related SAP Note corrections after NetWeaver 7.SAP HANA SPS 07 Database Revision 74 Note 1949273 .SAP GUI for HTML: Rendering problems in Enterprise Portal (EP) Note 1753544 . Furthermore you find these Notes useful for the current BW on HANA usage: Note 1947354 .40. powered by SAP HANA Note 1989896 .Collection of corrections in the BW OLAP/Data Manager on top of SP06 .40 SP08 October 2014 90 .Part 2 Note 2032030 .SAP applications iViews in EP: Rendering Modes Note 2000082 . reset the NOTES implementation for these Notes.HTML standards mode Note 1814711 .Web Dynpro .40 SP08 .31 SP09 SAPKW73110 HANA DSO Example: find all HANA InfoCube related SAP Note corrections after NetWeaver 7.Corrections: BW Data Warehousing Workbench SP07 Note 1966654 .Part 6 Note 1977882 .External SAP HANA view: corrections SAPKW74008 Note 2043836 .Runtime Exception when trying to add new user agent string Note 2008196 .BW modeling tools: Composite SAP Note for SAP NetWeaver 7.NWBC -Patch Collection.40 SP06 No.SAP HANA SPS 07 Database Revision 73 Note 2003736 . 1 Note 2000248 .SERVER SIDE (ABAP)+NWBC for HTML You can always look for the latest corrections in certain areas at http://service.irrelevant error messages in after import Note 2005699 . 2/2 Note 1955508 .Creation of Package RS_UDO_REPORTS as pre-requisite for collective notes Note 1990011 .BW 7.No.sap.SAP NWBC ABAP Runtime Patch 38 Note 1353538 .RSDDTMPTAB_DELETE Note 1974407 .InA 7. as they are Part of the SP08 for 7.40 SP06 SAPKW74007 HANA InfoCube Example: find all advanced DSO related SAP Note corrections after NetWeaver 7.Temporary BW objects are unexpectedly not deleted .External SAP HANA view: corrections SAPKW74008 .Use of "Edge" and "Compatibility" mode for HTTP system logon page Note 1970427 .40 SP8 (SAPBW74008) Notes to stay compatible with MS IE 9/10/11 Note 1989718 .Corrections 18 Note 2035324 . 11/2 Note 2011408 .40 SP8: HANA Analysis Processes and HANA Transformations Note 2031355 – Enhancements and Problem Solutions for SAP BW 7. .....................tool configuration............2% PREP_INSTALL/INITSHD ............................................................................................8% PREP_CONFIGURATIONS/SUBMOD_MIG_CONFIG/DETBWMODE ..................7% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/INSTHDBCLI .....................................include change request.........................................................................0% PREP_EXTENSIONS/BIND_PATCH .....................1% PREP_CONFIGURATION/INITSUBST ..................................................................................................41 20............................................................................7 % PREP_EXTENSION/UPLOAD_REQUEST ..............lock development environment ...................6% PREP_EXTENSIONS/IS_SELECT ................................30 SAP HANA Client Installation ...............41 Edit table RSADMINA ...6 List of manual Interactions with the DMO procedure 0............................start ASU toolbox .......................38 13.....................................44 24....select BEX REQUEST to delete ................................32 8.................................advanced option ....................................43 22....................................................long and intensive runtime phase ....................................................................................................................................................................... continue with procedure .................30 SAP HANA Studio ....................................................................................................1% PREP_PARSEETUP/CHECK4NOTES_TOOL ...................................................................35 11............................43 Transaction /ASU/UPGRADE .................................................................................adjustments made........................................check open transports .............................8% MAIN_SHDRUN/DDIC_UPG ...........................................................................................44 27..................................................26 7..........7% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/HDB_PREPARE ......................45 40............6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG ...............9% PREP_INPUT/MIG2NDDB_INI .........................36 11.8% PREP_EXTENSION/ADDONKEY_CHECK .................................................................................................38 12.............34 10...........5% PREP_PREPROC/SAVE_VAR_CHK ............................................................0% select STACK CONFIGURATION FILE .................................28 7........29 SAP HANA Studio ...3 ................................................................9% PREP_EXTENSIONS/BIND_PATCH ...........................9% MAIN_SHDRUN/ACT_UPG .............................46 October 2014 91 ...................................................................................38 12......................................31 7........................END (3) ...9% PREP_CONFIGURATION/INITSUBST .............................................................34 11.................................30 7...........................................................................22 1....8% PREP_EXTENSIONS/CONFLICT_CHECK ...................45 39................................................................................2% PREP_EXTENSIONS/BIND_PATCH ......................................1% PREP_INTERACTION/ADJUSTTPRP ...............................................................................0% PREP_EXTENSION/EHP_INCLUSION ..................................................................32 8..................................3% PREP_PREPPROC/REQ_ASU_RUN ..........4% MAIN_SHDRUN/SUBMOD_DIFFEXP/ADJUSTCHK_UPG .......................................................................................................4% PREP_PRE_CHECKPROFREAD ............................................END (1) .......................................................................9% MAIN_SHDRUN/ACT_UPG ....................................4% MAIN_SHDCRE/SHADOW_IMPORT_UPG1 ...........31 7.......................................................................................................................21 1....................long running phase ......................................................................43 21....................HDB Connection .......6% PREP_INPUT/SCANDIR_EXTRACT................36 11........................45 40......37 12...............Note 889596 .......................................................................................................................................................................27 7..................END (2) ................34 11................................................................................................32 8...0% PREP_EXTENSIONS/ADDON_LANGINC ..........................................................35 11..................9% PREP_INSTALL/JOB_FILL_TPF_CHK_PHASES ....DMIS Add-On decision ...........................7% PREP_EXTENSIONS/IS_SELECT ..........................42 21.............................................20 0...............0% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/MIG2NDDB_AUX_PRE ........................................................................report RSUGRCHECK ...................................................................................................................................................39 15.......21 1...................................3% PREP_INSTALL/SHD INST_CPY .......2 .......................................................................................Lifecycle Management ......................................................................................SAP First Guidance … database migration option (DMO) – BW on HANA 3..................4% PREP_CONFIGURATION/LANG_SELECT ........................................................................................4% PREP_EXTENSIONS/IS_SELECT ................................................................................22 7................37 12...........26 6........7% PREP_PRE_CHECK/SPAMCHK_INI ................................2 % PREP_EXTENSION/IS_INST.......................................................2% PREP_INPUT/READDATA_EXP .4% MAIN_INIT/BEGIN ............................................................33 9.........................................................................................................................45 37......................5% MAIN_INIT/REPACHK1 ...................................................................4% PREP_CONFIGURATION/LANG_SELECT .......................SPAM update ................................6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG.........39 14...................................save variants .......................................................................39 14..............................................................................19 0......use DDIC/000/SHD ................................41 20.........................0% MAIN_INIT/LOCKEU_PRE .............................................5% PREP_GENCHECKS/JOB_TS_UGR41 ...............................................40 18.........................................................................................................7% PREP_PREPPROC/SUBMOD_MIG_BI_TASKS_PREP/MIG2NDDB_HANA_BW_PARAMS .29 License Key Request (Internal View) ....................... ...48 52.5% MAIN_SHDIMP/SUBMOD_SHD2_RUN/NTACT_ALTNT ....................56 62.................................................................................47 42........68 99......................................4% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_DT_CREATE .....................5% MAIN_UPTRANS/MAIN_POSTP ......................................................49 58.......................................63 91.......4% MAIN_SHDIMP/SUBMOD_SHD2_RUN/TABIM_POST_SHD ......................long and intensive runtime phase .........accept non-severe errors and repeat phase........0% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK ..........................................................................................................3% MAIN_SHDRUN/RUN_INDC_UPG ..................................................................................64 92.......0% MAIN_SHDIMP/SUBMOD_MIG_UPTIME_PRP/RUN_SMIGR_CREATE_DDL ........0% MAIN_SHDRUN/ACT_UPG ..................................63 90...........................................0% MAIN_SWITCH/PARMVNT_XCNV .......69 100% YOUR UPGRADE IS COMPLETE ...........................................................................................................7% MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_UPG2 ...47 51.............62 81....................................57 65................................................................69 Back to Table of Content October 2014 92 .47 51...............................................................5% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/SUBMOD_SWITCH_KERNEL/KX_SWITCH ...64 91.........preparations for downtime ..............................59 67.60 68...........................4% MAIN_SHDIMP/SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE ...........................language import .......................................1% MAIN_SHDIMP/SUBMOD_CP2SHD/TP_ACTION_CP2STAB ....................3% MAIN_SHDIMP/SUBMODE_SHD2_RUN/RUN_RSGEN .....................48 53...................................64 91................................................5% MAIN_SHDIMP/NTACT_PREMV....0.....1% MAIN_DTTRANS/SETSYNC_PREUP_DT_CONFIRM .........................62 89........7% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_PSA_VERSION_CREATE ....................................................................................0% MAIN_SHDIMP/SUBMOD_MIG_BI_TASKS_PREDTT/RUN_WORKSPACE_BACKUP_CREATE .backup request ......END (5)...................intensive Phase (CPU) ....1% MAIN_NEWBAS/TABIM_UPG ................................................61 72......................................................7% MAIN_POSTP/RUN_RSDB02CHK_END .................48 54......................................................................47 48..............0% MAIN_SHDIMP/SUBMOD_CP2SHD/SUBMOD_DIFFCP2SHD/DIFFEXPABAP_CIGPR ............1% MAIN_SHDIMP/SUBMOD_FATESTS/RUN_RSDB02CK_MOD.......................1% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_TIMESTAMP_RESET .......END (4) ...........58 66...........................................1% MAIN_NEWBAS/XPRAS_AIMMRG .....................................5% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_UT ....long runtime phase ..................................................47 42..........................................................................0% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK ......................................END (6) ..0% MAIN_SHDIMP/SUBMODE_SHDIMP/TABIM_REDUCE .....................long runtime phase 4...65 92...................9% MAIN_UPTRANS/UPCONF .....start uptime migration ...........46 41................66 98............58 66.......8% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/REQ_LANDSCAPE_REORG .........................................................................49 63.......................47 51...............................................................................................................................1% MAIN_SHDIMP/PARMVNT_SHD ...................61 79...................49 62.............................SAP First Guidance … database migration option (DMO) – BW on HANA 41...............................................RSADMIN table parameter .............................67 98.................4% MAIN_POSTP/RUN_CUBE_INDEX_ADJUST ............................................................63 89...............................................................2nd backup request ..............................3% MAIN_SHDRUN/PARDIST_UPG......................................0% MAIN_SHDRUN/ACT_UPG ..........48 51.............................................7% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE....48 52........49 59....................................50 62........................................................8% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/EU_CLONE_MIG_DT_RUN ...................................................................................................2% MAIN_POSTP/SPAUINFO..................................................................................end of downtime...................................8% MAIN_POSTP/SETUPGPAR_UPG_POST ....................................................................................................................disable archive mode ........restart RDA daemons .....................59 66...............9% MAIN_POSTP/SAVELOGS ...........................2% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP2_REQRSRDA ......................................................9% MAIN_UPTRANS/STARTSAP_PUPG ...................................................................66 97...48 56..............................................................................repair with RSDU_TABLE_CONSISTENCY ...............................47 49.................................0% MAIN_DTTRANS/DOWNCONF_DTTRANS ..8% MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC ............. www.sap.sap.com/contactsap http://scn.com/docs/DOC-7856 .
Copyright © 2024 DOKUMEN.SITE Inc.