SAP BW Migration To HANA-eBook

SAP BW Migration to HANA
Published: 7 September 2016

Terry Kempis & Linh Nguyen
Preparation
Post-processing
Upgrade
Migrate
Any DB
Introduction
This eBook is a result of a 3-parts blog series which provided an overview
and explanation of major steps and considerations for BW on HANA
upgrade and migrations, based on a trial BW 7.5 system and HANA SPS10
Part 1: Migrating a BW system from anyDB (any database) to HANA
involves Preparatory work in the BW system
Part 2: SUM DMO Tool for SAP Upgrade and Migration
Part 3: Post processing on the migrated system
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com
BW Migration to HANA
Part 1 of 3
Preparation in BW System
By OZSoft Consulting for ITConductor.com

Editor: Linh Nguyen
ITConductor.com
Introduction
This series of publication intends to provide an overview and
explanation of major steps and considerations for BW on
HANA migrations
Migrating a BW system from anyDB (any database) to HANA
involves
1.
2.
3.
Preparatory work in the BW system

DMO and Actual migration
Post processing on the migrated systems
This first part focuses on the preparation tasks on the BW

system.

Editor: Linh Nguyen
ITConductor.com

Preparation is a collaborative work between Basis, BW
support team and ABAP/development team.
Create a production copy Sandbox
Best practice in doing an upgrade is to create and use a
production copy sandbox first before starting with the
development system. It offers the following benefits:
1. Identify potential issue and get a fix ready before hitting
the other systems used in development and production.
2. Allows optimization of the process to reduce the
downtime and impact to the business. The update and
migrate tool, SUMs DMO, provides a special feature which
allows repetition of the downtime for optimization.

Editor: Linh Nguyen
ITConductor.com
Target BW and HANA DB

Recommended to always use the latest BW release/level for
the target system.
The target HANA system has been installed as per SAP
requirements.
The target support package should be the latest, and ideally
installed with the DSP (datacenter service point).
The capacity should meet the result from the sizing report discussed at later stage.

Editor: Linh Nguyen
ITConductor.com
BW Housekeeping/data clean-up
Similar to preparing a BW system for upgrade and/or Unicode
conversion, reduction of the data volume should be done normally referred to as BW housekeeping tasks. This will
reduce the data to be exported from the source system and
imported to the target DB. This will reduce the downtime of
the system during the upgrade, and it also reduces the
capacity requirement of the target HANA DB.
The normal housekeeping/clean-up tasks involves the BW
functional team, which includes
PSA reduction and change log

Infocube compression
Deletion of temporary objects
Deletion of statistics data
In addition, the SAP BW Migration Cockpit includes a

Housekeeping section for common housekeeping tasks.
Editor: Linh Nguyen
ITConductor.com
SAP BW Migration Cockpit for SAP HANA

SAP provides the BW migration cockpit program, which is the
main entry point to all the tools for the BW to HANA
migration preparation. It also includes some post-task items
(e.g. ASU, Down-sizing Near-line Storage, extended tables)

Editor: Linh Nguyen
ITConductor.com
Migration Cockpit
From the cockpit, all the tools needed for can be executed (e.g.
sizing, list program codes that can be optimized for HANA). Also
incorporated previous tools like ASU, normal housekeeping tasks,
BW Checks.
Each tab has different tasks within it. If you hover to the right side
Documentation, it provides either
OSS note which contains the ABAP program to be uploaded to perform
the check, and how-to-guide, e.g. BW Checklist for SAP HANA
Link to the relevant SAP HELP page
The cockpit is installed by creating ABAP program

ZBW_HANA_MIGRATION_COCKPIT from OSS note 1909597, which
also contains the guide SAP Migration Cockpit.
The document SAP First Guidance - BW Housekeeping and BWPCA covers some of the major checks/tools
HANA checklist
Sizing Check
Note Analyzer
Editor: Linh Nguyen
ITConductor.com
Checks tab
This section has several items
Upgrade Paths
Install ABAP program from
OSS note 2296693, which
also contains the
documentation.
Sample report below note
that DMO will be used

Editor: Linh Nguyen
ITConductor.com
Checklist Tool
Install the program
ZBW_HANA_CHECKLIST
from OSS note 1729988
which also contains two
documents:
How to Checklist Tool for
SAP BW powered by SAP
HANA
SAP BW powered by SAP
HANA Checklist Tool

Editor: Linh Nguyen
ITConductor.com
10
Sample BW Checklist Report

Editor: Linh Nguyen
ITConductor.com
11
Other Checks
The lower screen contains more checks. The Documentation
tab points to the SAP Help page.

Editor: Linh Nguyen
ITConductor.com
12
BW (consistency) Checks
These are standard BW
transactions/programs.
BW Object Checks this is
transaction RSRV
BEx Query Check this runs the

ABAP program
ANALYZE_RSZ_TABLES
Editor: Linh Nguyen
ITConductor.com
13
Planning Function Check

