41 PAL sBWoH DB Migration Exercise

ONE-STEP UPGRADE/MI GRATI ON WI TH
DATABASE MI GRATI ON OPTI ON OF SUM

Exercises / Solutions
One-Step Upgrade/Migration with DMO of SUM
2
TABLE OF CONTENTS
Exercise 1: Checks ......................................................................................................................................................4
Solution 1 - Checks ......................................................................................................................................................5
Exercise 2: Preparation .............................................................................................................................................. 13
Solution 2 - Preparation ............................................................................................................................................. 14
Exercise 3: Start DMO run and execute the extraction phase ..................................................................................... 18
Solution 3 Start DMO run and execute the extraction phase .................................................................................... 19
Exercise 4 Roadmap Step Configuration .................................................................................................................... 30
Solution 4 Roadmap Step Configuration .................................................................................................................. 31
Exercise 5 Continue DMO procedure until Lock Now ................................................................................................. 40
Solution 5 Continue DMO procedure until Lock Now ............................................................................................... 41
Exercise 6 Reset DMO procedure .............................................................................................................................. 44
Solution 6 Reset DMO procedure ............................................................................................................................ 45
3
BEFORE YOU START
You should have an additional sheet of paper at hand that lists the system parameters and passwords.
Please note that for this hands-on workshop a special setup was chosen to enable the exercises. This includes
reduced resources for the SAP system to be migrated, so the setup and the duration for the procedure cannot be taken
for an estimate of a real migration. It includes a customized SUM archive as well, which may have been adapted to
allow a fast extraction.
The exercises can only cover the essential parts of the complete DMO-based upgrade and migration procedure, since
the complete DMO run would take several days.
Exercise Esti mated Duration
1. Exercise 1 Checks 15 minutes
2. Exercise 2 Preparation 20 minutes
3. Exercise 3 Start DMO run and execute the extracti on phase 90 minutes
4. Exercise 4 Roadmap Step Configuration 90 minutes
5. OPTIONAL-Exerci se 5 Conti nue DMO procedure until Lock Now 60 minutes
6. OPTIONAL-Exerci se 6 Reset DMO procedure 30 minutes
4 Exercise 1: Checks
EXERCI SE 1: CHECKS
CHECK SYSTEM LANDSCAPE AND REQUI RED FI LES
Estimated time: 15 mi nutes
Objective
In the following exercise you will check the status of the ABAP system and the required files and folders.
A colleague has already prepared the DMO procedure by creating a maintenance transaction in the Maintenance
Optimizer (MOpz) of the associated SAP Solution Manager system. The colleague has downloaded the files of the
download basket (software and kernel archives) and the stack.xml, both as a result of the maintenance transaction. In
addition, the SPAM update for the source release, a license file, and the latest SUM are made available.
You have to check the location of the files, and the status of the source system EH6.
Exercise Description
The following description only serves as a short overview to what objectives will be executed during the exercise.
Logon to the host
of your ABAP system EH6 using Putty and SAP GUI
Check the required files and fol ders:
download folder, stack.xml, license file, SUM archive, SPAM/SAINT update for source release, SAP HANA client
installation files
Check system EH6:
system status, SAP software release, database type, database software release, number of work processes
Note
Most of these actions are optional, but serve to understand the special requirements for DMO, especially the additional
files required, and additional steps compared to a standard update/upgrade using the SUM.
Checking the source system release relates to the minimum release required for DMO of SUM. SAP Note 1875197
lists the requirements, e.g. for the source release version of the SAP ERP system.
Solution 1 - Checks 5
SOLUTI ON 1 - CHECKS
Explanation Screenshot
1. Logon procedure to your
System Image for the
workshop exercises
Start the Putty (putty.exe) on
your client.
6 Solution 1 - Checks
2. Prepare your SAP GUI
To logon to the SAP System
you need to prepare your
SAP GUI. Start SAP Logon
and click the paper sheet
icon for a new system.
Select User Specified
System and press Next.
Enter following Parameter:
Description: ERP System
Application Server: <IP>
Instance Number: 00
System ID: EH6
Click Finish
3. Logon to system EH6
Use SAP Logon to log on to
client 120 of system EH6
with user WSuser wi th
password Welcome1
Use menu System -> Status
to open the system
information popup.
It shows the database
information MaxDB
7.9.07.010.
You may use the button (1)
below the Component
version to display the
Software Component
Version list.
The button (2) next to the
button Navigate shows the
details about the kernel (not
shown here).
4. Check the number of work
processes
5. Use Transaction SM50 to
check the number of Dialog/
Batch Processes configured
for the system
6. After Logon you are
connected with user root.
Switch user to eh6adm.
su eh6adm
1
2
7.
To l og off from the Virtual
Image after the session
type exi t and press enter
8. Check fil es and folder
Use the command to change
to the directory where the
files are located:
Check the every folder
download (folder):
containing the software and
kernel files as well as the
patch 50 for SPAM/SAINT
for the SAP NetWeaver
release 7.02
IMDB_CLIENT100_70_0-
10009663.SAR:
installation files for the SAP
HANA client
SAPHOSTAGENT188_188-
20005731.SAR
Installation files for the SAP
Host Agent 7.20 Patch 188
stack.xml
the definition file for the SUM
run
SUM.SAR
software update manager
EH6_multiple_HANA.txt
cd / usr / sap/ EH6/ Fi l es_f or _exer ci ses
cd <f ol der name>
l s l
cd . .
License file for the target
system on SAP HANA
Migration_Key.txt
Text file with the valid
migration key
Note: the folder scripts
contains additional files and
folders that may be required
during the exercise due to
the specific workshop setup.
9. Check download folder for
kernel fil es
Check the download folder
for kernel archives. You will
find (at least) three kernel
archives for 7.41 64-bit
Unicode Linux 64 bit:
SAPEXE_42-10012494 (DB-
independent)
SAPEXEDB_42-10012492
(MaxDB)
SAPEXEDB_42-10012510
(HDB)
Note:
1) While using the MOpz, the
kernel files for the SAP
HANA DB have to be
selected manually for the
migration.
2) Newer versions of the
kernel files are already part
of the download folder.
cd downl oad
l s l SAPEXE*. SAR
10.Check download folder for
new versi on of SPAM for
the source rel ease
Note:
If you copy the archive to the
download directory, SUM will
deploy the new version
automatically after your
confirmation.
cd downl oad
l s l KD7*. SAR
11.Check download folder for
the file UPGANA.XML
Providing an UPGANA.XML
file from one of the previous
cd downl oad
l s l UPGANA. XML
runs on a similar system,
makes the calculation of the
estimated end time more
precise.
12.Check system status
Dismiss the eh6adm role by
using the EXIT command.
Check that the system EH6
is running.
sapcont r ol - nr 00 - f unct i on Get Pr ocessLi st
You have compl eted the
exerci se!
You are now abl e to:
Check the prerequi si tes
Use the files and folders to prepare the DMO procedure
Exercise 2: Preparation 13
EXERCI SE 2: PREPARATI ON
Objective
After having checked the required files, it is now time to extract the archives and move the files to the appropriate
places.
Extract the SUM archive to the SAP systems instance folder (/usr/sap/EH6)
Move the download folder to the system SAP systems instance folder
Move the stack.xml file into the download folder
Extract the SAP HANA Client installation archive
Upgrade the SAP Host Agent
Create the necessary configuration file for SAP Host Agent, enabling the SUM start
Adapt a SUM configuration file to use different schema names in the SAP HANA database
14 Solution 2 - Preparation
SOLUTI ON 2 - PREPARATI ON
1. Extract SUM archive:
Logon to the NetWeaver
host and switch to user
eh6adm
Extract the archive
Check the new sub-folder
Note
1) The SUM folder can
reside on a different folder
than the instance folder,
but this is the usual
(default) folder.
su eh6adm
SAPCAR - R / usr / sap/ EH6 - xvf / usr / sap/ EH6/ Fi l es_f or _exer ci ses/ SUM. SAR
l s - l / usr / sap/ EH6/ SUM
2. Download folder
Move the download folder
into the instance folder
(/usr/sap/EH6).
Move the stack.xml file
into the download folder.
Note
1) For the DMO procedure,
it is required that the
stack.xml is located in the
download folder, as the
SUM only asks for the
stack.xml file and
presumes that it is located
in the download folder.
mv / usr / sap/ EH6/ Fi l es_f or _exer ci ses/ downl oad / usr / sap/ EH6/
l s - l / usr / sap/ EH6
mv / usr / sap/ EH6/ Fi l es_f or _exer ci ses/ st ack. xml / usr / sap/ EH6/ downl oad/
l s - l / usr / sap/ EH6/ downl oad/ st ack. xml
Solution 2 - Preparation 15
The download folder may
have a different name, but
it is common (and useful,
as we will see soon) to
name it download
3. Extract SAP HANA Cli ent
Installation Fi les
Change to the Instance
folder EH6
Extract the client archive
Check the new sub-folder
/usr/sap/EH6/SAP_HANA_
CLIENT
Note:
The SUM will ask for these
installation files to install
the SAP HANA Client. The
SAP HANA Client is
required for the
connectivity from the SUM
to the SAP HANA
database.
cd / usr / sap/ EH6
SAPCAR - xvf Fi l es_f or _exer ci ses/ I MDB_CLI ENT100_70_0- 10009663. SAR
l s l
4. Extract SAP Host Agent

