PUBLIC System Copy Guide System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP Target Audience n System administrators n Technology consultants Documentversion:1.0‒03/28/2008 Document History Caution Beforeyoustarttheimplementation,makesureyouhavethelatestversionofthisdocument. You canfindthelatestversiononSAPServiceMarketplacehttp://service.sap.com/instguides. Thefollowingtableprovidesanoverviewonthemostimportantdocumentchanges: Version Date Description 1.0 3/28/2008 InitialVersion 2/136 PUBLIC 03/28/2008 Table of Contents Chapter 1 HomogeneousandHeterogeneousSystemCopyforSAPSystemsBased onSAPNetWeaver7.0SR3 . . . . . . . . . . . . . . . . . . 7 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2 OnlineInformationfromSAP . . . . . . . . . . . . . . . . . . 8 1.3 SystemArchitecture . . . . . . . . . . . . . . . . . . . . . 8 1.4 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 8 1.5 Constraints . . . . . . . . . . . . . . . . . . . . . . . . 9 Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 11 Chapter 3 Preparations . . . . . . . . . . . . . . . . . . . . . . . . 19 3.1 GeneralTechnicalPreparations . . . . . . . . . . . . . . . . . 19 3.2 InstallingtheJavaRuntimeEnvironment . . . . . . . . . . . . . 21 Chapter 4 DatabaseIndependentSystemCopy . . . . . . . . . . . . . . 25 4.1 SystemCopyProcedure . . . . . . . . . . . . . . . . . . . . 26 4.2 GeneratingDDLStatements . . . . . . . . . . . . . . . . . . 29 4.3 PreparationforTableSplitting. . . . . . . . . . . . . . . . . . 30 4.4 PreparingtheExport . . . . . . . . . . . . . . . . . . . . . 33 4.5 ExportingtheSourceSystemUsingSAPinst . . . . . . . . . . . . . 34 4.5.1 RunningSAPinstonUNIXorWindowstoPerformtheExport . . . . . . 34 4.5.2 RunningSAPinstonSystemitoPerformtheExport . . . . . . . . . 41 4.5.2.1 PreparingtheWindowsHostfortheSAPSystemInstallation . . . . . . 41 4.5.2.2 PreparingaWindowsUserAccountandSystemiUserProfile . . . . . . 42 4.5.2.3 InstallingTMKSVRandCreatinganInstallationShare . . . . . . . . 44 4.5.2.4 StartingSAPinstonSystemi . . . . . . . . . . . . . . . . . . 47 4.5.3 RestartingR3loadProcesses . . . . . . . . . . . . . . . . . . 51 4.6 SettingUptheTargetSystem . . . . . . . . . . . . . . . . . . 53 4.6.1 InstallingtheTargetSystem . . . . . . . . . . . . . . . . . . 54 Chapter 5 Database-SpecificSystemCopy . . . . . . . . . . . . . . . . 57 5.1 Oracle-SpecificProcedure . . . . . . . . . . . . . . . . . . . 59 5.1.1 GeneratingtheControlFileStructure . . . . . . . . . . . . . . . 60 5.1.2 CreatinganOfflineBackup . . . . . . . . . . . . . . . . . . . 64 5.1.3 PreparingtheTargetSystem . . . . . . . . . . . . . . . . . . 64 03/28/2008 PUBLIC 3/136 5.1.4 RestoringtheDatabaseFilesontheTargetSystem . . . . . . . . . . 67 5.2 SAPMaxDB-SpecificProcedure . . . . . . . . . . . . . . . . . 68 5.3 MSSQLServer-SpecificProcedure . . . . . . . . . . . . . . . . 70 5.4 IBMDB2forLinux,UNIX,andWindowsSpecificProcedures . . . . . . 71 5.5 IBMDB2fori5/OSProcedure . . . . . . . . . . . . . . . . . . 74 5.6 IBMDB2forz/OSSpecificProcedure . . . . . . . . . . . . . . . 74 5.6.1 Step1: CheckConsistency . . . . . . . . . . . . . . . . . . . 76 5.6.2 Step2: StopandRestarttheSourceSystem . . . . . . . . . . . . . 76 5.6.3 Step3: RunSQLStatementsintheSourceSystem . . . . . . . . . . 77 5.6.3.1 SQLStatementNumber01 . . . . . . . . . . . . . . . . . . . 77 5.6.3.2 SQLStatementNumber02 . . . . . . . . . . . . . . . . . . . 77 5.6.3.3 SQLStatementNumber03 . . . . . . . . . . . . . . . . . . . 78 5.6.3.4 SQLStatementNumber04 . . . . . . . . . . . . . . . . . . . 79 5.6.3.5 SQLStatementNumber05 . . . . . . . . . . . . . . . . . . . 80 5.6.3.6 SQLStatementNumber06 . . . . . . . . . . . . . . . . . . . 81 5.6.3.7 SQLStatementNumber07 . . . . . . . . . . . . . . . . . . . 82 5.6.3.8 SQLStatementNumber08 . . . . . . . . . . . . . . . . . . . 83 5.6.3.9 SQLStatementNumber09 . . . . . . . . . . . . . . . . . . . 84 5.6.4 Step4: CapturingViewDefinitionswithDB2V9(iftheSchemaNameistobe Changed) . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.6.5 Step5: StoptheSourceSystem . . . . . . . . . . . . . . . . . 85 5.6.6 Step6: MakingCopiesofSourceDataSets . . . . . . . . . . . . . 85 5.6.7 Step7: CreatingtheTargetSystem . . . . . . . . . . . . . . . . 86 5.6.8 Step8: PrintingtheBootstrapDataSets . . . . . . . . . . . . . . 86 5.6.9 Step9a: ChangingtheBootstrapDataSets(BSDS) . . . . . . . . . . 87 5.6.10 Step9b: StarttheTargetSystem . . . . . . . . . . . . . . . . . 88 5.6.11 Step9c: CreatingaNewSTOGROUPUsingtheHLQoftheTargetSystem . . 89 5.6.12 Step9d: StoppingIndexSpaces . . . . . . . . . . . . . . . . . 89 5.6.13 Step9e: ChangingtheUser-DefinedIndexesintheDB2Catalog . . . . . 89 5.6.14 Step9f: RestarttheIndexSpaces . . . . . . . . . . . . . . . . . 89 5.6.15 Step9g: CreatingtheTemporaryFilesfortheDB2TargetSystem . . . . . 90 5.6.16 Step9h: ImplementingHLQoftheTargetSystemintheWorkFileDatabase . 90 5.6.17 Step9i: AdjustingtheDDFLocationNameandPortNumber . . . . . . 90 5.6.18 Step10(DB2V8andLower): ChangingtheVCAToftheTargetSystem . . . 91 5.6.19 Step10(DB2V9): ChangingtheVCAToftheTargetSystem . . . . . . . 92 5.6.20 Step11(DB2V9): ChangingtheSchemaoftheTargetSystem . . . . . . 92 5.6.21 Step12: AdaptingWLMApplicationEnvironmentsforDB2StoredProcedures 94 Chapter 6 Follow-UpActivities . . . . . . . . . . . . . . . . . . . . 95 6.1 PerformingFollow-UpActivitiesintheSourceSystem . . . . . . . . . 95 6.2 PerformingFollow-UpActivitiesintheTargetSystem . . . . . . . . . 95 6.2.1 PerformingFollow-UpActivitiesforABAP . . . . . . . . . . . . . 95 4/136 PUBLIC 03/28/2008 6.2.2 PerformingJobheadCorrectionafterHomogeneousSystemCopy . . . . 99 Chapter 7 AdditionalInformation . . . . . . . . . . . . . . . . . . . 101 7.1 R3loadProceduresUsingtheMigrationMonitor . . . . . . . . . . . 101 7.1.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . 101 7.1.2 AssigningDDLFilestoPackages . . . . . . . . . . . . . . . . . 109 7.1.3 DefiningGroupsofPackages . . . . . . . . . . . . . . . . . . 110 7.1.4 ProcessingSplitTables . . . . . . . . . . . . . . . . . . . . 110 7.1.5 StartingtheMigrationMonitor . . . . . . . . . . . . . . . . . 112 7.1.6 OutputFiles . . . . . . . . . . . . . . . . . . . . . . . . 117 7.1.7 InstallingtheTargetSystemUsingtheMigrationMonitor . . . . . . . 117 7.2 UsingSAPinstGUI . . . . . . . . . . . . . . . . . . . . . . 119 7.3 InterruptedInstallationwithSAPinst . . . . . . . . . . . . . . . 119 7.4 PerformingaRemoteExportUsingSAPinst . . . . . . . . . . . . . 122 7.4.1 PerformingaRemoteInstallationwithSAPinst(Optional) . . . . . . . 123 7.4.2 StartingSAPinstGUISeparately(Optional) . . . . . . . . . . . . . 124 03/28/2008 PUBLIC 5/136 6/136 PUBLIC 03/28/2008 HomogeneousandHeterogeneousSystemCopyforSAPSystemsBasedonSAPNetWeaver 1 7.0SR3 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 AsofSAPNetWeaver7.0,youcancopyABAPsystems,ABAP+JavasystemsandJavasystemsinonerun usingeitherdatabase-specificmethodsordatabase-independentmethods. 1.1 Terminology n HomogeneousSystemCopy Duringthesystemcopyyouusethesameoperatingsystemanddatabaseplatformastheoriginal system. n HeterogeneousSystemCopy Duringthesystemcopy,youchangeeithertheoperatingsystemorthedatabasesystem,orboth. Heterogeneoussystemcopyisasynonymformigration. n SourceSystemandTargetSystem TheSAPsystemcontainingtheoriginaldatabaseiscalledthesourcesystemandthesystemto whichthedatabasecopyistobeimportediscalledthetargetsystem. TheirSAPsystemnamesare abbreviatedtoSOURCE_SAPSIDandTARGET_SAPSID(Systemi: source_<SID>andtarget_<SID>). Thetermssourcedatabaseandtargetdatabasearealsousedinthisdescription. n SystemCopy DuplicationofanSAPsystem. CertainSAPparametersmightchangeinacopy. Whenyou performasystemcopy,SAPinstinstallsalltheinstancesagain,butitusesacopyofthesource systemdatabasetosetupthedatabase. n DatabaseCopy Database-dependentpartofthesystemcopy. n Placeholders Placeholderssuchas<SAPSID>areusedincommands. TheyareusedinthesamewayasintheSAP systeminstallationdocumentation. Youmustreplacethemwiththevaluesvalidforyoursite. Thefollowingadditionalplaceholdersareused: Placeholder Meaning Howtofindout <SAPSID> SAPsystemID <S_HOST> Systemnameofthesourcehost Commandhostname 03/28/2008 PUBLIC 7/136 HomogeneousandHeterogeneousSystemCopyforSAPSystemsBasedonSAPNetWeaver 1 7.0SR3 1.2 OnlineInformationfromSAP Placeholder Meaning Howtofindout <T_HOST> Systemnameofthetargethost Commandhostname <S_SAPSID> SAPsystemIDofthesourcesystem <SAPSID>oftheoriginalsystem <T_SAPSID> SAPsystemIDofthetargetsystem <SAPSID>ofthetargetsystem <S_DBSID> DatabaseIDofthesourcesystem <DBSID> oftheoriginalsystem <T_DBSID> DatabaseIDofthetargetsystem <DBSID>ofthetargetsystem 1.2 Online Information from SAP Moreinformationaboutsystemcopyisonlineavailableasfollows: n SAPSystemCopy&Migrationpageathttp://sdn.sap.com/irj/sdn/systemcopy. n SAPOS/DBMigrationpageathttp://service.sap.com/osdbmigration. Additionallytotheinformationcontainedonthispage,checktheSAPOS/DBMigrationPlanningGuide thatisavailableintheMediaLibrary. n SAPNote82478 Caution Onlyperformasystemcopyifyouhaveexperienceincopyingsystemsandgoodknowledgeofthe operatingsystem,thedatabase,andtheABAPDictionary. Onlyperformaheterogeneoussystem copyifyouareacertifiedsystemsupportconsultantoracertifiedSAPTechnicalConsultant. Note Ifyouencounterproblemsduringthesystemcopy,createacustomermessageusingthe applicationareaBC-INS-MIG. 1.3 System Architecture 1.4 Restrictions Thetargetsysteminstallationconsistsofboththetargetdatabaseandtargetinstances/application serversinstallations. Forthescenariosbelow,thefollowingholds: Onlyvalidfor: IBMDB2forLinuxandUNIXandWindows n TheoptionDeferredTableCreationisnotsupportedforload-basedsystemcopiesforSAPsystems thatarenotbasedonSAPNetWeaver7.0SR3. Endof: IBMDB2forLinuxandUNIXandWindows 8/136 PUBLIC 03/28/2008 HomogeneousandHeterogeneousSystemCopyforSAPSystemsBasedonSAPNetWeaver 1 7.0SR3 1.5 Constraints n Refreshofthedatabaseisnotsupported. Arefreshofthedatabasemeansthatonlythedatabase isloadedwiththecontentofadatabaseofadifferentsystem. Asinthisscenarionomigration controllerisinvoked,thisisnotsupported. n Copyingthedatabaseonlyisnotsupported. n Copyingthecentralinstanceonlyisnotsupported. Themigrationcontrollerdeletesalldialog instancesinthedatabase,sothesystemisnotcompleteanylonger. n Reinstallingthecentralinstancewithoutthedatabaseisnotsupported. Themigrationcontroller deletesalldialoginstancesinthedatabase,sothesystemisnotcompleteanylonger. 1.5 Constraints n SAPdoesnotsupportclienttransportasasystemcopymethod. Transportingproduction clientsisnotsupportedatall. YoucanuseclienttransportfortheinitialsetupofanSAPsystem infrastructure. Thisdocumentationdoesnotcovertheclientcopyprocedure. n Thisdocumentationdoesnotdescribehowtoexportandimportadatabasewiththeinstallation toolsforreorganizationpurposes. Usetheappropriatetoolsfordatabasereorganization,asSAP doesnotsupportthisinstallationoption. n Ifyouhavemademodificationsinyourdevelopmentsystemandwanttocopyyourquality assuranceorproductionsystemontothedevelopmentsystem,seeSAPNote130906. n ThisdocumentationdescribeshowtocopydatafromoneSAPsystemtoanotherSAPsystem basedonSAPNetWeaverApplicationServer. Thisdocumentationdoesnotdescribehowtocopy datafromnon-SAPsystemstoSAPsystems. n Ifyouwanttoconvertanon-UnicodesystemtoaUnicodesystemorperformthesystemcopyofa Unicodesystem,seeSAPNote551344. n ForthedevelopmentofJavaapplications,westronglyrecommendthatyoufollowtherules mentionedbelow. Otherwise,wecannotguaranteethatyoucancopyyourJavaenginelaterwith theSAPtoolstochangeyourunderlyingoperatingsystemand/ordatabasesystem. n SAPdoesnotgenerallysupportallDataArchivingoperationsafterasystemcopy. IfyouusedDataArchivinginthesourceorinthetargetsystem,accesstothecreatedarchivefile(s) fromthetargetsystemmaynotalwaysbepossible. Formoreinformation,seeSAPNote153433 andSystemLandscapeOptimizationathttp://service.sap.com/slo. Accesstoarchivedfilesfromthetargetsystemwithoutadedicatedarchivemigrationprojectis onlysupportedinthefollowingcases: l Yoursystemcopyclonesasourcesystemfornonproductivepurposes,onlyread-accesstothe previouslyarchiveddataisintendedfromthetargetsystem(noreloading),andyoudonot storearchivefilesusingArchiveLink/CMS. Youcaneithercopyallarchivefilestofilesystemsthatarenotsharedbetweenthesourceand thetargetsystem,oryouarrangenetworkaccessforappropriatearchivefilesharing. 03/28/2008 PUBLIC 9/136 HomogeneousandHeterogeneousSystemCopyforSAPSystemsBasedonSAPNetWeaver 1 7.0SR3 1.5 Constraints l Thesystemcopyisdonetoreplaceaproductivesystembyanewproductivesystem(for example,hardwaremigration),assumingthatthetargetsystemdidnotexistbeforeandthe sourcesystem’soperationisdiscontinuedafterthesystemcopy. YoumustnotchangethesystemIDduringsystemcopy,butarrangeforfileaccessand/or ArchiveLink/CMSconnectivity. Inallothercases,contactSAPSLOathttp://service.sap.com/[email protected]. n Whenyouperformasystemcopy,allsoftwareunitsorusagetypesinthesourcesystemarecopied tothetargetsystem. Thismeansthatnoneoftheusagetypesinthetargetsystemcanbeexcluded fromthesystemcopy,norcanyouselectusagetypes. n DosandDon’tsforsystemcopy: l Do: uSaveconfigurationdataandruntimedataintheJavadatabaseonly. Ifyouabsolutelyneed tosavethisdatatothefilesystemlevel,youmustusetheSoftwareDeploymentManager (SDM)tosavethedata. uFollowtheOpenSQLstandard. uMakesurethatallcommunicationrunsthroughthedatabasepool. l Don’t: uSaveanysystemandinfrastructure-specificdatainbusinessobjects. Useapointertothe centralstorageofsuchinformation,forexample: t SAPSystemIDandSID(SAPSID=SID=systemname) t Hostname t IPaddresses t ServicesandPorts t Logicaldestinationsandlogicalsystemnames t Othertechnicalinfrastructurenames uUsefilesystempersistency. uSetupdependenciesbetweenJavaandABAP. 10/136 PUBLIC 03/28/2008