This run program RSPLS_PLANNING_HDB_ANALYSIS it
checks if a planning function can be executed in memory, with
the following default screen
How to check whether a Planning function or
Disaggregation in PAK is executed in Memory provides
very good explanation on this subject.

Editor: Linh Nguyen
ITConductor.com
14
Sizing
This tab contains several sections
Sizing Tool
The tool provides an estimated size of eventual BW system
in the HANA database.
Note that the figure from this report does not include other
memory requirements within HANA (e.g. calculation space).
OSS note 2296290 provides more detail/guide on how the
sizing program works, prerequisite, how to run it, and how
to read the summary report. One of the attached guide also
provide overview on HANA BW Scale Out.

Editor: Linh Nguyen
ITConductor.com
15
Sizing Tool
Provides several
options/factors/simulation
Output report is written into
a file, into the work
directory
The report has several
sections:
Source DB contents, e.g. size
of different table types (e.g.
infocubes, PSA)

Editor: Linh Nguyen
ITConductor.com
16
Sizing Tool Sample Report

Minimum Sizing
Requirements - with
recommended number of
nodes
Sizing Details

Editor: Linh Nguyen
ITConductor.com
17
Iterative Sizing
Run the sizing tool several
times with or without selecting
any option to compare results
of the clean-up/data reduction
activities:
Change the filename of the
output result for comparison
purposes.
Result of each table are shown
in the reports Table Details,
broken down by row/column
types, and for each table estimated ABAP and HANA size.

Editor: Linh Nguyen
There is also an CSV file

containing the Table Detail, for
easier comparison, containing
total_size, ABAP size, HANA
size.
Note that some of options can
only be implemented after the
migration, e.g. Dynamic
Tiering. However, it is a good
idea to run this several times
with several options to see the
impact if they are done after
the migration, i.e. what if.
Reference : OSS note 1736976
Sizing Report for BW on
HANA, which contains two
document on sizing and Scaleout.
ITConductor.com
18
Future Growth Simulation

This option allows you to extrapolate the size based on
growth factor or absolute number.
With the example above, the report will show minimum and
recommended size per year

Editor: Linh Nguyen
ITConductor.com
19
Non-Active Data, Dynamic Tiering

This options are another what-if scenario, e.g. what if
dynamic tiering is used.
Non-Active Data
This is in relation to the new multi-colored - refer to blog
SAP BW on HANA : Data Classification (HOT/WARM/COLD)
If selected, there will be a section Non-Active data in the
report.

Editor: Linh Nguyen
ITConductor.com
20
Dynamic Tiering
BW on HANA introduced the multi-temperature data. Briefly,
data are classified as:
HOT data accessed very often, should stay in HANA memory
WARM data infrequent access, using HANA dynamic tiering (i.e.
extended storage, extended table), e.g. data more than 2 years old
COLD data sporadic/infrequent access, using Near-line Storage
(NLS)
PSA tables and Change Logs are considered non-active

automatically Reference OSS Note
References:
Big Data Management in HANA BW.pdf from OSS note 1983178

Editor: Linh Nguyen
ITConductor.com
21
Dynamic Tiering - Brief

Dynamic Tiering (aka extended storage) is another way of
reducing HANA memory footprint by moving some data into
Dynamic storage server.
For example, data from an infocube which are more 12 months
old can be moved to the dynamic storage, hence only the current
years data are the only ones that occupy the HANA memory. This
is done by
1. defining another table with the same definition as the
current table, with additional extended storage clause.
2. moving the data from the current table to the extended
table
3. creating a view with a join of the current table and the
extended table. If an SQL issue a select SQL which include
data from the extended table, then it is retrieved from the
extended storage into the Dynamic Tiering servers
memory - but still does not occupy HANA memory
References:
SAP HANA Dynamic Tiering for Using Extended Tables
OSS note 1983178 - HANA Dynamic Tiering

Editor: Linh Nguyen
ITConductor.com
22
Memory Configurations
Allowed Memory Configurations
Down-sizing (configuration) these are post-task activities
The document points to SAP Help portal on the subjects of NLS and
Data Archiving
Down-sizing (execution)
The Move to Extended Tables document refers to
OSS note 2557636 conversion of PSA and write-optimized DSO in
SAP-HANA extended tables which also contains document Changing
the Multi-Temperature Category of BW objects.

Editor: Linh Nguyen
ITConductor.com
23
Housekeeping
The tasks in this section are
to be used in conjunction
with the ASU tool (under
Migration). This has 2
sections:
Housekeeping Automation this is transaction STC01
Housekeeping Tasks

Editor: Linh Nguyen
ITConductor.com
24
Migration
ASU Toolbox:
Refer to 1000009 - ASU
Toolbox 2008, upload the
relevant DMO task list
(ASU_BW_70x_75x_DMO_3
.zip). As in other upgrade,
there are pre and posttasks.
There are other tools on this
tab, but note below.