Create a new folder
hostagent_upgrade in the
folder Files_for_exercises.
Change to the new folder
and extract the SAP Host
Agent SAP Archive
Check that the file
saphostexec.exe was
extracted.
mkdi r / usr / sap/ EH6/ Fi l es_f or _exer ci ses/ host agent _upgr ade
cd / usr / sap/ EH6/ Fi l es_f or _exer ci ses/ host agent _upgr ade
SAPCAR - xvf . . / SAPHOSTAGENT188_188- 20005731. SAR

16 Solution 2 - Preparation
5. Update SAP Host Agent
host as user root or exit
from the eh6adm user.
Change to the directory
with the extracted SAP
Host Agent files.
Update the SAP Host
Agent by executing the
command.
exi t
cd / usr / sap/ EH6/ Fi l es_f or _exer ci ses/ host agent _upgr ade
. / saphost exec - upgr ade
6. Check the version of the

SAP Host Agent:
Run the command as user
root.
It will display the patch
number 188 which is
sufficient for the
communication with SUM.
/ usr / sap/ host ct r l / exe/ saphost exec - ver si on
Solution 2 - Preparation 17
7. SAP Host Agent config
Verify as user root that the
file sumstart.conf in folder
/usr/sap/hostctrl/exe/opera
tion.d not yet exists.
Change to the SUM/abap
folder and run the script to
configure SAP Host Agent
for SUM.
Check for the success
message.
Note:
In a customer landscape, it
is highly recommended to
setup SSL for the SAP
Host Agent (not shown
here).
f i nd / usr / sap/ host ct r l / exe/ oper at i on. d name sumst ar t . conf
cd / usr / sap/ EH6/ SUM/ abap/
. / SUMSTART conf i ghost agent
You have compl eted the
exerci se!
Prepare the fil es and folders for the DMO run
Configure the SAP Host Agent to be able to start the SUM for DMO
18 Exercise 3: Start DMO run and execute the extraction phase
EXERCI SE 3: START DMO RUN AND EXECUTE THE EXTRACTI ON PHASE
Objective
In the following exercise you will start the DMO procedure, configure the phases of the first step Extraction, and get
familiar with the new UI that the SUM offers exclusively for the DMO procedure.
Note
The new UI is based on SAPs new user interface technology, called SAPUI5. It is a J avaScript framework and uses
jQuery. Advantages are an improved UI with improved usability, and that no client installation is required.
Most of the required input and options are well known from the standard SUM update/upgrade.
Open your browser and start the DMO procedure
Specify the location of the stack.xml file
Examine the UI elements
Set a breakpoint
View logs in the browser window
Provide the required passwords for DDIC, SAPServiceEH6, and eh6adm
Trigger the SPAM/SAINT update to version 50 (for 7.02)
Choose the migration to SAP HANA db, and specify the migration key
Implement missing SAP Notes
Solution 3 Start DMO run and execute the extraction phase 19
SOLUTI ON 3 START DMO RUN AND EXECUTE THE EXTRACTI ON PHASE
1. Start the DMO UI i n the
browser
Open the Internet Explorer.
Enter the URL pointing to
the SAP Host Agent with
the DMO-specific
application path:
Log on with credentials of
the user eh6adm.
<MASTERPASSWORD>
Note
The URL contains the
system-ID, in our case EH6.
(lmsl is the abbreviation for
Lifecycle Management
Software Logistics)
You would open the
browser on your PC, not on
the host this is due to the
workshop system
landscape.
ht t p: / / <Ser ver I P>: 1128/ l msl / upgr ade/ EH6/ doc/ gui
20 Solution 3 Start DMO run and execute the extraction phase
2. Stack Configuration Fil e
The DMO procedure
requires the stack.xml file
as a kind of recipe for the
maintenance operation.
As discussed before, the
SUM assumes for the DMO
procedure that the required
patches and kernel files are
located in the same folder
like the stack.xml file. There
is no possibility to specify a
different path.
Use the link Default Pattern
to set the default path for
the stack file, and add the
name of the stack file, in our
case stack.xml. You see
that it is beneficial, but not
necessary, to name the
folder download.
Choose Next to continue.
3. Exami ne UI el ements
While the SUM is scanning
the download directory, lets
take a minute to have a first
look onto the UI elements (a
detailed description will
follow later):
1) Tool tabs
2) Roadmap steps
3) Progress bar
4) Work in progress icon
5) Menu
6) Phaselist toggle
While the DMO procedure
is working without requiring
input, the UI shows the
Work in Progress icon. As
soon as input is required,
the UI shows the
appropriate input elements.
4. Display phase list
The SUM procedure
comprises 5 steps, each
with their own phases
(think of modules).
Click on the area Current
Phaselist at the right-hand
border to open the phase
list for the current roadmap
step. Phases already
executed are marked; the
current phase is shown
with a C (for current). Click
again on the area to close
the phase list.
5. Progress bar
It shows estimation on the
completion percentage,
and the current phase.
Hovering the mouse over
the progress bar shows the
Runtime Estimation.
Note
The estimation is based on
the number of phases.
Placing the UPGANA.xml
file from a previous DMO
run into the download
folder as we did in one of
the preparation steps will
make the prediction more
precise.
6. Check SAPup processes
host via Putty and enter the
command to list the SAPup
processes.
One SAPup process acts as
a handler for requests
coming from the SAP Host
Agent (the process with
option gt=httpchannel). This
process passes requests to
the second SAPup process,
which communicates with
other tools (e.g. tp, R3load).
ps - ef | gr ep SAPup
7. Required System
Passwords
Enter the password of the
DDIC users of the source
system EH6 Client 000.
<MASTERPASSWORD>
8. SCANDIR_EPS0
During phase
SCANDIR_EPS0, open
folder /trans/EPS/in to see
that the SUM is extracting
the files from the download
folder into this directory,
which in our case was
initially empty.
In the list of processes, you
may see the SAPCAR
process that was triggered
by the SUM.
This wi ll take some time
cd / usr / sap/ t r ans/ EPS/ i n
ps - ef | gr ep SAPCAR
l s - l | wc - l
9. SPAM Version Check
SUM requires a specific
minimum level of SPAM to
use its functionalities. The
existing SPAM version 50
is too low.
As you have moved the
SPAM/SAINT update 54 for
the source release 7.31 to
the download folder, the
SUM has extracted the
archive into trans\EPS\in
and proposes to import that
update.
Choose Import SPAM
version 54 and choose
Next to continue.
10. Exami ne menu options
In the upper right corner of
the browser window, the UI
displays three elements.
11. Menu options (1)
The first element shows the
role admin. There is no
menu behind this.
Note
The UI does currently not
offer other roles (e.g.
observer) like for a classical
update / upgrade with the
SDT GUI of SUM.
The Help menu offers to
change the color schema,
an About entry, and the
optionGet Support File.
The other options are
currently not used.
Note
In case of UI issues, it may
be required to provide the
Support File to SAP
support.
The third element is the
Logout icon. Clicking the
icon will display a dialog
explaining that you have to
close the browser to log off.
14. Menu Util iti es
Switch to the menu entry
Utilities to find the sub
menus Logs and
Breakpoints.
Switch to Breakpoints to
see how easy it is to set or
remove a breakpoint for a
phase.
Note
All phases are listed here,
in contrast to Current
Phaselist, where only the
phases of the current step
are listed.
15. Set Breakpoint
Set a breakpoint for phase
GENBUFFER_TOOLIMP.
Use the filter for column
Phase Name, enter a part
of the phase name (like
_TOOLIMP), and press
enter.
16. Set Breakpoint (2)
Mark the checkbox for the
phase.
Note
You do not have to save the
breakpoint settings.
17. Exami ne logs
Navigate back to the Logs
menu.
You may sort the logs per
name by clicking on the
column header and
choosing Sort Descending.
18. Search for Logs
Search for the log
SAPupConsole.log by
clicking on the column Log
File, entering SAPup and
pressing enter.
19. Open Logs
You can open the log by
clicking on the name link.
Note
1) SAPupConsole.log
includes all inputs done
during the SUM procedure.
2) SAPUPPHASES lists all
phases of the procedure.
20. Database Migration
Option
Here you have to choose to
migrate to SAP HANA,
otherwise only the system
update will be executed. As
with a classical migration, a
migration key is required.
For our system, the key is
1G5fdEM50DwSq3egt6h] pGhK
Note
This dialog is not shown
when the SUM is started
normally (via SDT GUI).
21. Breakpoint Encountered
As you have set a
breakpoint for phase
GENBUFFER_TOOLIMP,
the DMO procedure stops
here.
Examine the options.
Select optionContinue in
single step mode (stop
before each phase) and
choose Next to continue.
22. Breakpoint at next step
Choose option End single
step mode and continue to
next breakpoint.
23. Missi ng SAP Notes for
Tool s
The SUM checks for
required SAP Notes, and
lists them.
You will have to download
and implement these notes
before the procedure can
continue.
Note
Not all SAP Notes may be
applicable, but even non-
applicable notes must be
downloaded so that the
SUM can check whether
they are existing. For this
exercise, we have already
implemented some SAP
Notes.
24. Apply SAP Notes
Logon to the ABAP server
EH6, client 120, with your
user WSuser.
Start transaction SNOTE.
select GotoUpload SAP
note and select the
1680583.txt
25. Implement SAP Notes
(1) Select the first SAP
Notes in the list with a
simple mouse click.
(2) Choose the first button
Implement SAP Note.
(3) Read the SAP note text
(optional) and confirm with
Yes.
Confirm the information
popup about repairs in
foreign namespaces (not
shown here).
26. A popup Prompt for local
Workbench request is
shown.
Use the third icon Create
Request for the creation of
a new transport request.
27. Name the request SAP
Notes for DMO.
Confirm the creation with
Save, and confirm with
Continue that this request
shall be taken for the
changes of the SAP Note
(not shown here, similar to
Prompt for local Workbench
request).
Confirm all following popups
with Enter.
Implement the other SAP
Notes the same way,
reusing the transport
request.
1
2
3
28. Conti nue in the DMO GUI
After all required SAP Notes
have been implemented,
return to the browser
window with the DMO GUI
and choose Next to
continue.
29. Conti nue roadmap
Confi gurati on
Now that all the phases of
step Extraction are done,
the UI shows the dialog to
proceed to the next step, in
this case the step
Configuration.
Note
As you see, the button
Reset is offered in addition
to the two standard buttons
Back and Next.
This is due to the switch to
the next step. We will
discuss the possibilities of
Back and Reset later.
30. Information and Errors
You may hold the cursor
over the star icon left hand
to see status information
about infos and errors.
You may also click on the
icon to see detailed
information text.
31. Details on Infos
The Infos are listed in
separate segments that you
may open by clicking on the
>icon.
Click the icon again to close
the detail view.
Choose Next to continue
You have completed the
exercise!
Logon to the DMO procedure
Use the new DMO UI
Configure the first DMO step Extraction
30 Exercise 4 Roadmap Step Configuration
EXERCI SE 4 ROADMAP STEP CONFI GURATI ON
Objective
In the following exercise, you will configure the DMO procedure concerning use of resources and SAP HANA
database.
For example:
Set the preconfiguration mode
Adapt the resource parameters
Specify the parameters for the SAP HANA database
Change the resource parameters during the DMO procedure
Adapt the parameters of the source database to allow the creation of the shadow repository
Solution 4 Roadmap Step Configuration 31
SOLUTI ON 4 ROADMAP STEP CONFI GURATI ON
1) Tool Configuration
The CONFIGURATION
step starts with the two
options of the
preconfiguration mode, like
in a standard update /
upgrade.
Keep the Standard mode.
2) Parameters for
procedure
Scroll up to the upper part
of this long UI form.
The differences between
Standard andAdvanced
preconfiguration mode are
the default values for the
resources used during the
update, shown in this
dialog.
You have to consider the
available work processes
as checked in the first
exercise.
Keep the preconfigured
values for our exercise.
Scroll down to check the
next parameters.
3) Parameters (contd)
Keep the parameters
shown here at their default
values.
Note
There are no DMO specific
parameters in this
(complete) dialog
32 Solution 4 Roadmap Step Configuration
Parameters for procedure.
The only difference to a
standard SUM update /
upgrade is that it is not
possible to choose the
nZDM option (CRR; or
record & replay option of
SUM).
Scroll down.
4) Parameters (contd)
Now you are back on the
bottom part of the UI.
The general decision on
using SGEN for the ABAP
load generation depends
on project priorities, like
downtime optimization or
less resource consumption.
For this exercise, we will
anyhow not reach the
phase where SGEN is
relevant, so you keep the
Execution mode on default.
5) Hana Database Cli ent
Installer
Specify the location of the
SAP HANA Client
installation files which you
have provided (extracted)
in exercise 2.
/usr/sap/EH6/SAP_HANA_
CLIENT
SUM will install the client
and use it for the
connection to the SAP
HANA database.
6) Check the new directory
hdbclient with the HANA
client under /usr/sap/EH6
cd / usr / sap/ EH6
l s - l
7) Database Mi gration
Initi alization
Specify the information for
the SAP HANA database,
as SUM will connect to the
database and prepare the
migration, e.g. create the
user and schema (see
screenshot).
Target Hostname: <IP
HANA Server>
Target SID: HDB
Target Inst. Number: 00
You have to specify the
location of the license file
for the target SAP system
on SAP HANA.
8) Required Migration
Specific Passwords
Specify the password of
the existing user SYSTEM
on the SAP HANA
database.
<MASTERPASSWORD>
9) Required Migration
Specific Passwords 1
Enter a new password for
the DBACOCKPIT schema
user.
SUM will create this user
on the HANA DB.
Welcome1
10) Required Mi gration
Specifi c Passwords 2
Enter a new password for
the SAPEH6 schema user.
SUM will create this user on
the HANA DB.
Welcome1
11) Add-On Selection
When you press Next, the
validation will start. You will get
the information regarding the
BP-ERP component. Click Next.
You will get asked for a Vendor
Key for this specific Add-On
which can normally be found
here:
1644833 Vendor keys for SAP
Best Practice add-ons
For this exercise the key is:
799583
Click Next.
12) Add-On Keyword for BI
Content
Enter the IS keyword:
3821837
Click Next.
13) Support Package
Summary
Click next.

