sap first guidance using the dmo option to migrate bw on hana new

SAP First Guidance

SAP NetWeaver BW 7.3x

SAP Realtime Database Platform

Applicable Releases:

SAP NetWeaver BW 7.0x SP27/SP10

SAP NetWeaver BW 7.3x SP07/SP03

SAP NetWeaver BW 7.40 SP02

DMO is an option of SUM for combined update and migration: update an existing SAP system to a higher software release and migrate to SAP HANA database. 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 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 - migrate BW on HANA with the database migration option (DMO)

mailto:[email protected]

SAP First Guidance

SAP NetWeaver BW 7.3x

SAP Realtime Database Platform

Version 1.50

January 2014

© Copyright 2014 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP AG. The

information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9, iSeries,

pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,

OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power

Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,

MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and

Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other

countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open

Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,

and MultiWin are trademarks or registered trademarks of Citrix Systems,

Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks

of W3C®, World Wide Web Consortium, Massachusetts Institute of

Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and other

countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other

Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business

Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Sybase, Inc.

Sybase is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this

document may be reproduced, copied, or transmitted in any form or for

any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license

agreement or any other agreement with SAP. This document contains

only intended strategies, developments, and functionalities of the SAP®

product and is not intended to be binding upon SAP to any particular

course of business, product strategy, and/or development. Please note

that this document is subject to change and may be changed by SAP at

any time without notice.

SAP assumes no responsibility for errors or omissions in this document.

SAP does not warrant the accuracy or completeness of the information,

text, graphics, links, or other items contained within this material. This

document is provided without a warranty of any kind, either express or

implied, including but not limited to the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without

limitation direct, special, indirect, or consequential damages that may

result from the use of these materials. This limitation shall not apply in

cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not

affected. SAP has no control over the information that you may access

through the use of hot links contained in these materials and does not

endorse your use of third-party Web pages nor provide any warranty

whatsoever relating to third-party Web pages.

SAP “How-to” Guides are intended to simplify the product implement-

tation. While specific product features and procedures typically are

explained in a practical business context, it is not implied that those

features and procedures are the only approach in solving a specific

business problem using SAP NetWeaver. Should you wish to receive

additional information, clarification or support, please refer to SAP

Consulting.

Any software coding and/or code lines / strings (“Code”) included in this

documentation are only examples and are not intended to be used in a

productive system environment. The Code is only intended better explain

and visualize the syntax and phrasing rules of certain coding. SAP does

not warrant the correctness and completeness of the Code given herein,

and SAP shall not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change

in these components may cause unpredictable and severe malfunctions

and is therefore expressively prohibited, as is any decompilation of these

components.

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.

Document History

Document Version Description

1.00 First internal release (only SUM run)

1.10 SAPHostAgent 7.20 enablement, MSSQL for DMO, corrections

1.20 Further Improvements SUM/DMO, updates, corrections

1.30 First external release including DMO and Basis/BW-PCA

1.31 SPUMG, split off ASCS, further additions/corrections

1.40 DMO SP09 update, guide splitted, further additions/corrections

1.42 Further Updates, Additions for Pre/Post Migration Steps for DMO

1.43 Additions/Updates, SP10 usage, SL Monitor App, corrections

1.50 BW 7.40 SP06 as Target, further additions/corrections

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

SAP First Guidance … database migration option (DMO) – BW on HANA

January 2014 3

Table of Contents

1. Database migration option (DMO)................................................................................... 4

1.1 Prerequisites ..................................................................................................................... 4

2. DMO - Conceptional Overview ......................................................................................... 6

2.1.1 DMO in a Nutshell ................................................................................................ 6

2.1.2 DMO in Interaction with BW-PCA ...................................................................... 6

2.1.3 DMO in Interaction with the New SAPHostAgent ............................................ 7

2.1.4 DMO Milestones during the Procedure ............................................................. 7

2.1.5 DMO Procedure: In-Place Upgrade and Migration........................................... 8

2.1.6 BW Phases in the Overall DMO Process ........................................................... 8

2.1.7 DMO - Comparison Standard and New Process .............................................. 9

3. Step by Step – DMO Option ............................................................................................ 10

3.1 Application Specific Preparation Steps ........................................................................ 10

3.1.1 Interaction ASU Toolbox with DMO Procedure .............................................. 10

3.1.2 Notes for the BW-Specific Upgrade Phases .................................................... 11

3.1.3 BW Upgrade Task List with DMO Procedure ................................................... 11

3.1.4 Report UMG_ADD_PREP_STEP ....................................................................... 13

3.2 Unicode preparations for the DMO Procedure ............................................................ 14

3.3 The DMO Procedure in Detail ........................................................................................ 16

3.3.1 Usage of the SL Monitor App (iOS6) ............................................................... 16

3.3.2 Phase Extraction (1) .......................................................................................... 17

3.3.3 Phase Configuration (2)................................................................................... 24

3.3.4 Phase Checks (3).............................................................................................. 38

3.3.5 Phase Preprocessing (4) .................................................................................. 41

3.3.5.1 Result from the parallel export/import process...... 50

3.3.6 Phase Execution (5) ..........................................................................................54

3.3.7 Phase Postprocessing (6) ............................................................................... 59

3.4 Software Update Manager Evaluation ......................................................................... 66

3.5 Post Activities after the main DMO Procedure ............................................................ 67

3.5.1 Split off ASCS Instance from Existing Server ................................................. 67

3.5.2 Check HANA DB with transaction DBACOCKPIT .......................................... 72

3.5.3 Application check with RSDU_TABLE_CONSISTENCY ................................ 73

3.5.4 Correct missing views for selected Master Data ........................................... 76

3.5.5 BW Migration Post Task List with DMO procedure........................................ 76

3.5.6 Convert InfoCubes into in-memory optimized ............................................... 77

3.5.7 Convert DSO into in-memory optimized (obsolete) ...................................... 77

3.5.8 Check the updates for SNOTE corrections..................................................... 78

3.6 List of manual Interactions with the DMO procedure ................................................. 79


January 2014 4

1. Database migration option (DMO)

Note 1813548 - Database migration option (DMO) for Software Update Manager

Note 1799545 - Using DMO of SUM for SAP BW systems

Please read the note and apply for the Pilot/Restricted Usage for SUM 1.0 SP10.

The current Version with SUM 1.0 SP09 is now generally available!

https://service.sap.com/~sapidb/011000358700000950402013E/SUM_SP09_DMO_V1_10.pdf

The official SUM/DMO Documentation, please consult this first!

1.1 Prerequisites

Prepare the SAPHostAgent and DMO according to the following Notes:

Note 1799545 - Conditions for using database migration option of SUM

Note 1843776 - Central Note - Software Update Manager 1.0 SP09 [lmt_005] (password 1740067)

Note 1878193 - Central Note - Software Update Manager 1.0 SP10 [lmt_006] (password 1743651)

You also need to do the following:

Note 1556113 - sapevents.dll in DIR_CT_RUN is locked (rename sapevents.dll before upgrade)