Editor: Linh Nguyen
ITConductor.com
25
WHM
This contains the
Transformation Finder. There
are several options/selection
on the transformation
Install ABAP program
ZBC_TRANSFORMATION_FIND
ER from OSS note 1908367 ,
which also contains the SAP
BW Transformation Finder, a
how-to-guide.
The following blog provides a
good understanding of the
transformation and links to
various blogs on this subject,
HANA Transformations
Editor: Linh Nguyen
ITConductor.com
26
Optimization
Program to scan custom ABAP codes for potential

optimization for HANA.
Install the ABAP program from OSS note 1847431, which also
contain the how-to-guide.

Editor: Linh Nguyen
ITConductor.com
27
Next SUM DMO and Migration

Now that we have prepared the source BW system, we are
ready to proceed with SAP SUM (Software Update Manager)
using DMO (Database Migration Option) to carry out the
upgrade and migration of the BW system from anyDB to BW
on HANA.
Stay tuned for the next section DMO and Migration.

Editor: Linh Nguyen
ITConductor.com
28
BW Migration to HANA
Upgrade
Migrate
Any DB
Part 2 of 3
SUM DMO Tool for SAP Upgrade & Migration

Editor: Linh Nguyen
ITConductor.com
29
Introduction
This is Part 2 of the series of publication which provides an
overview and explanation of major steps and considerations
for BW on HANA migrations
involves
1.
2.
3.

SUM DMO Tool for SAP Upgrade and Migration
Post processing on the migrated systems
This part focuses on the tool used for the migration, prerequisites, optimization and the actual migration steps.

Editor: Linh Nguyen
ITConductor.com
30
DMO, Guides
SUMs DMO (Database Migration Option) is the tool to update and
migrate anyDB (any Database) to HANA.
HINT: It cannot be used for pure migration purposes only! If your current
release/level already meet the HANA requirement and does not want to
do go the latest release/level, then at least update other package (e.g.
ST-PI) so that you will have stack xml which is needed by DMO.
Before embarking on doing migration using DMO, first go through the
following
SAP First Guidance - Using the DMO Option to Migrate BW on HANA,
Database Migration Option (DMO) of SUM - Introduction - it provides a
very good introduction of DMO and contains links to other related blog
(e.g. optimization, technical background).
All notes in this document and the steps followed in this migration
exercise were based on the cookbook, blogs and the references below.
The central note 2257362 for DMO with SUM 1.0 SP 17
Update of SAP Systems using SUM 17 < read this one to appreciate
the SL Common UI, features, etc.
Database Migration Option of SUM SP17 - Target Database SAP HANA
Editor: Linh Nguyen
ITConductor.com
31
DMO (Database Migration Option)

DMO is an inplace-migration using SUM (Software Update Manager). The
target PAS will replace the source PAS in the same host, using same ID, network
configuration
SOURCE PAS
TARGET PAS
Source and Target System for this exercise

(TARGET) SID ABA
BASIS 750/04
HANA DB
KERNEL 745 patch 200
(SOURCE) SID ABA

BASIS 750/02
SYBASE DB
DMO needs two sets of kernel
Target software release of the source
DB i.e. 745 patch 200 for SYBASE DB

Editor: Linh Nguyen
Target
Target software
software release
release of
of the
the target
target DB
DB i.e.
i.e. 745
745
patch
200
for
HANA
DB
patch 200 for HANA DB
ITConductor.com
32
DMO uses memory pipe mode

The export and import occurs within the same server, so data
is passed through the same memory segment
EXPORT
Kernel : 745/200 SYBASE
Memory
PP
SOURCE
SYBASE DB
Import
Kernel: 745/200 HANA
TARGET
HANA DB
Reference: DMO: comparing pipe and file mode for R3load

Editor: Linh Nguyen
ITConductor.com
33
DMO - more
DMOs migration repetition for testing purposes of the downtime phase
See: 4.3.4 Using the Migration Repetition Option for Testing of the DMO Guide
DMO supports MDC

The target database in DMO can be a tenant database. DMO has option to
create the target DB, if it does not exist yet.
DMO Unicode conversion
DMO can convert a non-Unicode system to Unicode at the same
downtime. Note that only single-code page is supported, not multi-code
(MDMP).
DMO SQL DDL generation

DMO generates the DDL in one of its phase, so there is no need to
manually run this.
Editor: Linh Nguyen
ITConductor.com
34
SLUIGUI going around
The tab in the right hand side are Legend, More, Task List, Logs,
Breakpoints. Clicking on any tab to expand, click again on the tab to
hide.
Editor: Linh Nguyen
ITConductor.com
35
SLUIGUI - MORE
Under More,
SUM Guide this will take you to SAP marketplace, right to SUM guide page
SUM Note this will take you to the central note of the current SUM you are using
SAP Help Portal goes to https://help.sap.com
Log Tail this is the log tail viewer. You can choose any log file, e.g. SAPup.log