14) Change parameters
It is possible to change the
processing parameters
during SUM runtime.
To do so, open the Browser
and enter the following
URL:
To save your modifications
press Next.
ht t p: / / <NWSer ver >: 1128/ l msl / upgr ade/ EH6/ set / pr ocpar
15) Include Change Request
As we will not include any
change requests, choose
Next to continue.
16) Modifi cation Adjustment
As we will not include any
SPDD or SPAU transport
requests, choose Next to
continue.
17) Confi gurati on Error
The roadmap step
Configuration fails and a red
flag icon on the left side of
the DMO GUI appears.
To see whats the problem
click on the red flag icon.
DMO report that a database
parameter needs to be
adjusted.
Putty: eh6adm
Then NEXT
dbmcl i - d EH6 - U w
par am_di r ect put MAXSQLLOCKS 800000
db_st op
db_onl i ne
18) Complete the roadmap
step Configuration
with the roadmap step
Checks.
exercise!
You are now able to:
Configure the SUM parameters
Configure the parameters for the access to the SAP HANA database
Adapt the source database parameters to meet the SUM requirements
40 Exercise 5 Continue DMO procedure until Lock Now
EXERCI SE 5 CONTI NUE DMO PROCEDURE UNTI L LOCK NOW
Objective
In the following exercise you will continue the DMO procedure with the roadmap step CHECKS and a part of the
roadmap step PREPROCESSING.
Note
We will work until the lock of the development environment.
BW Task
Release open transport requests in EH6
Solution 5 Continue DMO procedure until Lock Now 41
SOLUTI ON 5 CONTI NUE DMO PROCEDURE UNTI L LOCK NOW
1. BWspecific task
This dialog only appears for
system where BW
functionality is used. To
reduce the runtime of this
process we increase the
number of days to 99999.
Note.
Normally this process is to
reduce the amount of
obsolete data which needs
to be migrated to the HANA
database.
2. Conti nue roadmap step
Checks
After a while, the DMO GUI
asks you to perform manual
application-specific pre-
upgrade steps documented
in the ASU Toolbox.
Note
These steps are not
relevant for the exercise so
that you can skip this
activity.
3. Conti nue roadmap
Preprocessing
with the roadmap step
PREPROCESSING.
42 Solution 5 Continue DMO procedure until Lock Now
4. Open Repairs Found
The SUM checks for open
repairs, like in a standard
update/upgrade scenario.
Logon to client 120 of
ABAP system EH6 with the
user wsuser / Welcome1
and start the Transport
Organizer (transaction
SE09).
(You may use SE80 as
well, not shown here).
5. Release transport
requests
Choose Display in the
transport organizer to get
the transport request listed.
Select the transport task
first and use the context
menu entry Release
Directly to release the
task.
Repeat the procedure for
the transport request itself
(not shown here).
Refresh the display to
check that no requests are
listed.
Repeat both steps for the
second transport.
6. Conti nue DMO
After all open transports
are release choose Next to
continue.
Solution 5 Continue DMO procedure until Lock Now 43
7. Lock Development
Environment
The lock of the
development environment
would be the next step.
After this dialog, the SUM
would create the shadow
repository on the source
database, which takes
more time than we have.
DO NOT proceed here; do
not choose any of the
buttons.
Continue with the next
exercise instead.
11) You have completed the
exercise!
Create addi tional data files in the source database
Rel ease open transport requests
44 Exercise 6 Reset DMO procedure
EXERCI SE 6 RESET DMO PROCEDURE
Objective
In the following exercise you will learn how easy it is to reset the DMO procedure.
Reset the DMO procedure
Check the SAPup processes
Restart the DMO procedure
Note
It is possible to start the reset throughout the whole DMO procedure, even after the update and migration is done. This
is based on the fact that the source database is not modified; only a shadow repository is created which is deleted by
the SUM anyhow, and which does not affect the data on the source release.
Solution 6 Reset DMO procedure 45
SOLUTI ON 6 RESET DMO PROCEDURE
1) On the UI, choose the
Reset button.
2) A popup warns that the
whole procedure is reset.
Confirm the popup with
OK.
3) After a short time, the
update is reset. Next step
is to cleanup the tool
directory (SUM folder) so
that the procedure can be
started again.
Choose Cleanup to
proceed.
46 Solution 6 Reset DMO procedure
4) After the tool directory is
cleaned up, the UI shows
the message Tool start
required.
To understand the
situation, logon to the
NetWeaver host and
search for SAPup
processes: only one
SAPup process is running.
This process represents
the dispatcher SAPup
which generates the
message Tool start
required. You can easily
start the tool (the second
SAPup) with Next.
ps - ef | gr ep SAPup
5) Now the initial UI for the
DMO procedure is shown,
in which you enter the path
to the stack.xml
Note
It is possible to reset the
DMO procedure with the
same steps until the end of
the procedure. The SUM
will reset the system to the
initial state and source
release, without the need
for a database restore.
exercise!
Reset the DMO procedure
2014 by SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications
may vary.
These materials are provided by SAP SE and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in
the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries.
Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.

41 PAL sBWoH DB Migration Exercise

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

41 PAL sBWoH DB Migration Exercise

Hochgeladen von

Copyright:

Verfügbare Formate

ONE-STEP UPGRADE/MI GRATI ON WI TH

DATABASE MI GRATI ON OPTI ON OF SUM

4. Extract SAP Host Agent

One-Step Upgrade/Migration with DMO of SUM

6. Check the version of the

Das könnte Ihnen auch gefallen