Migrating your HANA 1.0 Database to HANA 2.0

HANA 2.0

By now, you’ve probably heard that SAP has released their HANA 2.0 database on IBM Power Systems.

SAP Software Supported on HANA 2.0

SAP Note 2420699 “Release of SAP HANA Database 2.0 for older SAP Versions” lays out the basics for the SAP software that is currently supported on HANA 2.0 database. Notably, a lot of the Business Suite components are not listed, just ECC 6.0 EHP 8 so far. Note 1600929 lists BW Release 7.50 as the version to use with HANA 2.0. Therefore, you will have to plan some upgrade work to go along with the HANA database upgrade to 2.0.

Why Migrating HANA 2.0 from x86 to IBM Power Systems is easier than ever

IBM Power Systems supports a little endian version of SAP HANA, just like x86 appliances. That means that you can move data seamlessly between HANA 2.0 on Power Systems and HANA 2.0 on x86 because they are both little endian. Clients can use backup and restore or HANA Data Replication to move databases between x86 and IBM Power Systems, making it easier to replace scale-out HANA x86 appliances with the better-performing and more easily managed Power server in a Tailored Datacenter Integration (TDI) configuration (SAP TDI FAQ).

Certain revision levels of HANA 1.0 on x86 can also use the backup and restore approach to convert the database to HANA 2.0 on Power.

Migrating Data from HANA 1.0 to HANA 2.0 on IBM Power Systems

If you are currently running HANA 1.0 on Power Systems and would like to migrate to HANA 2.0 on Power Systems, the recommended path to migrate your existing SAP data in big endian format in a HANA 1.0 database to little endian format in a new HANA 2.0 on Power Systems database is to use the new SAP system migration tool for big endian to little endian on Power architectures which is described in the “SAP_HANA_System_Migration_en.pdf” attachment to multiple SAP notes such as SAP Note 2380257 “SAP HANA Platform 2.0 SPS 00 Release Note”
The new SAP system migration tool uses Smart Data Integration (SDI) to efficiently move the data from the source to the target. This process SDI to define the tables in the source database as remote objects in the target database, then to migrate the data directly across the network from the source to the target.

The advantage of using SDI is that all the data is moved across the network so there is not disk I/O time. There are additional functions built into the tools to allow for large tables to be split into multiple jobs.

My IBM colleague, Walter Orb, who works at the IBM SAP International Competency Center has these recommendations for using the SDI approach:
“It is important that you are on the SPS01 level of HANA 2.0, as there are a number of improvements that went into the new revision. Also make sure that you are using the latest available version of the dpagent. The migration tool tries to parallelize on the partition level. For very large tables, that's not enough and this is where the splitThreshold comes into play. But again, a lot of improvements in that area went into the SPS01 release, so don't waste your time with the SPS00 release.”

Mark is a Lead Migration Consultant for the IBM Migration Factory. He has 20 years of experience with IBM and more than 30 years of experience in the IT industry.

Like what you just read? To receive technical tips and articles directly in your inbox twice per month, sign up for the EXTRA e-newsletter here.

comments powered by Disqus



2018 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.

A Blue Business Future

New IBM strategy promises ease of use for SMB customers

A Bountiful Harvest

IBM shares the fruits of its labor with faster Power processors, solid-state disk and more

Adding to the Family

IBM announces two new System i Express models—the 515 and the 525

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
IBMi News Sign Up Today! Past News Letters