Editor: Linh Nguyen
ITConductor.com
36
SLUIGI Utilities and Task List
Utilities can also be viewed directly from the extended viewer <server>:1128/lmsl/sumabap/<SID>/doc/sluigui_ext/
Editor: Linh Nguyen
ITConductor.com
37
SLUIGUI LOGS, BREAKPOINTS

Breakpoints can be set from here
Logs can be viewed without going
to the OS
V

Editor: Linh Nguyen
ITConductor.com
38
Observer Mode
This feature allows monitoring for the

update process from a mobile device or
desktop. To use,
1. Prepare the observer mode (create

new user <sid>obs, add a password,
then add group SAPSYS to <sid>obs.
2. Start the observer monitor with the
following URL, login with the <sid>obs
user
<server>:1128/lmsl/sumobserver/ABA/mo
nitor/index.html

Editor: Linh Nguyen
ITConductor.com
39
Resetting DMO, source DB instance after migration

RESETing the DMO
After migration, the source database remains intact. Its on the state before the shutdown. If
for whatever reason, it can be used again after a reset which is provided by DMO. Note that
the reset will delete data from the target HANA DB.
Reference: DMO technical background
Source database after migration
After the migration testing, we installed another PAS pointing to the source database so we
ended up with two running systems:
1. A migrated system in HANA
2. The original source ASE system
The normal steps in installing a Distributed system are:
1. ASCS instance
2. Database Instance
3. Primary Application System (PAS)
But only step 1 and 3 are needed. Note that by skipping step 2, the profile parameter,
environment (env.csh) and DB (dbenc.csh) variables may have some missing items.
Fortunately, that DMO backup the source system versions, including the kernel for
reference/re-use.
This is handy for production copy sandbox for comparison purposes, but not on
production. Ensure that this is totally isolated from normal use.
Editor: Linh Nguyen
ITConductor.com
40
DMO - Optimization
During the days of Combined Upgrade and Unicode
Conversion (CUUC) downtime optimization was a challenge.
You need to manually specify table split, which tables to do
first, etc.
With DMO, tools and features are available to reduce the
downtime, including optimized table splitting
Benchmark Tool
Migration repetition

Editor: Linh Nguyen
ITConductor.com
41
Benchmarking tool
DMOs benchmarking (migration) tool is
available to simulate the export and import
process to check the migration rate/speed. It
has repetition option to enable optimization by
adjusting the process parameters (SQL uptime,
SQL downtime, R3load uptime, R3load
downtime).
This should be done before the DMO and
against a production copy which mirrors the
production setting, (i.e. capacity, network,
target HANA)
HINT: benchmark both export and import to
simulate production run
For more details, refer to the following

Optimizing DMO Performance

Editor: Linh Nguyen
ITConductor.com
42
Migration Repetition/Optimizing downtime

DMO provides migration repetition to help
reduce the system downtime.
For each DMO run, the following files are
created
MIGRATE_UT/DT_DUR.XML - contains
statistics for each migrated table
UPGANA.XML
These files can be use for subsequent DMO run

to optimize and reduce the downtime. See
DMO Guide
Cookbook

Editor: Linh Nguyen
ITConductor.com
DMO
UPGANA.XML
MIGRATE_*_DUR.XML
43
Preparations/Checks - 1
Migration Key - Generate the system migration key
License - Generate the license for the target migrated system (i.e. based on HANA
DB).
Time zone
Make sure both source system and the HANA severs have the same time zone
settings and within SAP (transaction STZAC).
DB Free space
As a shadow system is created, there should be at least 50Gb database free space,
or more, depending on the existing components.
SAPLOCALHOST/Hostname
Make sure that the profile parameter SAPLOCALHOST matches the hostname in
SM51.
WARNING: Hostname 'XXXXXXXX' is different from hostname 'YYYYYYYY' system runs with!
If you encounter the issue in the shadow instance, stop SAPup, stop the shadow
instance, edit the parameter in the SHADOW profile directory, restart the shadow
instance. Resume the process.
Editor: Linh Nguyen
ITConductor.com
44
SAP Host agent install/update to the latest version
SPAM Update to the latest SPAM, or download and extract it into
/trans/EPS/in
SAPCAR download the latest SAPCAR for extraction
HANA Client
Download and extract the HANA client
For LINUX PAS, the DMO will install it as part of the migration
For Windows PAS, install it manually before starting the DMO.
DOWNLOAD/Stack.xml
The Maintenance Planner is now used to generate the stack.xml
and download the target components, including the latest SUM,
ACPs, and kernel (for all platforms)
Target HANA DB log mode
Set the log_mode parameter to overwrite
Editor: Linh Nguyen
ITConductor.com
45
Deletion of some BW objects
In one of the dialog, you will enter values as per below. Discuss with your BW team.
Delete temporary BW query bookmarks older than ... days:: 99

Delete sent BW query bookmarks older than ... days:: 9
Delete BW traces older than ... days:: 99
Delete BW statistics older than ... days:: 9
SUM
After extracting the SUM package, change owner to <sid>adm and the group to sapsys
As root, register to host agent cd <download directory>/SUM
./STARTUP confighostagent <SID>
Normal upgrade preparations are not included in this document, e.g. pre-downtime tasks
like queue processing, stopping jobs, locking users, etc.

Editor: Linh Nguyen
ITConductor.com
46
Migration Steps/Screenshots - 1
Start DMO
http://sid-aba-aba:/1128/lmsl/sumabap/<SID>/doc/sluigui
Extracts from SAPupConsole.log note that only DMO-related
phases are included here
======= This is SAPup release lmt_008 V53.000 - all engines are running =======
=========== Welcome to Software Update Manager ===========
Important information for this program is included in * SAP Note 2223738* and
further SAP Notes mentioned therein. The keyword is included in the relevant
product-specific SAP Note. Read the current version before you start preparing
the procedure and check the SAP Note again for changes before you start the
procedure.

Editor: Linh Nguyen
ITConductor.com
47
>> 2016/08/05 13:14:32 START OF PHASE PREP_INPUT/MIG2NDDB_INI
=========== Database Migration Option ===========
Enter the target database type:
01) - No migration
02) * SAP HANA
DATABASE TYPE: SAP HANA
=========== Migration Parameters ===========
Select tables for table comparison checks.
01) * Do not compare table contents
02) - Operate on all tables
3) - Operate on selected tables only
Provide a valid migration key for installation number "0123456789".
For a detailed description of generating the key, see SAP note *317096* .
Migration Key: 1W5gdEM50D001eqtdQQ011e3

