20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog

INTRUSTSAP&ITBlog
(http://blog.intrust.co.il)

SAPBlog|SAPBASISBlog|SAPBASIS|SAPERP|SAP|SAPUpgrade|SAPSolutionManager|Linux|
Apache|Unix|MySQL

MigrationtoSAPHANAusingSAPDMO

(http://blog.intrust.co.il/2014/11/06/migrationtosap
hanausingsapdmo/)
SAP(http://blog.intrust.co.il/category/sap/),SAPBASIS(http://blog.intrust.co.il/category/sap/sap_basis/),SAP
Technology(http://blog.intrust.co.il/category/sap/sap_tech/)
06.11.2014

SAPHANAisaninmemoryplatformforprocessinghighvolumesofoperationaland
transactionaldatainrealtime.SAPHANAspeeduptheprocessbycompressingthedata,by
storingcolumnandrowbaseddatainthememory,RAMsitsnexttotheCPU,andoneCPUcan
havemultiplecoresandoneSAPHANAboxcanhavemorethanoneCPU,whichmakesSAP
HANA10000timesfaster.
TherearemanyoptionsavailabletomigratetoSAPHANA.CommonmethodstomigrateSAP
HANAcanbedoneeitherusingclassicalmethodorSAPDMOmethodology.SAPDMOislatest
methodologyfromSAPwhichisusedformigrationofSAPABAPsystemtoSAPHANA.SAP
recommendsusingSAPDMOtooltomigrateSAPsystem(SAPBWorSAPBusinessSuites)to
SAPHANA.Ihopethecontentoftheblogwouldbebeneficialtoallitsreadersandwould
accomplishitsintentnaturebyprovidingyoualltheimportantinformationaboutSAPDMO.
MigrationOptiontoSAPHANA:Therearemainlythreemigrationoptionsavailable
1)NewInstallation(usingSWPM)Inthisoptionweinstallnewsystemandtransform
anexistingdatatoSAPHANAbyperforming(selective)datamigration
2)ClassicalMigration(usingSUMandSWPM)Inthisoptionweupgradeorupdate
originalsystemtoreleasesupportedbySAPHANA(ifrequired)usingSUM,thenwemigrate
traditionaldatabasetoSAPHANAusingclassicalheterogeneousmigrationmethodusingSWPM
3)OnestepprocedureorinplaceupgradeandmigrationwithDMO(usingSUM)
Inthisoption,inplacecombinedupgradeanddatabasemigrationisdoneinonestep.

(http://blog.intrust.co.il/wp
content/uploads/2014/11/HANA1.png)

BenefitsofSAPDMO
Migrationstepsaresimplified
Systemupdateanddatabasemigrationarecombinedinonetool
BusinessDowntimeisreduced,Unicodeconversioncanbeincludedaswell
WellknowntoolSUMisused,withimprovedUI
Combinedprocedureneedsonlyonemaintenancephase(nottwo)

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

1/7

20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog
InplaceupgradeandmigrationkeepsapplicationserverandSystemIDstable(avoids
landscapechanges(SID,hostname,))
Originaldatabaseiskept,canbereactivatedasfallback
LowerprerequisitesforSAPandDBstartreleases
WellknowntoolSUMisused,withimprovedUI
DMOcanbeusedforSAPNetweaverBWandforSAPBusinessSuitessystems

TechnicalaspectandRestrictionsofSAPDMO
NocertificationrequiredforconsultantsusingDMOofSUM
NomigrationcheckservicerequiredforDMOonproductivesystems
StillthemigrationkeyhastobeenteredduringtheDMOrun,asR3loadrequiresthekey
DMOsupportsamigrationonlytoSAPHANADB
DMOworksonlyforASABAPbasedsystems
AdualstacksplitisnotbeincludedinDMO
StartreleaseofdifferentdatabasewhichsupportSAPDMO

(http://blog.intrust.co.il/wp
content/uploads/2014/11/HANA41.png)

PrerequisitesforDMO
SAPHANAappliancemustbeavailable
Dualstackhastobesplitbeforehand
OS/DBsoftwareupdatemayberequired
xmlfilehastobecreated(&SAPsoftwarefileshavetobedownloaded:MOPZ)
WebBrowserversionmighthavetobeupdated.Theuserinterface(UI)oftheDMO
procedureisbasedonSAPUI5andrequiresaspecificinternetbrowserversionasbelow
InternetExplorer9orhigher(notusingcompatibilityview)
Chrome28orhigher
Firefox21orhigher
SAPsoftwarewhichneedstodownloadfromSAPServiceMarketplaceforDMO
SPAM/SAINTupdateforSAPsourcereleaseneedstobedownloaded
SoftwareUpdateManager(SUM)latestversion(SP11)needstobedownloaded
SAPHostAgentlatestpatchneedstobedownloaded
SAPHANAClientinstallationfilesneedtobedownloaded
Migrationkeyneedtoberequested
SAPlicensefilefortargetsystemneedtoberequested
DMOTechniqueHowdoesinplaceupgradeandmigrationworks

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

2/7

