• Screenshots and text on the upper part of the slide taken from
http://www.saphana.com/
• Lower left screenshot taken from session “TEC204 How to Migrate to SAP HANA
(2h lecture)”
• Lower right screenshot taken from session “EIM205 Implementing SAP
NetWeaver BW on SAP HANA – Lessons Learned (2h lecture)”
5
SAP NetWeaver BW loads data from connected application systems such as SAP
ERP, SAP CRM, SAP SRM – also known as SAP NetWeaver BW source systems
In the figures of this presentation, SAP NetWeaver BW systems are painted black,
SAP NetWeaver BW source systems are painted blue, and SAP NetWeaver powered
by SAP HANA are painted orange.
8
Next generation near-line SMART STORE solution for BW powered by HANA.
• Combining real-time analysis with cost-efficient data storage
• Cost- + Performance-Optimized EDW
• Data lifecycle management
• Data Aging strategy
Implementation of the SAP-NLS Solution
• https://scn.sap.com/docs/DOC-39627
Location of the SAP first guidance document – BW on HANA
■ http://scn.sap.com/docs/DOC-29915
15
SAP NetWeaver BW ABAP post-copy automation preparation of initial copy task list
(BW ABAP PCA Prepare)
Creates duplicated delta queue in SAP NetWeaver BW source system for
target SAP NetWeaver BW system
Enables parallel operation of both SAP NetWeaver BW systems with
optimized downtime
SAP NetWeaver BW ABAP post-copy automation initial copy task list (BW ABAP PCA
Initial Copy)
Performs activities required after the initial system copy of an SAP
NetWeaver BW system reliable
Reduces efforts and accelerates overall migration process
17
Parallel implementation approach
SAP strongly recommends you to follow a parallel approach in which you keep your
production landscape in place for the time being as a fallback. You can implement
SAP NetWeaver BW scenario by scenario, with the assurance that the existing
production landscape is still available as a fallback if required. This approach greatly
mitigates risk while simultaneously enabling you to familiarize yourself with the
administration and capabilities of SAP HANA. SAP strongly recommends that you
consider the high availability and backup/recovery procedures of SAP HANA before
starting to use it in production systems.
Pre-installed SAP HANA database
The SAP HANA appliance software with SAP HANA database is pre-installed by your
certified SAP partner on a server separate from the SAP NetWeaver BW system. For
SAP NetWeaver BW 7.3 you need SAP HANA SPS3 or higher. For SAP NetWeaver
BW 7.3 EhP1 you need SAP HANA SPS4 or higher. We recommend to apply the
latest available revision. Note that the components of SAP HANA and of the SAP
HANA database can only be installed by certified hardware partners on validated
hardware running a specific operating system. Any other system or content
developed with such systems is not supported by SAP. During the setup of the SAP
NetWeaver BW system the ABAP schema and the data are loaded remotely into the
SAP HANA database.
18
We recommend that you always download the latest versions of the SL tools with the
latest available Support Package Stack, as they contain the latest corrections and are
updated regularly (as stated in the Release Note for SL Toolset 1.0 SPS07 -
1758266).
Please note that you can only download the SL tools, but not the SL Toolset as such.
See all Details at – http://service.sap.com/sltoolset
The e2e Guide will be updated by the time of releasing the database migration option
(DMO) for BW migrations in Q3/2013
19
Step 7: Database migration + Unicode conversion – for more information about how
to combine heterogeneous system copy/DB migration with Unicode conversion, see
SAP Note 1051576 (Conversion of Single Code Page Systems to Unicode)
21
Additional Details in the following Notes:
• Note 1600929 - SAP BW powered by SAP inMemory DB – Information
• Note 1600066 - Available DBSL patches for NewDB
• Note 1639744 - heterogenious systemcopy NetWeaver 7.30 to HANA target DB
• Note 1657994 - SAP BW 7.30 powered by HANA - Special SP06
• Note 1715048 - BW 7.30 new features for installation or migration
• Note 1718576 - Migration from SAP HANA to another database system
• Note 1563579 - Central Release Note for Software Logistics Toolset 1.0
• Note 1680045 - Release Note for Software Provisioning Manager 1.0
• Note 1753759 - Migration/system copy to SAP HANA SWPM 1.0 SP0
• Note 1775293 - Migration/system copy to SAP HANA SWPM 1.0 SP1
• Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database
• Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database
• Note 1736976 - Sizing Report for BW on HANA
• Note 548016 - Conversion to Unicode
• Note 1051576 - Conversion of Single Code Page Systems to Unicode
• Installation/Operational Guides: http://help.sap.com/nw73bwhana
http://help.sap.com/nw731bwhana
25
For additional Information's regarding the checklist tool refer to the attachment of the
following Note:
Note 1729988 - SAP NetWeaver BW powered by SAP HANA - Checklist Tool
Attachment to the note contains two ABAP programs
■ ZBW_HANA_CHECKLIST (for BW 7.x and higher) tables
■ ZBW_HANA_CHECKLIST_3X (for lower BW releases)
Attachment to the note contains a How To Guide to perform checks in a matter of
minutes that would otherwise take hours or days to execute manually.
Automate the check of best practice guidelines for operations and prerequisites for
migration of an existing SAP NetWeaver BW deployment to the SAP HANA platform
Note: The checks are not necessarily complete or intended to replace existing tools
and checks (like the ASU-Toolbox or Early Watch Reports). The goal is rather to
automate and combine various checks that would have to be performed manually
otherwise.
Prerequisites for ZBW_HANA_CHECKLIST:
■ BW release 7.00 or higher
■ ST-PI add-on release 2008_1_700 SP06 or higher
Report /SDF/HANA_BW_SIZING (no additional script needed)
Note 1736976 - Sizing Report for BW on HANA
ABAP report developed to overcome deficiencies of DB scripts:
• DB independence
• Easier deployment
• Distinct size information for different types of tables (InfoCubes, DSOs, PSAs, …)
• Extrapolation of memory consumption based on future growth
• Room for more sophisticated sizing approaches (e.g. cold / hot data)
Availability
• Prerequisite: Support Tools Plug-in ST-PI 2008_1_7xx SP7 (released in October
2012)
• Preliminary version based on ST-PI 2008_1_7xx SP6 available with note 1736976
• Report: /SDF/HANA_BW_SIZING for full system sizing
• Function Module: /SDF/HANA_TABLE_SIZE for single tables or list of tables
Documentation
• Please read documentation attached to note 1736976 for details and tips how to
run the report
26
Transaction RSBATCH
See more details in SAP Help
■ http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/d2a551003c04e9e10
000000a42189c/frameset.htm
■ Clean/delete the messages for error logs (Note 1095924)
• Check: RSB_ANALYZE_ERRORLOG
• Clean: RSBM_ERRORLOG_DELETE
■ Run Report SAP_DROP_TMPTABLES and
RSAN_UT_RESULT_DROP_RESULTS (interim) to delete all kind of BW
specific temporary tables beforehand.
27
Report SMIGR_BIG_ROW_STORE_TABS (for row store tables)
Copy the file rowstorelist.txt to the following location /data/sap/<SID>/global/
Note 1659383 - RowStore List for SAP Netweaver on SAP HANA Database
.
28
Run Transaction DBACOCKPIT/DB02 (for row/column store tables) in the original
system and evaluate the possible tables
■ consider table splitting for export/import for the „top50“ largest tables
■ house keeping jobs, cleaning, reduction of data in the largest tables to
consider prior to the export
■ Note 1734333 - BW Pre and Post Upgrade and Migration Tasks
Furthermore run the sizing report in the source system provided in the following Notes:
■ Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database
■ Note 1736976 - Sizing Report for BW on HANA
• Report /SDF/HANA_BW_SIZING
• Report /SDF/HANA_TABLE_SIZE
• The improved Version 1.4 is included in ST-PI 2008_1_7xx SP7 and the
Implementation of this Note.
• The Scale out Recommendations are also included in the Note as
Attachment.
■ Note 1767880 - Non-active data concept for BW on SAP HANA DB
29
Report UMG_R3LOAD_RUNTIME_PREDICTION
Note 857081 - Unicode conversion: downtime estimate
If no detailed information about target ressources is available, defaults are used (see
example)
The program used simple algorythmen and includes the unicode conversion impact,
and it is a solid measure to calculate the overall times for export and import
A BW system held‘s a single non blended codepage, which is the easiest one to
convert.
Furthermore from 6.20 onwards coding in a NetWeaver system is already unicode
enabled, beside own customer based coding. As in BW Systems maily business
content is used and standard objects, the amount of potential non-unicode coding is
faily small
30
Transaction SPUMG
Always check for the latest corrections before you execute Transaction SPUMG
• Note 662215 - SPUMG and SUMG in Basis Release 6.20, 6.40 and 7.0X
• Note 1319517 - Unicode Collection Note
• Note 1051576 - Conversion of Single Code Page Systems to Unicode
• Note 1457258 - Correction instruction for the Additional Preparation Steps
• Note 837173 - RADCUCNT in Unicode Conversion: Collective Note
• Note 932779 - Unicode conversion - analysis of nametab problems
SPUMG after running the pre checks
31
Executed in original SAP NetWeaver BW system Technical name:
SAP_BW_COPY_INITIAL_PREPARE
Scope:
Prepare to easily bring new SAP NetWeaver BW system (to be created as copy) in consistent state and enable that it can immediately start to receive delta loads – Making complete reload of data from source system obsolete – Includes handling of transfer structure prefix (TSPREFIX) – an identifier
that distinguishes the transfer structures of data sources of different BW source systems, for which the new SAP NetWeaver BW system and the BW source system have to agree on a unique identifier
Enable migration with optimized downtime: – No downtime required in SAP NetWeaver BW source systems – Downtime in SAP NetWeaver BW system only for system copy
Key features: Automatic preparation of delta queue cloning in all involved systems Automatic cloning of delta queue Automatic synchronization of both delta queues (making re-initialization of
delta process obsolete)
Each task contains a description of the impl. activities, which is available in the Help column of the task list.
1. Select System Connections to be retained after Copy:
With this task, you specify for each connected SAP NetWeaver BW system and SAP NetWeaver BW
source system whether connection is retained and whether system is copied as well. For our migration use
case, you choose “Retain connection” (without copy of source system), so that delta queues in source
system will be cloned and synchronized with original SAP NetWeaver BW system in following steps.
2. Clone delta queues before System Copy
With this task, you enter new logical system name for target SAP NetWeaver BW system. The task
execution disables creation of delta-initialization requests until successful completion of task list and
checks if recently started delta-initialization requests have completed successfully. If this is the case, delta
queues for this SAP NetWeaver BW system are cloned within chosen SAP NetWeaver BW source
systems, using new logical system name.
3. Confirmation: Requests for all delta queues created? (user interaction)
After delta queues are cloned in chosen BW source systems, you have to trigger delta requests in the
original SAP NetWeaver BW system for all cloned delta queues and confirm this manually.
4. Stop RDA Daemons and Process Chains
After you have loaded delta for all cloned delta queues, system is prepared for actual copy. This task
prevents the creation of new process chain runs and stops the RDA (real-time data acquisition) daemons
to assure no data loads or process chains are currently running, in order to have target system in clean
state. Then, task list waits until all currently running process chains and daemons are finished.
5. Synchronize delta queues in BW source systems
This task checks whether delta requests have been triggered and completed successfully and creation and
repetition of delta requests is disabled until successful completion of task list. If this is true, cloned delta
queues for new logical system names are synchronized with those of original SAP NetWeaver BW system.
6. Confirmation: Database Copied or Exported? (user interaction)
This task lets you confirm that actual system copy is complete.
7. Resume Request Processing after Delta Queue Cloning
The creation of delta-initialization, delta and repeat requests is enabled again.
8. Restart RDA Daemons and Process Chains
Finally, execution of process chains is continued and RDA daemons are started again.
33
Report SMIGR_CREATE_DDL
The report cannot create the HDB specific sql prior to 7.30 SP05.
Always check for the latest corrections before you execute SMIGR_CREATE_DDL
The Unicode Migration has no influence for HDB, as the command is called
automatically unicode based
Crosscheck the availability of the following files prior to the import into HDB:
■ The DDLHDB.TPL file in <export>/ABAP/DB (Note 1639744)
■ The (correct) *.SQL files with report SMIGR_CREATE_DDL in
<export>/ABAP/DB/HDB (Note 1600929)
■ The updated rowstorelist.txt in <drive>:\usr\sap\<SID>\SYS\global (Notes
1617020 and 1659383)
■ Note 1659383 - RowStore list for SAP NetWeaver in SAP HANA database
for Systems based on 7.30/7.31, with 7.40 this is part of ABAP DDIC
■ Note 1783238 - SMIGR_CREATE_DDL: Estimated Row Count for Facttables
■ Note 1593998 - SMIGR_CREATE_DDL for MSSQL
Contains Explanations for BW specific tables, e.g. /BIC/A,B* etc.
■ Hinweis 1815547 - Row/ColumnStore Check ohne rowstorelist.txt
heterogeneous system copy can be done without external row store list now
34
older SAPinst versions (SAP NetWeaver 7.30, used for early BW migrations) do
not show "in-memory computing engine“ use MaxDB
use the original sapinst Version for 7.30/7.31 to create the system export (weather
it is homogeneous or heterogeneous).
In the meantime the Software Provisioning Manager 1.0 is available, which is
recommended by SAP. Please follow the Instructions in the SWPM 1.0 GUI.
use the standard settings for splitting the STR files
the current supported procedure is the asynchronous export/import on file base
Note 1563579 - Central Release Note for Software Logistics Toolset 1.0
Note 1680045 - Release Note for Software Provisioning Manager 1.0
Note 1683455 - Inst. SAP NetWeaver BW 7.31: Windows / SAP HANA Database
Note 1706931 - Inst. SAP Sys. Based on NW 7.3 incl. EHPs: SAP HANA DB, Win
Note 1702987 - SAP Release Note for SL Toolset 1.0 SPS05
Note 1716219 - SAP Release Note for SL Toolset 1.0 SPS06
Note 1753759 - Migration/system copy to SAP HANA SWPM 1.0 SP0
Note 1775293 - Migration/system copy to SAP HANA SWPM 1.0 SP1
Note 1806935 - SAP HANA: Corrupt database after R3load import
Note 1722395 - SAP HANA: Known problems during migration or installation
Note 1686144 - Dual-Stack Split 2.0 SP2 for Systems Based on SAP NetWeaver
Note 1655335 - Use Cases for Splitting Dual-Stack Systems
35
Location of the SAP first guidance document – BW on HANA
■ http://scn.sap.com/docs/DOC-29915
36
37
Software Logistics Toolset 1.0 - OVERVIEW AND CONCEPT
SL Toolset Basic Concept:
Software Logistics Toolset (SL Toolset) stands for a product-independent delivery
channel for software logistics tools.
It enables the delivery of up-to date software logistics tools and a unified consumption
experience with the target to reduce total cost of ownership.
For further general information, see Central Release Note for Software Logistics
Toolset 1.0 – SAP Note 1563579
Connection to SAP NetWeaver BW source:
• Remote Function Call (RFC): standard SAP interface for communication between SAP systems
• Application Link Enabling (ALE): technology for setting up and operating distributed applications
• RSBASIDOC: this table stores the assignment of SAP NetWeaver BW source system to SAP NetWeaver
BW - some of the fields are SLOGSYS (logical system name of source system) and RLOGSYS (receiver
system - logical system name of SAP NetWeaver BW system), but also TSPREFIX (two-character identifier
to distinguish transfer structures of data sources of different BW source systems) to re-connect the target
SAP NetWeaver BW system with the cloned delta queue
For copies in SAP NetWeaver BW landscapes, several aspects have to be considered:
Connections
SAP NetWeaver BW connection is known at both partners copies + name changes of one partner
also affect partner that was not copied, has to be adapted after copy
Most issues with system copy in SAP NetWeaver BW environments stem from connections, not from
complicated customizing
Metadata
SAP NetWeaver BW has a lot of metadata (such as data models)
Dependent on (and named like) source system connection metadata has to be recovered after copy
Generation
SAP NetWeaver BW metadata objects generate DDIC structures and programs naming of these
generated objects is dependent on connection and must therefore be recovered after copy
Landscape
One SAP NetWeaver BW system might be connected to several source systems, one source system
might be connected to several SAP NetWeaver BW systems when copying more than one system,
whole landscape has to be considered
BW ABAP PCA Initial Copy: Restore of connections, which will be retained as you specified in task Select System
Connections to be Retained after Copy. New destinations to remote systems are checked. Next, any naming
conflicts for connection prefix are resolved, and connection is re-established on source system
Report RS_BW_POST_MIGRATION - detailed view of the steps (Variant
SAP&POSTMGRHDB)
The report can be used on HDB based BW systems from 7.30 SP05 onwards.
Always check for the latest corrections before you execute
RS_BW_POST_MIGRATION
Note 1695112 - Activities in BW after migrating to the SAP HANA database
Note 1746147 - BW 7.30 SP8: Enhanchements for Report RS_BW_POST_MIGRATION
Hinweis 1825305 - BW Column Views nach automatischer Migration auf SAP HANA
Hinweis 1815547 - Row/ColumnStore Check ohne rowstorelist.txt
Optional: Transaction RSSGPCLA
ODS/DTP migration after BW Systemcopy
43
Report RSDU_TABLE_CONSISTENCY
The report can be used on HDB based BW systems from 7.30 SP07 onwards.
Always check for the latest corrections before you execute the Report
In case of errors in the section «Find fact tables with a secondary index»
(cl_scen_sec_index) check, if the report RS_BW_POST_MIGRATION was running
successfully (section 3-4)
• Note 1695778 - Partitioning BW tables in SAP HANA database
• Note 1750965 – change of RowStore/ColumnStore
• Note 1798612 - SHDB: Einbau eines zu SP8 verlorenen optionalen Parameters
• Note 1756099 - RSHDB: Consistency check for tables (7.30 SP9)
• Note 1814097 - RSHDB: Development RSDU_TABLE_CONSISTENCY NW7.30
SP10
Additional Notes to consider: 1660125 and 1674377
/usr/sap/<SID>/SYS/global/rowstorelist.txt
■ Note 1659383 - RowStore List for SAP Netweaver on SAP HANA Database
■ Note 1695778 - Partitioning BW tables in SAP HANA database
44
Transaction DBACOCKPIT/DB02
The Transaction can be used in all HDB based BW systems from 7.30 SP05
onwards.
Always check for the latest corrections before you execute Reports
RS_NAMT_CLEAR and SAP_UPDATE_DBDIFF
Note 1669250 - DBDIFF entries for HANA DB-optimized change log tables
Note 1640741 - Different database user for DBA Cockpit for SAP HANA
Note 1691096 - Transport of InfoCubes from and to SAP HANA database
45
Transaction RSMIGRHANADB
The Transaction can be used on HDB based BW systems from 7.30 SP07 onwards.
• Note 1767880 - Non-active data concept for BW on SAP HANA DB
• Note 1736976 - Sizing Report for BW on HANA
• Note 1749848 - DSO: SAP HANA-optimized DSOs for quantity conversion
• Note 1776749 - DSO: SAP HANA conversion for write-optimized DSOs
• Note 1790134 - Error message for RSMIGRHANADB due to incorrect partitioning
• Note 1644694 - Backing up data and adjusting SAP HANA for BW Workspaces
• Note 1849497 - SAP HANA: Optimizing standard DataStore objects
• Note 1849498 - SAPHANA: Rückkonvertierung von SAP HANA-opt. DataStores
Convert InfoCubes:
• http://help.sap.com/saphelp_nw73/helpdata/en/14/268a8602b241d0b6df1e6f3028c702/fra
meset.htm
Convert Data Store Objects:
• http://help.sap.com/saphelp_nw73ehp1/helpdata/en/ab/ff28d090744388b67595684bb962
06/frameset.htm
• Note 1740633 - HANA: Converting DataStore objects with large data volume
As of SAP HANA Revision 30, you can configure the critical merge process for HANA in
such a way that it optimizes the uncompressed data structures (delta indexes) already
during an ongoing conversion to release surplus memory again. ALTER SYSTEM
ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM')
SET ( 'mergedog', 'critical_merge_decision_func') = 'DRC>200'
WITH RECONFIGURE
46
Details of the Solution:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000757418&
47
49
With parallel operation of original + new system, you enable non-disruptive
usage and real-time comparison
Enabled by automated delta queue cloning + synchronization (BW ABAP
PCA prepare)
– Optimized downtime, especially for SAP NetWeaver BW source system
– Delta queue cloning not possible before
BW ABAP PCA initial copy cleans up and configures target system automatically
Crucial for reliable and fast migration process
Available for regular initial copies of SAP NetWeaver BW systems under
license of SAP NetWeaver Landscape Virtualization Management
Profit from a rapid deployment solution that provides end-to-end solution for
migrating existing SAP NetWeaver BW to SAP HANA without disruption of
existing content – with a possible go live in as little as 8 weeks! Overall, migration made easier, faster and more reliable by
presented offerings from SAP
© 2013 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, 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.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate 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.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.
www.sap.com
Top Related