Editor: Linh Nguyen
ITConductor.com
48
SAP HANA SCALE OUT
Are you running a SAP HANA Scale Out Landscape as a target for this migration?
*If so, you can enable the landscape reorganization during the preprocessing
of the migration.* .
01) Execute Landscape Reorg
Enter a number/range/"all" to change selection or "ok" or <ENTER> to complete
Migration Repetition
Test cycle
This option will stop the tool after the downtime migration phase, enabling a
simple repetition of it to optimize the procedure by tuning the parameters
(like R3load processes). You should in no case use this option for a
productive run!
NOT for
01) X Enable Migration Repetition Option
production
Choose an execution strategy for transaction SGEN.
Select option Do not start ABAP load generation during the update. There is more flexibility
when doing it as a post-task (e.g. use more servers)
Author: Terry Kempis Editor: Linh

Nguyen
ITConductor.com
49
PREP_CONFIGURATION/SUBMOD_MIG_INSTCLIENT/HDB_INSTCLIENT
=========== Target database client ===========

The tool needs access to the target database client.
Enter the following information:
Path to "hdbinst" for client installation:
(This is where the HANA DB Client will be installed in LINUX. For Windows, this should be
installed before starting DMO)
=========== Database Migration Initialization ===========
You are going to migrate your system to a new database.
Enter the following parameters of the target database:
Target Hostname: xxxxxxxx
Enter the SID and instance number of the target database instance (might be
different from your SAP system):
SID of the target database: A4H
Target Instance Number: 00
Editor: Linh Nguyen
Tenant DB name. If it does not exist yet, it will

be created during the process. See next slide
ITConductor.com
50
Enter the path of the SAP License file for your migrated SAP system:
Target System License:
(License key based on HANA DB)
*Additional Information:*
Specify the database connectivity data of the target database to be used for
the SAP system migration.
In case you are using a SAP HANA multitenant database container, specify the
connectivity data of the target database tenant.
In case you are using a SAP HANA multitenant database container, and want to
create a new database tenant, specify the connectivity data of the database
tenant to be created.
Enter password for target database user "SYSTEM".
Enter password for target database SYSTEMDB superuser (MultiDB).

Editor: Linh Nguyen
ITConductor.com
51
=========== Parameters for BW-Specific reports ===========
Within the next phases certain BI housekeeping tasks will be performed. Please
decide which data shall be deleted in the database.
**Caution:* The data deleted during the next phases as specified in the fields
below cannot be restored by resetting update process.*
Enter the amount of data to be deleted:

Delete temporary BW query bookmarks older than ... days:: 99
Delete sent BW query bookmarks older than ... days:: 9
Delete BW traces older than ... days:: 99
Delete BW statistics older than ... days:: 9

Editor: Linh Nguyen
ITConductor.com
Values agreed with BW

