TADM70.docx

Tas1 (: In an Oracle OS igration the database ust be installed ?ith dictionary7anaged tables!aces because o3 certain reasons. $3ter the test i!ort@ soe large tables and indexes sho? a huge aount o3 extents. ,. The custoer ada!ted the +ext (xtents values in the source database on a regular base. Ahat are the reasons o3 so any extents in the target database a1 The next extent values used by &'4O$ are obtained 3ro the si9e categories o3 the $0$P ictionary. These si9e categories are !art o3 the technical settings o3 tables and ?ill not be u!dated by any external database adinistration tool. I3 &'SNCFE co!utes the initial extent o3 tables saller than needed@ the nuber o3 next extents increases because the si9e category values are o3ten too sall. 2. Ahat can be done to reduce the nuber o3 extents in the next test run a1 The initial or next extent values o3 the involved tables should be increased by odi3ying the V.(KT or V.ST& 3ile.

-xer"ise : ,&3OAD 4 53OAD 6i*es ;Part !!I >andsOn -xer"ise< (xercise urationD 2" Minutes

-xer"ise O%e"tives  $3ter co!leting this exercise@ you ?ill be able toD > )se &'4O$ standalone. > Manually create V.TSE and V.CM 3iles.

Business -xam'*e ou ?ant to execute &'4O$ standalone@ to 3ix !robles or to ae use o3 s!eci3ic settings not !ossible in the standard setu!@ i.e. ?ith S$PI+ST.

So*ution : ,&3OAD 4 53OAD 6i*es ;Part !!I >andsOn -xer"ise< Tas1 : This is a hands7on exercise 3or ?hich you ust logon to the source syste o3 the exa!le igration. FostnaeD  Grou!7I   Telnet user  Pass?ordD   Fostnae  Instance \D   S$P user  Pass?ordD   Client \   I3 there is a uniue grou! nuber on your ?orstation onitor@ !lease use this nuber as your Grou!7I. e!ending on the training setu!@ use the Aindo?s &eote esto! Connection or Telnet to logon to syste (< /logon ethod@ user@ !ass?ord@ and hostnae as su!!lied by the trainer1. /ote: ou ?ill logon as an adinistratorL Please do not ae any changes to the syste@ exce!t 3or those ex!lained in this exercise. ,. Per9orm t$e 9o**owing 're'aration ste's: Change to the drive and the directory as su!!lied by the trainer Co!y the ?hole directory HT(MP4$T( to your ?or directory. )se nae ?orJgrou'idK /i.e. Hxco!y T(MP4$T( ?or--1 (xecute Henv.bat in your ?or directory. It ?ill set reuired environent variables. &e!eat this ste! a3ter each logonL Change to your ?orJgrou'idK directory /i.e. ?or--1 )se the editor note'ad 3or the Aindo?s &eote esto! Connection or xvi 3or Telnet to !er3or the 3ollo?ing odi3icationsD In NN$&(SS.ST& change the table and !riary ey nae NN$&(SS to NN$&(SSJgrou'idK /i.e. NN$&(SS--1

NN$&(SS]- to NN$&(SSJgrou'idK]- /i.e. NN$&(SS--]-1 In NN$&(SS.(KT change the table and !riary ey nae NN$&(SS to NN$&(SSJgrou'idK NN$&(SS]- to NN$&(SSJgrou'idK]In NN$&(SS.TOC change the table nae N$&(SS to NN$&(SSJgrou'idK >int: -dit /otes  xvi surviva* guide The editor Hxvi is a Hvi i!leentation 3or Aindo?s systes@ ?hich ?ors very ?ell on telnet sessions. Insert odeD !ress Hi@ end insert odeD !ress H(sca!e elete character under cursorD !ress Hx elete character ?hile in insert odeD !ress H0acs!ace Save 3ileD enter HD? /?rite and uit1@ i3 it doesnBt ?or@ !ress H(sca!e and try it again o not use cursor eys ?hile in insert odeU !ress H(sca!e 3irst a1 QQADD,-SS.ST, tabD NN$&(SS-- attD SS(KC - KK T all NN$&(SS--]- )S(& 3ldD +$M( CF$& '- - - notnull , 3ldD CIT CF$& '- - - notnull -

QQADD,-SS.-HT NN$&(SS-- ,%'8# NN$&(SS--]- ,%'8#

QQADD,-SS.TOC vnD &%.#-*<,.# idD adb,c'%e------#% c!D #,-' data?ithchecsu tabD F($(&Q 3ilD NN$&(SS.--, ,-2# , , eotD \- ro?s 2--"-%-%,#,:"8 tabD N N$&(SS-3ilD NN$&(SS.--, ,-2# 22 eotD \2- ro?s 2--"-%-%,#,:"8 eo3D \2--"-%-%,#,:"8

Tas1 #: ,. Ahich 3ields belong to the !riary ey o3 table NN$&(SS Jgrou'idK a1 The !riary ey uses 3ield +$M( only.

Tas1 &: ,. 4ogon to S$P Syste (< and veri3y the $0$P ictionary against the 0 ictionary in transaction 0-2. Save the sho?n out!ut to a 3ile. a1 Chec 3or tables that only exist in the database@ but not in the $0$P ictionary

Tas1 ): ,. )se &'4O$ to create the i!ort tas 3ile NN$&(SS.TSE. a1&'load 7ct3 I NN$&(SS.ST& 4MSS.TP4 NN$&(SS.TSE MSS7l NN$&(SS.log QQADD,-SS.TS2: T NN$&(SS-- C xe P NN$&(SS--]- C xe  NN$&(SS-- I xe

Tas1 (: ,. )se an editor to create an &'4O$ coand 3ile@ ?hich can be used to i!ort table NN$&(SS Jgrou' idK /ote: &'load 3or Aindo?s is recogni9ing H^ and H* as !ath se!arator. a1 tsD NN$&(SS.TSE ic3D NN$&(SS.ST& dc3D 4MSS.TP4 datD .^ bsY,E 3sY,---M dirD NN$&(SS.TOC extD NN$&(SS.(KT

A*ternate notation: tsD NN$&(SS.TSE ic3D NN$&(SS.ST& dc3D 4MSS.TP4 datD .* bsY,E 3sY,---M dirD NN$&(SS.TOC extD NN$&(SS.(KT

Tas1 +: ,. I!ort table NN$&(SSJgrou'idK ?ith &'4O$ and chec the content o3 table NN$&(SS Jgrou' idK by using the MSS coand line utility Hosl. The coand line is case sensitiveL osl 7( 7 S(4(CT V 5&OM dev.NN$&(SSJgrou'idK a1 I!ort table NN$&(SS--D &'load 7dbcode!age #,-' 7i NN$&(SS.cd 7l N N$&(SS.log

NN$&(SS.logD /IMP1 I+5OD i!ort o3 NN$&(SS-- co!leted /2- ro?s1

NN$&(SS.TSED T NN$&(SS-- C o P NN$&(SS--]- C o  NN$&(SS-- I o osl 7( 7 S(4(CT V 5&OM dev.NN$&(SS-- Aattenberg Muenchen Aerle O33enbach /2- ro?s a33ected1

/ote: $s the du! ?as created on a little endian )nicode syste /see NN$&(SS.TOC1@ the i!ort ust be !er3ored ?ith dbcode!age H#,-'. 5or ore in3oration on Hosl@ see docuent HMSSosl.txt in your ?or directory. Ignore &'4O$ essages starting ?ith Hsa!!araD sa!!araD sa!argv/ argc@ argv1 has not been called. sa!!ara/,c1D +o Pro3ile used. sa!!araD S$PSST(M+$M( neither in Pro3ile nor in Coandline

Tas1 7: &e!eat the veri3ication o3 the $0$P ictionary against the 0 ictionary /do a re3reshL1. ,. oes the out!ut loo di33erent than be3ore +e? entries a1 Transaction 0-2 ?ill sho? your i!orted table NN$&(SS--. I3 not@ re3resh the dis!lay /tables o3 your student neighbors ight be visible as ?ell1.

Tas1 : Try to load table NN$&(SS Jgrou'idK again by changing the NN$&(SSZgrou!7id[. TSE 3ileD  NN$&(SSZgrou!7id[ I o R  NN$&(SSZgrou!7id[ I xe

,. Ahat ha!!ened Ahat is the content o3 NN$&(SS.TSE and NN$&(SS.log a1 0ecause o3 the !riary ey on 3ield H+$M(@ it is i!ossible to insert t?o identical naes. &'4O$ returns an error /rcY2% error1. The NN$&(SS.TSE 3ile containsD  NN$&(SS-- I err 

NN$&(SS.logD /IMP1 (&&O&D bSl(ndModi3y 3ailed rc Y 2%@ table NN$&(SS--

2. Try the i!ort again@ ?hat ha!!ens no? a1 The i!ort ?ors the second tie as the status Herr in NN$&(SS.TSE 3orces &'4O$ to delete the table content be3ore starting the i!ort.. NN$&(SS.logD /IMP1 I+5OD i!ort o3 NN$&(SS-- co!leted /2- ro?s1

Tas1 : ,. Create a ne? sub7directory in your ?or directory. +ae it Hex!ort. Create a tas and a coand 3ile to ex!ort NN$&(SSZgrou!7id[. (x!ort table NN$&(SSZgrou!7id[ and co!are the nuber o3 ex!orted ro?s against the nuber o3 table ro?s in the database. osl 7( 7 Hselect count/V1 3ro dev.NN$&(SSgrou!7id /ote: Mae sure not to over?rite your existing NN$&(SS.TOC and NN$&(SS.--, 3ileL a1 Create directory Hex!ort and co!y NN$&(SS.CM into it. Change to directory Hex!ort. (dit the co!ied coand 3ileD NN$&(SS.CM tsD NN$&(SS.TSE ic3D ..^NN$&(SS.ST& dc3D ..^4MSS.TP4 datD .^ bsY,E 3sY,---M dirD NN$&(SS.TOC

A*ternate notation: tsD NN$&(SS.TSE ic3D ..*NN$&(SS.ST& dc3D ..*4MSS.TP4 datD .* bsY,E 3sY,---M dirD NN$&(SS.TOC

Create the tas 3ile NN$&(SS.TSE containing the 3ollo?ing line /you can use &'4O$ or an editor1D &'load 7ct3 ( ..^NN$&(SS.ST& ..^4MSS.TP4 NN$&(SS.TSE MSS 7l NN$&(SS.log

NN$&(SS.TSE  NN$&(SS-- ( xe

Start the ex!ortD &'load 7datacode!age #,-' 7e NN$&(SS.CM 7l NN$&(SS.log

There should be 2- ro?s in the database@ and the sae nuber should be entioned in the V.TOC 3ile.

Unit 8  Advan"ed Migration Te"$ni8ues This unit describes advanced techniues@ ?hich can be utili9ed to s!eed u! the ex!ort and the i!ort !hase o3  a igration.

3esson: Time Consuming Ste's during -x'ort  !m'ort 3esson Overview Fo? to identi3y@ inii9e@ or avoid tie consuing ste!s during the ex!ort*i!ort !hases

3esson O%e"tives  $3ter co!leting this lesson@ you ?ill be able toD > Identi3y the tie consuing ste!s during ex!ort * i!ort > Minii9e the do?ntie by a!!lying a!!ro!riate easures 5or the students@ itBs i!ortant to no? the tie consuing igration ste!s. $s a conclusion they ?ill be able to execute the as early as !ossible and to avoid the during the do?ntie /i3 !ossible1.

Business -xam'*e ou need to no? the long running OS*0 Migration ste!s to estiate the tie schedule in a cut7over !lan.

6igure 7: Fenera* ,emar1s Please tae into account@ that the nuber o3 ro?s on $0$P cluster tables ?ill di33er bet?een source and target syste in case o3 a )nicode Conversion because o3 their co!ressed content. 5or co!arable results use a S4 stateent lie thisD S(4(CT CO)+T /V1 5&OM CC4S AF(&( P$G(+OYB-B .

6igure 0: Te"$ni"a* =iew: Time Consuming -x'ort Ste's ;< It de!ends on the S$PI+ST version and database ?hether the above tass are available or not. i33erent databases have di33erent s!ace reuireents 3or storing the data. The !rogras &'4CT4*&'SNCFE co!ute the I+ITI$4 (KT(+T o3 all tables and indexes 3or the target database. The su o3 all o3 these !rovides the estiated si9e o3 the target database.

e!ending on the database@ table s!litting can be a tie consuing !rocess@ ?hich should run be3ore the ex!ort. In ost cases there is not enough tie 3or that during the ex!ort*i!ort do?ntie. The co!uted AF(&( conditions are de3ined in such a ?ay that data added or deleted a3ter?ards doesnt atter@ the conditions ?ill 3etch all data in the table. I3 !ossible@ large data u!dates should be avoided a3ter creating the AF(&( conditions /or co!ute the again1. I3 using the Oracle P4*S4 table s!litter@ s!ecial consideration a!!ly to &OAI s!litting. More in3oration in S$P +oteD ,-#''8-. S$PI+ST (x!ort Pre!arationD ou ?ant to build the target syste u! to the !oint ?here the database load starts@ be3ore the ex!ort o3 the source syste has 3inished. (x!ort and i!ort !rocesses should run in !arallel during the syste co!y !rocess. S$PI+ST Table S!litting Pre!arationD O!tional ste! 3or !re!aring the table s!litting be3ore starting the ex!ort o3  a S$P Syste based on $0$P. I3 soe o3 the tables a very large the do?ntie can be decreased by s!litting the large tables into several saller !acage@ ?hich can be the !rocessed in !arallel.

6igure : Te"$ni"a* =iew: Time Consuming -x'ort Ste's ;#< The ost i!ortant ?ay to tune ex!ort !er3orance is to o!tii9e the use o3 !arallel ex!ort !rocesses. Trans!ortable storage devices can be <s@ external )S0 diss@ la!to!s@ or ta!es. Ahen &'4O$ stores the ex!orted data into du! 3iles@ it uses a very e33icient co!ression algorith. ou do not need to co!ress these 3iles again /you ay even 3ind that the resulting 3ile is larger than be3ore1. To save tie 3or co!ing very large aounts o3 du! data to the target edia*syste@ it can be use3ul to set the du! 3ile si9e to a sall value@ lie '-- M0. $s soon as a du! 3ile is co!leted@ the co!y can be started. +oteD the MIG&$TIO+ MO+ITO& ?aits until all du! 3iles o3 a !acage have been co!leted.

6igure #: Te"$ni"a* =iew: Time Consuming !m'ort Ste's I3 a !arallel ex!ort * i!ort using &'4O$ is !lanned the database ust be ready to i!ort ?hen the ex!ort starts. +orally the 3irst database u!date statistic is started directly a3ter the database i!ort. I3 short on tie@ the u!date statistic can be !ost!oned to a later !oint in tie ?here it can run in !arallel ?ith other activities.

6igure &: Saving Time on !m'ort  A9ter 3oad -rrors &'S(T)P or S$PI+ST is starting a one7tie &'4O$ !rocess 3or each !acage. I3 &'4O$ !rocesses terinate ?ith an error condition@ &'S(T)P*S$PI+ST ?ill sto! a3ter all &'4O$ !rocesses are 3inished. The execution o3 &'S(T)P*S$PI+ST ust be re!eated until all &'4O$ !rocesses are success3ul. I3 you no? that the cause o3 an &'4O$ error terination is 3ixed@ you can save tie by starting &'4O$ beside &'S(T)P or S$PI+ST. our o?n &'4O$ !rocess ust be started ?ith the sae !araeter set as ?as used by &'S(T)P or S$PI+ST be3ore. The !araeters can be obtained 3ro the corres!onding HZP$CE$G([.4OG 3ile. 4og7on as the o!erating syste user ?ho o?ns the HZP$CE$G([.log 3iles in the installation directory /3or exa!leD Zsa!sid[ad1. Change into the install directory. Only start &'4O$ !rocesses 3or the V.ST& 3iles that have already been !rocessed by the current run o3 &'S(T)P or S$PI+ST. +ever restart &'S(T)P ?hile your o?n &'4O$ !rocesses are running. This ?ill cause co!etition bet?een your &'4O$ !rocess and the &'4O$ !rocesses started by &'S(T)P to !rocess the sae V.ST& 3ile. In the case o3 using S$PI+ST@ the second &'4O$ !rocess ?ill be sto!!ed autoatically@ as a bacu! tas 3ile already exists. &'S(T)P*S$PI+ST ust be restarted a3ter all data is loaded@ to execute the reaining ste!s o3 the installation*igration.

6igure ): ,&3OAD Parameters 9rom !m'ort G.3OF 6i*e o not 3orget to add the restart !araeter H7r to the coand line o3 &'4O$ /#.% and belo? only1. I3 you are starting &'4O$ anually@ ae sure that your current ?oring directory is the installation directoryL

6igure (: -x'ort  !m'ort Time Diagram In custoer databases@ ost o3 the transaction data is stored in tables belonging to only a 3e? T$0$&Ts. This causes long running &'4O$ ex!ort and i!ort !rocesses 3or the T$0$&Ts. To save tie and o!tii9e the !arallelis o3 &'4O$ !rocesses@ you canD S!lit !acage 3iles /V.ST&1 into several saller 3iles@ or se!arate large tables into additional !acage 3iles.

6igure +: O'timi@ing t$e -x'ort  !m'ort Pro"ess (x!ort and i!ort ties are reduced by s!litting !acage 3iles /V.ST&1 and creating additional !acage 3iles 3or large tables.  $l?ays try to ex!ort*i!ort large tables 3irst. This ensures the axiu !arallelis o3 &'4O$ !rocesses.
6igure 7: 5A=ABased Pa"1age S'*itter  The 6$<$ Pacage S!litter can also be used 3or earlier releases than Aeb $S %.#-. The ter !acage is used a synony 3or V.ST& 3iles. S$PI+ST %.#- 3or +etAeaver B-# can call the 6$<$ or the P(&4 Pacage S!litter  /de!ending on the selected o!tion1. Starting ?ith +etAeaver -#S@ only the 6$<$ S!litter ?ill be used.

The S!litter analy9es the content o3 V.(KT 3iles to 3ind the best s!litting !oints. 5ine tuning can be done to V.ST& 3iles a3ter a test igration. The s!litting o3 V.ST& 3iles is even !ossible ?ithout V.(KT 3iles@ i3 tables are naed in a !rovided in!ut 3ile. Pacage 3ile naes 3or the s!lit V.ST& 3iles are generated autoatically. The docuentation is !rovided as P5 3ile together ?ith the s!litting tool. In the case ?here no 6$<$ 6&( ,.#.x or higher is installed@ the V.ST& 3iles can be trans!orted to another syste@ and s!lit there.

6igure : P-,3Based Pa"1age S'*itter  The Perl scri!t SP4ITST&.P4 ay also be used 3or earlier &elease #.x igrations. o not use the Perl s!litter 3or )nicode conversionsL The 0(KPO&T.&'S coand 3ile 3or &'S(T)P releases since #.% and S$PI+ST calls SP4ITST&.P4 i3 the o!tion has been selected. SP4ITST&.P4 analy9es the content o3 V.(KT 3iles to 3ind the best s!lit !oints. 5ine tuning can be done to V.ST& 3iles a3ter a test igration. Pacage 3ile naes 3or s!lit V.ST& 3iles are generated autoatically. The Perl scri!t is sel37ex!lanatory. Calling SP4ITST&.P4 ?ithout !araeters or using the H7hel! o!tion causes a hel! text to a!!ear. o not use SP4ITST&.P4 on already s!lit 3iles@ as it can lead to !robles. $l?ayss!lit 3ro the original 3iles@ thus !reserving the The SP4ITST&.P4 scri!t is not intended to be used on '.x V.ST& 3iles. The results are erroneousL  $ Perl version is available 3or every o!erating syste. The installed version o3 Perl can be checed ?ith H!erl X v. In the case ?here no Perl is installed@ the V.ST& 3iles can be trans!orted to another syste@ and s!lit there.

6igure : ,&3OAD -x'ort!m'ort Using So"1ets Socet connections are released 3or &'4O$ %.#- and later. /o not try to use an earlier version@ even i3 &'4O$ !rovides the socet o!tion1. &'4O$ ?rites directly to the o!ened socet and does not need any du! or table o3 content /V.TOC1 3ile. (rror situations ?ill be handled@ as ?ith conventional ex!orts and i!orts. The ex!orting and i!orting !rocesses ?ill use their res!ective tas 3iles 3or restart. +et?or interru!tions ?ill terinate the ex!ort and i!ort !rocess iediately. Mae sure that the ex!ort or i!ort !rocess does not 3ail because o3 database resource bottlenecs. &'4O$ restarts can ae the i!ort ore tie consuing than ex!ected. The &'4O$ i!ort !rocess has to be started 3irst@ because the ex!ort !rocess ust connect to an existing socet 7 other?ise the !rocess 3ails. The Migration Monitor does su!!ort socet connections in an easy7to7con3igure ?ay.

6igure 0: ,&3OAD So"1et Conne"tions  Te"$ni"a* =iew The sae 3iles are used@ as in standard &'4O$ scenarios@ but no du! or V.TOC 3iles are created. The &'4O$ control 3iles ust be accessible as usual@ on the source and target syste.

6igure : JPAC2AF-K.CMD  So"1et Conne"tion E +.)0 &'4O$ ust be started ?ith the H7socet coand line o!tion. The i!orting !rocess ust be invoed be3ore the ex!ort !rocess can be started. The socet !ort can be any 3ree nuber bet?een ,-2# and %""'" on the i!ort host. Meaning o3 section naesD > tsD Tas 3ile > ic3D Inde!endent control 3ile > dc3D atabase de!endent control 3ile > datD Socet !ort nuber and nae or IP address o3 the i!ort host > extD (xtent 3ile /not reuired at ex!ort tie1 The Hdir section is not reuired because no ZP$CE$G([.TOC 3ile ?ill be created

6igure #: JPAC2AF-K.3OF  ,&3OAD So"1et 3ogs E +.)0 The i!orting !rocess listens on the s!eci3ied !ort and ?aits 3or the ex!orting !rocess to connect.

6igure &: Migration  Ta*e C$e"1er ;M!FC>-C2<  6eatures The 6$<$7based HMigration Checer ?as develo!ed to chec that there is a log 3ile 3or each !acage 3ile /o!tionD 7checPacages1. This is an indicator that &'4O$ did run 3or the. The second chec is to veri3y that each action in the tas 3ile is co!leted success3ully /o!tionD 7checObjects1. )nsuccess3ul tass are listed in an out!ut 3ile. The t?o 3eatures are used by S$PI+ST 3or +etAeaver -#S and later@ to chec the i!ort co!leteness. atabase and table de!ending exce!tions are handled autoatically. The HTable Checer 3eature is used to chec the nuber o3 table ro?s. It can be used to ae sure@ that tables are containing the right nuber o3 ro?s a3ter i!ort. $s this is a long running tas@ it can be started anually only.

6igure ): SAP!/ST: Com'*ete  Modi9y Pa"1age Ta*e ;+.)0< S$PI+STD allo?s 3or custo ex!ort*i!ort order de3initions and even the change o3 individual !araeters 3or each single !acage.

O&(&D de3ines the seuence in ?hich the !acages are to be loaded. The load starts ?ith the lo?est values 3irst. +egative values are also allo?ed. PEGID Identi3ier ZS$PSI[Z0SI[. PEG+$M(D +ae o3 the !acage /V.ST& 3ile1. PEG5I4(SIN(D Si9e o3 the data du! 3ile. PGEI&D Path ?here $T$ and 0 sub7directories 3or the !acage reside. PEG45I4(D The nae o3 the 4Z0S[.TP4 3ile. PEGCM5I4(D The nae o3 the coand 3ile 3or this !acage. /Aill be generated autoatically@ but i3 you ?ant to use your o?n@ you ay enter its nae1. PEG4O$OPTIO+SD $dditional 0 s!eci3ic &'4O$ o!tions that ?ill be a!!lied ?hen this !acage is i!orted.  $s +etAeaver -#S uses MIGMO+ to start &'4O$@ the advanced 3eatures o3 the Migration Monitor are used@ instead o3 the echanis above.

6igure (: Unsorted -x'ort 0e3ore starting an unsorted ex!ort@ !lease read S$P +oteD H="#2%8 O!tii9ation o3 ex!ortD )nsorted unloadingL 0y de3ault@ the syste unloads the data as sorted. This is controlled by the 3ollo?ing entry in the 4Z0S[.TP4 3ileD !rieyD .... O&(&0PE(. Sorting taes tie and needs a large te!orary storage@ i3  it can be oitted@ the ex!ort ?ill be 3aster. Tae care about conseuences in the target syste /!er3orance i!act1. I3 you use Max0 as target database@ you ust ex!ort all o3 the tables as sorted. I3 you use Max0 as the source database@ you can unload sorted data only. o not override this o!tion ?hen you ex!ort Max0. I3 you use MSS4 as the target database@ you should ex!ort all o3 the tables as sorted@ so that you can avoid !er3orance !robles during the i!ort. I3 you have to unload the tables as unsorted and i3 you use MSS4 as the target database@ you should re3er to +ote ,-"#8"2. Certain table ty!es are not allo?ed to be ex!orted in an unsorted ?ay. S$P +ote ="#2%8 ex!lains the considerations release and code !age de!endent. &'4CT4 generates 4Z0S[4&G.TP4 3iles to si!li3y unsorted ex!orts since +etAeaver -#.

6igure +: C$anging ,&3OAD Ta*e 3oad Se8uen"e in G.ST, o not re7order tables in V.ST& 3iles a3ter ex!ort. I3 ore than one du! 3ile exists 3or a single V.ST& 3ile@ &'4O$ ?ill not be able to read table data 3ro i.e. 5ile V.--2 and 3or the next table 3ro 3ile V.--,@ i3 the table order in the V.ST& 3ile ?as changed a3ter ex!ort.

6igure 7: !nitia* -xtent 3arger t$an Conse"utive DB Storage The situation above can be a !roble on Oracle dictionary anaged tables!aces@ but should not a!!ly to locally anaged tables!aces as ?ell. Custoer databases can contain tables and indexes that reuire a larger Hinitial extent than the axiu !ossible in a single data container. In such cases@ reduce the Hinitial extent in the V.(KT 3ile and ada!t the Hnext extent si9e class in the relevant V.ST& 3ile. The ne? Hinitial extent si9e should be slightly less than the axiu available s!ace in the data container. This gives the database soe s!ace 3or internal adinistration data.

3esson: M!FMO/  Migration Monitor 9or ,&3OAD Business -xam'*e ou need to no? the a!!ro!riate MIGMO+ con3iguration scenario 3or s!eci3ic custoer S$P Syste landsca!es.

6igure : Migration Monitor ;M!FMO/<  6eatures ;< S$P +oteD :8#,,8 HSyste Co!y 6$<$ Tools. The note also describes ho? to do?nload the so3t?are 3ro S$P Maret!lace. The ex!ort server ode a!!lies ?here &'S(T)P*S$PI+ST ?ill be re!laced 3or the ex!ort. (ven i3 MIGMO+ is not used 3or the i!ort@ the advanced control 3eatures o3 the ex!ort !rocesses can hel! to save tie.  $lready existing V.TSE or V.CM 3iles ?ill not be over?ritten@ but used.

6igure : Migration Monitor ;M!FMO/<  6eatures ;#< The ex!ort client ode a!!lies@ ?here &'S(T)P*S$PI+ST !er3ors the database ex!ort@ and MIGMO+ is used 3or the i!ort. The client MIGMO+ is used to trans3er the 3iles to the target host and to signal the i!orting MIGMO+@ that a !acage is ready to load. (ven i3 MIGMO+ ?as not used to !er3or the ex!ort@ the i!ort can still bene3it 3ro the advanced MIGMO+ &'4O$ control 3eatures.

6igure #00: Migration Monitor ;M!FMO/<  Parameters The nuber o3 ex!ort and i!ort !rocesses can be di33erent. In the case o3 socet usage@ the nuber o3 ex!ort and i!ort !rocesses is the sae. The ex!ort job nuber is ignored@ because the (x!ort Monitor reuests the  job nuber 3ro I!ort Monitor during startu!. Grou!s o3 !acages can be assigned to di33erent 4V.TP4 3iles. ata trans3er con3iguration variants

> 5TPD 5ile trans3er via 5TP bet?een source and target syste > +et?orD (x!ort directory is shared bet?een source and target syste > SocetD &'4O$ ?ill use socets /reuires &'4O$ %.#- or higher1. It can be cobined ?ith 3t! to co!y &'4O$ control 3iles to the target syste. > Stand7aloneD MIGMO+ runs stand7alone@ i.e. the ex!ort ?ill be !rovided on a trans!ortable edia only /!ossibly no 3ast net?or connection to source syste available1. 5TP Paraeters contain the logon !ass?ord. To hide 5TP !ass?ord in the coand line /visible using H!s X e3 coand on )+IK@ or various Aindo?s tools1 @the ex!ortonitorsecure.sh*bat 3iles should be used. The usage o3 5TP ight be a security ris@ but it is a reliable ethod o3 data trans3er.

6igure #0: Migration Monitor  /et Con9iguration =ariant The Migration Monitor +et Con3iguration
6igure #0#: Migration Monitor  6TP Con9iguration =ariant

The Migration Monitor 5TP Con3iguration
6igure #0&: Migration Monitor  So"1et Con9iguration =ariant The Migration Monitor socet ethod is in theory@ the 3astest ethod ever in ex!ort and i!ort o3 data in that ?e have to have a stable net?or and ?e have to ae sure that the ex!orting and i!orting databases al?ays have enough resources to serve the &'4O$ !rocesses.  $ net?or share@ a anual 3ile co!y@ or the Migration Monitor 5TP 3ile trans3er /o!tion X3t!Co!y1 can be used to co!y the &'4O$ control 3iles to the target syste. The i!orting Migration Monitor ust be started 3irst. The ex!orting Migration Monitor connects to the i!orting Monitor@ using the !rovided socet !ort. The socet !ort nubers are increented one7by7one@ 3or each &'4O$ !rocess started. The counication bet?een the ex!ort and i!ort Monitor ensures@ that the right !ort nubers ?ill be ?ritten into the corres!onding V.CM 3iles. +o !ort nuber is used t?ice. )nusable !ort nubers are si!!ed /ay be in use by others1. I3 a 3ire?all is bet?een the source and target syste@ ae sure that a ?hole !ort range /base !ort _ nuber o3 &'4O$ !acages _ sa3ety1 is released 3or the duration o3 the igration.

6igure #0): Migration Monitor  StandA*one Con9iguration The Migration Monitor Stand7$lone Con3iguration
6igure #0(: Migration Monitor  Contro* 6i*es The ex!ort*i!ort state or the 3ile trans3er state can be changed 3ro inus /H71 to 9ero /H-1 3or restarting &'4O$ or a 3ile trans3er. Socets onlyD MIGMO+ 3or +etAeaver B-# cannot restart the &'4O$ !rocess by changing the state only /3uture versions ?ill su!!ort this1. In case o3 a 3ile trans3er restart@ all du! 3iles o3 a !acage are co!ied again. (xa!leD i!ortstate.!ro!erties S$P$PP4,Y- +ot started yet CO(PY &unning SAACO+T7,Y_ 5inished /!art , o3 s!litted table1 SAACO+T72Y_ 5inished /!art 2 o3 s!litted table1 SAACO+T7'Y7 (rror /!art ' o3 s!litted table1 SAACO+T7#Y- +ot started yet /!art # o3 s!litted table1 SAACO+T7"Y- +ot started yet /!art " o3 s!litted table1 SAACO+T7!ostY- +ot started yet /secondary index creation@ !ost7!rocessing1 SAACO+T7!reY_ 5inished /table and !riary ey creation@ !re7!rocessing1

6igure #0+: M!FMO/ !nsta**ation Too* !ntegration ;< The MIGMO+ server ode 3or !re7+etAeaver -# S&, versions can only be used i3  S$PI+ST has been 3orced to sto!@ i.e. by i!leenting an intended error situation.

6igure #07: M!FMO/ !nsta**ation Too* !ntegration ;#< The MIGMO+ server ode 3or +etAeaver -# S&, can only be used i3 S$PI+ST had been 3orced to sto!@ i.e. by i!leenting an intended error situation. S$PI+ST +et?eaver -#S reuires a anual start o3 MIGMO+ i3 using the socet ode.

6igure #0: Summary: ,&3OAD Un*oad3oad Order y Too* The MIG&$TIO+ MO+ITO& unload*load !rocess order can be de3ined in the res!ective !ro!erties 3ile. In addition@ a 3ile can be !rovided that contains a list o3 !acages used to de3ine the unload*load order. I3 the 3ile does not contain all existing !acages@ the reaining !acages are unloaded in al!habetical order and loaded by si9e X starting ?ith the largest !acage. /+othing ?ill be lost1. S$PI+ST allo?s you to select di33erent orders 3or unloading or loading the database. The 3eature o3 custoi9ing the execution order o3 each V.ST& 3ile gives a good control over the unload or load !rocess. S$PI+ST +etAeaver -#S uses MIGMO+ to start &'4O$ !rocesses. The MIGMO+ &'4O$ start 3eatures are integrated into S$PI+ST dialogs.

6igure #0: M!FMO/ -x'ort  !m'ort Order  In the above exa!le@ the largest tables should be ex!orted 3irst. 5or that !ur!ose@ the tables ?ere s!litted 3ro its standard V.ST& 3iles into !acage 3iles containing one table only. The !acage naes ?ere inserted into Hex!ortorder.txt. The Migration Monitor ?ill ex!ort the !acages in exactly the order as de3ined in Hex!ortorder.txt. $3ter?ards it ?ill ex!ort the reaining !acages in al!habetical order. On the target syste@ the !acages ?ill be i!orted as s!eci3ied in Hi!ortorder.txt. I3 no !acage entioned in Hi!ortorder.txt@ is available 3or i!ort /still ex!orting1 the !acage ?ith the next largest du! 3ile ?ill be used instead. O3ten t?o di33erent ex!ort7 and i!ort7order 3iles ae sense@ i.e. i3 soe tables have a lot o3 indexes but are sall co!ared to the largest tables. In this case the overall run7tie o3 a saller table can be uch longer then 3or the larger table@ because o3 the index creation tie. In the above exa!le the tables G4PC$ and MS(G are big@ but not the biggest. 5or the i!ort it ?as decided to give the to! !riority because they have a lot o3 indexes and so the index creation ties ?ill exceed even the i!ort tie o3 the largest table SO55CO+T,.

6igure #0: Advan"ed M!FMO/ DD3G.TP3 6i*e Usage The Migration Monitor can be used to ex!ort or i!ort selected !acages ?ith s!eci3ic 4Z0S[.TP4 3iles. The above ex!ort exa!le@ sho?s a ho? to ex!ort three !acages unsorted /4O&$4&G.TP41 and the ajority o3 all tables the standard ?ay /4O&$.TP41.

The i!ort exa!le@ utili9es a s!ecial Oracle 3eature to !aralleli9e the index creation. 5or that !ur!ose t?o di33erent 4Z0S[.TP4 3iles ?ere generated to i!ort t?o !acages ?ith index creation !arallel degree 2 /4O&$!ar2.TP41 and the other t?o !acages ?ith index creation !arallel degree # /4O&$!ar#.TP41. The reaining !acages are i!orted as usual /4O&$.TP41.

3esson: M!FT!M- 4 5M!FT!M-  Time Ana*y@er  Business -xam'*e ou need to analy9e the ex!ort*i!ort behavior in an OS*0 Migration to inii9e the do?ntie 3or the 3inal igration o3 a !roductive syste.

6igure #: Time Ana*y@er ;M!FT!M-  5M!FT!M-<  6eatures S$P +oteD :8#,,8 HSyste Co!y 6$<$ Tools. The note also describes ho? to do?nload the so3t?are 3ro the S$P Maret!lace. Over tie@ the content o3 &'4O$ V.4OG and V.TOC 3iles has been i!roved by adding ore and ore in3oration. The Tie $naly9er can handle all existing 3orats. &'4O$ %.#- ?rites se!arate tie sta!s 3or data load and index creation /earlier versions did notL1. MIGTIM( obtains the ex!ort i!ort tie in3oration 3ro V.TOC and V.4OG 3iles. 6MIGTIM( retrieves the tie in3oration 3ro the 64O$ ZP$CE$G([.ST$T.KM4 3iles.

6igure ##: Time Ana*y@er  Out'ut Based on -x'ort 6i*es ;< The list out!ut sho?s the start*end date and the ex!ort duration o3 each !acage@ and additionally !rovides run7tie in3oration@ as seen above in the longest running tables.

6igure #&: Time Ana*y@er  Out'ut Based on -x'ort 6i*es ;#< The FTM4 out!ut gives a uic overvie? on the !acage run7tie distribution.

6igure #): Time Ana*y@er  Out'ut Based on !m'ort 6i*es ;< The list out!ut sho?s the start*end date and the i!ort duration o3 each !acage. I3 the used &'4O$ version /i.e. %.#-1 !rovides tie sta!s 3or each table i!ort and !riary ey*index creation@ the out!ut list can then distinguish bet?een data load and index creation tie. The list o3 long running tables can be generated 3or !re7%.#- &'load releases too@ but it does not contain data and index coluns@ only a tie colun. The log 3ile contains tie in3oration 3or data load ends@ there3ore the tie 3or tables in the old &'load releases is not ,--W correctD table tie Y table load tie _ index*!ey creation tie 3or the !revious table /i3 index*!ey is created a3ter data load1. 5ro &'4O$ %.#-@ table tie is correctly deterined@ because create table*index ties are !resent in the log 3iles.

6igure #(: Time Ana*y@er  Out'ut Based on !m'ort 6i*es ;#<

6igure #+: Time Ana*y@er  Time 5oin

3esson: Ta*e S'*itting 9or ,&3OAD 3esson Overview (x!lanation o3 the table s!litting !rocedure 3or &'4O$

Business -xam'*e ou need to no? ho? &'4O$ table s!litting is ?oring and ho? to troubleshoot !robles.

6igure #7: ,&TA Ta*e S'*itter  &'T$ analy9es a given table and returns a set o3 AF(&( conditions that ?ill select a!!roxiately the sae aount o3 ro?s. 5or each AF(&( condition one &'4O$ can be started. The !arallel ex!ort does not reduce the ex!ort tie only@ it ?ill also allo? an earlier start o3 the i!ort. 0ecause o3 the co!lex handling o3 s!litted tables@ the usage o3 MIGMO+ is andatory. The resulting HZtable[.AF& 3ile reuires 3urther s!litting into HZtable[7n.AF& 3orat /AF(&( SP4ITT(&1. I3 the !arallel i!ort into a single table is not !ossible on a !articular database ty!e@ a seuential i!ort o3 s!litted tables can be 3orced by de3ining MIGMO+ load grou!s. Please chec the res!ective syste co!y anual and related notes 3or current liitations. (ven i3 the !arallel i!ort into a single table is not su!!orted on your database@ the overall tie saving because o3 the !arallel ex!ort itsel3 is signi3icantly enough. S$P +oteD ="2",# )sing the table s!litting 3eature

6igure #: Ora"*e P3SN3 Ta*e S'*itter  The P4*S4 table s!litter analy9es a given table and returns a set o3 AF(&( conditions that ?ill select a!!roxiately the sae aount o3 ro?s. 5or each AF(&( condition one &'4O$ can be started. +orally the P4*S4 scri!t is 3aster then &'T$ as it is using Oracle s!eci3ic 3eatures. The resulting V.AF& 3iles can be used ?ithout 3urther s!litting /no AF(&( SP4ITT(& reuired1. S$P +oteD ,-#''8- (33icient Table S!litting 3or Oracle atabases /the current P4*S4 table s!litter scri!t is attached to the note1 S!eci3ic &OAI table s!litting liitationsD > &OAI table s!litting M)ST be !er3ored during do?ntie o3 the S$P syste. +o table changes are allo?ed 3or &OAI s!litted tables a3ter ranges have been calculated and ex!ort ?as co!leted. $ny table change be3ore the ex!ort reuires a recalculation o3 the &OAI ranges. > &OAI s!litted tables M)ST be i!orted ?ith the H7load!rocedure 3ast o!tion o3 &'load. > &OAI table s!litting ?ors only 3or trans!arent and non7!artitioned tables. > &OAI table s!litting C$++OT be used i3 the target database is a non Oracle database.

6igure #: Ta*e S'*itting in SAP!/ST E /0) Table s!litting is a tas ?hich ?ill be done be3ore the ex!ort. The Hs!litin!ut.txt 3ile ust s!eci3y the tables to s!lit and ho? o3ten. Tae care about the di33erent in!ut 3orats in case o3 &'T$ or the Oracle P4*S4 table s!litter. Chec the corres!onding syste co!y guide. The H&'tahints.txt contains !rede3ined s!lit 3ields 3or the ost coon large tables. More tables and 3ields can be inserted ?ith an editor. The 3ile has to be located in the directory in ?hich &'ta ?ill be started. I3 H&'tahints.txt ?as 3ound and the table to s!lit is inside@ the !rede3ined 3ield ?ill be used@ other?ise &'T$ analy9es each 3ield o3 the !riary ey to 3ind the best atching one. The H&'tahints.txt is !art o3 the &'T$ archive ?hich can be do?nloaded 3ro S$P Maret!lace@ i3 not already on the installation edia.

C$)TIO+D Ahen doing a syste co!y ?ith the change o3 the code !age /non7)nicode to )nicodeU #,-2 to #,-'U #,-' to #,-21@ ae sure not to use a AF(&( condition ?ith the P$G(+O colun included 3or cluster tables /i.e. CC4S@ &504G@ 1. The resulting HV.AF& 3iles ?ill be ?ritten into subdirectory $T$ o3 the s!eci3ied ex!ort directory. Table s!litting ?ill tae !lace i3 the s!eci3ied ex!ort directory is the sae lie 3or the &'4O$ ex!ort later on. The H?hr.txt 3ile contains the nae o3 the s!litted tables. It can be used as an in!ut 3ile 3or the !acage s!litter to ae sure that each s!litted table has it o?n V.ST& 3ile. It de!ends on the S$PI+ST release ?hether a database ty!e can be selected or not. S$PI+ST :.-2 can ae use o3 the Oracle P4*S4 s!litter i3 the database ty!e Oracle ?as selected. &adio buttons allo? to choose bet?een the &'T$ and the P4*S4 table s!litter.

6igure ##0: -xam'*e o9 an ,&TA Based Ta*e S'*itting The above exa!le sho?s the &'T$ AF(&( 3ile creation 3or an Oracle database. The CEIS.ST& is !rovided to the coand line to tell &'T$ ?hich 3ields belong to the !riary ey. &'T$ generates a CEIS.AF& 3ile containing the co!uted &'4O$ AF(&( conditions@ a set o3 3iles to create a te!orary index@ and a 3urther set o3 3iles to dro! the te!orary index. It ust be decided on an individual base@ ?hether it aes sense to create an additional index or not.

6igure ##: ,&TA -xam'*e: Create Tem'orary !ndex ;O'tiona*< e!ending on the database ty!e@ database o!tii9er behavior@ table ty!e@ table 3ield or table si9e@ a te!orary index can i!rove the &'4O$ data selection considerably. To 3ind out ?hether a te!orary index aes sense or not@ a S4 (KP4$I+ stateent can hel! to chec the database o!tii9er cost 3actor on the data to select. Indexes should be checed on a co!y o3 the !roductive syste 3or exa!le.

The corres!onding syste co!y guide describes ho? to create or delete &'T$ related indexes.

6igure ###: ,&TA -xam'*e: Dro' Tem'orary !ndex I3 the te!orary index does not i!rove the &'4O$ ex!ort@ it can be dro!!ed using the !rede3ined 3iles or ?ith S4 coands directly.

6igure ##&: ,&TA -xam'*e: >-,- Condition 6i*e C2!S.>, &'T$ ?rites all AF(&( conditions 3or a table into one single 3ile. It ust be s!lit into !ieces to utili9e a !arallel ex!ort ?ith MIGMO+. I3 it cannot be achieved to create exactly the nuber o3 s!lits as reuested@ it can ha!!en that ore or less AF(&( conditions are created. In the exa!le above@ ,- s!lit ?ere reuested but &'T$ created ,,.

6igure ##): ,&TA -xam'*e: C2!S.>, S'*itting (ach AF(&( condition ust be !ut into a se!arate 3ile@ other?ise the MIGMO+ echanis to su!!ort table s!litting ?ould not ?or as intended. The AF(&( s!litter is !art o3 the 6$<$ !acage s!litter archive. In case o3 S$PI+ST@ it ?ill be called autoatically. I3 &'T$ ?as called directly@ the AF(&( s!litter ust called anually. $ descri!tion o3 the AF(&( s!litter usage is available in the s!litter archive.

6igure ##(: -xam'*e o9 an Ora"*e P3SN3 Based Ta*e S'*itting The above exa!le sho?s the P4*S4 scri!t based AF(&( 3ile creation 3or an Oracle database. $ s!lit strategy can be chosen bet?een 3ield or &OAI s!litting. &OAI s!litting can be used i3 the target database is Oracle /H7load!rocedure 3ast ust be used 3or the i!ort1. O!!osite to &'T$@ the P4S*S4 s!litter creates V.AF& 3iles directly usable by MIGMO+.

6igure ##+: -xam'*e: M!FMO/ -x'ort Pro"essing ;<  $s soon as MIGMO+ 3inds HV.AF& 3iles@ it generates the necessary HV.TSE and HV.CM 3iles autoatically. The HV.TSE 3iles ?ill be created ?ith the s!ecial o!tion H7?here to !ut the AF(&( condition into it. Mae sure to have a se!arate HV.ST& 3ile 3or each s!litted table.

6igure ##7: -xam'*e: M!FMO/ -x'ort Pro"essing ;#< 5or each HV.TSE 3ile a corres!onding HV.CM 3ile ?ill be created.

6igure ##: -xam'*e: M!FMO/ -x'ort Pro"essing ;&< &'4O$ inserts the used AF(&( condition into the V.TOC 3ile. So it is easy to 3ind out ?hich !art o3 a table is stored in ?hich du! 3ile. 5urtherore this in3oration is used 3or a sa3ety echanis to ae sure the i!ort does run ?ith the sae AF(&( conditions as the ex!ort did /other?ise it could lead to a !otential data lost in i!ort restart situations1. I the case o3 a isatch@ &'4O$ sto!s on error.

6igure ##: -xam'*e: Dire"tory Content a9ter -x'ort To si!li3y the gra!hic above@ no dee! directory structures are sho?n /lie S$PI+ST is creating1 and the 3iles under HZex!ortdir[*0 are not ex!licitly entioned. &'4O$ is assued to run in H*inst and the ex!ort directory is naed H*ex!. The H*inst*s!lit directory is used to run &'T$ soe days or hours be3ore the database ex!ort. The &'T$ AF(&( 3ile ?as s!litted and the results ?ere co!ied into H*ex!*$T$. In case o3 the Oracle P4*S4 s!litter@ the AF(&( 3iles and be !ut directly into H*ex!*$T$. The ex!ort log 3ile in3oration o3 &'4O$ :.2-D /01 I+5OD &ead hint3ileD D^(KPO&T^$0$P^$T$^CEIS7,.AF& eans@ the res!ective V.AF& 3ile is scanned 3or an o!tional database hint to be utili9ed during the data ex!ort /currently i!leented 3or Oracle only@ directing the o!tii9er to choose a certain execution !lan1.

6igure #&0: -xam'*e: M!FMO/ !m'ort Pro"essing ;< MIGMO+ aes autoatically sure@ that the HV.TSE and HV.CM 3iles 3or table creation are generated be3ore data i!ort. $3ter success3ully creating the table@ the data load !rocesses are started. This !re!aration !hase is ared in the MIGMO+ Hi!ort.state.!ro!erties 3ile as HZtable[7!reY_. 5or databases ?ith the need o3 a !riary ey be3ore i!ort@ it ?ill be created together ?ith the table.

6igure #&: -xam'*e: M!FMO/ !m'ort Pro"essing ;#<  $3ter the table ?as created success3ully@ ulti!le HV.TSE 3iles are generated 3or each AF(&( condition. The HV.TSE 3iles ?ill be created ?ith the s!ecial o!tion H7?here to !ut the AF(&( condition into it.

6igure #&#: -xam'*e: M!FMO/ !m'ort Pro"essing ;&< 5or each HV.TSE 3ile@ the corres!onding HV.CM 3ile is generated. 0e3ore starting the i!ort@ &'4O$ co!ares the AF(&( condition bet?een the HV.TOC and HV.TSE 3iles. &'4O$ sto!s on error in case o3 a isatch.

6igure #&&: -xam'*e: M!FMO/ !m'ort Pro"essing ;)<  $3ter start@ &'4O$ co!ares the AF(&( condition bet?een the HV.TOC and HV.TSE 3iles and terinates on error in case o3 a isatch. $ success3ul i!ort is only !ossible i3 the AF(&( condition used 3or the ex!ort is identical to the one during i!ort. Other?ise a !ossible restart ?ould delete ore or less data 3ro a table@ ?hich can result in a data loss. In case o3 an Oracle H7load!rocedure 3ast@ &'4O$ does not coit data until the i!ort is 3inished success3ully.

6igure #&): -xam'*e: M!FMO/ !m'ort Pro"essing ;(<  $3ter all !arallel i!ort !rocesses 3or the s!litted table ?ere 3inished@ the reaining tass can be startedD creating the !riary ey and secondary indexes. This !ost7i!ort !hase is ared in the MIGMO+ Hi!ort.state.!ro!erties 3ile as HZtable[7!ostY_. 5or databases creating the !riary index be3ore i!ort@ the reaining tas is the secondary index generation only.

6igure #&(: -xam'*e: 6or"e Se8uentia* !m'ort o9 C2!S S'*its I3 the target database does not allo? to i!ort ?ith ulti!le &'4O$ !rocesses into the sae table /because o3 !er3orance or locing issues1@ MIGMO+ can be instructed to use a single &'4O$ !rocess 3or a s!eci3ied list o3 !acages. In the above exa!le@ the 3ile Hi!ortorder.txt is read by MIGMO+ to set the i!ort order.  $ll !acages belonging to grou! CEISQ@ that is CEIS7, to CEIS7,,@ ?ill be i!orted using one single &'4O$ !rocess /job+u Y ,1. This does not guarantee@ that CEIS7, is i!orted be3ore CEIS72@ but it ?ill ae sure that no t?o &'4O$ !rocesses i!ort into CEIS.  $ grou! can have any nae@ but it aes sense to nae it lie the table in charge. 0eside the nuber o3 &'4O$ !rocesses /job+uY1 the &'4O$ arguents 3or tas 3ile generation /tas$rgsY1 and i!ort /load$rgsY1 can be de3ined individually 3or each grou!. The total nuber o3 running &'4O$ !rocesses is the su o3 the s!eci3ied nuber o3 !rocesses in Hi!ortonitorcd.!ro!erties and the nuber o3 !rocesses de3ined in Hi!ortorder.txt.

6igure #&+: -xam'*e: Dire"tory Content a9ter !m'ort 5or OracleD > CEISPI.TSED create table@ but do not create !riary ey@ indexes@ or load data > CEISTPI.TSED load data@ but do not create table@ !riary ey@ or indexes > CEIST.TSED create !riary ey and indexes@ but do create table@ or load data

3esson: D!STMO/  Distriution Monitor 9or ,&3OAD Business -xam'*e In a test run o3 a )nicode Conversion !roject@ it ?as identi3ied that the CP) load on the database server ?as the bottlenec o3 the &'4O$ ex!ort. &unning &'4O$ on a se!arate server ?ould solve the !roble. I3 ore than one &'4O$ server is !lanned@ it aes sense to utili9e the istribution Monitor.

6igure #&7: D!STMO/  Distriution Monitor  To distribute the &'4O$ CP) load to di33erent systes@ various ty!es o3 a!!lications servers can be used@ i.e. a ix o3 t?o # CP) systes and one 8 CP) syste or even systes running on di33erent o!erating systes. $s long as the o!erating systes and 0 clients libraries are su!!orted by the res!ective S$P release@ a ?ide range o3 syste cobinations are !ossible. +evertheless@ 3ro an adinistrative !oint o3 vie? it ?ill be ore easy to have a hoogeneous o!erating syste landsca!e@ 3ile syste sharing can be co!lex other?ise.

6igure #&: D!STMO/  ,estri"tions

ISTMO+ is aing use o3 &'4O$ 3eatures not available belo? %.#-. ISTMO+ can only handle the $0$P data ex!ort. 6$<$ stacs ust be ex!orted using 64O$.

6igure #&: D!STMO/ Server 3ayout The counication directory is used to share con3iguration and status in3oration aong the servers. It is !hysically ounted on one o3 the involved systes and shared to the other a!!lication servers. Control 3iles /V.ST&@ 4V.TP4@ ex!ortonitorcd.!ro!erties and i!ortonitorcd.!ro!erties1 are generated here and distributed during the !re!aration !hase. 0ecause o3 sa3ety reasons@ the ex!ort o3 each a!!lication server is ?ritten to local ounted diss and not to +5S ounted 3ile systes.

6igure #)0: D!STMO/ Distriution Pro"ess (ach MIGMO+ ?ill be started locally on the res!ective a!!lication server. That eans@ each a!!lication server  can run a MIGMO+ 3or ex!ort and a second one 3or the i!ort. The start is initiated by ISTMO+. (ach MIGMO+ runs inde!endently and does not no? about other MIGMO+s in the case o3 !arallel ex!ort*i!ort on the sae server. The status onitor allo?s the onitoring o3 the a!!lication servers 3ro a single user inter3ace. Status in3oration is read 3ro the shared counication directory. (ach MIGMO+ ?ill be started locally on the res!ective a!!lication server. That eans@ each a!!lication server  can run a MIGMO+ 3or ex!ort and a second one 3or the i!ort. The start is initiated by ISTMO+. (ach

MIGMO+ runs inde!endently and does not no? about other MIGMO+s in the case o3 !arallel ex!ort*i!ort on the sae server. The status onitor allo?s the onitoring o3 the a!!lication servers 3ro a single user inter3ace. Status in3oration is read 3ro the shared counication directory.

3esson: 5M!FMO/  Migration Monitor 9or 53OAD Business -xam'*e ou need to no?@ the a!!ro!riate 6MIGMO+ con3iguration scenario 3or a s!eci3ic custoer S$P Syste landsca!e.

6igure #): 5A=A Migration Monitor ;5M!FMO/<  6eatures The very 3irst i!leentation cae ?ith S$PI+ST :.-2. The 64O$ !acage 3iles ust be created ?ith 6PEGCT4 be3ore starting the ex!ort or i!ort. The !arallel ex!ort * i!ort aes use o3 HV.SG+ 3iles lie in the MIGMO+ i!leenation. 6PEGCT4 creates a Hsi9es.xl containing the !acage si9es to su!!ort an ordered ex!ort ?ith the largest !acages 3irst. 5ailed 64O$ !rocesses can be restarted by changing the content o3 the 3ile Hex!ort*i!ort.jigon.states.

6igure #)#: 5M!FMO/  /et Con9iguration The 6MIGMO+ net?or con3iguration is use3ul in environents@ ?here 3ile systes can be shared bet?een source and target syste. 5or consistency reasons@ ex!orts should al?ays be done to local 3ile systes * directoriesL In the exa!le above@ the ex!ort directory and the net?or exchange directory are shared 3ro the ex!orting to the i!orting syste. $s soon as a !acage is success3ully ex!orted@ the corres!onding signal 3ile /V.SG+1 ?ill be created in the net?or exchange directory. +o? the i!orting 6MIGMO+ starts an 64O$ !rocess to load the du! 3ro the shared ex!ort directory.

6igure #)&: 5M!FMO/  StandA*one Con9iguration The 6MIGMO+ HStand7$lone Con3iguration is use3ul in environents@ ?here source and target systes do not have a net?or connection@ or the existing connection is too slo? 3or a 3ile trans3er. In the above exa!le@ the ex!ort and i!ort directories are located on se!arate hosts in di33erent locations. The 6MIGMO+ is used to start 64O$ !rocesses only. The 3ile trans3er bet?een the source and target syste ?ill be done using trans!ortable edia.

6igure #)): 5M!FMO/ Contro* and Out'ut 6i*es The Hjigon.console.log should be ins!ected in case o3 ex!ort or i!ort errors. More detailed in3oration can be 3ound in the res!ective job log. The 6MIGMO+ state 3iles are used to control ?hich !acages are already ex!orted@ currently in use@ or terinated on error. Changing a !acage state 3ro inus /H71 to 9ero /H-1@ ?ill 3orce 6MIGMO+ to restart the  job. (xa!le ex!ortjigonstatesD (KPO&TM(T$$T$.KM4Y_ 5inished (KPO&T,'62((CO+5IG(+T&.KM4Y_ 5inished /s!litted table1 (KPO&T,#62((CO+5IG(+T&.KM4Y_ 5inished /s!litted table1 (KPO&T-.KM4Y_ 5inished (xa!le Ii!ort.jigonstatesD IMPO&TM(T$$T$.KM4Y_ 3inished MPO&T,'62((CO+5IG(+T&.KM4Y_ 3inished /s!litted table1 IMPO&T,#62((CO+5IG(+T&.KM4Y running /s!litted table1 IMPO&T-.KM4Y7 3ailed

3esson: Ta*e S'*itting 9or 53OAD Business -xam'*e ou need to no?@ ho? 64O$ table s!litting is ?oring and ho? to troubleshoot !robles.

6igure #)(: 5P2FCT3  Pa"1age and Ta*e S'*itting The Hs!lit !araeter de3ines the si9e liit 3or 64O$ !acages. 6PEGCT4 ?ill add as any tables to a !acage until the si9e liit is reached. The nuber o3 !acages is related to the si9e liit !araeter. $ sall si9e ?ill result into a large nuber o3 !acage 3iles co!ared to a large si9e ?hich ?ill create 3e? !acages only. I3 a table is eual or larger then the given si9e@ the !acage 3ile ?ill contain this single table only. The Hs!litrules3ile is only reuired i3 table s!litting is !lanned. It can contain entries in three di33erent 3orats. I3 only the nuber o3 s!lits is s!eci3ied@ all 3ields o3 the !riary ey are checed 3or highest selectivity. In the case ?here a single 3ield is ex!licitly given@ only this 3ield is used 3or s!litting. I3 ulti!le 3ields are !rovided@ the ost selective 3ield is used.

6igure #)+: 5P2FCT3 ;5SP3!TT-,<  or19*ow The Hjs!littercd.!ro!erties 3ile is generated according user in!ut by S$PI+ST. 6PEGCT4 connects to the database@ reads the database objects de3initions and calculates the si9es o3 ites to be ex!orted. The tables are distributed to the 64O$ job 3iles /!acages1. The distribution criteria is the !acage si9e as !rovided in the Hjs!littercd.!ro!erties 3ile.  $3ter all !acages are created@ the Hsi9es.xl 3ile containing the ex!ected ex!ort si9e o3 each !acage is ?ritten. 6MIGMO+ ?ill use the content to start the ex!ort in the !acage si9e order.

6igure #)7: 5P2FCT3 ;5SP3!TT-,<  Ta*e S'*it Strategy Table s!litting is an o!tional tas. It aes sense 3or large tables ?hich do in3luence the ex!ort tie signi3icantly. 6PEGCT4 is able to 3ind a use3ul s!lit colun autoatically@ but then it ?ill only chec the 3ields o3 the !riary ey. I3 a di33erent 3ield should be used@ it ust be ex!licitly entioned in a s!lit rule 3ile. I3 the reuested nuber o3 s!lits cannot be achieved@ the nuber o3 s!lits ?ill be autoatically reduced. I3 even this does not result into use3ul AF(&( conditions@ 6PEGCT4 gives u! and no table s!litting taes !lace.

6igure #): -HPO,TJPAC2AF-K.HM3 o9 a s'*itted Ta*e The AF(&( condition is used to select data o3 a s!eci3ied range. 5or each job 3ile o3 a s!litted table@ a se!arate 64O$ is started.

-xer"ise : Advan"ed Migration Te"$ni8ues So*ution : Advan"ed Migration Te"$ni8ues Tas1 :  $ custoer database o3 an $0$P S$P Syste has ,- very large tables that are bet?een 2 and 2- G0 in si9e and soe other large tables ranging 3ro "-- X 2.--- M0. $3ter the 6$<$7 or Perl7based Pacage S!litter ?as executed ?ith o!tion H7to! ,- /ove the ,- largest tables to se!arate V.ST& 3iles1 ,- additional V.ST& 3iles exit@ but contain other tables than ex!ected. ,. Ahat can be the reason o3 this behavior >int: Ahat 3ile is read to get the table si9e Ahat ha!!ens to large tables

a1 &'SNCFE liits the co!uted table si9es to a axiu o3 ,.:8 G0. 0e7cause o3 this@ the !acage s!litter catches the 3irst ,- largest tables 3ound in the V.(KT 3iles. $ 2- G0 table ?ill have the sae V.(KT entry as a 2--- M0 table.

Tas1 #: In a !re!aration o3 an &'4O$ heterogeneous syste co!y@ the custoer ?as ased to install Perl " or a 6$<$ 6E on his Aindo?s !roduction syste@ but he denied@ because o3 restrictive so3t?are installation !olicies. ,. +evertheless@ ?hat can be done to i!rove the ex!ort tie a1 The V.ST& 3iles can be s!lit anually using an editor@ or can be trans3erred to another syste ?here Perl or 6$<$ is available to !er3or the s!lit. In order to do this@ the ex!ort ?ill need to have been sto!!ed a3ter &'SNCFE has started. Caution: I3 the s!lit is done in advance@ be sure that no ne? changes have been ade to the $0$P dictionary since the initial creation o3 the V.ST& 3ilesL Other?ise you ris inconsistencies.

Tas1 &: The Migration Monitor has a client and a server ex!ort ode. ,. Ahat are the bene3its o3 using the client ode a1 +o changes to the standard &'S(T)P or S$PI+ST ex!ort !rocess is reuired. b1 $utoatic 3ile trans3er to the target syste is !ossible. c1 The data load can be started autoatically as soon as the 3irst !acage is signaled to be ready.

Unit 9 Per9orming t$e Migration 3esson: Per9orming an ABAP System Migration Business -xam'*e ou need a uic overvie? about the executed ste!s in an $0$P Syste Migration.

6igure #): Te"$ni"a* Migration Ste's ;ABAPBased System< Many igration ste!s can be !er3ored in !arallel in the source and target systes.  $3ter ste! ' /generate te!lates 3or 0 si9es1 has been !er3ored in the source syste@ you should be !re!ared to start ste! 8 /create database in the target syste1. Once ste! % /3ile trans3er1 is co!lete@ ste!s :7 8 should already have been !er3ored in the target syste. In the case ?here MIGMO+ is used 3or concurrent ex!ort*i!ort@ the ste!s #@ "@ %@ =@ ,- ?ill run in !arallel

6igure #(0: Te"$ni"a* Migration Pre'aration ;< 6ust be3ore you start the igration@ chec all the igration7related S$P +otes 3or u!dates. 6igure #(: Te"$ni"a* Migration Pre'aration ;#< To reduce the tie reuired to unload and load the database@ inii9e the aount o3 data in the igration source syste. 0e3ore the igration ae sure to de7schedule all jobs in the source syste. This avoids jobs 3ailing directly a3ter the 3irst start o3 the igrated S$P Syste. The re!orts 0TCT&+S, /set jobs into sus!end ode1 and 0TCT&+S2 /reactivate jobs1 can be hel!3ul. Chec the corres!onding S$P +otes and S$P Syste u!grade guides 3or 3urther re3erence. I3 the target syste has a ne? S$P SI@ release all the corrections and re!airs be3ore starting the ex!ort. I3 the database contains tables that are not in the $0$P ictionary@ chec ?hether soe o3 these tables also have to be igrated. 6igure #(#: Te"$ni"a* Migration Pre'aration ;&<

The execution o3 re!ort HSMIG&C&($T(4 is andatory 3or all S$P systes using non7standard database objects /0I*0A@ SCM*$PO1. 5or +etAeaver -# and later@ the execution o3 HSMIG&C&($T(4 is a ustL Mae sure not to ae any changes to the non7standard objects a3ter HSMIG&C&($T(4 has been calledL I3 no database s!eci3ic objects exist@ then no ZT$0$&T[.S4 3iles ?ill be generated.  $s long as the re!ort terinates ?ith status Hsuccess3ully@ everything is o. The HInstallation irectory can be any 3ile syste location. Co!y ZT$0$&T[.S4 3iles to the S$PI+ST ex!ort install directory or directly into the HZex!ortdir[*0*Ztarget0S[ directory. 5ollo? the guidelines in the hoogeneous*heterogeneous syste co!y anual. e!ending on the target database additional o!tions ight be available@ ?hich can be selected in the 3ield Hatabase ::,2-= H+etAeaver -#D Syste co!y /su!!leentary note1 > 8882,- H+etAeaver :.--*:.,-D Syste Co!y /su!!leentary note1 6igure #(&: Fenerate G.-HT and G.ST, 6i*es &'S(T)P*S$PI+ST calls &'4CT4 and &'SNCFE. The runtie o3 &'SNCFE de!ends on the version@ the si9e o3 the database and the database ty!e. 0SIN(.TP4 is created by &'S(T)P@ 3ro the in3oration co!uted by &'SNCFE and stored in table 4O$. 6igure #(): S'*it G.ST, 6i*es and Ta*es The generated V.ST& and V.(KT 3iles ?ill be s!lit into saller units to i!rove the unload*load ties. &'S(T)P calls the Perl scri!t to s!lit V.ST& 3iles. e!ending on the version@ S$PI+ST uses the 6$<$7 or the Perl7based Pacage S!litter. On large databases table s!litting ?ill reduce the ex!ort * i!ort run7tie signi3icantly.

6igure #((: Fenerate -x'ort G.CMD and G.TS2 6i*es S$PI+ST*MIGMO+ call &'4O$ to create tas 3iles. &'S(T)P*S$PI+ST*MIGMO+ generates coand 3iles. I3 AF(&( 3iles exist@ the AF(&( conditions ?ill be inserted into the V.TSE 3iles.

6igure #(+: -x'ort Dataase wit$ ,&3OAD &'S(T)P*S$PI+ST*MIGMO+ start a nuber o3 &'4O$ !rocesses. $ se!arate &'4O$ !rocesses is started 3or each coand 3ile. The &'4O$ !rocesses ?rite the du! 3iles to dis.  $s soon as an &'4O$ !rocess terinates /?hether success3ully or due to error1@ &'S(T)P*S$PI+ST*MIGMO+ start a ne? &'4O$ !rocess 3or the next coand 3ile. o not use +5S 3ile systes as an ex!ort target 3or the du! 3ilesL u! 3iles can be unnoticeably daaged and cause data corru!tionL 6igure #(7: Manua* 6i*e Trans9er ;< (0CIC &'4O$ control 3iles created on $S*#-- systes ust be trans3erred in $SCII ode@ i3 the target syste is to run on an $SCII7based !lat3or. In cases ?here du! 3iles ust be co!ied to trans!ortable edia@ ae sure that the 3iles are co!ied correctly. Its better to s!end additional tie on veri3ying the co!ied 3iles against the original 3iles than s!ending several hours or even days to trans!ort the to the target syste@ only to discover that soe 3iles had been corru!ted by the co!y !rocedure used. $!!ro!riate checsu tools are available 3or every o!erating syste. 6igure #(: Manua* 6i*e Trans9er ;#<

The 3ile H4$0(4.$SC is generated during the ex!ort o3 the source database. &'S(T)P*S$PI+ST uses its content to deterine ?hether the load data is read 3ro the correct directory. Since :.-2@ the S45iles.4ST is generated by SMIG&C&($T(4 together ?ith the V.S4 3iles. The V.CM and V.TSE 3iles are generated se!arately 3or ex!ort and i!ort. There3ore@ do not co!y theL 6igure #(: Fet Migration 2ey ;< The igration ey ust be reuested 3ro the custoer@ because he has to acce!t the sho?n igration ey license agreeent. Chec the igration ey as soon as !ossibleL $ll entries are case sensitive. 0e3ore o!ening a !roble call@ See S$P +ote ''8':2. 6igure #+0: Fet Migration 2ey ;#< Since #.%@ the igration ey is identical 3or di33erent S$P Systes o3 the sae installation nuber. The igration ey ust atch the &'4O$ version. I3 ased 3or the S$P &*' &elease@ enter the release version o3 the used &'4O$. I3 in doubt chec the log 3iles. Soe systes are using several di33erent hostnaes /i.e. in a cluster environent1. The node nae sho?n by Hunae 7a or Hhostnae should be the H0 Server Fostnae. Starting ?ith #."$@ al?ays generate the igration ey 3ro the node nae ?hich is listed in the H/GSI1 I+5O section o3 the &'4O$ ex!ort log /source syste1 and MIGE(.log /target syste1. In soe installations the Syste I can even be in lo?er7case letters@ because it is obtained 3ro the 3irst three characters o3 H/GSI1 I+5OD dbnaeL The &'4O$ log 3iles o3 '.,I and #.-0 do not contain in3oration about the source syste@ as in versions #."$ and above. &'S(T)P and S$PI+ST test the igration ey by calling &'4O$ 7E /u!!er7case E1. The 3ile HMIGE(.log contains the chec results. The igration ey in +etAeaver :.-- Systes ?ith Hold S$P license installed /u!graded syste1 is di33erent then 3or the Hne? S$P license. Chec the corres!onding syste co!y note 3or details. See S$P +ote ''8':2 HMigration ey does not ?or 3or 3urther re3erence. 6igure #+: !nsta** SAP and Dataase So9tware 6igure #+#: Create Dataase The si9e values 3or the target database that are calculated 3ro the source database serve only as starting !oints. Generally@ soe values ?ill be too large and others ?ill be too sall. There3ore@ be generous in your database si9ing during the 3irst igration test run. The ex!erience gained through the test igration is better than any advanced estiate you could calculate@ and you can al?ays adjust the values in subseuent tests.

6igure #+&: Fenerate !m'ort G.CMD and G.TS2 6i*es S$PI+ST*MIGMO+ call &'4O$ to create tas 3iles. &'S(T)P*S$PI+ST*MIGMO+ generate coands 3iles. I3 AF(&( 3iles exist@ the AF(&( conditions ?ill be inserted into the V.TSE 3iles.

6igure #+): !m'ort Data wit$ ,&3OAD &'S(T)P*S$PI+ST*MIGMO+ starts the i!ort &'4O$ !rocesses.

6igure #+(: Te"$ni"a* PostMigration A"tivities ;< The general 3ollo?7u! activities are described in the hoogeneous and heterogeneous syste co!y guides and their res!ective S$P +otes. 0e3ore the co!ied syste is started the 3irst tie@ the consistency bet?een the $0$P and database dictionary ?ill be checed and u!dated. &'S(T)P*S$PI+ST ?ill start the !rogra Hdi!gntab 3or that !ur!ose. $ll u!dates o3 the active +$M(T$0 are logged in the 3ile Hdi!gntabZS$P SI[.log. The suary at the end o3 this 3ile should not re!ort any errorL

6igure #++: Te"$ni"a* PostMigration A"tivities ;#< In any cases@ the change o3 a database syste ?ill also include a change in the bacu! echanis. Mae sure to get 3ailiar ?ith the changed*ne? bacu!*restore !rocedures.  $3ter the igration@ the S$P Syste statistics and bacu! in3oration 3or the source syste can be deleted 3ro the target database. 5or a list o3 the tables@ see the syste co!y guide. 6igure #+7: Te"$ni"a* PostMigration A"tivities ;&< &e!ort &$0I5 creates database7s!eci3ic objects /tables@ vie?s@ indexes1. &$0I5 is usually called by &'S(T)P*S$PI+ST via &5C /user IC@ client ---1 a3ter the data is loaded.  $3ter o 3ro custoer side@ the S$P jobs that have been set to sus!end ode via re!ort 0TCT&+S,@ can no? be rescheduled ?ith 0TCT&+S2.

6igure #+: Te"$ni"a* PostMigration A"tivities ;)< The non7standard database objects /ainly 0A objects1 ?hich ?ere identi3ied on the source syste and are recreated and i!orted into the target syste@ ?ill need soe adjustents. The re!ort &S0APOSTMIG&$TIO+ ?ill do this. 5or 3urther re3erence chec S$P +ote :::-2# H0A '.- and 0A '., Syste co!y and*or read the corres!onding cha!ter H5inal $ctivities in the hoogeneous and heterogeneous syste co!y %.#- or higher. The !rogra should run inde!endently@ ?hether or not a V.S4 3ile ?as used or not. The data source syste connection can be checed in transaction &S$,. The &5C !araeters can be changed in transaction SM"=.

6igure #+: Te"$ni"a* PostMigration A"tivities ;(< The re!ort variants S$PPOSTMG&0 and S$PPOSTMG& are !re7de3ined 3or syste co!ies changing*not changing the database syste. &un the re!ort in the bacground@ because the execution can tae a ?hile. Invalidate Generated PrograsD Generated !rogras can be database s!eci3ic. In order to ae sure that every !rogra ?ill be re7generated according to the ne? database needs@ the already generated !rogras ?ill be invalidated.  $da!t 0I55 to +e? 0D e!ending on the database ty!e@ ore or less indexes ?ill be reuired. Table 0I55 ?ill be ada!ted accordingly. +o issing 0A objects ?ill be sho?n in transaction 0-2 a3ter?ards.  $da!t $ggregate IndexesD runs CF(CEI+(KST$T( $da!t 0asis Cube IndexesD runs CF(CEI+(KST$T( Generate +e? PS$
6igure #70: Te"$ni"a* PostMigration A"tivities ;+< The tables in the S$P----.ST& 3ile contain the generated $0$Ps /$0$P loads1 o3 the S$P Syste. These loads are no longer valid a3ter a hard?are igration. 5or this reason@ &'S(T)P*S$PI+ST does not load these tables. (ach $0$P load is generated autoatically the next tie a !rogra is called. The syste ?ill be slo? unless all coonly used !rogras are generated. )se transaction SG(+ /starting ?ith &elease #.%01 to regenerate all $0$Ps. On versions be3ore #.%0@ run transaction S$MT or re!ort &G(+4. The re!ort &G(+4 reuires the 3ile &(P4IST in the S$P instance ?or directory. To create the 3ile &(P4IST in the source syste@ call re!ort &4TC2.

6igure #7: PostMigration Test A"tivities Tae care ?hen setting u! the test environent. To !revent un?anted data counication to external systes@ isolate the syste. (xternal systes do not distinguish bet?een igration tests and !roduction access.

To develo! a cut over !lan@ an already existing checlist 3ro a !revious u!grade*igration can be a valuable source o3 ideas. To identi3y any di33erences bet?een the original and the igrated syste@ involve end users as soon as !ossible.

3esson: Per9orming a 5A=A System Migration Business -xam'*e ou need a uic overvie? about the executed ste!s in a 6$<$ Syste Migration. 6igure #7#: Te"$ni"a* Migration Ste's ;5A=ABased System<

6igure #7&: Te"$ni"a* Migration Pre'aration 6ust be3ore you start the igration@ chec all the igration7related S$P +otes 3or u!dates. 6igure #7): Fenerate Tem'*ate 9or Target DB Si@e

6igure #7(: Co**e"t A''*i"ation Data 9rom 6i*e System I3 S$PI+ST does not recogni9e the installed a!!lication and its related 3iles@ no archives ?ill be created. Mae sure to use the right version o3 the installation C@ as entioned in the a!!ro!riate S$P +otes regarding hoogeneous and heterogeneous syste co!ies.  $!!lications that are not recogni9ed by S$PI+ST ay reuire o!eration syste s!eci3ic coands to co!y the res!ective directories and 3iles to the target syste. I3 this is the case@ the corres!onding S$P +otes ?ill give instructions ho? to deal ?ith it. The co!y o3 other a!!lications ight need the installation o3 a certain su!!ort stac and a atching S$PI+ST.

6igure #7+: Co**e"t SDM Data In S$P releases belo? :.,-@ the SM re!ository itsel3 is installed in the 3ile syste and ?ill be rede!loyed into the target syste 3ro the SMEIT.6$& 3ile. 6igure #77: 5P2FCT3 ;5SP3!TT-,< on*y 6PEGCT4 is o!tional used since S$PI+ST :.-2. Pacaged job 3iles containing ulti!le tables are naed H(KPO&TZn[.KM4 and job 3iles 3or a single table only are naed H(KPO&TZn[ZT$04([.KM4. I3 a table ?as s!litted@ the resulting job 3iles are naed the sae but ?ith a di33erent nuber. 5or every ex!ort job 3ile an i!ort job 3ile is generated ?ith the sae nae but H(KPO&T is re!laced ?ith HIMPO&T. The Hsi9es.xl 3ile contains the ex!ected ex!ort si9e o3 each generated !acaged job 3ile. It hel!s 6MIGMO+ to ex!ort the !acages by si9e. The largest !acage ?ill be ex!orted 3irst@ then the next saller !acages@ and so on. 6igure #7: -x'ort Dataase wit$ 53OAD +oteD In versions ?ithout 6PEGCT4@ 64O$ is generating the (KPO&T.KM4 and IMPO&T.KM4 by itsel3.

6igure #7: 6i*e Trans9er  The 3ile H4$0(4IK.$SC and the H4$0(4.$SC 3iles are generated during the ex!ort o3 the source database. S$PI+ST uses its content to deterine ?hether the load data is read 3ro the correct directory. The HZex!ortdir[*$PPS directory ight be e!ty i3 no a!!lications are installed@ i.e. those ?hich are ee!ing their data in the 3ile syste. $nother !ossibility can be that the a!!lication is not no?n by S$PI+ST.

5uture releases ay be able to create additional directories*3iles in the ex!ort directory@ ?hich are naed HOthers in the above slide.

6igure #0: !nsta** DBSAP So9tware and -xtend Dataase In S$PI+ST versions belo? +etAeaver -#S the database si9e is set using a de3ault value. 6igure #: De'*oy SDM 6i*e System Data The So3t?are e!loyent Manager holds its re!ository in the 3ile syste. 5or a re7installation@ the content o3 SMIT.6$& ?ill be used@ ?hich contains the necessary 3ile syste co!onents as collected in the source syste. This ste! is not necessary anyore in +etAeaver :.,- and later.

6igure ##: !m'ort dataase wit$ 53OAD In versions ?ithout 6PEGCT4@ 64O$ is generating the (KPO&T.KM4 and IMPO&T.KM4 by itsel3. 6igure #&: ,estore A''*i"ation Data to 6i*e System More and ore 6$<$7based so3t?are co!onents ?ill be integrated into the S$PI+ST syste co!y !rocedure. In the eantie@ S$P +otes ?ill give instructions ho? to co!y or to extract data anually@ i3 reuired. Since :.,- ?ell behaving 6$<$ !rogras should not ?rite !ersistent data into the 3ile syste.

6igure #): Te"$ni"a* Post Migration A"tivities The general 3ollo?7u! activities are described in the hoogeneous and heterogeneous syste co!y guides and their res!ective S$P +otes. The license ey o3 the source syste is not valid 3or the target syste. ou ?ill reuired to !rovide a ne? one. 6$<$ systes that include co!onents that connect to an $0$P bacend using the S$P 6$<$ Connector /S$P 6Co1@ 3or exa!le S$P 0A or S$P (nter!rise Portal@ need to aintain the &5C destination.  $3ter syste co!y@ the !ublic7ey certi3icates ?ill be invalid on the target syste. ou ?ill need to recon3igure the. Co!onent s!eci3ic 3ollo?7u! activities 3or S$P 0A@ $dobe ocuent Services@ S$P Eno?ledge Aarehouse@ S$P (&P@ S$P C&M.

6igure #(: PostMigration Test A"tivities Tae care ?hen setting u! the test environent. To !revent un?anted data counication to external systes@ isolate the syste. (xternal systes do not distinguish bet?een igration tests and !roduction access. To identi3y any di33erences bet?een the original and the igrated syste@ involve end users as soon as !ossible.

-xer"ise 0: Per9orming t$e Migration Business -xam'*e ou need to reuest an OS*0 Migration Eey 3ro S$P. 5or that !ur!ose@ you need to no? the right installation nuber 3or the ey reuest.

So*ution 0: Per9orming t$e Migration Tas1 : In the !re!aration o3 a &'4O$ syste co!y@ the custoer ?as ased 3or scheduled bacu!s@ scheduled S$P Syste jobs@ external !rogras or inter3aces ?hich are ?riting directly to the database and the !lanned S$P SI o3 the target syste. ,. Ahy is it i!ortant to no? ?hich jobs are scheduled /S$P Syste or external jobs1 a1 Ahile the ex!ort is running@ only the S$P instance is shutdo?n. (xternal !rogras or inter3aces that are directly ?riting into the database@ ?hile the ex!ort is running@ can cause inconsistenciesL

b1 Scheduled database bacu!s can shutdo?n the database@ or decrease the ex!ort !er3orance. c1 $3ter starting the igration target syste the 3irst tie@ scheduled jobs ay be executed iediatelyU this can either be har3ul or not har3ul@ de!ending on their nature. In this stage@ the target syste has not been !ro!erly con3igured. 6obs that need to be run 3or veri3ication !ur!oses ay only be ca!able o3 being executed once. >int: The 0TCT&+S, and 0TCT&+S2 re!orts are available to set all scheduled jobs to Hsus!ended status on the source syste@ and to invoe the again on the target syste. On earlier S$P Syste versions@ critical jobs should be set to H!lanned status be3ore starting the ex!ort. I3 this is not !ossible@ tae suitable !recautions in the target syste. 2. In the case that the S$P SI ?ill be changed during the syste co!y@ ?hich actions should be taen be3ore the ex!ort a1 In the case that the S$P SI is changed@ all o!en Corrections and &e!airs should be released in the source syste. I3 not@ the trans!ort syste initiali9ation /S(-%1 ?ill close the ?ithout releasing the trans!orts to the 3ile syste.

Tas1 #: The ex!ort o3 a heterogeneous syste co!y runs on the central instance S$P Syste ?ith the 3ollo?ing con3igurationD Source systeD Installation nuberD -,2--#:,, Standalone database server hostnaeD Hdbsrv-, Central instance server hostnaeD Hcisrv-, Target systeD Installation nuberD -,2---8," Central instance ?ith database@ hostnaeD Hcidb--, ,. Ahat ?ould be the correct installation nuber to reuest the igration ey a1 The installation nuber o3 the source syste ?ill al?ays be used to generate the igration ey. In this case@ H-,2--#:,,. 2. Ahich hostnaes ust be !rovided ?hen 3illing the igration ey reuest 3or in the S$P Service Maret!lace a1 The hostnae o3 the syste that &'4O$ is running on is o3 great i!ortance. $s the ex!ort has to be done on the central instance@ the 3ollo?ing cobination o3 hostnaes are needed to reuest the igration eyD (x!ort systeD Hciserv-, I!ort systeD Hcidb--, '. Ahere can in3oration about the &'4O$ version and ?hich hostnaes ?ere used 3or ex!ort*i!ort /es!ecially in environents ?here systes have a lot o3 net?or controllers and IP addresses or are even clustered1 be 3ound a1 The &'4O$ ex!ort and i!ort log 3iles contain the used hostnaes. In case o3 a igration ey isatch@ al?ays chec these entries. >int: Ahen reuesting the igration ey@ ae sure to enter the version o3 &'4O$ and not the version o3 the S$P /base1 Syste. The &'4O$ version is entioned in the log 3iles. The versioning can be con3using on S$P releases running on a bac?ard co!atible ernel.

Unit 10  Trou*es$ooting This unit is discussing s!ecial error situations. Soe o3 the are uite rare@ but nevertheless they occurL Point outU the ost i!ortant no?ledge 3or trouble shooting is to understand the restart behavior o3 &'4O$ and 64O$ very ?ell.

Unit Overview 3esson: Trou*es$ooting Business -xam'*e

There are soeties strange error situations ?hich are not easy to understand. ou ?ant to understand their reasons and ho? to avoid the.

6igure #+: ,&3OAD  Un*oad Terminations The igration tools used are not co!atible ?ith the current S$P Syste or database version Pass?ord !robles Changes to the root user or the environent necessary be3ore starting &'S(T)P*S$PI+ST The active object de3inition in the $0$P ictionary di33ers 3ro the object de3inition in the database@ or the tables do not exist on 0 at all. 5or soe tables@ this is intentional and is caught by a s!ecial handling routine in &'4CT4. These tables are usually recorded in the exce!tion table 0I55@ and do not cause errors. There3ore@ i3 an error occurs@ it ust involve a table ?hose data de3inition is unintentionally ?rong. This situation ust be corrected. O3ten CMV tables are involved. +ot enough s!ace to unload the data in the du! 3ile syste. $s a rule o3 thub@ the ex!ort can be started to a 3ile syste ?hich has about ,-W 7 ,"W o3 the database si9e. I3 no additional dis s!ace is available@ co!y already 3inished du! 3iles to a di33erent location ?hile the ex!ort is running. 5or the Perl P$CE$G( SP4ITT(&D Is at least Perl version " installed oes the de3ault search !ath !oint to the right Perl executable oes the 3irst line o3 the SP4ITST&.P4 scri!t contain the right nae o3 Perl in your syste 5or the 6$<$ P$CE$G( SP4ITT(&D Is the right 6$<$ version installed &'4O$ ex!orts data in the !riary ey order. e!ending on the database used@ ore te!orary databases dis s!ace ay be reuired 3or sorting. Increase database storage units that are used 3or sorting /i.e. PS$PT(MP1. &elated S$P +oteD ='8" HAhat to do ?ith CM tables

6igure #7: ,&3OAD  3oad Terminations +ot enough te!orary database dis s!ace 3or index creation /sorting1. Increase the database storage units that are used 3or sorting /i.e. PS$PT(MP1@ or reduce the nuber o3 !arallel running &'4O$ !rocesses. Oracle rollbac segent !roblesD &estart &'S(T)P*S$PI+ST and try again. $lternatively@ you can reduce the nuber o3 !arallel running &'4O$ !rocesses@ or i!leent the necessary easures in the database /Oracle1. Older installation so3t?are ay not activate Oracle undo anageent. The igration tools used are not co!atible ?ith the current S$P Syste or database version $re changes to the root user environent necessary be3ore starting &'S(T)P*S$PI+ST Mae sure that the database user can access the directories and 3iles o3 the i!ort 3ile syste.

6igure #: Use9u* ,&3OAD -nvironment =aria*es ;< The &'4O$ ?arning level can have any value@ as long as soething is set. The &'4O$ trace level is 3or?arded to the 0S4 inter3ace only. )se3ul values are bet?een , and #. The higher the value@ the ore out!ut that is ?ritten. Most o3 the out!ut can only be inter!reted 3ro develo!ers@ but in the case o3 database connection !robles@ the trace can give valuable hints 3or troubleshooting. 6igure #: Use9u* ,&3OAD -nvironment =aria*es ;#< The &'4O$ ?arning level is use3ul in cases ?here 3iles cannot be 3ound or o!ened ?ithout an obvious reason. The contained list o3 environent variables can assist you in the analysis o3 database connection !robles@ caused by ?rong environent settings. In general@ uch ore in3oration is ?ritten then noral.

6igure #0: ,&3OAD  3oad Termination -xam'*e Initial situationD ,. Table $T$0 has been created success3ully. 2. 02 S4 error "", occurs during an I+S(&T to table $T$0. '. (rror textD atabase user S$P&' is not authori9ed to !er3or the I+S(&T. &'4O$ res!onseD

The &'4O$ !rocess that is !rocessing 3ile HS$PPOO4.CM cannot continue@ due to the S4 error. $ terination occurs. &'S(T)P*S$PI+ST is given a negative return code and starts a ne? &'4O$ !rocess 3or  the next coand 3ile. Correcting the !robleDGrant access authori9ation 3or table $T$0 to user S$P&'

6igure #: ,&3OAD  ,estart -xam'*e ,&3OAD  ).+D Situation a3ter &'4O$ has been started againD ,. &'4O$ reads the last entry in the HS$PPOO4.4OG 3ile. 0ecause the error occurred during the load@ and not ?hile creating the table@ the table contents ust be deleted 3irst. To do this@ &'4O$ executes the S4 stateent H(4(T( 5&OM. In the above case@ no data has been loaded yet@ ?hich ex!lains the S4 error ,-- /&o? not 3ound1. 2. &estart co!lete. ata ?ill be loaded.

6igure ##: ,&3OAD  ,estart -xam'*e ,&3OAD E +.0 Situation a3ter &'4O$ has been started againD /,1 &'4O$ reads the 3irst tas o3 status Herr or Hxe 3ro the HS$PPOO4.TSE 3ile. 0ecause the error occurred during the load@ and not ?hile creating the table@ the table contents ust be deleted 3irst. To do this@ &'4O$ executes the truncate*delete S4 stateent ?hich is de3ined in the 4Z0S[.TP4 3ile. /21 &estart co!lete. ata ?ill be loaded.

6igure #&: Du'*i"ate 2ey at !m'ort Time In ost cases@ du!licate eys are caused by unex!ected terinations at ex!ort or i!ort tie. The 3ollo?ing !ages ?ill !rovide reasons and !roble solutions. Soe tables ight not have a !riary ey on the source database@ but in the $0$P IC. This ay or ay not be intentional. Please as the custoer 3or reasons and*or chec 3or S$P +otes. +o V.S4 3ile ?as 3ound by &'4O$@ or SMIG&C&($T(4 ?as not called on the source syste. In the source database@ silently corru!ted !riary eys can lead to double ex!orted data records. In this case@ the nuber o3 records in the V.TOC 3ile ?ill be larger than the nuber o3 ro?s ?hich are re!orted by a S(4(CT CO)+T/V1 stateent.
6igure #(: Power 6ai*ure  OS Cras$ at -x'ort Time ;#< In the above exa!le@ a !o?er 3ailure or o!erating syste crash occurred. $s the o!erating syste could not 3lush all o3 the 3ile bu33ers to dis@ the result ?as a isatch bet?een the du! 3ile and the V.TOC or V.TSE 3ile content. &'load ex!orted T$04(-8 already and the V.TOC or V.TSE ?as u!dated@ but the data ?as not yet ?ritten by the o!erating syste into the du! 3ile. The V.TOC 3ile contains bloc #8@ as the last data bloc in the du! 3ile. &'4O$ until #.%D  $3ter restarting the ex!ort !rocess@ &'4O$ loos 3or the last ex!orted table in the V.TOC 3ile@ ?hich is T$04(-8. &'4O$ no? o!ens u! the du! 3ile and does a see to the next ?rite !osition bloc #= /?hich is behind end o3 3ile in this case1. The next table in the V.ST& 3ile to be read is T$04(-=@ ?hich ?ill be stored at

bloc #= and so on. The ga! bet?een bloc #2 /last !hysical ?rite1 and #= contains rando data. &'4O$ versions since #."$ ?ill create a bloc chec su /C&C1 to identi3y corru!ted data. (arlier versions ?ill try to load the data and ?ill usually sto! on error ?hile unco!ressing the data@ or ?ill sto! ?ith du!licate ey errors. &'4O$ %.,- and aboveD  $s it is not clear ?hether the V.TSE 3ile contains ore or less entries than the corres!onding du! 3ile@ the use o3 the Herge o!tion ay not be ,--W sa3e and can thus@ lead to the sae !robles as in earlier &'4O$ versions. This !roble is rare and it usually only ha!!ens to very sall tables that are ex!orted co!letely@ ?here only a 3e? blocs have to be 3lushed to the du! 3ile@ and the entry o3 V.TOC or V.TSE 3iles has already been ?ritten. 6igure #+: Power 6ai*ure  OS Cras$ at -x'ort Time ;&< In the above exa!le@ a !o?er 3ailure or o!erating syste crash occurred. $s the o!erating syste could not 3lush all o3 the 3ile bu33ers to dis@ the result is a isatch bet?een the du! 3ile and the V.TOC or V.TSE 3ile content. &'load ex!orted the large T$04(-2 already and the V.TOC or V.TSE ?as u!dated@ but the last 8 data blocs ?ere not yet ?ritten by the o!erating syste into the du! 3ile. The V.TOC 3ile contains bloc '2-.--as the last valid data bloc in the du! 3ile. &'4O$ until #.%D  $3ter restarting the ex!ort !rocess@ &'4O$ loos 3or the last ex!orted table in the V.TOC 3ile@ ?hich is T$04(-2. &'4O$ no? o!ens u! the du! 3ile and does a see to the next ?rite !osition bloc '2-.--, /?hich is behind end o3 3ile in this case1. The next table in the V.ST& 3ile to be read is T$04(-'@ ?hich ?ill be stored at bloc '2-.--, and so on. The ga! bet?een bloc ',=.==2 /last !hysical ?rite1 and '2-.--, contains rando data. &'4O$ versions since #."$ ?ill create a bloc chec su /C&C1 to identi3y corru!ted data. (arlier versions ?ill try to load the data and ?ill usually sto! on error ?hile unco!ressing the data@ or ?ill sto! ?ith du!licate ey errors. &'4O$ %.,- and aboveD  $s it is not clear ?hether the V.TSE 3ile contains ore or less entries than the corres!onding du! 3ile@ the use o3 the Herge o!tion ay not be ,--W sa3e and can thus lead to the sae !robles as in earlier &'4O$ versions. This !roble is rare and it can ha!!en to tables that are ex!orted co!letely ?here only the last blocs have to be 3lushed to the du! 3ile@ and the entry o3 V.TOC or V.TSE 3iles has already been ?ritten. 6igure #7: Power 6ai*ure  OS Cras$ at -x'ort Time ;)< &eove only 3iles 3or !acages that ?ere not co!leted at the tie o3 the syste crash. I3 the V.TSE 3ile has been u!dated be3ore all data ?as 3lushed to the du! 3ile by the o!erating syste@ the content can be isleading. Tas 3iles can be re7created by using the sae &'4O$ coand line as sho?n in the V.4OG 3ile. In the described case@ it is not recoended to use the Herge o!tion to restart ?ithout re!eating the ex!ort o3 the involved &'4O$S 3ro scratch.

6igure #: ,&3OAD  -x'ort -rror due to S'a"e S$ortage ;< In the described case@ it is not recoended to use the Herge o!tion to restart ?ithout re!eating the ex!ort o3 the involved &'4O$S 3ro scratch. The sae scenario can ha!!en i3 an ex!ort !rocess is ?riting to an +5S 3ile syste ?hile a net?or error occurs. &55D Cannot read 3ro 3ile error. &50D Cannot read 3ro bu33er error. 6igure #: ,&3OAD  -x'ort -rror due to S'a"e S$ortage ;#< S$P +oteD :%=#:% Hanger o3 inconsistencies The above ex!ort log sho?s unload terinations due to a shortage o3 s!ace in the 3ile syste. $3ter increasing the s!ace o3 the 3ile syste@ the ex!ort ?ill restart and 3inish ?ithout 3urther !robles. $t i!ort tie@ &'4O$ ?ill sto! ?ith a checsu error.

6igure &00: -x'ort ,u*es 9or ,&S-TUP  SAP!/ST  M!FMO/ The &'4O$ ex!ort !rocess is very sensitive@ so be sure to !revent any disturbance. I3 the &'4O$ ex!ort ?as done by soeone else and you are res!onsible 3or the i!ort only@ !lease ae sure to receive the ex!ort logs along ?ith the ex!ort du! 3iles. In case o3 i!ort errors@ because o3 du! corru!tions@ the ex!ort logs should be exained 3or troubleshooting. 6igure &0: Power 6ai*ure  OS Cras$ at !m'ort Time ;<

6igure &0#: Power 6ai*ure  OS Cras$ at !m'ort Time ;#< In the case o3 an OS crash or !o?er 3ailures@ it is di33icult to ascertain ?hich OS bu33ers ?ere 3lushed to the o!en 3iles or ?hat ha!!ened to the entire 3ile. In the above exa!le@ a !o?er 3ailure or o!erating syste crash occurred. $s the o!erating syste could not 3lush all o3 the 3ile bu33ers to dis@ the result is a isatch bet?een database content and the V.4OG or V.TSE 3ile. &'load i!orted Table-8 already@ but the V.4OG or V.TSE 3ile contained only the in3oration that Table-" and its !riary ey ?ere created. &'4O$ until #.%D The restart ?ill try to create Table-%@ but it already exists. &'4O$ sto!s on error. $ restart beginning ?ith data load@ can result in du!licate eys. $nother scenario that could occur is that the 3irst table ?ill be treated right and the !roble 3irst arises ?ith the second table. This de!ends on the V.4OG 3ile content. &'4O$ %.,- and aboveD The erge o3 V.TSE and V.0CE is necessary. $ll entries that are not ared as executed /Hxe1 ?ill be set to error /Herr1@ &'4O$ ?ill dro! or delete objects and data 3irst@ be3ore restarting a tas. This usually only ha!!ens to sall tables. $s databases are designed to ?rite data in a sa3e ?ay@ the &'4O$ i!ort is less critical in the case o3 !o?er 3ailures or o!erating syste crashes as o!!osed to the ex!ort o3 data.

6igure &0&: Power 6ai*ure  OS Cras$ at !m'ort Time ;&<

6igure &0): Du'*i"ate 2ey Pro*em a9ter ,estarting !m'ort ;< In a restart scenario ?here the i!ort o3 a large table 3ails and the S4 coand that deletes the entire table content has also 3ailed ?ith an error@ &'4O$ assues that the table has been e!tied and thus@ restarts the i!ort. The creation o3 the !riary ey sto!s ?ith a du!licate ey error. This ind o3 !roble has o3ten been caused by Oracle HSna!shot too old situations. $s &'4O$ %.x is using the Oracle HT&)+C$T( stateent to delete data@ the described error should not ha!!en any ore. +evertheless other database errors can lead to a siilar erroneous restart situations. 6igure &0(: Du'*i"ate 2ey Pro*em a9ter ,estarting !m'ort ;#< atabase7s!eci3ic delete coands /3or exa!le@ the Oracle coand T&)+C$T(1 can ?or 3aster than the standard S4 coand (4(T(. Ahen ani!ulating the HZP$CE$G([.4OG 3iles@ be very cautious and exaine the co!leted results care3ully. o not odi3y the V.4OG 3iles unless absolutely necessary. 5or veri3ication@ count the table ro?s a3ter i!ort.

6igure &0+: Du'*i"ate 2ey Pro*em a9ter ,estarting !m'ort ;&< 5or veri3ication@ count the table ro?s a3ter i!ort. 6igure &07: Corru'ted ,&3OAD Dum' 6i*es ;< &55Y&ead 3ro 3ile &50Y&ead 3ro bu33er  /&551 (&&O&D S$Pxxx.TOC is not 3ro sae ex!ort as S$Pxxx.--,

The du! 3ile is corru!ted@ or 3iles o3 di33erent ex!orts have been accidentally ixed. /&551 (&&O&D bu33er /... E01 too sall /the 3igure is larger than ,-.---1 &'4O$ read an invalid bu33er si9e 3ro the du! 3ile. The bu33er is used to load a certain nuber o3 data blocs to unco!ress it. Ty!ical bu33er si9es range only a 3e? M0. /&501 (&&O&D Cseco!r rc Y 7,0u33er data can not be deco!ressed. /&501 (&&O&D ?rong checsu X invalid data The checsu o3 loaded data blocs is ?rong. See S$P +otesD ,#'2:2 &'4O$D /&551 (&&O&D bu33er /xxxxx 01 to sall #'8='2 &'4O$D (rror during restart /ex!ort1 6igure &0: Corru'ted ,&3OAD Dum' 6i*es ;#<  $nalysisD Chec the ex!ort log 3iles. id soething tae !lace during the ex!ort Aas there a restart situation )se di33erent checsu tools to co!are original and co!ied 3iles@ or use di33erent algoriths@ i3 !ossible.

6igure &0: S!C2  System !nsta**ation C$e"1 6ai*ed Transaction SICE detects errors that generally indicate an incorrect S$P 0asis installation.

6igure &0: DB0#  ABAP DD!C  Dataase Consisten"y C$e"1 Soe reuired tables are created 3ro external !rogras@ such as S$P0$*0&CO++(CT. Soe database s!eci3ic objects are created in the last ste! o3 the syste co!y via &5C !rogras. id they really 3inish success3ully I3 tables or indexes are issing@ chec to see i3 there are S$P +otes related to these issues. The only ,--W chec ?hether a table in a !acage 3ile is in the database or not@ is to co!are the database dictionary ?ith the content o3 the V.ST& 3iles.

6igure &: ,&3OAD  3oad Termination due S'a"e S$ortage 0e generous ?ith database s!ace during the 3irst test igration /$dd@ 3or instance@ 2-W s!ace as a rule o3 thub1. $djustents 3or the !roduction igration can be deterined 3ro the results o3 the test igrations.

6igure &#: /ameta !m'ort Pro*em ;Uni"ode Conversion< Aarn the students they ust never ever use the Perl7based Pacage S!litter ?hen !er3oring a )nicode ConversionL ProbleD (xecuting H&'trans 7d returns H+o T$I& in this syste@ and the trans.log 3ile contains the ?arning HThe F($ entry in T$I& is issing. Ahen using the Perl7 or 6$<$7based Pacage S!litter /version ,1@ it can ha!!en that the $ctive +aetab tables ay be se!arated into di33erent V.ST& 3iles. uring the )nicode Conversion@ the $ctive +aetab tables ust be s!ecially treated by &'4O$. This ?ill be !ossible@ only i3 the tables ?ere i!orted in a certain order in the sae V.ST& 3ile. +orally@ S$PSIC.ST& contains the tables in the right ?ay. 0ut a3ter a s!lit@ S$PSIC.ST& does not necessarily contain all $ctive +aetab tables anyore. In +etAeaver -#S@ the 6$<$7based Pacage S!litter has been i!roved to ?rite the $0$P +aetab tables into a single !acage called HS$P+T$0.ST&@ aing sure that the right i!ort order is used. The revised 6$<$ !acage s!litter is also available 3or S$P Maret!lace. 5or ore in3oration see S$P +oteD 8''=#% HS!litting o3 ST& 3iles.

6igure &&: Data!ndex in rong Dataase Storage Unit

In any cases@ tables and indexes are oved to database storage units created by custoers@ ?ithout aintaining the a!!ro!riate $0$P ictionary tables. The result is that the 3iles H4Z0S[.TP4 and V.ST& ?ill contain the original S$P T$0$&T settings. The installation !rogras &'S(T)P and S$PI+ST can change the content o3 the 4Z0S[.TP4 3ile be3ore starting the i!ort. Chec the V.CM 3iles to 3ind out ?hich 4Z0S[.TP4 3ile have been used. Oracle databases running on the Hold tables!ace layout ?ill be autoatically installed ?ith the reduced tabels!ace set on the target syste.

6igure &): 53OAD -x'ort ,estart Be$avior  0ecause it does not ae sense to continue ?ith another table i3 a !revious table 3ailed to ex!ort@ 64O$ sto!s i3 an error occurs. In +etAeaver -# S&,@ the H(KPO&T.ST$ 3ile can be 3ound underD H*usr*sa!*ZS$PSI[*ZInstance[*j2ee*sltools. Chec the S$PI+ST log 3ile 3or the 3ile location in other versions. In +etAeaver B-# and +etAeaver :.--@ there is only a single (KPO&T.ST$ 3ile. Since +etAeaver :.-2 there can be ulti!le 64O$ job 3iles /!acages1. 6igure &(: 53OAD !m'ort ,estart Be$avior  (ven i3 a table 3ails to i!ort@ it aes sense to !roceed ?ith other tables /thus@ saving tie1. $ later restart ?ill only deal ?ith the erroneous objects. I3 the last unsuccess3ul action ?as load data@ the restart action ?ill be delete data. I3 the last unsuccess3ul action ?as create object /table or index1@ the restart action ?ill be dro! table. In +etAeaver B-# S&,@ the HIMPO&T.ST$ 3ile can be 3ound underD H*usr*sa!*ZS$PSI[*ZInstance[*j2ee*sltools. Chec the S$PI+ST log 3ile 3or the 3ile location in other versions. In +etAeaver B-# and +etAeaver :.-- there is only a single IMPO&T.ST$ 3ile. Since +etAeaver :.-2 there can be ulti!le 64O$ job 3iles /!acages1.

-xer"ise : Trou*es$ooting Business -xam'*e ou need to no? ?hich 3iles are read during a restart and ?hich !recautions are reuired de!ending on the cause o3 an error.

So*ution : Trou*es$ooting Tas1 : uring the i!ort o3 a table &'4O$ %.x sto!!ed@ because the database returned an error. $3ter the !roble ?as 3ixed@ &'4O$ ?as started again. ,. Ahich restart action ?ill be autoatically executed by &'4O$ a1 &'4O$ ?ill delete all table data 3ro the table be3ore loading it again. 2. Ahat is the exact database stateent that &'4O$ ?ill use 3or the restart a1 &'4O$ ?ill use the database coand@ ?hich is de3ined as truncate ta7ble stateent /section trcdatD 1 in the 4Z0S[.TP4 3ile. I3 nothing is de3ined@ (4(T( ?ill be used as de3ault. /ote: The 3irst guess ight be ?rongL Thin about ?hich &'4O$ 3iles are read.

Tas1 #: &'4O$ !rovides restart 3unctionality on ex!ort and i!ort ,. Ahy could it be dangerous to restart a terinated ex!ort@ caused by Hout o3 s!ace in the ex!ort 3ile syste a1 It is not certain ?hich &'4O$ 3ile ?as ?ritten last. I3 the du! 3ile con7tains less blocs than recorded in the V.TOC 3ile@ a restart ?ill start behind end7o373ile. The blocs bet?een end7o373ile and the ne? ?rite !osition contain rando data. 2. Ahy isnBt it a !roble to restart a terinated i!ort@ caused by Hout o3 s!ace in the database a1 In the case that &'4O$ ?ere to sto!@ because o3 a database i!ort error@ it can still close all 3iles !ro!erly /that eans the 3iles have a consistent state1. $3ter?ards &'4O$ is able to !er3or the right restart activities.

Tas1 &: 64O$ can restart a terinated ex!ort or i!ort@ ?hich 3ailed because o3 errors. ,. Ahich 3iles are read to 3ind the restart !osition in the du! 3ile

a1 64O$ reads the content o3 the (KPO&TZP$CE$G([Q.ST$ to identi3y already ex!orted tables. The du! 3ile is o!ened and blocs o3 already ex7!orted tables are si!!ed. 64O$ !roceeds ?ith ?riting 3ro the !osition 3ound. The next table to ex!ort is read 3ro the ex!ort job 3ile (KPO&TZP$CE$G([Q.KM4. 2. Ahich 3iles are read to restart an i!ort a1 64O$ reads the content o3 the IMPO&T ZP$CE$G([Q.ST$ 3ile 3or erroneous entries. $s a Hcontinue7on7 error strategy is used@ error 3lagged tables o3 the IMPO&TZP$CE$G([Q.ST$ 3ile ?ill be re!eated@ and re7 aining tables ?ill be read 3ro the job 3ile IMPO&TZP$CE$G([Q.KM4.

Unit 11 S'e"ia* Pro%e"ts This unit can be inserted bet?een any lessons a3ter co!leting the 3irst 3our units.

3esson: S'e"ia* Pro%e"ts 4esson urationD ," Minutes

3esson Overview Contents > S!ecial considerations 3or +NT*MS syste co!ies and )nicode Conversions > Technical descri!tion o3 the +NT*MS ethod

Business -xam'*e 6igure &+: /QDT  A Minimi@ed Downtime Servi"e ;MDS< The +ear Nero o?ntie ethod /+NT1 is a S$P Minii9ed o?ntie Service /MS1 using an increental igration a!!roach@ ?hich has been develo!ed to co!y very large databases. Co!ared to the standard syste co!y !rocedure@ it can reduce the technical syste co!y do?ntie signi3icantly to 3e? hours or even less. $t the oent /May 2-,21@ the +NT ethod can be a!!lied by s!ecially trained S$P consultants only /?hich ight change ?ith 3uture +NT versions or !rocedures1. It is suitable 3or heterogeneous syste co!ies and )nicode Conversions /or a cobination o3 both1. S$P delivers this ty!e o3 !roject usually 3or a 3ixed !rice. In 0A and SCM systes@ structure changes o3 tables and indexes are uite coon. Please discuss ?ith S$P@ ?hether a custoer s!eci3ic +NT !roject is !ossible. 5urtherore other technical aintenance events lie u!grades or u!dates can be !er3ored in course o3 this ty!e o3 +ear Nero o?ntie !rocedure.

6igure &7: /QDTMDS  6eatures The +NT Aorbench runs on a +etAeaver syste ?ith installed MIS $dd7On. It is used to con3igure and control the igration !rocess bet?een the source and the target syste. uring the table synchroni9ation@ the data strea runs through the +NT Aorbench. In case o3 an )nicode Conversion@ it is also !er3oring the data translation to )nicode. e!ending on the igration scenario@ the +NT Aorbench ?ill be a se!arate syste or is installed on the target syste. To log table changes@ insert@ u!date@ delete table triggers are created@ ?hich ?ill be 3ired as soon as the content o3 the table is changed. The !riary ey o3 the record ?ill be ?ritten into a log table.  $ 3ree9e trigger is used to 3orce a short du!@ i3 a transaction tries to change the content o3 a record. This ?ill set the res!ective table to a read only ode. 5ree9e triggers are created 3or tables ?here no change is ex!ected@ or it ?as agreed ?ith the custoer to allo? no change during the +NT igration !rocess. This ?ill i!ly soe syste usage restrictions@ but reduces the nuber o3 tables ?hich ust be synchroni9ed during the online or o33line delta re!lay@ ?hat hel!s to shorten the do?ntie.

6igure &: /QDTMDS S"enario: -x'ort ,emaining Ta*es The table insert@ u!date@ delete triggers ?ill usually be i!leented 3or the ,-- X 2-- largest tables@ to cover about =-W o3 the database data 3or the online delta re!lay. The re!lay trans3ers nearly all data o3 the triggered tables@ ?ith the increental trans3er echanis@ be3ore do?ntie. uring the do?ntie@ a 3inal synchroni9ation taes !lace@ trans3erring the records@ ?hich ?ere not already synchroni9ed or changed

during the ra! do?n. )sually@ this taes 3e? inutes only. (very table@ ?hich ?as synchroni9ed ?ith the delta re!lay@ does not need to be ex!orted by &'4O$. &'4O$ is used to ex!ort the clone syste@ ?hich is created a3ter the triggers ?ere established on the source syste.  $3ter co!leting the last delta re!lay@ the reaining tables are ex!orted*i!orted using &'4O$ during the do?ntie. The technical do?ntie de!ends ainly on the source syste database !er3orance and on the aount*si9e o3 the reaining tables. The achievable do?ntie is uite sall co!ared to a conventional database ex!ort. The table structure o3 the selected tables ust not change during the +NT !rocess. $s a conseuence@ all trans!orts into the source syste ust be exained 3or dangerous objects. This eans@ trans!orts ?hich are intending to odi3y triggered tables@ ust be !ost!oned to a !oint in tie@ ?hen the +NT !rocedure is co!leted. 6igure &: Pre'are /QDT or1en"$ and Sour"e System ;S< Setu!D > Install a se!arate +etAeaver syste ?ith the MIS $dd7On@ running the +NT Aorbench /based on S4O Migration Aorbench technology1. > Install the MIS $dd7On on the source syste )sing the +NT Aorbench@ the selected ,-- X 2-- large tables in the source syste can no? be !re!ared. Triggers and logging tables are created to record inserts@ u!dates@ and deletes in the source database. There ust be enough 3ree s!ace 3or the logging tables. 6igure �: Create C*one and Target System ;S<  $3ter the triggers ?ere established in the source syste@ the syste is cloned /co!ied via bacu!*restore or advanced storage co!y techniues1. $ll tables ?ill be ex!orted via &'4O$ and i!orted into the target syste. The S$P Syste o3 the clone ?ill never be started and is used 3or the ex!ort only. The target syste ?ill be isolated be3ore starting it the 3irst tie@ to avoid any data change. The database triggers and log tables are not active in the target syste. In cases ?here the +NT ethod is used 3or a hoogeneous syste co!y@ it ight be !ossible to use the clone syste directly as the target syste. 6igure &#: On*ine De*ta ,e'*ay  Syn"$roni@e Ta*e Data ;S< The online delta re!lay table synchroni9ation can be scheduled individually 3or each table@ thus balancing the batch load on the source syste. On heavily7used systes@ it ight be advisable to install a se!arate a!!lication server 3or running the synchroni9ation batch !rocesses. The logging tables contain the !riary eys o3 changed records@ additional in3oration about the ty!e o3 change /insert@ u!date@ delete1@ a tie sta!@ and the !rocess status. (very tie a ro? is inserted@ u!dated@ or  deleted@ a database trigger ?ill be 3ired to u!date the logging table. Changes to the sae record ?ill be o!tii9ed in a ?ay that the last recorded change is transitted only. The synchroni9ation jobs scan the logging tables /here T$0-,B and T$0-2B1 3or un!rocessed records. These records ?ill be transitted via the +NT Aorbench to the target syste. $ sa3e !rotocol aes sure that only those records are ared as co!leted /!rocessed1@ ?hich have been success3ully u!dated in the target database. In case o3 an )nicode Conversion@ the translation to )nicode is done in the +NT Aorbench. 6igure &##: System ,am' Down ;S<  $3ter the online re!lay is 3inished@ the source syste ust be ra!ed do?n 3or the 3inal o33line delta re!lay. That eans@ there ust be no syste activity anyoreD users are loced out@ no jobs are running@ inter3aces are sto!!ed@ etc. to avoid 3urther data changes.

6igure &#&: O99*ine De*ta ,e'*ay and Target C*eanu' ;S<  $3ter the source syste ?as ra!ed do?n@ the o33line /3inal1 delta re!lay taes !lace@ ?hich trans3ers the data 3or those tables@ ?here the online re!lay ?as not ,--W co!leted@ or data ?as changed during ra! do?n.  $3ter?ards@ the source and target systes ?ill be sto!!ed. The reaining tables ?ill be deleted 3or the target syste to !re!are the &'4O$ i!ort.

6igure &#): -x'ort!m'ort ,emaining Ta*es ;S< The reaining tables ?ill be ex!orted*i!orted by &'4O$. The aount o3 data in the reaining tables ust not be larger than that o3 ?hich can be ex!orted and i!orted in the custoer7de3ined axiu technical do?ntie /i.e. 3e? hours1.  $3ter the i!orted is co!leted@ the technical igration is 3inished. The resulting target syste can be !re!ared 3or !roductive o!eration no?. 6igure &#(: /QDTMDS S"enario: O99*ine De*ta ,e'*ay  $ll tables o3 the syste ust be classi3ied to a!!ly insert@ u!date@ delete triggers or a 3ree9e trigger to the. 5or tables ?ith insert@ u!date@ delete triggers@ it ust be s!eci3ied ?hether they should be synchroni9ed during the online delta re!lay or the o33line delta re!lay. The table insert@ u!date@ delete triggers ?ill be usually i!leented 3or thousands o3 tables. The rest ?ill get 3ree9e triggers. &'4O$ is used to ex!ort the clone syste@ ?hich is created a3ter the triggers ?ere established in the source syste. Tables ?ith 3ree9e triggers have already their 3inal state a3ter the i!ort.  $3ter co!leting the online delta re!lay@ the reaining unsynchroni9ed table data ?ill be trans3erred during the do?ntie o33line delta re!lay. The technical do?ntie de!ends ainly on the source syste database !er3orance and on the aount o3 delta data ?hich ust be synchroni9ed o33line. The achievable do?ntie is very sall co!ared to a conventional database ex!ort@ and even saller than in the +NT scenario@ ?here the reaining tables are ex!orted by &'4O$. +o table structures ust be changed during the +NT !rocess. $s a conseuence@ there ust be strict trans!ort rules in !lace@ only allo?ing eergency trans!orts into the source syste. 0ecause alost all tables have triggers /and any o3 the have 3ree9e triggers1@ trans!orts are di33icult to anage. Most trans!orts ust be !ost!oned to a !oint in tie@ ?hen the +NT !rocedure is co!leted. 6igure &#+: Pre'are /QDT or1en"$ and Sour"e System ;S#< Setu!D > Install a se!arate +etAeaver syste ?ith the MIS $dd7On@ running the +NT Aorbench /based on S4O Migration Aorbench technology1. > Install the MIS $dd7On on the source syste. On the +NT Aorbench@ the tables o3 the source syste can no? be classi3ied and the triggers and logging tables ?ill be created. There ust be enough 3ree s!ace 3or the logging tables. 6igure : Create C*one and Target System ;S#<  $3ter the triggers ?ere established in the source syste@ the syste is cloned /co!ied via bacu!*restore or advanced storage co!y techniues1. $ll tables ?ill be ex!orted via &'4O$ and i!orted into the target syste. The S$P Syste o3 the clone ?ill never be started and is used 3or the ex!ort only. The target syste ?ill be isolated be3ore starting it the 3irst tie@ to avoid any data change. The database triggers and log tables are not active in the target syste. In cases ?here the +NT ethod is used 3or a hoogeneous syste co!y@ it ight be !ossible to use the clone syste directly as the target syste. 6igure &#: On*ine De*ta ,e'*ay  Syn"$roni@e Ta*e Data ;S#< The online delta re!lay table synchroni9ation can be scheduled individually 3or each table@ thus balancing the batch load on the source syste. On heavily7used systes@ it ight be advisable to install a se!arate a!!lication server 3or running the synchroni9ation batch !rocesses. The logging tables contain the !riary eys o3 changed records@ additional in3oration about the ty!e o3 change@ and the synchroni9ation status /insert@ u!date@ delete@ !rocessed1. (very tie a ro? is inserted@ u!dated@ or deleted@ a database trigger ?ill be 3ired to u!date the logging table. Changes to the sae record ?ill be o!tii9ed in a ?ay that the last recorded change is transitted only. The synchroni9ation jobs scan the logging tables /here T$0-,B and T$0-2B1 3or un!rocessed records. These records ?ill be transitted via the +NT Aorbench to the target syste. $ sa3e !rotocol aes sure that only

those records are ared as co!leted /!rocessed1@ ?hich have been success3ully u!dated in the target database. In case o3 a )nicode Conversion@ the translation to )nicode is done in the +NT Aorbench. 6igure &#: System ,am' Down ;S#<  $3ter the online re!lay is 3inished@ the source syste ust be ra!ed do?n 3or the o33line delta re!lay. That eans@ there ust be no syste activity anyoreD users are loced out@ no jobs are running@ inter3aces are sto!!ed@ etc. to avoid 3urther data changes.

6igure &&0: O99*ine De*ta ,e'*ay  Syn"$roni@e ,emaining ;S#<  $3ter the source syste is ra!ed do?n@ the o33line /3inal1 delta re!lay taes !lace. It trans3ers the changes o3 those tables@ ?here the online delta re!lay ?as not ,--W 3inished or data ?as changed during ra! do?n@ and 3or tables ?hich could not be trans3erred online /i.e. )S&-21. The o33line delta re!lay is ty!ically co!leted in less than one hour and is 3inishing the technical igration. The resulting target syste can be !re!ared 3or !roductive o!eration no?. Scenario 2 is synchroni9ing alost all tables using the delta re!lay@ exce!t the ones ?ith a 3ree9e trigger. 0ecause o3 the 3ree9e triggers@ the aount o3 tables needing a trans3er@ is saller than in scenario ,@ ?here the largest tables are synchroni9ed only and the rest ust be ex!orted*i!orted /trans3erred1 using &'4O$.

6igure &&: ,&3OAD Uni"ode Conversions )nicode S$P Systes reuire S$P Aeb $S %.2- and above. The )nicode Conversion is only a!!licable i3 a iniu Su!!ort Pacage 4evel is installed. Chec the )nicode Conversion S$P +otes 3or ore in3oration. The HOS*0 Migration Chec a!!lies to )nicode Conversions changing their target o!erating syste or database syste. &'4O$ converts the data to )nicode ?hile the ex!ort is running. $s it is not su33icient 3or &'4O$ to read the ra? data@ additional 3eatures are i!leented regarding the data context. 0ecause the context is only available in the source syste@ a )nicode conversion at i!ort tie is not su!!orted 3or custoer systes. $ reverse conversion 3ro )nicode to non7)nicode is not !ossible. uring the )nicode ex!ort@ &'4O$ ?rites .KM4 3iles ?hich are used 3or 3inal data adjustents in the target syste /transaction S)MG1. In MMP systes@ not all tables !rovide a language identi3ier 3or their data. 5or this data@ a vocabulary ust be created to allo? an autoated conversion. The creation and aintenance o3 this vocabulary is a tie consuing tas. The involveent o3 ex!erienced consultants ?ill shorten the ?hole !rocess signi3icantly. &elated S$P +otesD -"#8-,% Conversion to )nicode ,',=",: )nicode Collection +ote

6igure &&#: Uni"ode Conversion C$a**enges