Upload
ritssoni788
View
58
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Ramp-Up Migration
Citation preview
SoH Ramp-Up Migration
Johan Parent
+32 (0)2 6903670 [email protected]
March 12th 2013
Your business technologists. Powering progress For Internal Use
AUTHOR(S) : Johan Parent
DOCUMENT NUMBER : sapCC-RU-015
VERSION : 1
STATUS : Draft
SOURCE : Atos
DOCUMENT DATE : March 12th
, 2013
NUMBER OF PAGES : 103
FOR INTERNAL USE
SOH RAMP-UP MIGRATION
Copyright 2012, Atos Belgium S.A./N.V. All rights reserved. Reproduction in whole or in part is prohibited without the prior
written consent of the copyright owner. For any questions or remarks on this document, please contact Atos, +32-(0)2-6903670.
SoH Ramp Up Migration
version: 1 For internal use document number: sapCC-RU-015
Atos
March 12th
, 201
3 of 103
Contents
1 About .............................................................................................................................. 5
1.1 Scope / Purpose ........................................................................................................ 5 1.2 Document Control .................................................................................................... 5 1.3 Contact Information ................................................................................................ 5
2 History Overview ...................................................................................................... 6
3 Preparations................................................................................................................ 7
3.1 Software ........................................................................................................................ 7 3.2 Documentation .......................................................................................................... 9
4 System Export/Import ERP ............................................................................. 11
4.1 Some Export Preparations ................................................................................. 11 4.2 Some additional Export Preparations........................................................... 12 4.3 Run the Export Preparation ............................................................................... 12 4.4 Run the Export ......................................................................................................... 20 4.5 Some Import Preparations ................................................................................. 28 4.6 Run the Import ........................................................................................................ 34 4.7 Post-Migration Steps ............................................................................................. 47
5 System Export/Import CRM ........................................................................... 57
5.1 Some Export Preparations ................................................................................. 57 5.2 Run the Export Preparation ............................................................................... 58 5.3 Run the Export ......................................................................................................... 64 5.4 Some Import Preparations ................................................................................. 72 5.5 Run the Import ........................................................................................................ 77 5.6 Error Solving ............................................................................................................. 89 5.7 Post-Migration Steps ............................................................................................. 95
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
4 of 103
List of changes
Version Date Description Author(s)
1 March 12th
, 2013 Start Initial Draft by Johan Parent Johan Parent
2
SoH Ramp-Up MigrationDMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
5 of 103
1 About
1.1 Scope / Purpose
The purpose of this document is to provide an overview of the Installation/Migration activities during the systems involved with SoH RU (Business Suite on Hana Ramp-up)
1.2 Document Control
Please submit your contributions, insights and lessons learnt to the sap Competence Center. See contact information in section 1.3.
1.3 Contact Information
Contact Persons at the sap Competence Center
Johan Parent Function : SAP Technical Consultant
Tel: +32 (0)2 690 3670
Mail: [email protected]
Peter Joris Function : SAP Technical Consultant
Tel: +32 (0)2 690 3594
Mail: [email protected]
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
6 of 103
2 History Overview
Date Action Performed By
12/3/2013
-
15/4/2013
Start the initial draft
Download Software
Download Installation Guides-
Gather important SAP Notes
Export Systems (ER6 / CR3)
Import ERH
Post Installation ERH
Import CRH
CRH Import troubleshooting
Post Installation CRH
sapCC specific Activities
Finalize documentation
Johan Parent
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
7 of 103
3 Preparations
3.1Software
Download all the required software from the Service Market Place by adding them to the download basket!
Add the latest Installation software to the download basket http://service.sap.com/swdc Ramp-Up Releases and Beta Software Installation and Upgrade EHP6 FOR SAP ERP 6.0 ON HANA
SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA
Update/Migration to HANA Microsoft SQL/Server Add the required installation Components
Add the latest Installation software to the download basket http://service.sap.com/swdc Ramp-Up Releases and Beta Software Installation and Upgrade EHP2 FOR SAP CRM 7.0 ON HANA
SAP enhancement package 2 for SAP CRM 7.0, version for SAP HANA
Update/Migration to HANA Microsoft SQL/Server Add the required installation Components
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
8 of 103
Add the latest Installation software to the download basket http://service.sap.com/swdc Ramp-Up Releases and Beta Software Installation and Upgrade EHP2 FOR SAP SCM 7.0 ON HANA
SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA
Update/Migration to HANA Microsoft SQL/Server Add the required installation Components
All selected components are downloaded with the Software Download basket
Download is started to a local drive on the fileserver K:\BoH_Download
Running the export is performed with the SAPInst program. These days it is provided together with the Software Provisioning Manager in the Software Logistics Toolset. https://websmp102.sap-ag.de/sltoolset
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
9 of 103
It can be downloaded from SAPNet
3.2Documentation
3.2.1Installation / Migration Documentation
https://service.sap.com /erp-ehp6hana-inst
3.2.2Product Documentation
Please also do check the product documentation & guides at help.sap.com help.sap.com SAP Business Suite SAP HANA Innovations for SAP Business Suite Products powered by SAP HANA
SAP ERP 6.0, SAP Enhancement Package 6, Version for SAP HANA. SAP Enhancement Package 2 for SAP CRM 7.0, Version for SAP HANA SAP Enhancement Package 2 for SAP SCM 7.0, version for SAP HANA
3.2.3Important SAP Notes
Note Number Title
1825774 SAP Business Suite Powered by SAP HANA - Multi-Node Support
1774566 SAP Business Suite Powered by SAP HANA - Restrictions
1768031 Release Restrictions for SAP EHP 6 for SAP ERP 6.0, version for SAP HANA
1768032 Release Restrictions for SAP EhP 2 for SAP CRM 7.0, version for SAP HANA
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
10 of 103
Note Number Title
1768043 Release Restrictions for SAP EhP 2 for SAP SCM 7.0, version for SAP HANA
1789659 Release Restrictions for SAP Netweaver AS ABAP 7.40
1812713 Add-on compatibility of SAP NW AS ABAP 7.4 for Suite on HANA
82478 SAP system OS/DB migration
1680045 Release Note for Software Provisioning Manager 1.0
1738258 System Copy of Systems Based on SAP NetWeaver 7.3 and Higher
1762766 EHP6 for SAP ERP 6.0, version for SAP HANA: Required SWC
1785057 Recommendations for migrating suite systems to SAP HANA
1747673 R3load on SAP HANA: SQL error: sql syntax error: near ";"
3.2.4Interesting Links
SAP HANA Database Server Migration http://www.saphana.com/community/blogs/blog/2013/01/15/lets-talk-sap-hana-database-
server-migration
SAP Business Suite powered by SAP HANA http://www.saphana.com/community/learn/solutions/sap-business-suite-on-hana/business-
suite-on-hana-faq/content
OSDB Migration http://service.sap.com/osdbmigration
System Copy and Migration http://scn.sap.com/docs/DOC-8324
Cookbook experience https://cookbook.experiencesaphana.com
Software provisioning Manager http://blogs.msdn.com/b/saponsqlserver/archive/2012/10/10/sap-software-provisioning-
manager-swpm.aspx
https://websmp102.sap-ag.de/sltoolset
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
11 of 103
4 System Export/Import ERP
4.1Some Export Preparations
System that was identified for the Export and migration of ERP on HANA
Description Information
Host Dmzvm050.atosorigin-ica.com
IP 212.190.195.207
OS Version Windows Server 2008 R2 Enterprise
Winver
SAP System ID ER6
SAP System nr 00
SAP Installation nr 0020709309
SAP Comp Version SAP ECC 6.0
Unicode System Yes
Database Microsoft SQL Server 10.50.2769
Request for an additional LUN on the system with enough free disk space to host the export LUN G has been assigned
Create 2 additional folders on this newly created LUN and use these as working folder RU_SoH_Software RU_SoH_ERP_Export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
12 of 103
Download the latest R3load and R3szchk and R3ldctl from the marketplace and copy them in the kernel directory
Check If no canceled or pending update requests are left in the system. (Transaction SM13). If canceled or pending updates exist, you must update these again or delete them from all clients.
You can see whether canceled or pending updates exist by checking if table VBDATA contains any
entries.
Before the export, delete QCM tables from your system as follows: Call transaction SE14 : Choose Extras -> Invalid temp. table All QCM tables that can be deleted are displayed. Mark the tables and delete them.
make sure that no incremental conversion is in progress by running transaction ICNV
Before you start the export of your source system, make sure that the tables TATGPC and TATGPCA are empty.
To do so, use a database utility and delete the contents of these tables.
Make sure there is a recent and valid Backup of the system (Backup is started with CommVault backup software)
Set all released jobs from Released to Scheduled Make note of all the jobs that where changed to bring set them back after the export.
4.2Some additional Export Preparations
These have been overlooked in this guide Make sure the user DDIC in client 000 has a valid password and is not locked Make sure all the jobs have been suspended before the export takes place
4.3 Run the Export Preparation Log on to the Source system as the SIDADM user
er6adm
Make sure Virus on Access Scanner is disabled to improve performance
Locate sapinst in the downloaded Software Provisioning Manager folders
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
13 of 103
G:\RU_SoH_Software\SWPM Choose the option to run as an administrator
Locate the Export Preparation option for ERP on HANA
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
14 of 103
Provide profile information for the system identification
Provide password for the local SIDADM user
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
15 of 103
Provide the SID of the database for database identification
Provide a path for the export G:\RU_SoH_ERP_Export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
16 of 103
Select SAP HANA Database as target database
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
17 of 103
Parameter summary is displayed
Export preparation is running
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
18 of 103
Preparation finished
Show Details
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
19 of 103
HTML Results page No specific messages displayed
a DBSIZE.xml has been created in the export folder under the respective database
The runtime of this preparation was about 20 minutes
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
20 of 103
4.4 Run the Export Log on to the Source system as the SIDADM user
er6adm
Make sure Virus on Access Scanner is disabled to improve performance
Shut down the SAP system using the SAP MMC, but leave the database running
Locate the Database Instance Export option for ERP on HANA
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
21 of 103
Provide profile information for the system identification
Provide password for the local SIDADM user
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
22 of 103
Provide the SID of the existing database for database identification
Provide a path for the export G:\RU_SoH_ERP_Export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
23 of 103
SMIGR_CREATE_DDL ended successfully but did not generate SQL files so select NO
Some more details on the source and select the target database We do not choose to split any STR files
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
24 of 103
Some more export parameters We leave everything as default
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
25 of 103
Parameter summary is displayed
Export started at about 5pm in the afternoon and was run together with the ERP export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
26 of 103
Export is running
Export finished successfully
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
27 of 103
Show Details
HTML Results Page
The export took about 3 hours 40 minutes
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
28 of 103
Size of the export file after the export
4.5 Some Import Preparations
4.5.1 Prepare new System
The server received for performing the install The server will be an applications server only
The database will be the HANA system
Hostname : DMZVM058 IP address : 212.190.195.215
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
29 of 103
Winver
Install the latest Windows Update
Assign additional and enough disk space to the new server For the installation of the Ramp-Up, 2 systems have been made available.
Only one of them an additional LUN has been assigned for copying the Installation DVD
DMZVM002 G: drive
Copy the downloaded installation software from the SAP Market place and place them on the server drive mentioned above
(DMZVM002\G\SoH_SW_Download
A Local folder has also been created on the C-drive where some of the mains software components is copied to
C:\RU_SoH_Software
Unzip \ uncar the required DVDs
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
30 of 103
Copy the exported Database to the local Server G:\RU_SoH_ERP_Export
Create a local Admin installation user (screenshot is from different install) SAPInstall Standard Server password User was assigned to the local Administrator group
Check the firewall settings on the server Make sure that the firewall on Windows 2008 server is disabled Choose Start -> Administrative Tools -> Windows Firewall with Advanced Security Right-click Windows Firewall with Advanced Security and choose Properties.
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
31 of 103
Choose the relevant profile (in most cases Domain Profile) and set the Firewall state to Off.
Windows File System : Make sure that the windows file system is NTFS
Windows Performance Setting: Set the Power setting to Performance Choose Start -> Control Panel -> Power Options
Select Power Options
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
32 of 103
In the Select a power plan window, select High Performance.
Create the system on SAPNET Installation Number to use : 0020616974 SID : RE2 Hardware Key : K0299811691
Generating SAP Solution Manager Key Define new system in Solution Manager Generate key : 72B1BD1B96
Installing JDK Locate the software and run the EXE
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
33 of 103
Welcome to the JAVA installation
Provide Installation path
Installation in progress
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
34 of 103
Installation completed
4.5.2 HANA Database
Current version of the HANA database software is SAP HANA 1.0 SP5 revision 41
SAP HANA 1.0, Support Package 5 (Rev 45 or higher), is required for SAP ECC on SAP HANA.
Database software has been updated to revision 52 by Peter Joris
Client software was copied to the Staging directory
Backup the HANA Database
4.6 Run the Import
Log on to the system with the Installation User created before SAPInstall
Make sure the On access scanning of the Virus scanner is disabled
Start SAPinst in the SWPM folder as an administrator C:\RU_SoH_Software\SWPM\sapinst.exe
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
35 of 103
On the welcome screen navigate to the folder shown in the screenshot
Choose Typical installation
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
36 of 103
Installer requires to log off
General SAP System Parameters ERH and the E-drive
Enter location of the Kernel
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
37 of 103
Master Password information (Check password file)
System default could not be used
Database Copy method used
Provide Database parameters
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
38 of 103
An entry in the host file is required according to the message after continuing
Below entry was added
After log off of the server, sapinst was restarted but same error was displayed Tried the short name and continued
According to prerequisite checker the Swap size is not large enough
Swap size enlarged
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
39 of 103
Check was performed again : YES
Enter the location of the HANA client (Client software was copied to the Staging directory)
The latest version of the HANA client was copied into a new folder (Version 52) C:\RU_SoH_Software\Hana_Client_51043656\DATA_UNITS\HDB_CLIENT_WINDOWS_X86_64_V5
2
Migration Export Location
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
40 of 103
SAP HANA database system administrator
Database Schema password : DBACOCKPIT (same as SPB standard)
Database Schema password : SAPERH (same as new Master password of dmzvm058)
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
41 of 103
Password of the DDIC user in the source system
Unpack archives
General System parameters for the Diagnostic Agent
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
42 of 103
DAA message : Continue YES
Do not register the Diagnostic agent in the SLD
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
43 of 103
Parameter summary screen
Import is started
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
44 of 103
Migration key is wrong
A key was requested on SAPNET
Key inserted and import continued
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
45 of 103
Import completed
Show Details
HTML Results page A local copy of the html file was saved
ERH Import Overall Status.mht.zip
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
46 of 103
Print screen
The export took about 8 hours 41 minutes
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
47 of 103
4.7Post-Migration Steps
4.7.1 SAP Specific Migration steps
Log on to the application host with the ERHADM user and start and stop the SP system with the SAP Management Console
Installation check using Transaction SICK (or SM28)
Import the profiles of the active servers via transaction RZ10
Delete the old profile versions of the source system via transaction RZ10
Check SAP Parameters in the default and instance profiles on the server in folder E:\usr\sap\ERH\SYS\profile No changes required sapCC specific changes done at a later stage
Short Dumps are being thrown in the system for almost every transaction See Error Resolution 1 for more information
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
48 of 103
Post Installation actions for the transport organizer Transaction SE06 Database migration post installation activities
Launch the wizard The wizard performs a basic, automated configuration of the Transport System (CTS) as a
Single system.
A series of confirmation pop-ups appear in succession: Yes to all
Configure transaction STMS Create the DOMAIN when opening STMS transaction in client 000 Set password for user TMSADM
Add a virtual system to Single system landscape by launching the systems overview Create the Virtual system
Distribute the Transport System configuration:
Open the transport route editor
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
49 of 103
Create 2 transport routes, 1 for SAP and 1 for ZTEC
Save and Distribute across all systems
Operation mode NORMAL in transaction RZ04 has already been configured
It has already been assigned to the 24h time schedule (transaction SM63)
Recreate a work process distribution plan Delete the old one Recreate a new based on the new active server
Check for the latest version of the kernel Latest 7.20 Kernel has been deployed as indicated by SAP See Error Resolution 1 for more information
Check the SAPOSS connection. It has already been configured Test was successful
SAPRouter definition, transaction OSS1 has been checked and configured
Online documentation had already been configured via transaction SR13
Printers have already been configured
Delete old spool request (transaction SP01 and program RSPO0041)
Execute the following reports in SE38/SA38 to delete old logs: RSPO1041: Deletes old spool requests RSBPSTDE: Deletes statistic data from the job runtime statistics RSBTCDEL2: Deletes batch jobs RSM13002: Deletes update requests RSARFCER: Deletes old trfc entries SWNC_COLLECTOR_CLEAN_SWNCMONI: Deletes old ST03N data from the source system
Standard jobs have already been configured on the system and are running
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
50 of 103
Delete all entries from the following tables (in client 000, transaction SE16): SDBAD : Deleted SDBAH : Deleted SDBAP : already empty SDBAR : already empty OSMON :old entries Deleted DBSNP: already empty ALCONSEG : all entries with ER6 deleted ALSYSTEMS : already empty
Delete canceled and finished jobs Run RSBTCDEL in SE38 Select Force Mode
Clean the transactional RFC via transaction SM58
Table TLOCK was already empty
Logon groups were checked
There are no self-defined external commands (transaction SM69)
No entries in tables TXCOM (transaction SM54) and THOST (transaction SM55)
Reorganize TEMSE database with transaction SP12 Consistency check -> delete error objects
Maintain New system in the Service Market Place http://service.sap.com/system-data
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
51 of 103
Fill-in the registration form:
Apply for SAP License Installation number to use received by Dagwin
0020616974
Obtain hardware key
Request the licenses from SAP http://service.sap.com/licensekey Mail with License was received
Install SAP License Transaction sLicense Delete all existing Licenses
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
52 of 103
Press and point wizard to received license installation file Returns: 2 licenses installed successfully
Check RFC Server Groups in RZ12. Use Delete Group to delete any source system login groups or instances. Assign the group parallel_generators to the current server instances by double-clicking the
instance name and entering a new group name.
Clean up SecStore transaction
Create and assign logical names to new clients with BD54 and SCC4 Launch transaction BD54 Create new entries
CLNT
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
53 of 103
Maintain the logical system names for all the clients as per standard SAP naming convention Browse to SCC4 transaction Click on change & double click on each of the clients and assign the appropriate logical system
name and save. Perform the same for all the clients in the system.
Click on Save
BDLS Conversion Launch the BDLS conversion tools to apply the logical systems to application tables. Transaction BDLS Uncheck Test run
Perform the operation for client 000 (for instance) with the following Client-Independent option:
Perform for all other clients with only the Client-dependent option:
Performed in every client
SGEN Load activation
4.7.2 sapCC Specific Migration steps
Maintain company address and set AtoS as standard address Transactions for SAPs Address administration is : SUCOMP Logon to Client 000 with user SAP* Company AtoS was already created It was set as default
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
54 of 103
Create my own user in all the clients mentioned below
Change SAP standard user password in all clients mentioned below Client 000 : sap*, DDIC, SAPJSF, EP_REMOTE Client 001 : sap*, DDIC Client 066 : sap*, EARLYWATCH Client 100 : sap*, DDIC, SAPJSF, EP_REMOTE, TMSADM, ADS_AGENT, SM_SCC, SMDAGENT_SCC Client 110 : sap*, DDIC, ADSUSER, ADS_AGENT, SAPJSF, EP_REMOTE, TMSADM Client 120 : sap*, DDIC, ADSUSER, ADS_AGENT, SAPJSF, EP_REMOTE, TMSADM Client 130 : sap*, DDIC, ADSUSER, ADS_AGENT, SAPJSF, EP_REMOTE, j2EE_ADMIN, j2EE_GUEST,
SAPCPIC
Client 200 : sap*, DDIC, EP_REMOTE Client 300 : sap*, DDIC, SAPJSF, EP_REMOTE
Check on the ZTECH development package transaction SE80 Already there
Profile maintenance according to the parameter settings in the sapCC cookbook DEFAULT ERH_DVEBMGS00_DMZVM058 System was stopped and started to make the changes effective
The ZINSDEVKEY program is already available in the system
Regenerate SYSTEM PSE Transaction StrustSSO2
Import sapCC portal certificate in order to enable Single Sign on to Transaction StrustSSO2 Add it to the ACL list in every client
Include in weekly backup schedule
4.7.3 Error Resolution 1
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
55 of 103
Short Dumps are being thrown in the system for almost every transaction
Although the first line in every dump might be a little different ... the following lines are recurring in each dump :
"The kernel module "AB_SHMKMPROPAGATEAREA" is not registered for the im" "plementation of method "_PROPAGATE_AREA" of class "CL_SHM_AREA"."
Check for the latest version of the kernel Kernel installed with the migration is currently the latest available kernel Some new Disp+Work patches have been released Downloaded and deployed the latest available patches
Same issue
Found a blog mentioning a Downgrade of the Kernel http://zir3.tumblr.com/ Downloaded, extracted and copied the latest version of the 720 EXT Kernel, version 402
System was restarted and no more short dumps Message to SAP was created on this issue
Reply from SAP
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
56 of 103
Yes, this Runtime Error is known issue reported by several customer before. Currently there are two solution for this problem.
1. A workaround as you know, please use kernel release 720 instead. So it's fine to continue using the 7.20 kernel.
2. If you want to continue using kernel 738, please apply the EHP 2 for SAP HANA
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
57 of 103
5 System Export/Import CRM
5.1Some Export Preparations
System that was identified for the Export and migration of ERP on HANA
Description Information
Host Dmzvm006.atosorigin-ica.com
IP 212.190.195.189
OS Version Windows Server 2008 R2 Enterprise
Winver
SAP System ID CR3
SAP System nr 00
SAP Installation nr 0020616977
SAP Comp Version EHP2 FOR SAP CRM 7.0
Unicode System Yes
Database Microsoft SQL Server 10.50.2769
Request for an additional LUN on the system with enough free disk space to host the export LUN G has been assigned
Create 2 additional folders on this newly created LUN and use these as working folder RU_SoH_Software RU_SoH_CRM_Export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
58 of 103
Download the latest R3load and R3szchk and R3ldctl from the marketplace and copy them in the kernel directory
Check If no canceled or pending update requests are left in the system. (Transaction SM13). If canceled or pending updates exist, you must update these again or delete them from all clients.
You can see whether canceled or pending updates exist by checking if table VBDATA contains any
entries.
Before the export, delete QCM tables from your system as follows: Call transaction SE14.; Choose Extras -> Invalid temp. table All QCM tables that can be deleted are displayed. Mark the tables and delete them.
make sure that no incremental conversion is in progress by running transaction ICNV
Before you start the export of your source system, make sure that the tables TATGPC and TATGPCA are empty.
To do so, use a database utility and delete the contents of these tables.
Make sure there is a recent and valid Backup of the system (Backup is started with CommVault backup software)
Set all released jobs from Released to Scheduled Make note of all the jobs that where changed to bring set them back after the export.
5.2 Run the Export Preparation Log on to the Source system as the SIDADM user
cr3adm
Make sure Virus on Acces Scanner is disabled to improve performance
Locate sapinst in the downloaded Software Provisioning Manager folders G:\RU_SoH_Software\SWPM Choose the option to run as an administrator
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
59 of 103
Locate the Export Preparation option
Provide profile information for the system identification
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
60 of 103
Provide password for the SIDADM user
Provide the SID of the database for database identification
Provide a path for the export G:\RU_SoH_CRM_Export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
61 of 103
Select SAP HANA Database as target database
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
62 of 103
Parameter summary is displayed
Export preparation is running
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
63 of 103
Preparation finished
Show Details
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
64 of 103
HTML Results page No specific messages displayed
a DBSIZE.xml has been created in the export folder under the respective database
The runtime of this preparation was about 20 minutes
5.3 Run the Export Log on to the Source system as the SIDADM user
Cr3adm
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
65 of 103
Make sure Virus on Access Scanner is disabled to improve performance
Shut down the SAP system using the SAP MMC, but leave the database running
Locate sapinst in the downloaded Software Provisioning Manager folders G:\RU_SoH_Software\SWPM Choose the option to run as an administrator
Locate the Export Preparation option
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
66 of 103
Provide profile information for the system identification
Provide password for the SIDADM user
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
67 of 103
Provide the SID of the database for database identification
SMIGR_CREATE_DDL ended successfully but did not generate SQL files so select NO
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
68 of 103
Some more details on the source and select the target database We do not choose to split any STR files
Some more export parameters We leave everything as default
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
69 of 103
Parameter summary is displayed
Export started at about 5pm in the afternoon and was run together with the ERP export
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
70 of 103
Export is running
Export finished successfully
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
71 of 103
Show Details
HTML Results Page
The export took about 1 hour 20 minutes
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
72 of 103
Size of the export file after the export
5.4 Some Import Preparations
5.4.1 Prepare new System
The server received for performing the install The server will be an applications server only
The database will be the HANA system
Hostname : DMZVM002 IP address : 212.190.195.185
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
73 of 103
Winver
Install the latest Windows Update
Assign additional and enough disk space to the new server For the installation of the Ramp-Up, 2 systems have been made available.
Only one of them an additional LUN has been assigned for copying the Installation DVD
DMZVM002 G: drive
Copy the downloaded installation software from the SAP Market place and place them on the server drive mentioned above
(DMZVM002\G\SoH_SW_Download
Unzip / uncar the required DVDs
Copy the exported Database to the local Server G:\RU_SoH_CRM_Export
(see above)
Create a local Admin installation user (screenshot is from different install) SAPInstall
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
74 of 103
Standard Server password User was assigned to the local Administrator group
Check the firewall settings on the server Make sure that the firewall on Windows 2008 server is disabled Choose Start -> Administrative Tools -> Windows Firewall with Advanced Security Right-click Windows Firewall with Advanced Security and choose Properties.
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
75 of 103
Choose the relevant profile (in most cases Domain Profile) and set the Firewall state to Off.
Windows File System : Make sure that the windows file system is NTFS
Windows Performance Setting: Set the Power setting to Performance Choose Start -> Control Panel -> Power Options
Select Power Options
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
76 of 103
In the Select a power plan window, select High Performance.
Swap size enlarged based on the ERP import
5.4.2 HANA Database
Database software has been updated to revision 52 by Peter Joris
Client software was copied to the Staging directory
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
77 of 103
Backup the HANA Database
5.5Run the Import
Log on to the system with the Installation User created before SAPInstall
Make sure the On access scanning of the Virus scanner is disabled
Start SAPinst in the SWPM folder as an administrator C:\RU_SoH_Software\SWPM\sapinst.exe
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
78 of 103
On the welcome screen navigate to the folder shown in the screenshot
Choose Typical installation
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
79 of 103
Installer requires to log off
SAPinst restarts after log of
General SAP System Parameters CRH and the E-drive
Enter location of the Kernel
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
80 of 103
Master Password information (Check password file)
Note that the password of the DBUser must consist of at least 1 number, 1 lowercase alphabetical letter and one uppercase.
Database Copy method used
Provide Database parameters
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
81 of 103
An entry in the host file is required according to the message after continuing
Below entry was added
After log off of the server, sapinst was restarted but same error was displayed Tried the short name and continued
There was no prerequisite checker pop up this time Swap size was enlarged in the preparation phase
Enter the location of the HANA client (Client software was copied to the Staging directory)
The latest version of the HANA client was copied into a new folder (Version 52) C:\RU_SoH_Software\Hana_Client_51043656\DATA_UNITS\HDB_CLIENT_WINDOWS_X86_64_V5
2
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
82 of 103
Migration Export Location
SAP HANA database system administrator
Database Schema password : DBACOCKPIT (same as SPB standard)
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
83 of 103
Database Schema password : SAPERH (same as new Master password of dmzvm002)
Password of the DDIC user in the source system
Unpack archives
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
84 of 103
General System parameters for the Diagnostic Agent
DAA message : Continue YES
Do not register the Diagnostic agent in the SLD
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
85 of 103
Parameter summary screen
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
86 of 103
Import is started
Migration key is wrong
A key was requested on SAPNET
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
87 of 103
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
88 of 103
Key inserted and import continued
Import seems to be failing
A first error was encountered
For more details see Error Stop 1
Error Stop 1 was solved and SAPinst was continued
A little later a new error was encountered
For more details see Error Stop 2
SAPINst was continued
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
89 of 103
completed
Show Details
HTML Results page A local copy of the html file was saved
CRH Import Overall Status.zip
The export took about 1 hours 40 minutes
5.6 Error Solving
5.6.1 Error Stop 1 A first error was encountered
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
90 of 103
See Log file
CRH Error Stop 1 Installation Overall Status.zip
All logs show similar error message DbSl Trace: execute(), rc=1, rcSQL=257 (sql syntax error: incorrect syntax near ";":
line 1 col 87 (at pos 87))
DbSl Trace: EXECUTE on connection 0, rc=257 (sql syntax error: incorrect syntax
near ";": line 1 col 87 (at pos 87))
(DB) ERROR: DDL statement failed
( ALTER TABLE "RSDMDIMTAB" enable persistent merge; )
DbSlExecute: rc = 99
(SQL error 257)
error message returned by DbSl:
sql syntax error: incorrect syntax near ";": line 1 col 87 (at pos 87)
One SAP note was found that provides similar error description Note 1747673 - R3load on SAP HANA: SQL error: sql syntax error: near ";"
The note mentions to swap the attached file "ABAP/DB/HDB/DDLHDB.TPL in the export directory. You can then restart the installation or migration.
Similarly, patch level 22 solves this problem for R3ldctl.has an attached
Decided to download and replace the latest R3l executables
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
91 of 103
Original files where renamed to .orig
SAPInst was restarted
Same error was displayed
Second option from the Note was applied Changing the DDLHDB.tpl file
SAPInst was restarted
Same error was displayed
In one of the log files I found a path pointing to the above TPL file in the location mentioned below C:\Program
Files\sapinst_instdir\BSHANA10\BSONHANA10\CRM\HDB\HDB\COPY\HDB\SYSTEM\STD\AS-
ABAP
So I changed the file also in this file location
Migration was Retried This time it seemed to proceed!
Error Stop one was solved
5.6.2 Error Stop 2 A second error was encountered
See Log file
CRH error stop 2 Installation Overall Status.zip
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
92 of 103
log shows error message Wed Apr 03 11:13:29 CEST 2013 | com.sap.hdb.sl.lib.utils.cmd.clazz.AbapPostLoadExecution | -------------------------------------------
-----------------------------
Wed Apr 03 11:13:29 CEST 2013 | com.sap.hdb.sl.lib.utils.cmd.clazz.AbapPostLoadExecution | Next clazz for
BatchExecution is: CreateSchemaMappingForAbap
Wed Apr 03 11:13:29 CEST 2013 | com.sap.hdb.sl.lib.utils.cmd.clazz.AbapPostLoadExecution | Execute HdbCmdClazz: class
com.sap.hdb.sl.lib.utils.cmd.clazz.CreateSchemaMappingForAbap
Wed Apr 03 11:13:29 CEST 2013 | com.sap.hdb.sl.lib.connection.sql.JdbcDriver | URI:
file:/E:/usr/sap/CRH/hdbclient/ngdbc.jar
Wed Apr 03 11:13:29 CEST 2013 | com.sap.hdb.sl.lib.connection.sql.JdbcConnection | Start new connection with connect
URL: jdbc:sap://dmzim001:30115 connect user: System
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.sl.lib.connection.sql.JdbcConnection | Start new connection with connect
URL: jdbc:sap://dmzim001:30115 connect user: System
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.sl.lib.utils.cmd.clazz.CreateSchemaMappingForAbap | SAP_ABAP authoring
schema already exists for a different physical schema in _SYS_BI.M_SCHEMA_MAPPING.
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain | Error during execution of HdbCmdClazz
section!
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain | A schema mapping for authoring schema
SAP_ABAP already exists for a different physical schema.
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.sl.lib.utils.cmd.clazz.CreateSchemaMappingForAbap.createSchemaMapping(CreateSchemaMappingForAba
p.java:62)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.sl.lib.utils.cmd.clazz.CreateSchemaMappingForAbap.execute(CreateSchemaMappingForAbap.java:51)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.sl.lib.utils.cmd.clazz.BatchExecutionBase.executeCmdClazz(BatchExecutionBase.java:52)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.sl.lib.utils.cmd.clazz.BatchExecutionBase.executeCmdClazzes(BatchExecutionBase.java:15)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.sl.lib.utils.cmd.clazz.AbapPostLoadExecution.execute(AbapPostLoadExecution.java:14)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.core.main.cmd.HdbCmdMain.execute(HdbCmdMain.java:113)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
com.sap.hdb.core.main.cmd.HdbCmdMain.main(HdbCmdMain.java:74)
Wed Apr 03 11:13:30 CEST 2013 | com.sap.hdb.core.main.cmd.HdbCmdMain |
*************************************************************
SAP_ABAP authoring schema is already existing as shown in table below in HANA studio
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
93 of 103
A message to SAP was created
SAPInst dir was zipped and uploaded on request
Reply from SAP Dear Customer, Note that SAP_ABAP will not be used anymore after SWPM SP2. Also problem that you has will be fixed on SWPM SP2 which will be released next week. For workaround, please use following steps:
1. remove SAP_ABAP, SAP_ECC entries from m_schema_mapping 2. install CRM system 3. add SAP_CRM to physical CRM schema - you can also remove SAP_ABAP since it will
not going to be used anymore 4. add SAP_ECC & ABAP to physical ERP schema
After all above steps, your m_schema_mapping table should looks some like this: ABAP -> SAPERH SAP_ECC -> SAPERH SAP_CRM -> SAPCRH Thanks, jaram
Changes to the table were made
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
94 of 103
Instead of removing at this point, I renamed both authoring schemas as follows,
Select statements where used
SAPINST was continued
Step with Post Load activities was competed
Status of the table after the continuation of the import
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
95 of 103
According to the recommendations from SAP following changes were made
Result
5.7Post-Migration Steps
5.7.1 SAP Specific Migration steps
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
96 of 103
Log on to the application host with the CRHADM user and start and stop the SP system with the SAP Management Console
Installation check using Transaction SICK (or SM28)
Import the profiles of the active servers via transaction RZ10
Delete the old profile versions of the source system via transaction RZ10
Check SAP Parameters in the default and instance profiles on the server in folder E:\usr\sap\ERH\SYS\profile No changes required sapCC specific changes done at a later stage
Post Installation actions for the transport organizer Transaction SE06
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
97 of 103
Database migration post installation activities
Launch the wizard The wizard performs a basic, automated configuration of the Transport System (CTS) as a
Single system.
A series of confirmation pop-ups appear in succession: Yes to all
Configure transaction STMS Create the DOMAIN when opening STMS transaction in client 000 Set password for user TMSADM
Add a virtual system to Single system landscape by launching the systems overview Create the Virtual system
Distribute the Transport System configuration:
Open the transport route editor
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
98 of 103
Create 2 transport routes, 1 for SAP and 1 for ZTEC
Save and Distribute across all systems
Operation mode NORMAL in transaction RZ04 has already been configured
It has already been assigned to the 24h time schedule (transaction SM63)
Recreate a work process distribution plan Delete the old one Recreate a new based on the new active server
Check the SAPOSS connection. It has already been configured Test was successful
Short Dumps are being thrown in the system, similar to ERH system Change Kernel in order to solve this Latest 7.20 Kernel has been deployed as indicated by SAP
See Error Resolution 1 for more information
SAPRouter definition, transaction OSS1 has been checked and configured
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
99 of 103
Online documentation had already been configured via transaction SR13
Execute the following reports in SE38/SA38 to delete old logs: RSPO1041 / RSPO0041: Deletes old spool requests RSBPSTDE: Deletes statistic data from the job runtime statistics RSBTCDEL2 / RSBTCDEL: Deletes batch jobs RSM13002: Deletes update requests RSARFCER: Deletes old trfc entries SWNC_COLLECTOR_CLEAN_SWNCMONI: Deletes old ST03N data from the source system
Printers have already been configured
Standard jobs have already been configured on the system and are running
Delete all entries from the following tables (in client 000, transaction SE16): SDBAD : already empty SDBAH : already empty SDBAP : already empty SDBAR : already empty OSMON :old entries Deleted DBSNP: already empty ALSYSTEMS : already empty
Clean the transactional RFC via transaction SM58
Reorganize TEMSE database with transaction SP12 Consistency check -> delete error objects
Table TLOCK was already empty
Logon groups were checked - SMLG
There are no self-defined external commands (transaction SM69)
No entries in tables TXCOM (transaction SM54) and THOST (transaction SM55)
Maintain New system in the Service Market Place http://service.sap.com/system-data
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
100 of 103
Fill-in the registration form:
Apply for SAP License Installation number to use received by Dagwin
0020616974
Obtain hardware key
Request the licenses from SAP http://service.sap.com/licensekey Mail with License was received
Install SAP License Transaction sLicense Delete all existing Licenses
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
101 of 103
Press and point wizard to received license installation file Returns: 2 licenses installed successfully
Check RFC Server Groups in RZ12. Use Delete Group to delete any source system login groups or instances. Assign the group parallel_generators to the current server instances by double-clicking the
instance name and entering a new group name.
Clean up SecStore transaction
Create and assign logical names to new clients with BD54 and SCC4 Launch transaction BD54 Create new entries
CLNT
Maintain the logical system names for all the clients as per standard SAP naming convention Browse to SCC4 transaction Click on change & double click on each of the clients and assign the appropriate logical system
name and save. Perform the same for all the clients in the system.
Click on Save
BDLS Conversion Launch the BDLS conversion tools to apply the logical systems to application tables. Transaction BDLS Uncheck Test run
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
102 of 103
Perform the operation for client 000 (for instance) with the following Client-Independent option:
Perform for all other clients with only the Client-dependent option:
Performed in every client
SGEN Load activation
5.7.2 sapCC Specific Migration steps
Maintain company address and set AtoS as standard address Transactions for SAPs Address administration is : SUCOMP Logon to Client 000 with user SAP* Company AtoS was already created It was set as default
Create my own user in all the clients mentioned below
Change SAP standard user password in all clients mentioned below Client 000 : sap*, DDIC, Client 001 : sap*, DDIC Client 066 : sap*, EARLYWATCH Client 100 : sap*, DDIC, SAPJSF, EP_REMOTE, ADS_AGENT
Check on the ZTECH development package transaction SE80 Already there
Profile maintenance according to the parameter settings in the sapCC cookbook
DMZVM019 RE2 Reach 2
version: 2 For internal use document number: sapCC-1WOW-DMZVM019
Atos
March 12th
, 201
103 of 103
DEFAULT CRH_DVEBMGS00_DMZVM002 System was stopped and started to make the changes effective
The ZINSDEVKEY program is already available in the system
Regenerate SYSTEM PSE Transaction StrustSSO2
Import sapCC portal certificate in order to enable Single Sign on to Transaction StrustSSO2 Add it to the ACL list in every client
Include in weekly backup schedule Backup HANA Database