team
52
=========== Perform Scale Up (Single Node) Prerequisite on SAP HANA if necessary ===========
*Action Required (if condition is met):*
*You decided to NOT run the SAP HANA Landscape Reorganization.
However, if you run an SAP HANA Single-Node system with scale-up, you must
manually import a file with specific SQL-information to enable the optimal
table partition.
Carry out the following procedure:*
1. Download the appropriate file that is in the attachment of the following
SAP Notes:
* For SAP Business Warehouse on SAP HANA, see SAP Note 1908075. From the
attachment TABLE_PLACEMENT_BW.zip, select the suitable SQL-file.
* For SAP Business Suite on SAP HANA or SAP S/4HANA, see SAP Note 1899817.
Choose the attachment: TABLE_PLACEMENT_ERP_* or TABLE_PLACEMENT_S4H_*
according to the version and SP level of the target system.
2. Edit the downloaded file by replacing all occurrences of $$PLACEHOLDER with
your SAP<sid>.
3. Import the edited files to SAP HANA using one of the following commands on
OS level of the managed system:
* */usr/sap/ABA/hdbclient/hdbsql -U SYSTEM -I <filename> -E 1*
* */usr/sap/ABA/hdbclient/hdbsql -U SUPER -I <filename> -E 1*
4. After the import, continue with the migration procedure.

Editor: Linh Nguyen
ITConductor.com
53
Migration Steps/Screenshots
Export/Import/Downtime
Checks after phase
MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_
MIG_DT_RUN were negative!
Last error code set:
Found 12 failed export processes
REPEAT some errors due to export and import server
Found 64 failed import processes
capacity (e.g. memory)
<< 2016/08/10 18:35:33 END OF PHASE
MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_
MIG_DT_RUN
Downtime reached, migration repetition prompt

=========== Testcycle ===========
Downtime migration finished successfully.
01) - Yes, initialize the downtime migration phase and repeat
02) * No, continue with next phase
Do you want to repeat the downtime migration phase?:
No, continue with next phase
Editor: Linh Nguyen
ITConductor.com
54
Next Post-processing on the New System

Now that we have prepared the source BW system, and
We have completed the SAP SUM (Software Update
Manager) upgrade & migration using DMO (Database
Migration Option) for the BW system from anyDB to BW on
HANA.
Stay tuned for the next section Post-processing on the
Upgraded/Migrated System.

Editor: Linh Nguyen
ITConductor.com
55
BW Migration
to HANA
Preparation
Post-processing
Upgrade
Migrate
Any DB
Part 3 of 3
Post-processing on the Migrated System

Editor: Linh Nguyen
ITConductor.com
56
Introduction
This is Part 3 of the series of publication which provides an
overview and explanation of major steps and considerations
for BW on HANA migrations
involves
1. Preparatory work in the BW system
2. SUM DMO Tool for SAP Upgrade and Migration
3. Post processing on the migrated system
This part focuses on post-processing, which

includes standard tasks after upgrade and HANAspecific post-tasks.
Editor: Linh Nguyen
ITConductor.com
57
Post-processing - general
After migrating a BW system to HANA, there are two general groups of
post-tasks
1. Standard tasks after a release upgrade or Unicode conversion
2. HANA-specific tasks
After the downtime processing AND before doing anything:

1. Create a backup of the database
2. Configure HANA parameter log_mode to normal
3. Configure HANA parameter enable_auto_log_backup to YES

Editor: Linh Nguyen
ITConductor.com
58
Standard post tasks

Below are some post tasks after a release upgrade/or Unicode conversion.
The list is not exhaustive, not necessarily in sequence, and does not
include site-specific process.
Adapt dialog instances to the new release/kernel Run SECSTORE (OSS note 816861)
Run SICK
Configure SAINT parallelism (OSS note 1309506)
For each instances, run SM51 and SM21
RZ12 configure number of free WPs
Run SGEN (SAP_BASIS first, then the rest)
DB13 maintain standard jobs
Reconfigure/adapt 3rd party products
RSA1 check source systems - activate
Import profile parameters
Solution Manager configuration
Note that the DMO tool, automatically run RS_BW_POST_MIGRATION

during its post-processing phase, but there maybe a case of running some
steps.
Editor: Linh Nguyen
ITConductor.com
59
HANA-specific post-tasks
The cookbook, SAP First Guidance DMO BW on HANA
lists down the tasks and steps in detail.
OSS notes, blogs that were referenced while doing the
steps, (i.e. to get more background information), are added
in this document.
Some of the tasks need to be a collaborative work with the
BW Administrators and Security team.

Editor: Linh Nguyen
ITConductor.com
60
HANA-specific post-tasks - 1
Task Activate new HANA server functions (scriptserver)
Login to the system database container to adjust the scripserver section
of the daemon.ini and nameserver.ini
Task Enable Dynamic Range Partitioning feature of DataStore objects
Refer to OSS note 2081135 for background on this Dynamic Range

Partitioning
Task Install Application Function Library (AFL)
For the brief on AFL, refer to SAP help page - AFL
For HANA Analysis Process (HAP) background, refer to First Guidance
SAP BW 7.40 powever by HANA - HANA Analysis Process
Editor: Linh Nguyen
ITConductor.com
61
Task Configuring DBMS User Management for SAP HANA
This task need to be done in collaboration with the security team
For more detail/additional document, refer to DBMS Users in SAP NW ABAP
7.40
Additional information Configuring DBMS User Management for SAP HANA
SQL syntax to get the SQL_port for the connection information in DBCO
select sql_port from sys.m.services where service_name = indexserver
SQL syntax to list DBMS users assigned roles