20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog

SAPDMOisexecutedfromthehostwhereSAPPAS(primaryapplicationserverearlierknownas
centralinstance).TousetheDMO,youstarttheSoftwareupdateManagernotasdescribedin
SUMGuidebutbymeansoftheSAPHostAgentandtheSAPHostAgenthasbeenupdatedto
thelatestversion.
Step0.BrowserRequest>SUMTheDMOprocedureisstartedfromwithinabrowser,
sendinganHTTPrequesttotheSAPHostAgent,asshowninbelowscreen.

(http://blog.intrust.co.il/wp
content/uploads/2014/11/HANA2.png)

TostarttheSoftwareUpdateManagerviatheSAPHostAgent,youopenabrowserwindowand
enterthefollowinginternetaddressintheaddressbar:
https://<host>:1129/lmsl/sumabap/<SID>/doc/gui
Where<SID>hastobereplacedwiththeSystemID,1129isthehttpsportoftheSAPHost
Agent,lmslistheabbreviationforLifecycleManagementSoftwareLogistics,Usehttpinsteadof
httpsiftheSSLisnotconfiguredanduseport1128insteadof1129:
http://<hostname>:1128/lmsl/sumabap/<SID>/doc/gui
(http://%3chostname%3e:1128/lmsl/sumabap/%3cSID%3e/doc/gui)

TheSAPHostAgentrequestsauthorizationfromthebrowser,thisuserisusedtostarttheSUM.
AstheDMOprocedureisonlyworkingonASABAPbasedsystems(forwhichtheSAPupisthe
relevantSUMpart),theSAPupisstarted.
Step1.UptimeProcessingAftersomebasicconfigurationsettingslikecheckingthe
stack.xml,theSAPupwillstarttocreatetheshadowsystem.Theshadowsystemconsistsofa
shadowrepositoryandashadowinstance.TheshadowinstanceisrunningonthePAShost,
andisbasedontheshadowkernel.Theshadowkernelisthekernelforthesourcedatabase,
butforthetargetrelease.
Step2a.UptimeMigrationAftertheshadowrepositoryhasbeenbuildupcompletely,itis
copiedontothetargetdatabase,theSAPHANAdatabase.ThekernelexecutableR3loadis
triggeredbySAPuptoexecutethecopyoftheshadowrepository.
Step2b.DowntimeMigration(ApplicationData)Nowtheapplicationtableshavetobe
updatedtothenewrelease,sothesystemhastobeshutdowntopreventchangesonthe
applicationtables.Thedowntimemigrationisexecuted,inwhichthetargetkernelisusedin
addition:itisthekernelforthenewdatabase(SAPHANADB)andforthetargetrelease.
Step3.KernelSwitchandFinishingForthemigrationoftheapplicationdata,twoR3load
processesarerunninginparallel.ThefirstR3loadoftheshadowkernelexportsthedatafrom
thesourcedatabase,andthesecondR3loadprocessimportsthedataintothetargetdatabase
(SAPHANA).BothR3loadprocessesarerunningonthePAShost.Thetransferofthe
applicationdataincludestheupdateaccordingtothereleasechange.
Oncedataismigrated,theDMOprocessisfinished.Theshadowsystemisremoved,thesystem
isstarted,andthetargetkernelisnowusedforthesystem.Thesystemisnowmigratedtothe
targetdatabase,andupdatedtothetargetrelease.FinallystartstheSAPsystemwhichisnow
runningonthenewdatabaseandonthenewSAPsoftwarerelease.
ComparisonbetweenClassicalApproachvsSAPDMO

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

3/7

20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog

(http://blog.intrust.co.il/wp
content/uploads/2014/11/HANA3.png)

Prerequisite

ClassicalApproach

SAPDMO

Shouldsystemsupportpacklevel
shouldbeasperprerequisiteof
EHPupgrade.

SAPBusinessSuite7orabove&
SAPERP6.0orabove,SAP
NetWeaverBW7.0above,
componentSAP_BASIS7.0
shouldbeatleastSP17orhigher
andSAP_BWcomponenthasto
SP17isrequiredforSAPDMO
SP11

StartProcedure

UpgradeusingSUMand

SAPHostAgentisusedtostart

heterogeneousmigrationusing
SWPM

SUM

DifferentUI

SAPUI5isnotneeded

SUMstartsnewinterfacethatis
basedonSAPsUI(SAPUI5)

Download

ItsneededinSAPupgradeperform SUMpresumesstack.xmlfileis

Directory

usingSUM.

locatedindownloaddirectory.

Additionalkernel
Files

Norequiredinclassicalapproach

Inthisapproachweneedto
selectthekernelfilesofthetarget
softwarereleaseforboththeany
DBandtheSAPHANAdatabase

AdditionalSteps

Inclassicalapproach,upgradewill

Sincethemigrationisan

beexecutedusingSUMand
heterogeneousmigrationwillbe
executedusingSWPM

additionalpartoftheDMO
procedure(comparedtothe
updateprocedureoftheSUM).
duringtheDMOprocedureyou
willhavetoprovidespecific
informationformigrationandfor
theSAPHANAdatabase,suchas
amigrationkey,andproviding
accesstotheHANAdatabase
clientinstaller

Exportand
Import

SWPMtriggerstheR3loadto
exportandimportthedata.

SUMtriggerstheR3loadtoexport
andimportthedata.Furtheron,
theshadowrepositoryiscreated

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

4/7

20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog
onanyDBfirst,andthencopied
totheSAPHANAdatabase

Exportand
Import

Exportdumpiscreatedinthefile
systemandforimportexportfileis
copiedtotargetsystem

Exportandimportisdonein
memoryofPASorCIinstance.

EasyFallback

Fallbackispossiblebyapplying
databasebackup.SUMdoesnot
haveoptiontoreset.

Aneasyfallbacktothetraditional
databaseispossible,aslongas
thesourcedatabase(anyDB)and
theSUM
directory(oftheexistingupdate)
exist.Aresetshouldnotbedone
inaproductiveenvironmentafter
theendusersstartedworkingon
thenewsystemontheSAPHANA
database

DMOConcept

Notapplicableinclassical

TheSUMtoolcombinesall

approach.SUMisusedtoupgrade
thesystemandforheterogeneous

relevantstepsfortheinplace
migrationtoSAPHANA:Unicode

migrationuseSWPM

Conversion,Upgrade,and
Migration

SUMVersion

LatestSUM1.0SP10versioncan
beusedtoupgradeSAPsystem

SUM1.0SP08supportDMO.
LatestversionisSUM1.0SP10.

Unicode

SAPHANAdatabaserunson
Unicodesystemonlysoconversion
needtobedoneseparately.

UsingSUM1.0SP10version,Non
Unicodeconversionofsingle
codepagetoUnicodeispossible.
MDMPsystemsarenotsupported
fortheconversion

DualStackSplit

TomoveanyDBintoSAPHANA,

SincetheDMOworksonlywith

dualstacksplitisrequired.

ABAPsystems,soadualstack
splitmayberequiredbeforehand.

Incrementalconversionoftablesis
supportedinclassicalapproachof

Incrementalconversionoftables
isnotpossibleinaDMOrunand

upgrade(usingSUM)

willbeautomaticallydisabled
beforehand.

InstallingSAP

NeedtoinstallSAPHANAdatabase

Makesure,thatyouhave

HANADatabase

beforemigration

successfullyinstalledanSAP
HANAdatabaseandthatyouare
preparedtoentersystemdetails

ICNV

andthepasswordofuserSYSTEM
aswell

Gettingthe

Notapplicableforclassical

Makesure,thatyouhaveavalid

MigrationKeyfor

approach

migrationkeyforthenewSAP
HANAdatabase.

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

5/7

20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog
SAPHANA
Database

Gettingthe
LatestHANA

Notapplicableforclassical
approach

ClientSoftware

InstallHANAclientmanuallyon
theserverwhereyouexecute
DMO.Ifyourapplicationserver
OSisotherthanLinux.

Gettinga

Notapplicableforclassical

Makesure,thatyouhavea

PermanentSAP
License

approach

permanentSAPlicenseforyour
systemmigratedtoSAPHANA.

InstallingLatest
SAPHostAgent

Notapplicableforclassical
approach

ApplicabletoSAPDMOonly

ConfiguringSUM
forUsewithSAP
HostAgent

Notapplicableforclassical
approach

ApplicabletoSAPDMOonly

Downloading

Foranyupgradeweneedtofollow

Whenyouselectthekernelfiles

NecessaryFiles
from

this.

usingtheMaintenanceOptimizer,
takeintoconsiderationthatyou

Maintenance
Optimizer

havetoselectthekernelfilesof
thetargetsoftwarereleasefor
boththeanyDBandtheSAP
HANAdatabase.Thereasonis
thattheshadowinstanceis
createdforthetargetsoftware
releaseontheexistinganyDB
first,andthencopiedtotheSAP
HANAdatabase

StartingSUMvia

Notapplicableforclassical

SAPHostAgent

approach

ApplicabletoSAPDMOonly

SAPNotesreferencefortheDMO
1813548Databasemigrationoption(DMO)forSoftwareUpdateManager
1799545UsingDMOofSUMforSAPBWsystems
1875197UsingDMOofSUMforSAPBusinessSuitesystems
1031096InstallingPackageSAPHOSTAGENT
1968508Releasechange&SingleCodePageConversiontoUnicodewithDMO
1813548forthelatestinformationregardingDatabasemigrationoption(DMO)for
SoftwareUpdateManager
1926261CentralNoteSoftwareUpdateManager1.0SP11
Abbreviations
SWPMSoftwareProvisioningManager
SUMSoftwareUpdateManager

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

6/7

20/10/2016

MigrationtoSAPHANAusingSAPDMO|INTRUSTSAP&ITBlog

PostedbyMikiBarzilay@8:10PM

LeaveaReply

http://blog.intrust.co.il/2014/11/06/migrationtosaphanausingsapdmo/

7/7