Galben= intrebarea , Verde = raspunsul
1.What do you need to take in consideration for a migration from windows MaxDB to linux Hana
Target kernel Windows MaxDb
Target kernel Linux Hana
1. SUM 2.0 ->NW 7.50 or higher
6.You are converting a 3 system landscape, DEV->QUAL->PROD, and you manage to concert DEV and
QUAL
Upgrade of PRD must be performed before importing TR from DEV
2. As of SUM 1.0 SP10, the DMO procedure allows you to include the Unicode conversion (for SCP systems)
3. Unicode conv only – SUM with DMO
4. Remote Code Analysis in ATC via transaction
Se80, ATC
5. Download simplicator DB from portal
NZDM is not possible if the SUM procedure contains a DMO
6. NZDM only upgrade
7. Apply note for framework + use the framework
8. App guide : free space + target release specific
9. R3 load parallel 40 - 80 R3load
More → Utilities and then Process Control Center and Charts Control Center
10. Stop - the early downtime - before downtime
11. SPACE – Green - …modification are lost
A scale out is a landscape reorganization. It distributes the SAP HANA database among several nodes. This is
used for SAP BW, only.
A scale up is an optimization of the index server
12. What need to be modified in case of a scale-out
scaleout – edit a file + 7.40 minimum
13. When can user connect to system , the earliest = during postprocessing phase, after post
activities are done
14. Phases of DMO – EU_CLONE_MIG_UT_RUN, EU_CLONE_MIG_DT_RUN ,DOWNCONF_DTTRANS
15. ICNV -> DELETE triggers in target tables
Mark as flag the tables to be deleted
16. Downtime optimized – move table data conversion to uptime
----------------------------------------------------------------------------------------------------
1. Download dir content
Duration XML(MIGRATE_DT_DUR.XML)
Stack XML
2. DMO monitoring
Process Control Center
SM37 job log
SGEN
export dump
3. Simplification list – download from SAP Support Portal
4. SPDD
release transport
activate objects
modif versions
assign transport in SPDD
5. ASU toolbox with
/ASU/UPGRADE
/ASU/START
/ASU/SHOW_NOTE
/ASU/SSM
6. DMO benchmark uses
Duration files
Performance evaluation
SPDD
stack.xml
7. Which maintenance events are possible with SUM for an SAP system based on AS ABAP 7.40 and
above?
Support Package Stack update
Database migration
Release upgrade
System copy
Dual stack split
8. UPGANA.XML
% bar information from a previous run
9. The SUM procedure stops with an error during uptime.
How can you identify the current phase, the one in which SUM encountered an error?
SUM UI
SUM/abap/logs
SM21
sapevt.trc
10. SPDD - named user in shadow system, client 000
11. You are performing an S/4HANA conversion of the development system.
Which credentials do you use in which system to perform the adjustment of programs and other non-
dictionary repository objects (SPAU)?
- Credentials of a named user in the development client of the development system
12. S/4HANA conversion necessary kernels
target release level for source and target database
13. Preparation steps
Delete 066 and all other unused clients
Uninstall Fiori
Uninstall industry extension (not possible)
Install SAP Gateway
14. S/4HANA conversion phases
DIFF*
DOWNCONF_TRANS
EU_IMPORT
RUN_RSDBSCPY (only for update)
RUN_RSPTBFIL_ISUTABU (only for nZDM)
15. You don’t perform SPAU, and hit next
SUM continues, and modifications are lost
16. You are planning to upgrade your SAP ECC 6.07 system running on a single codepage (SCP) to SAP
ECC 6.08.
- Perform the Unicode conversion before the upgrade to SAP ECC 6.08
17. hostagent config: sumabap.conf
18. During an SAP S/4HANA conversion with DMO, which of the following actions take place during the
business downtime of the SUM procedure?
SPAU
XPRAs
eCATTs
20. Do not compare table contents = row count on all tables
21. Single System - no shadow instance in update (not available with DMO)
22. Standard mode - shadow stops before downtime
23. Expert mode
Shadow instance number
Reuse profiles
24. SPDD transport - umodauto.lst
25. DMO: 2 R3loads per split - export+import
26. Calculated level - packages present in download dir
More → Utilities and then Process Control Center and Charts Control Center
28. More -> Utilities
DMO Migration Control Center
SUM parameters
29. Advanced, shadow:
SPDD
ACT_UPG
31. SUM 2.0 - S/4, EHP 8
32. XPRAs: job log sm37, SUM log
33. Steps in uptime
ACT_UPG
DDIC_UPG
CLONE_MIG_DT_CREATE
34. UC only -> SWPM load
35. SHADOW_IMPORT_INC - R3trans, tmp
36. In which part of an upgrade does SUM allow you to generate ABAP loads (SGEN)?
during uptime
post-downtime
38. Benchmarking - specific set of tables
39. SAPup param migration_only = 1
DB type change, and no component change
In case the target release contains SAP_BASIS 7.50 and above, you have to perform the Unicode conversion stand
alone, before starting SUM!
As of SAP NetWeaver 7.50 and ECC 6.08, only Unicode will be supported!
An upgrade of a non-Unicode system to SAP ECC 6.08 or higher is NOT possible, because SAP ECC 6.08 is based
on SAP NetWeaver 7.5, which does not offer any non-Unicode kernel anymore. Therefore, you need to perform two
projects:
First, a Unicode Conversion
Second, upgrade to ECC 6.08
NZDM is not possible if the SUM procedure contains a DMO.