select * from effective_roles where user_name = <DBMS_USER>
If you remove the assigned DBMS user through SU91, the DBMS user will notbe
deleted from the HANA side. Remove it through program RSUSR_DBMS_USERS

Editor: Linh Nguyen
ITConductor.com
62
DBMS roles that are available for DBMS users

Editor: Linh Nguyen
ITConductor.com
63
Task Install Smart Data Access (SDA) Drivers
Reference: SAP help page SDA
Task Transaction RS3HANA_CHECK/ADMIN
This is for SAP HANA view. For background, refer to SAP First Guidance SAP BW 7.40 on HANA - View Generation
Task Create CDS views after migration
CDS stands for Core Data services

For brief on CDS, see Enhanced ABAP development with CDS

Editor: Linh Nguyen
ITConductor.com
64
Task RowStore to Column conversion
In our migration, only empty, temporary
tables were listed during the check
Task Check HANA with DBACOCKPIT
No issue found
Task RS_BW_POST_MIGRATION
As the source system was already on 750/02, all mentioned OSS notes
were already in place and no issue found.

Editor: Linh Nguyen
ITConductor.com
65
Task ASU Tool box
There are some follow-up post-tasks
Task RSDU_TABLE_CONSISTENCY
For more information, refer to Table Consistency Check for BW Tables on
HANA
Task RSDDB_INDEX_CREATE_MASS
For more information, refer to BWonHANA: InfoProvider column views
Editor: Linh Nguyen
ITConductor.com
66
HANA-specific post-tasks 7
Task - Migration Check SHDB_MIGRATION_CHECK
Note 1785060 - Recommendations for
performing the migration to SAP HANA
Task - RS_BW_POST_MIGRATION
If OSS note 2060342 has been implemented, then run step 12 Create
views for InfoProvider. This was not performed since the system is
already 7.50
Task - Repair inconsistent PSA tables
No issue found
Editor: Linh Nguyen
ITConductor.com
67
Task - Regenerate all Transformations
For reference, see Transformation Consistency check programs
Refer to OSS note 1408161 Program for transformation activation
The note refers to required input parameters
Transformation ID can be derived from table RSTRAN

Editor: Linh Nguyen
ITConductor.com
68
Task - Convert InfoCubes into in-memory optimized
It is highly recommended to convert existing InfoCubes to SAP HANAoptimized Infocubes to reduce the data load. Note that after the migration to
HANA, all newly created InfoCubes will be automatically be SAP HANAoptimized Infocubes.
References:
Converting Standard InfoCubes to SAP HANA-Optimized InfoCubes
Aspects of the HANA-optimized InfoCube
To check if an infocube is optimized, go to RSA1, under Settings Subtype =
SAP HANA optimized Infocube.

Editor: Linh Nguyen
ITConductor.com
69
Task Migrate BW Workspaces
Report RS_BW_POST_MIGRATION steps 12 - 15
For explanation on Unload Priority, refer to SAP BW on HANA: Data

Classification

Editor: Linh Nguyen
ITConductor.com
70
The following tasks were not performed in our migration, some of them
maybe required to take advantage of simpler data models on BW, and
especially with the new BW/4HANA, just announced by SAP in Sep-2016:
Converting DataStore Objects and Infocubes into advanced DSO
Convert MultiProvider to CompositeProvider

Editor: Linh Nguyen
ITConductor.com
71
Summary
The SAP BW upgrade and migration to SAP HANA has over
100 steps, and each environment maybe a little different
based on the usage scenario and customer specific data
encountered. However, these publication seek to provide an
overview of the processes for planning and guidance so that
you can confidently create a roadmap for BW on HANA and
even next generation BW/4HANA migration involving:
Preparation of the source BW system
Carrying out the SAP SUM (Software Update Manager)
upgrade & migration using DMO (Database Migration
Option) for the BW system from anyDB to BW on HANA.
Finally, post-processing on the Upgraded/Migrated System.
GOOD LUCK!
Editor: Linh Nguyen
ITConductor.com
72
About OZSOFT
OZSOFT CONSULTING HEADQUARTER
20660 Stevens Creek Blvd., Suite 261
Cupertino, CA 95014. USA
Email: [email protected]
Worldwide: +1 (408) 416-2482
North America Toll-free: +1 (888) 876-2482
http://www.ozsoft-consulting.com
Company
> Delivering IT, with Peace of Mind! Specializing in SAP since 1996
Services
SAP on AWS (Amazon Web Services) Cloud-based Managed Services
Plan, Practice, Perform & Perfect IT
SAP Implementation: SAP Netweaver, SAP HANA, SAP BusinessObjects architected for secure, scalable,
high-performance and availability, as well as time/cost efficiencies.
SAP OS/DB Migration: Certified migrations using best practices to mitigate risks and minimize downtime.
Combined Upgrade and Migration support.
Cloud Excellence Operations: IT Process Automation increases operating efficiencies, and agility best
suited for cloud services. We provide partial to fully managed services while your SAP environment runs
at AWS, using IT-Conductor for Cloud-based monitoring & automation.
Software Solutions
Full suite of SAP systems monitoring solutions for Microsoft Systems Center Operations Manager (SCOM) focus on
Availability, Alerting, and Performance Management:
SAP Management Pack
HANA Management Pack
BusinessObjects Management Pack
ASE Management Pack