run saphostexec.exe -install from the extracted SAP Agent 7.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.exe -upgrade -archive

D:\_install\download\SAPHOSTAGENT176_176-20005735.SAR

Run the command /usr/sap/<SID>/SUM/abap/SUMSTART confighostagent to create the file sumstart.conf in (SAPHOSTAGENT ≥ 173)

D:\usr\sap\N4S\SUM\abap>SUMSTART.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...

Creation of file C:\Program Files\SAP\hostctrl\exe\operations.d\sumstart.conf

Registering SUM in SAP Host Agent finished.

D:\usr\sap\N4S\SUM\abap> C:\Program Files\SAP\hostctrl\exe\operations.d\sumstart.conf Name:SUMStart

Authorization:$[SID:#required#tolower]adm

Command:D:\usr\sap\$[SID:#required]\SUM\abap\SUMSTART.BAT

Username: $[SID:#required#tolower]adm

Workdir: D:\usr\sap\$[SID:#required]\SUM\abap

ResultConverter: flat

https://service.sap.com/sap/support/notes/1813548

http://service.sap.com/sap/support/notes/1799545


https://service.sap.com/~sapidb/011000358700000950402013E/SUM_SP09_DMO_V1_10.pdf







January 2014 5

Optional: Enable SSL for the SAPHostAgent (Port 1129). http://help.sap.com/saphelp_erp2004/helpdata/en/56/a92f3ae689f058e10000000a11402f/content.htm

C:\Program Files\SAP\hostctrl\exe>mkdir sec

C:\Program Files\SAP\hostctrl\exe>

set SECUDIR=C:\Program Files\SAP\hostctrl\exe\sec

sudo -u sapadm LD_LIBRARY_PATH=/usr/sap/hostctrl/exe

SECUDIR=/usr/sap/hostctrl/exe/sec /usr/sap/<SID>/SYS/exe/run/sapgenpse

get_pse -p SAPSSLS.pse -x password -r /tmp/<server>-csr.p10

"CN=<server>.<domain>.<ext>, O=<company>, C=DE"

Or copy the files from D:\usr\sap\<SID>\DVEBMGS<nr>\sec

Restart the SAPHostAgent C:\Program Files\SAP\hostctrl\exe> saphostexec.exe -restart

Start the DMO Frontend with the following URL – (HTTP/HTTPS) http://<server>.<domain>.<ext>:1128/lmsl/upgrade/<SID>/doc/gui

https://<server>.<domain>.<ext>:1129/lmsl/upgrade/<SID>/doc/gui

To reset or check the DMO procedure, use the following step-by-step procedure: o Start SAPup in scroll mode

cd /usr/sap/<SID>/SUM/abap/bin

./SAPup <option> gt=scroll (httpserver0/allowjump/set allpwd/set procpar)

2) Choose the option “Back”

Back

Exit

Cleanup and start fresh.

[Exit]: 01

To reset the Upgrade/DMO process run (includes old ABAP Report upgreset)

Note 1790486 - SAP_ABA is in an undefined state that is not safe to be upgraded

cd /usr/sap/<SID>/SUM/abap/bin

./SAPup reset prepare

delete the directory /usr/sap/<SID>/SUM/ and start from scratch with the SUM sar file unpack.

Changing Process Parameters during runtime using UI browser access:

http://<host>.<domain>.<ext>:1128/lmsl/upgrade/<SID>/set/procpar

You can use the command /usr/sap/<SID>/SUM/abap/bin/SAPup dmpspc

to check the used space at different points of time.

Get a migration key for anyDB to HDB - see internal Note (SAP Employees) Note 1134948 - ABAP Migration Key for special installation numbers

Get the license key for HDB - see internal URL (SAP Employees) https://isp.<domain>.<ext>/sap(bD1kZSZjPTAwMQ==)/bc/bsp/sap/zkey_webas/start.htm

Additional Tipp’s and Tricks for the usage of the DMO procedure within the SUM

https://jam4.sapjam.com/#wiki/show/98019

http://help.sap.com/saphelp_erp2004/helpdata/en/56/a92f3ae689f058e10000000a11402f/content.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/56/a92f3ae689f058e10000000a11402f/content.htm

http://iwdf4366.wdf.sap.corp:1128/lmsl/upgrade/N4S/doc/gui

https://iwdf4366.wdf.sap.corp:1129/lmsl/upgrade/N4S/doc/gui




https://isp.wdf.sap.corp/sap(bD1kZSZjPTAwMQ==)/bc/bsp/sap/zkey_webas/start.htm

https://jam4.sapjam.com/#wiki/show/98019


January 2014 6

2. DMO - Conceptional Overview

2.1.1 DMO in a Nutshell Scenario

You want to migrate your existing SAP BW system to SAP HANA

You choose the in-place migration option to avoid landscape changes (SID, hostname, …) and

need an update of your SAP BW 7.x system

The procedure is complex, and several steps have to be considered

Before upgrading to NetWeaver 7.3x, the source database has to be upgraded

Solution

Use the database migration option (DMO) of Software Update Manager (SUM)

Benefits

Migration steps are simplified

System update and database migration are combined in one tool

Business downtime is reduced

Well known tool SUM is used, with improved UI

2.1.2 DMO in Interaction with BW-PCA


January 2014 7

2.1.3 DMO in Interaction with the New SAPHostAgent

2.1.4 DMO Milestones during the Procedure


January 2014 8

2.1.5 DMO Procedure: In-Place Upgrade and Migration

2.1.6 BW Phases in the Overall DMO Process


January 2014 9

2.1.7 DMO - Comparison Standard and New Process

Further Notes on Naming:

Software Update Manager (SUM) is the tool for system maintenance:

Release upgrades, EHP implementation, applying SP stacks

SUM 1.0 is currently available with SP09, part of the SL Toolset 1.0:

“Software Logistics Toolset 1.0”, see http://service.sap.com/sltoolset

Database migration option (DMO) is an option in SUM - DMO is not a separate tool and no

additional license costs.

This build is only using the ABAP part of SUM, called SAPup The Software Update Manager for HANA (SUM4HANA) is a different tool:

- SUM4HANA updates the HANA DB software

- SUM4HANA is now the “Lifecycle Manager”

The following Blog explains the pipe and file mode for R3load which is used in the DMO process.

https://jam4.sapjam.com/#blogs/show/32699

An additional Introduction to the DMO process can be found here -

https://jam4.sapjam.com/profile/11496/documents/322115

http://service.sap.com/sltoolset

https://jam4.sapjam.com/#blogs/show/32699

https://jam4.sapjam.com/profile/11496/documents/322115


January 2014 10

3. Step by Step – DMO Option

3.1 Application Specific Preparation Steps

3.1.1 Interaction ASU Toolbox with DMO Procedure To save time, you can already start working with the ASU toolbox in the original system.

Check for the latest XML file in Note 1000009 - ASU Toolbox 2008

Upload the XML file and create a new task list, Go to the task list you have created

Check/execute the tasks in advance before the technical DMO procedure starts.



January 2014 11

3.1.2 Notes for the BW-Specific Upgrade Phases

These Notes must/should be checked before the DMO process for BW based systems is started.

Note 1609441 - Add. info about the upgrade to SAP NetWeaver 7.3 EHP1

Note 912369 - FINB_TR_DEST, after import failures, transport errors

Note 1741015 - Repartitioning of BW tables (contains Report RSDU_REPART_UI)

Note 1908075 - BW on SAP HANA SP6: Landscape redistribution (at least Rev. ≥ 60 for HANA needed)

Note 1891393 - Automated Configuration scripts for HANA Landscape (contains HDB script for reorg)

Note 1775293 - Migration/system copy to SAP HANA using latest SWPM 1.0 (HDB specific parameter for <sid>adm: HDB_MASSIMPORT=YES)

Note 1720495 - Invalid deimplementation of obsolete notes by SNOTE tool

Note 1668882 - Note Assistant: Important notes for SAP_BASIS 730,731,740

(Check/Implement after the Upgrade)

These Notes are still valid for the changeability of BW objects during upgrade.

Note 851449 - Changeability of BW objects during the upgrade

Note 1395027 - Message E861/E862(rso) when you create/change InfoPackage

Note 780710 - Upgrade already running - you are not able to change objects

3.1.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.sap.com/docs/DOC-46433, there are also additional Task Lists available to simplify

preparation of the application-specific part. Implement the following SAP Note to enable usage of task list

SAP_BW_BEFORE_UPGRADE via transaction STC01.

Note 1734333 - BW Pre and Post Upgrade and Migration Tasks

(contains manual report ZNOTE_1734333_PRE_70x/ZNOTE_1734333_PRE_73x, and NO automated

steps applied with SNOTE)


















http://scn.sap.com/docs/DOC-46433



January 2014 12

You might now find overlapping tasks in the ASU toolbox and in the SAP_BW_BEFORE_UPGRADE Task List.

This is due to the enablement of this new Task List as part of the BW Housekeeping Tasks Lists, and

allows you to use one Interface for all necessary upgrade pre and post steps.

The list of used tasks lists those are mandatory before, during and after the technical DMO procedure

(with the BW-PCA procedure included):

Additional Notes to apply:

Note 1845061 - Background user has no authorization for scheduling

Note 1860274 - SAP HANA adj. for BW Workspaces: Inactive CompositeProviders

Note 1861585 - RSUMOD20/func sumo_is_adjust: handling for cluster table

Note 1940679 - 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

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.

Transaction SPRO F5 Business Intelligence Transport Settings Create Destination for …

Furthermore make sure that the password you choose here is the correct one. In advance check with Transaction SU01 the correct password. At the end of the DMO procedure the program RS_UPG_TOOL_HMW is also using this destination. The password of BWREMOTE must be correct.










January 2014 13

After this use the Transaction FINB_TR_DEST to create RFC Destinations for Transport Methods. This will

prevent additional errors in the Phase MAIN_NEWBAS/XPRAS_AIMMRG.

Additional Notes for optimizing the phase MAIN_NEWBAS/XPRAS_AIMMRG

Note 1801400 - Error FINB_TR 032 during upgrade in phase XPRAS_AIMMRG

Note 1649901 - Time-critical processes in BW upgrade/Support Package import

Note 1894463 - Upgrade terminates with error RS0 871 or RS0 876

Note 1668456 - DTP: Error msg RSO851 during upgrade or Content installation

Note 1813468 - Web Dynpro: Conversion for non-printable chars (NON-UNICODE)

Note 1835882 - Error in XPRAS_AIMMRG phase during EHP installation for BADI Multiple active

implementations

Note 1701115 - Error in phase XPRA_* during support packs update: Job RDDEXECL fails with

SYNTAX_ERROR

3.1.4 Report UMG_ADD_PREP_STEP

This additional report was originally used with UC migrations (which also is valid for the DMO process).

It performs additional checks and makes repairs that help to ensure consistency prior to the Upgrade.

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.













January 2014 14

3.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.

In all other Systems based on NetWeaver BW 7.0x and BW 7.3x must run the Transaction SPUMG first to

prepare the existing data for the unicode conversion. For these Systems the complete and successful

preparation with SPUMG is a mandatory step.

The Transaction SPUMG is a complete set of preparation modules which can run independently from the

other preparation steps. 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.20 and onwards.

The Reason for this is the fact, 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.

The following Note contains the detailed Guide for the usage of SPUMG for every NetWeaver Release

based on 7.0x and 7.3x

Note 1051576 - Conversion of Single Code Page Systems to Unicode

check for corrections of SPUMG and additional preparation steps

Note 662215 - SPUMG and SUMG in Basis Release 6.20, 6.40 and 7.0X

Note 1457258 - Correction instruction for the Additional Preparation Steps

Note 1319517 - Unicode Collection Note

In addition check with Transaction I18N the RSCPINST settings






January 2014 15

Starting Transaction SPUMG the first time (follow the first steps)

SPUMG after running the pre checks

Additional troubleshooting Notes

Note 837173 - RADCUCNT in Unicode Conversion: Collective Note

Note 932779 - Unicode conversion - analysis of nametab problems






January 2014 16

3.3 The DMO Procedure in Detail

3.3.1 Usage of the SL Monitor App (iOS6)

You can download the SL Monitor App (currently only in the SAP Internal Store) via the following URL:

https://internalstore.sap.com/sap/cp/ui/resources/cstore/html/SolutionDetails.html?pid=00000003

92&pcntry=US&sap-language=EN&_cp_id=id-1386329181030-0

Customers can apply for the Pilot Usage. Please contact [email protected] for more details.

https://internalstore.sap.com/sap/cp/ui/resources/cstore/html/SolutionDetails.html?pid=0000000392&pcntry=US&sap-language=EN&_cp_id=id-1386329181030-0

https://internalstore.sap.com/sap/cp/ui/resources/cstore/html/SolutionDetails.html?pid=0000000392&pcntry=US&sap-language=EN&_cp_id=id-1386329181030-0

mailto:[email protected]


January 2014 17

3.3.2 Phase Extraction (1)

After you start the Software Update Manager (SUM), specify the correct stack.xml file.

Please note: the following directories are selected by default.

- SUM root directory: \\sapmnt\<SID>\SUM

- Download directory: \\sapmnt\<SID>\download

If you want to use a different location for the SUM directory, you must specify this in the Instance Parameter DIR_PUT and restart the server.

The Download Directory is the location where the stack.xml is resided including all additional needed

files during the SUM/DMO process. On Win64 based systems remain to the default download directory to avoid ACL errors in the phase EHP_INCLUSION.

Unpack the SUM 1.0 SP09 or higher file as follows:

/usr/sap/<SID>/SAPCAR -xvf SUM10SP09_0-20006676.SAR

Start the SUM/DMO UI with the following URL:

http://<server>.<domain>.<ext>:1128/lmsl/upgrade/<SID>/doc/gui

Phase: 3-1 0.0% STACK CONFIGURATION FILE

Location of the stack.xml file:

/usr/sap/<SID>/download/SMSDXML_<SID>_20130526170456.682.xml

(path valid also for Win64)

By selecting the stack.xml you define the download directory, where all necessary files, support

packages, updates, etc. can be found for the following phases. The stack.xml cannot be loaded from a

local destination.

In addition provide any updated files here as well, e.g. SAPCryptoLib, ST-A/PI, Kernel etc. which are not

collected by the stack.xml.

http://iwdf4366.wdf.sap.corp:1128/lmsl/upgrade/N4S/doc/gui


January 2014 18

If you already have executed several SUM/DMO runs you can place the existing UPGANA.xml files into

the download directory as well. This allows the DMO process to calculate the different Phases more

precisely, especially the comparison between long and short runtimes Phases (e.g. TABIM_UPG vs. 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.

In this phase the download directory must be already available, as all needed files are extracted to /EPS/in

Phase: 3-2 0.4% PREP_PRE_CHECKPROFREAD

For a better overview you can always open the “CURRENT PHASELIST” on the right side of the UI.


January 2014 19

Phase: 3-3 0.7% PREP_PRE_CHECK/SPAMCHK_INI

In case you didn’t applied the latest SAPM update, yet you will be asking to install the latest Version for

your NetWeaver Release.

In this phase the download directory is checked for the Kernel archives. You can also copy newer *.SAR

packages to the directory. The SUM/DMO process will always recognize the latest file and also, if your

source kernel is higher than in the scan directory.

Phase: 3-4 1.9% PREP_INPUT/MIG2NDDB_INI


January 2014 20

Check the log MIG2NDDB_INI.LOG to make sure your database is supported for the DMO procedure.

Note 1134948 - ABAP Migration Key for special installation numbers

Migration key 1G5fdEM50DwSq3egt6h]pGhK for instance number SAP-INTERN lasts until 2014/12/31

The CHECKS.LOG can be checked by clicking the Star on the left side of the UI.

By pressing refresh in the Browser the overlaying CHECKS window will disappear and you are back in the

COCKPIT monitor.

Log Files, setting break points or additional settings can be accessed by clicking on UTILITIES.

An error in the file CHECKS.log appears as a red flag.



January 2014 21

This is also suitable, when you have the following Pop-Up due to inactivity of the screen.

By hoover the Mouse Pointer over the Phase Bar, automatically you will see the overall rumtime estimate of the DMO procedure (file SAPupStat.log constantly updated).


January 2014 22

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 FINBASIS is described in note 438520.

INFO: The upgrade strategy for the addon PI_BASIS is described in note 555060.

INFO: The upgrade strategy for the addon SAP_ABA 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 SAP_BS_FND is described in note 632429

INFO: The upgrade strategy for the addon SAP_BW is described in note 632429.

INFO: The upgrade strategy for the addon SEM-BW is described in note 186299.

INFO: The upgrade strategy for the addon ST-A/PI is described in note 69455.

INFO: The upgrade strategy for the addon ST-PI is described in note 539977.

INFO: The upgrade strategy for the addon WEBCUIF is described in note 632429.


January 2014 23

Phase: 3-5 7.1% PREP_PARSEETUP/CHECK4NOTES_TOOL

1142427

1388287

1667685

1689526

1714734

1860274

Phase: 3-6 7.1% PREP_CONFIGURATION/INITSUBST - END (1)


January 2014 24

3.3.3 Phase Configuration (2)

Phase: 3-7 7.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.


January 2014 25

Even if you try to change the settings in the next screen, it will go back to these settings. 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.

You may want to change the suggested value for the used SGEN processes.


January 2014 26

As with a BW upgrade the “downtime” is not really relevant, the “Downtime-minimized” strategy is not

from concern here. So the Advanced/Standard strategy is the right choice.

Please Note that the Parameters have a massive influence of the time consuming phase during the

SUM/DMO procedure. So the seen values might not fit to your environment (increase them accordantly).

Phase: 3-8 7.6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG

SAP HANA 1.0 License

\\<server>.<domain>.<ext>\sapmnt\<SID>\download\<SID>_multiple.txt

d:\usr\sap\N4S\download\N4S_multiple.txt

SAP HANA 1.0 ODBC Client (≥ Rev.57)

\\<server>.<domain>.<ext>\sapmnt\<SID>\download\SAP_HANA_CLIENT

d:\usr\sap\N4S\download\N4S_multiple.txt\SAP_HANA_CLIENT

D:\usr\sap\N4S\download\N4S_multiple_24.01.2015.txt


January 2014 27

Phase: 3-9 7.6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG

See the Details to examine the correct license (7.31 - BW on HANA) on the target system and the details

for the used HANA appliance

Phase: 3-10 Transaction SLICENSE

Phase: 3-11 License Key Request (Internal View)


January 2014 28

Phase: 3-12 SAP HANA Studio - HDB Connection

Phase: 3-13 7.7% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/INSTHDBCLI

Note 1825053 - Installation of current SAP HANA client with SWPM

Unpack the archive, for example to /tmp

SAPCAR -R /tmp -xvf IMDB_CLIENT100_56-10009664.SAR

Generate the file LABEL.ASC in the directory SAP_HANA_CLIENT.

echo HDB_CLIENT:10xxx:RDBMS:*:*:* > /tmp/SAP_HANA_CLIENT/LABEL.ASC

The DMO procedure looks for the correct LABEL.ASC file in the Directory. In addition see Note 1943235.



January 2014 29

Phase: 3-14 SAP HANA Studio - HDB Connection - 2

Phase: 3-15 7.7% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/HDB_PREPARE


January 2014 30

Phase: 3-16 7.8% PREP_CONFIGURATIONS/SUBMOD_MIG_CONFIG/DETBWMODE

Phase: 3-17 8.0% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/MIG2NDDB_AUX_PRE

Exit the UI, and restart the DMO process to make the HDB client available. In Advance install the HANA client and add the path d:\usr\sap\<SID>\hdbclient before you start the DMO process.

As an additional alternative copy the library D:\usr\sap\<SID>\hdbclient\libSQLDBCHDB.dll to

the Directory D:\usr\sap\N4S\SUM\abap\exe_2nd to avoid follow up R3load errors.

Obsolete Workaround:

- Restart the SAPHostExec Process which automatically restarts SAPHostControl as well

- Alternative from the Directory hostctrl\exe\saphostexec.exe –restart

- Delete the single SAPup.exe process in the Task Manager of the OS

- Reconnect to the URL - http://<server>.<domain>.<ext>:1128/lmsl/upgrade/<SID>/doc/gui/


January 2014 31

If you run the DMO process on a system based on copy, make sure you applied a valid license; otherwise

an error will occur in this phase.

Phase: 3-18 10.0% PREP_EXTENSION/EHP_INCLUSION

Depending on the amount of available files in the download directory this can be a time consuming phase.

On Win64 based system make sure, that the directory \\<server>.<domain>.<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.


January 2014 32

Phase: 3-19 11.6% PREP_EXTENSIONS/IS_SELECT

Phase: 3-20 11.7% PREP_EXTENSIONS/IS_SELECT - 2

Please Note that the MOPZ process is not reflecting the existence of the ST-A/PI Add-On when the

stack.xml is created. Copy the necessary file to the download directory.

D:\usr\sap\<SID>\download\KITAB9J.SAR (Installation instead of Exchange-Upgrade)

Furthermore also the current SAPCryptoLib package SAPCRYPTOLIBP_8xxx-200xxxxx.SAR must be

added to the download directory (where the stack.xml is provided) manually.


January 2014 33

Phase: 3-21 11.6% PREP_EXTENSIONS/IS_SELECT - 3

Phase: 3-22 11.8% PREP_EXTENSION/ADDONKEY_CHECK

Note 1678780 - Installation or upgrade of BI_CONT/BI_CONT_XT 7x7

Password (SUM/DMO): 3668936

Note 1943931 - Installation/Upgrade for the ABAP Add-On BI_CONT / BI_CONT_XT 757

Password (SUM/DMO): 3821837

Note 1807738 - Business function / set DATA_PROVIDER_DUN_BRADSTREET

This Note becomes obsolete, as SP04 for BC 7.47 is included in the DMO process.






January 2014 34

In case of additional Support Packages, e.g. ST-PI 2008_1_700/710 you should take over the calculated

level. This will include the additional updates.

Phase: 3-23 12.5% PREP_EXTENSIONS/BIND_PATCH


January 2014 35

Phase: 3-24 12.5% PREP_EXTENSIONS/BIND_PATCH - include change request

The Report SCWN_TRANSPORT_NOTES allows you to add SAP Notes as transports, instead of having this

interaction screen. See more details here - Note 1788379 - Transport of SAP NOTES

Phase: 3-25 13.0% PREP_EXTENSIONS/CONFLICT_CHECK - Note 889596

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.

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. Since the contents of

the table depend on the type of character encoding used (UNICODE, non-UNICODE), the contents must

be deleted prior to a UNICODE conversion.

After the UNICODE conversion has been completed, these contents are rebuilt during the normal use of

the OCS tool (Manager Support Package, Add-On Installation Tool).




January 2014 36

Phase: 3-26 13.7% PREP_INTERACTION/ADJUSTTPRP

Phase: 3-27 14.5% PREP_INSTALL/INITSHD

Phase: 3-28 14.6% PREP_INSTALL/SHD INST_CPY


January 2014 37

Phase: 3-29 15.9% PREP_INSTALL/JOB_FILL_TPF_CHK_PHASES - END (2)


January 2014 38

3.3.4 Phase Checks (3)

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


January 2014 39

Phase: 3-30 20.9%

PREP_PREPPROC/SUBMOD_MIG_BI_TASKS_PREP/MIG2NDDB_HANA_BW_PARAMS

Check that the table RSADMINA (transaction SE16) the entry BEX REQUEST is removed.

Later in the process the correct entry TPBWMANDTRFC to logon on will be used as well.

Phase: 3-31 Edit table RSADMINA - BEX REQUEST


January 2014 40

Phase: 3-32 22.9% PREP_PREPPROC/REQ_ASU_RUN

Transaction /ASU/UPGRADE

Phase: 3-33 Transaction /ASU/UPGRADE

Phase: 3-34 22.9% MAIN_INIT/BEGIN - END (3)


January 2014 41

3.3.5 Phase Preprocessing (4)

Phase: 3-35 22.9% MAIN_INIT/REPACHK1 - check open transports

Phase: 3-36 24.4% MAIN_INIT/REPACK_CLONE - lock development environment


January 2014 42

Checking instance number 11 for used ports on host '<server>'.

SYSTEM HEALTH MANAGER: Port 3211 appears to be unused.






Phase: 3-37 26.8% MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE

Phase: 3-38 29.7% MAIN_SHDINST/SUBMOD_SHSALIASCRE/EU_CLONE_CRE_SHDVIEWS


January 2014 43

Phase: 3-39 40.2% MAIN_SHDRUNDDIC_UPG - long and intensive runtime phase - 1

Phase: 3-40 41.4% MAIN_SHDRUN/ACT_UPG - DDIC/000/SHD (11)

Phase: 3-41 41.4% MAIN_SHDRUN/ACT_UPG


January 2014 44

Phase: 3-42 41.4% MAIN_SHDRUN/ACT_UPG - long and intensive runtime phase - 2

Phase: 3-43 41.4% MAIN_SHDRUN/ACT_UPG - 2

ACTUP.ELG Repair of InfoObjects was not performed (DDIC is not allowed to activate customer objects, create code or activate BEx standard transports) In the Preparation phase the repair of InfoObjects must run, to avoid additional errors here.


January 2014 45

Phase: 3-44 51.0% SHADOW_IMPORT_INC - long and intensive runtime phase – 3

Phase: 3-45 51.2% - MAIN_SHDIMP/SUBMODE_SHDIMP/TABIM_REDUCE - Intensive Phase (CPU)

Phase: 3-46 55.1% MAIN_SHDIMP/SUBMODE_SHD2_RUN/RUN_RSGEN - Intensive Phase (CPU)


January 2014 46

Phase: 3-47 58.1% MAIN_SHDIMP/SUBMOD_FATESTS/RUN_RSDB02CK_MOD


January 2014 47

Phase: 3-48 62.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)

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



January 2014 48

Phase: 3-49 62.5% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/REQ_LANDSCAPE_REORG

This Phase is very important, so please inform yourself about the correct procedure.

For a correct Landscape Reorg, at least HANA 1.0 Rev. 68 or higher is needed.

Note 1815547 - Row/ColumnStore check without rowstorelist.txt

Note 1883487 - SMIGR: Rowstore Tables Without file access needed

Note 1908075 - BW on HANA SP6: Landscape Redistribution

Note 1908073 - BW on HANA Scale Out: Tabellenverteilung / -partitionierung

Note 1891393 - Automated Configuration scripts for HANA Landscape (contains HDB script for reorg)

For more details see also the following Blog:

http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape-

redistribution-with-sp6

Phase: 3-50 59.5%

MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_UT - start parallel export/import

MIGRATE_UT_00045_IMP.LOG (Example Import Log from MSS to HDB)

D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.EXE: START OF LOG: 20140127135355

D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.EXE: sccsid @(#) $Id:

//bas/741_REL/src/R3ld/R3load/R3ldmain.c#7 $ SAP

D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.EXE: version R7.41/V1.8 [UNICODE]

Compiled Jan 19 2014 18:14:03

D:\usr\sap\N4S\SUM\abap\exe_2nd\R3load.EXE -decluster -i

D:\usr\sap\N4S\SUM\abap\migrate_ut\MIGRATE_UT_00045_IMP.CMD -dbcodepage 4103 -l

D:\usr\sap\N4S\SUM\abap\migrate_ut\MIGRATE_UT_00045_IMP.LOG -loadprocedure fast

-table_suffix ~ -k 1G5fdEM50DwSq3egt6h]pGhK

-------------------- Start of patch information ------------------------

patchinfo (patches.h): (0.017) R3load conversion of REPOTEXT (note 1925533)

DBSL patchinfo (patches.h): (0.017) Datatype NCLOB missing in tablesize

calculation (note 1952609)

--------------------- End of patch information -------------------------

process id 23108

(DB) INFO: connected to DB






http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6

http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/sap-hana-landscape-redistribution-with-sp6


January 2014 49

(DB) INFO: Loading Data with mass import for lobs.

(DB) INFO: NewDB Kernel version 1.00.69.02.387329

SQLDBC 1.00.69.02.0387329

(DB) INFO SUPPORT: mass import for table with lobs should be active.

(Enviromnent Variable HDB_MASSIMPORT=YES).

(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.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: found SQLFiles.LST

(SQL) INFO: Trying to open SQLFiles.LST

(SQL) INFO: SQLFiles.LST opened

(SQL) INFO: Searching for SQL file APPL0.SQL

(SQL) INFO: found APPL0.SQL

(SQL) INFO: Trying to open APPL0.SQL

(SQL) INFO: APPL0.SQL opened

(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


January 2014 50

3.3.5.1 Result from the parallel export/import process

EUMIGRATEUTRUN.LOG


January 2014 51

EUMIGRATEDTRUN.LOG

Size of MSS DB before Export (transaction DBACOCKPIT)

Result from Report /SDF/HANA_BW_SIZING

SUMMARY

|=======

|

| ABAP Size Row Store: 14.9 GB. No. of tables: 1575

|

| ABAP Size Column Store: 5.4 GB. No. of tables: 31960

==============================================================

HANA DB size 20.3 GB. 33725


January 2014 52

Phase: 3-51 62.1% MAIN_DTTRANS/DOWNCONF_DTTRANS - preparations for downtime

Phase: 3-52 63.6% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK - backup request


January 2014 53

Phase: 3-53 63.7% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK - disable archivemode

Phase: 3-54 63.6% MAIN_DTTRANS/SETSYNC_PREUP_DT_CONFIRM - END (4)


January 2014 54

3.3.6 Phase Execution (5)

In case the message of the UI shows “the tool is not running”, restart the SAP Host Agent and reconnect to the URL.

Phase: 3-55 65.3% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/EU_CLONE_MIG_DT_RUN

Optional: if you encounter any import problems which are not critical, the quickest approach is to use the guidance of the following note:

Note 885441 - Common Migration Errors

Examples (might differ with you own system export)

Error in file MIGRATE_DT_00067_IMP.TSK I /BIC/4EEB_CU2~P C ign

/BIC/AZMKPTYPK00

/BIC/AZMKPBM00



January 2014 55

Nevertheless you should check the root cause of the problem.

This method is not intend to correct a large amount of table/indexes, therefore you have to check your source system, and if you missed some steps in preparation beforehand, the best approach is to restart the export process, rather than to spend too much time on solving some problems which can be prevented with a correct export source.


January 2014 56

Phase: 3-56 66.2%

MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/SUBMOD_SWITCH_KERNEL/KX_SWITCH

Note 1556113 - sapevents.dll in DIR_CT_RUN is locked (rename sapevents.dll before upgrade)

Rename to sapevents.dll.tmp will not work, rename to sapvents_old.dll

With SUM 1.0 SP10 the error will not occur anymore.

Phase: 3-57 76.8% MAIN_NEWBAS/TABIM_UPG - long runtime phase 4

Settings in table RSADMIN to optimize runtime in Phase XPRAS_AIMMRG:

Note 1629923 - Skip BW technical content objects activation during upgrade SKIP_TCO_ACTIVATION_XPRA

Note 1649901 - Time-critical processes in BW upgrade/Support Package import

PSEUDO_D_AFTER_IMPORT_D

















January 2014 57

Phase: 3-58 79.0% MAIN_NEWBAS/XPRAS_AIMMRG

Phase: 3-59 86.3% MAIN_UPTRANS/STARTSAP_PUPG


January 2014 58

Phase: 3-60 86.8% MAIN_UPTRANS/UPCONF - END (5)


January 2014 59

3.3.7 Phase Postprocessing (6)

Phase: 3-61 86.8% MAIN_POSTP/SETUPGPAR_UPG_POST

Phase: 3-62 90.2% MAIN_UPTRANS/REQ_ASCS_SWITCH_CLUSTER

Phase: 3-63 90.3% MAIN_UPTRANS/STARTSAP_PUPG – backup request


January 2014 60

Phase: 3-64 90.8% MAIN_UPTRANS/UPCONF - end of downtime

Phase: 3-65 91.9%

MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE


January 2014 61

Phase: 3-66 94.8% MAIN_POSTP/RSDB02CK_END


January 2014 62

Phase: 3-67 96% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE

Phase: 3-68 96.7% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP2_REQRSRDA


January 2014 63

Phase: 3-69 98.0% MAIN_POSTP/SPAUINFO


January 2014 64

You can call transactions SPAU and SPAU_ENH and check for any open adjustments.

All SPAU activities can be performed without object registration key (SSCR) for a period of 14 days after

you first entered this phase.

If you have registered a SPAU transport, it will be exported when choosing "Continue" below. Such a

transport is needed to perform automatic adjustments in subsequent SAP systems.

In that case, exit the program now and continue after SPAU has been finished.

Phase: 3-70 99.8% MAIN_POSTP/RUN_RSDB02CHK_END


January 2014 65

Phase: 3-71 99.9% MAIN_POSTP/SAVELOGS

Phase: 3-72 100% YOUR UPGRADE IS COMPLETE - END (6)


January 2014 66

3.4 Software Update Manager Evaluation http://<server>.<domain>.<ext>:1128/lmsl/upgrade/<SID>/doc/eval/index.html

http://<server>.<domain>.<ext>:1128/lmsl/upgrade/<SID>/doc/UPGANA.XML


January 2014 67

3.5 Post Activities after the main DMO Procedure

3.5.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, you have to check the file structure of your SAP Instance manually. See the following Notes for

details:

Windows Note 919046 - Upgrade to the New Instance-Specific Directory Structure

UNIX Note 1104735 - Upgrade to new instance-specific directory on UNIX

The following graphic illustrates the new structure (since NetWeaver 7.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.

This can be done via a software provisioning manager (SWPM) option. See the following pages for details.

The software provisioning manager can be downloaded either from http://service.sap.com/patches

or http://service.sap.com/sltoolset

http://service.sap.com/patches

http://service.sap.com/sltoolset


January 2014 68


January 2014 69


January 2014 70


January 2014 71

The SAP Instance after the Split of the ACSC Instance

If you want to use the DMP procedure to take care of this step you can do the manual changes to automate this step as well.

Two actions have to be done for the switch to the ASCS instance to happen automatically.

- Before starting the SUM for the first time, have the new DEFAULT.PFL accessing the ASCS instance stored somewhere, e. g. “/sapcd09/COSMOS/HANA_CMS/upgrade/DEFAULT.PFL”.

Add the line to SAPup_add.par. Note that this option is available with the next version of the tool.

/profile/backuppath/default = /sapcd09/COSMOS/HANA_CMS/upgrade/DEFAULT.PFL

- At the end of preprocessing, exit the SAPup tool (only ONE SAPup process left on OS level and “Tool start required” on the screen).

Modify SUM/abap/mem/INSTANCELIST.DMP and remove the “START” for the old SAP Instance:

OLD: wbaucs10,00,50013,…,STOP|START,…

NEW: wbaucs10, 00,50013,…,STOP,…

Restart the tool and continue.


January 2014 72

3.5.2 Check HANA DB with transaction DBACOCKPIT

Please Note that the DMO process includes also all post activity steps after the Upgrade and Migration as well. There is no need to run the Report RS_BW_POST_MIGRATION separately. The usage of the ASU toolbox is already mentioned before.

From the technical perspective your database migration process including the upgrade to NetWeaver BW 7.31/7.40 is complete.


January 2014 73

Please Note you manually have to create the DBCON entry for the HDB connection with the user

DBACOCKPIT

3.5.3 Application check with RSDU_TABLE_CONSISTENCY

Before you run the Report RSDU_TABLE_CONSISTENCY make sure the following corrections are applied:

Note 1953493 - RSHDB: RSDU_TABLE_CONSISTENCY NW7.30 SP12

Note 1953984 - SHDB: Development tool classes NW 7.30 SP12

Note 1888511 - RSHDB: Dev. RSDU_TABLE_CONSISTENCY NW 7.30 SP11

Note 1892492 - SHDB: Development Tool-Classes NW7.30 SP11

Note 1814339 - SHDB: Development tool classes NW7.30 SP10

Note 1814097 - RSHDB: Development RSDU_TABLE_CONSISTENCY NW7.30 SP10

Note 1939413 - SHDB: misleading security error in class cl_shdb_ddl

Note 1908854 - RSHDB: Hash partition keys of PSA tables without PARTNO














January 2014 74

Use the Back Button and show the current Issues from the Log.

DoubleClick on the selected Line in the Log list (1)


January 2014 75

Press the Save Button (2)

Continue with these Steps (1-2) for the other entries in the Log List as well.

Go back to the main entry screen and start the “Repair” option with “Execute in Background”

The Repair Job is now running as background job. Check either with SM50 or SM37.

Please Note that the following Notes cannot be implemented as SAP Note Correction. You must wait for

SP06 for NetWeaver 7.40, which includes the corrections for the Program RSDU_TABLE_CONCISTENCY.

Note 1953984 - SHDB: Development tool classes NW 7.30 SP12

Note 1888511 - RSHDB: Dev. RSDU_TABLE_CONSISTENCY NW 7.30 SP11

Note 1892492 - SHDB: Development Tool-Classes NW7.30 SP11








January 2014 76

3.5.4 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 1891981 - HANADB: Performance - missing views when updating master data

Note 1847728 - SQL errors 257 and 443 when creating BW column views

Note 1898395 - Secondary Index on InfoObject master data tables

Note 1860274 - SAP HANA adj. for BW Workspaces: Inactive CompositeProviders

Note 1942547 - SAP HANA: Improvement in the use of persistent database locks

3.5.5 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. However this Task List is implemented with the DMO procedure as well.








January 2014 77

3.5.6 Convert InfoCubes into in-memory optimized

Use Transaction RSMIGRHANADB to convert InfoCubes on demand, DSO objects remains unchanged.

Note 1731569 - SAP HANA DB: Check for correct InfoCube migration

Note 1925571 - BW on SAP HANA: Conversion of an InfoCube terminates

Note 1926112 - BW on SAP HANA: Merge after InfoCube compression

Note 1952076 - Report BW_POST_MIGRATION causes ABAP memory shortage

3.5.7 Convert DSO into in-memory optimized (obsolete)

The conversion of DSO into in-memory optimized is obsolete, when you fulfill the following pre-requisites:

- HANA 1.0 Rev. 57 or higher

- 7.30 SP10 or 7.31 SP08 or the mentioned Notes

Note 1873687 - Improve activation performance for SAP HANA-opt. BI Content

Note 1849498 - SAP HANA: Reconversion of SAP HANA-optimized DataStores

Note 1849497 - SAP HANA: Optimizing standard DataStore objects

Note 1873686 - BI Content 737/747 SP4: Use of in-memory optimized DSOs

Note 1947480 - SAP HANA: Possible data loss during reconversion of DataStores

Note 1940630 - Key Figure with Data Type DATS or TIMS and Aggr SUM on gives error on SAP HANA

Note 1937898 - SAPHANA: Enhanced consistency checks on reconversion of DataStores

Note 1919101 - DataStore: Error message in the system log: DSO_VERSION is missing

Note 1825665 - BW corrections for SAP HANA DB in BW 7.30 SP10

Note 1872391 - SMIGR_CREATE_DDL changes for HANA table placement

Note 1919101 - DataStore: Error message in the system log: DSO_VERSION is missing

Note 1937898 - SAPHANA: Enhanced consistency checks on reconversion of DataStores

Note 1947480 - SAP HANA: Possible data loss during reconversion of DataStores
















































January 2014 78

3.5.8 Check the updates for SNOTE corrections

If you have inconsistencies with the BW-PCA or the BW Housekeeping Task Lists, reset the NOTES implementation for these Notes, as they are Part of the SP08 for 7.31 now.

Furthermore you find these Notes useful for the current BW on HANA usage

Note 1883124 - SAP_DROP_TMPTABLES deletion of BWA/SAP HANA objects

Note 1843700 - F4 returns more value for compounding InfoObject

Note 1900357 - IOBJ with master data read class: Change of attributes

Note 1897595 - RSDU_RECREATE_CHGLG_HDB legt CalcView nicht an

Note 1879512 - Long runtime with many single value filters and compounding

Note 1900656 - Correction of SAP Note 1838299; IOBJ link with HANA field

Note 1897239 - RSPLS_SQL_SCRIPT_TOOL Fehlerhafter Umgang mit tech. IOBJNM

Note 1879512 - Long runtime with many single value filters and compounding

Note 1899247 - Unsuccessful deletion of BW column view

You can always look for the latest corrections in certain areas at http://service.sap.com/notes

with the keywords like:

Example: find all HANA DSO related SAP Note corrections after NetWeaver 7.31 SP09

SAPKW73110 HANA DSO

Example: find all HANA InfoCube related SAP Note corrections after NetWeaver 7.30 SP10

SAPKW73011 InfoCube










http://service.sap.com/notes


January 2014 79

3.6 List of manual Interactions with the DMO procedure

0.0% STACK CONFIGURATION FILE ................................................................................................................... 17

0.4% PREP_PRE_CHECKPROFREAD ................................................................................................................. 18

0.7% PREP_PRE_CHECK/SPAMCHK_INI .......................................................................................................... 19

1.9% PREP_INPUT/MIG2NDDB_INI .................................................................................................................... 19

7.1% PREP_PARSEETUP/CHECK4NOTES_TOOL ............................................................................................ 23

7.1% PREP_CONFIGURATION/INITSUBST - END (1) ....................................................................................... 23

7.1% PREP_CONFIGURATION/INITSUBST - (Tool Configuration) ................................................................. 24

7.6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG ............................................... 26

7.6% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG ............................................... 27

Transaction SLICENSE ......................................................................................................................................... 27

License Key Request (Internal View) ................................................................................................................... 27

SAP HANA Studio - HDB Connection .................................................................................................................. 28

7.7% PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/INSTHDBCLI ........................................................ 28

SAP HANA Studio - HDB Connection - 2 ............................................................................................................. 29

7.7% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/HDB_PREPARE ..................................................... 29

7.8% PREP_CONFIGURATIONS/SUBMOD_MIG_CONFIG/DETBWMODE .................................................... 30

8.0% PREP_CONFIGURATION/SUBMOD_MG_CONFIG/MIG2NDDB_AUX_PRE ........................................ 30

10.0% PREP_EXTENSION/EHP_INCLUSION .................................................................................................... 31

11.6% PREP_EXTENSIONS/IS_SELECT ............................................................................................................. 32

11.7% PREP_EXTENSIONS/IS_SELECT - 2 ........................................................................................................ 32

11.6% PREP_EXTENSIONS/IS_SELECT - 3 ........................................................................................................ 33

11.8% PREP_EXTENSION/ADDONKEY_CHECK ............................................................................................... 33

12.5% PREP_EXTENSIONS/BIND_PATCH ........................................................................................................ 34

12.5% PREP_EXTENSIONS/BIND_PATCH - include change request ............................................................. 35

13.0% PREP_EXTENSIONS/CONFLICT_CHECK - Note 889596 .................................................................... 35

13.7% PREP_INTERACTION/ADJUSTTPRP ...................................................................................................... 36

14.5% PREP_INSTALL/INITSHD ......................................................................................................................... 36

14.6% PREP_INSTALL/SHD INST_CPY ............................................................................................................. 36

15.9% PREP_INSTALL/JOB_FILL_TPF_CHK_PHASES - END (2) ................................................................... 37

20.9% PREP_PREPPROC/SUBMOD_MIG_BI_TASKS_PREP/MIG2NDDB_HANA_BW_PARAMS ............. 39

Edit table RSADMINA - BEX REQUEST ............................................................................................................... 39

22.9% PREP_PREPPROC/REQ_ASU_RUN ........................................................................................................ 40

Transaction /ASU/UPGRADE .............................................................................................................................. 40

22.9% MAIN_INIT/BEGIN - END (3) ................................................................................................................... 40

22.9% MAIN_INIT/REPACHK1 - check open transports .................................................................................. 41

24.4% MAIN_INIT/REPACK_CLONE - lock development environment ......................................................... 41

26.8% MAIN_SHDCRE/SUBMOD_SHDDBCLONE/DBCLONE ....................................................................... 42

29.7% MAIN_SHDINST/SUBMOD_SHSALIASCRE/EU_CLONE_CRE_SHDVIEWS ...................................... 42

40.2% MAIN_SHDRUNDDIC_UPG - long and intensive runtime phase - 1 ..................................................... 43

41.4% MAIN_SHDRUN/ACT_UPG - DDIC/000/SHD (11)................................................................................ 43

41.4% MAIN_SHDRUN/ACT_UPG ...................................................................................................................... 43

41.4% MAIN_SHDRUN/ACT_UPG - long and intensive runtime phase - 2 ..................................................... 44


January 2014 80

41.4% MAIN_SHDRUN/ACT_UPG - 2 ................................................................................................................. 44

51.0% SHADOW_IMPORT_INC - long and intensive runtime phase – 3 ......................................................... 45

51.2% - MAIN_SHDIMP/SUBMODE_SHDIMP/TABIM_REDUCE - Intensive Phase (CPU) .......................... 45

55.1% MAIN_SHDIMP/SUBMODE_SHD2_RUN/RUN_RSGEN - Intensive Phase (CPU) ............................. 45

58.1% MAIN_SHDIMP/SUBMOD_FATESTS/RUN_RSDB02CK_MOD ........................................................... 46

62.4% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_DT_CREATE......................................... 47

62.5% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/REQ_LANDSCAPE_REORG .............................................. 48

59.5% MAIN_SHDIMP/SUBMOD_MIG_UPTIME/EU_CLONE_MIG_UT - start parallel export/import...... 48

62.1% MAIN_DTTRANS/DOWNCONF_DTTRANS - preparations for downtime ........................................... 52

63.6% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK - backup request .................................................... 52

63.7% MAIN_DTTRANS/DOWNCONF_DTTRANS_BCK - disable archivemode ........................................... 53

63.6% MAIN_DTTRANS/SETSYNC_PREUP_DT_CONFIRM - END (4) .......................................................... 53

65.3% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/EU_CLONE_MIG_DT_RUN......................................... 54

66.2% MAIN_SWITCH/SUBMOD_MIG_DOWNTIME/SUBMOD_SWITCH_KERNEL/KX_SWITCH ............ 56

76.8% MAIN_NEWBAS/TABIM_UPG - long runtime phase 4 .......................................................................... 56

79.0% MAIN_NEWBAS/XPRAS_AIMMRG ......................................................................................................... 57

86.3% MAIN_UPTRANS/STARTSAP_PUPG ..................................................................................................... 57

86.8% MAIN_UPTRANS/UPCONF - END (5) ..................................................................................................... 58

86.8% MAIN_POSTP/SETUPGPAR_UPG_POST .............................................................................................. 59

90.2% MAIN_UPTRANS/REQ_ASCS_SWITCH_CLUSTER .............................................................................. 59

90.3% MAIN_UPTRANS/STARTSAP_PUPG – backup request ...................................................................... 59

90.8% MAIN_UPTRANS/UPCONF - end of downtime .....................................................................................60

91.9% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE ................60

94.8% MAIN_POSTP/RSDB02CK_END ............................................................................................................. 61

96% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP1/RUN_CUBE_CALC_VIEW_CREATE .................. 62

96.7% MAIN_POSTP/SUBMOD_MIG_BI_TASKS_POSTP2_REQRSRDA ...................................................... 62

98.0% MAIN_POSTP/SPAUINFO ....................................................................................................................... 63

99.8% MAIN_POSTP/RUN_RSDB02CHK_END ................................................................................................ 64

99.9% MAIN_POSTP/SAVELOGS ...................................................................................................................... 65

100% YOUR UPGRADE IS COMPLETE - END (6) .............................................................................................. 65

Back to Table of Content

www.sap.com/contactsap

http://scn.sap.com/docs/DOC-7856

sap first guidance using the dmo option to migrate bw on hana new

Documents