Editor: Linh Nguyen
ITConductor.com
73
About IT-Conductor
IT-CONDUCTOR HEADQUARTER
20660 Stevens Creek Blvd., Suite 261
Cupertino, CA 95014. USA
Email: [email protected]
Worldwide: +1 (408) 416-2565
North America Toll-free: +1 (888) 666-2899
http://www.itconductor.com
Company
> Stop Guessing, Start Managing!
IT-Conductor is the AMMO you need to:
Automate
Monitor
Manage &
Optimize your SAP Performance & Operations including Performance Testing/Tuning as a Service.
IT-Conductor was officially founded in 2014 after more than 10 years of turning a big idea of automating IT into a practical
solution. The big idea is to enable customers to "Stop Guessing, and Start Managing" their enterprise IT application
environment. It's all about the integrated ability to collect vast amount of application and supporting infrastructure
instrumentation data into standardized and time-synchronized intelligence that can be action upon.
> Monitor SAP WITHOUT Installation!

The power of IT-Conductor lies in it's ease of access through a cloud platform to simply hook up to your environment via a
secured connection and start agentlessly monitor and manage the applications, databases, hosts and related infrastructure
components. Templates make application discovery fast and easy to go from monitoring to managing in minutes!
___________________________________________________________________________________________________________________________________________
2016 IT-Conductor, Inc. and/or its affiliates. All rights reserved. IT-Conductor is a trademark of IT-Conductor, Inc. or its affiliates. This publication may
not be reproduced or distributed in any form without IT-Conductors prior written permission. If you are authorized to access this publication, your use
of it is subject to the Terms of Service and Copyright and Trademarks posted on itconductor.com. The information contained in this publication has
been obtained from sources believed to be reliable or from IT-Conductors own experience and research. IT-Conductor disclaims all warranties as to the
accuracy, completeness or adequacy of such information and shall have no liability for errors, omissions or inadequacies in such information. This
publication consists of the opinions of IT-Conductor organization and should not be construed as statements of fact. The opinions expressed herein are
subject to change without notice. Although IT-Conductor may include a discussion of related legal issues, IT-Conductor does not provide legal advice or
services and its research should not be construed or used as such.

Editor: Linh Nguyen
ITConductor.com
74
Let
itconductor.com
Any Questions?
@itconductor
Contact Info:
Linh Nguyen
[email protected]
Terry Kempis
[email protected]
75

SAP BW Migration To HANA-eBook

Uploaded by

Copyright:

Available Formats

SAP BW Migration To HANA-eBook

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP BW Migration To HANA-eBook

Uploaded by

Copyright:

Available Formats

SAP BW Migration to HANA

Published: 7 September 2016

Author: Terry Kempis

Preparatory work in the BW system

This first part focuses on the preparation tasks on the BW

Author: Terry Kempis

Preparatory work in the BW system

Author: Terry Kempis

Target BW and HANA DB

Author: Terry Kempis

PSA reduction and change log

In addition, the SAP BW Migration Cockpit includes a

SAP BW Migration Cockpit for SAP HANA

Author: Terry Kempis

The cockpit is installed by creating ABAP program

Author: Terry Kempis

Author: Terry Kempis

Sample BW Checklist Report

Author: Terry Kempis

Author: Terry Kempis

BEx Query Check this runs the

Planning Function Check

Author: Terry Kempis

Author: Terry Kempis

Author: Terry Kempis

Sizing Tool Sample Report

Author: Terry Kempis

Author: Terry Kempis

There is also an CSV file

Future Growth Simulation

Author: Terry Kempis

Non-Active Data, Dynamic Tiering

Author: Terry Kempis

PSA tables and Change Logs are considered non-active

Author: Terry Kempis

Dynamic Tiering - Brief

Author: Terry Kempis

Author: Terry Kempis

Author: Terry Kempis

Author: Terry Kempis

Program to scan custom ABAP codes for potential

Author: Terry Kempis

Next SUM DMO and Migration

Author: Terry Kempis

Author: Terry Kempis

Preparatory work in the BW system

Author: Terry Kempis

DMO (Database Migration Option)

Source and Target System for this exercise

(SOURCE) SID ABA

Author: Terry Kempis

DMO uses memory pipe mode

Reference: DMO: comparing pipe and file mode for R3load

Author: Terry Kempis

DMO supports MDC

DMO SQL DDL generation

SLUIGUI going around

Author: Terry Kempis

SLUIGI Utilities and Task List