SAP BASIS BASIC OVERVIEW: January 2017

SAP HANA is an in-memory computing platform and latest innovation from SAP that has completely transformed the relational database industry. It combines database, application processing, and integration services on a single platform. SAP recommends their existing customers to migrate their SAP systems to SAP HANA to make maximum use of the In-Memory platform for OLTP and OLAP applications

	OLTP	OLAP
Age Of Data	Current	Historical
System	ECC	BW
Queries	Relatively standardized and simple queries	Often complex queries involving
Data Base Operations	Add , Modify , Delete , Update and Read	Read
What the data Reveals	Ongoing business processes	Multi-dimensional views of various kinds of business activities
Source of data	Operational data; OLTPs are the original source of the data	Consolidation data
Purpose of data	To control and run fundamental business tasks	To help with planning, problem solving, and decision support

SAP HANA Architecture:

Server Component	OS Process	Service Name	Description
Index server	hdbindexserver	indexserver	Contains the actual data stores
			It contain Engines for processing the data
Preprocessor server	hdbpreprocessor	preprocessor	Used by the index server to analyze text data
Name server	hdbnameserver	nameserver	Owns the information about the topology of the SAP HANA system
XS Server	hdbxsengine	xsengine	Known as SAP HANA Extended Application Services (SAP HANA XS)
			Provide Access for Application and developers to access Hana Database using HTTPS.
Compile server	hdbcompileserver	compile server	Compile stored procedures and programs
			It runs on every host and does not persist data.
SAP Web Dispatcher	hdbwebdispatcher	webdispatcher	Inbound HTTP and HTTPS connections to XS services.
SAP start service	sapstartsrv	sapstartsrv	It starts and stops the other services in the correct order.
			It also performs monitoring of services at runtime state.

HANA Migration options

SAP recommends that you perform a system copy to create test, demo and training systems. (Export and Import)

If you need to change your operating system or database, you have to perform a migration of your SAP system.

Non-SAP methods to replicate existing SAP systems (for example, methods offered by hardware partners).

A system copy can be either homogeneous or heterogeneous:

Homogenous System Copy

Both operating system and database system stay the same

Performed in most cases with database-specific procedure (database-independent procedure could optionally also be used)

Heterogeneous System Copy

One of the following is changed during the system copy:

Operating system (in this case, system copy is called OS migration)

Database system (in this case, system copy is called DB migration)

Operating system and database system (in this case, system copy is called OS/DB migration)

STEPS:

Export

Transfer load (bring dumps of export to server)

Install (Install target system + empty DB (without load)

Import DB load Source DB

Software provisioning manager used for the following activity:

Dual-stack split

System copy and migration

System installation

System rename

We can download latest version of documentation, from SAP Service Marketplace at:

http://service.sap.com/sltoolset

Software Logistics Toolset 1.0 --> Documentation --> System Provisioning

There are separate guides for every use case:

Installation Guides

System Copy Guides

System Rename Guides

Dual-Stack Split Guides

You read the SAP Note that contains latest information:

Installation: SAP Note 1680045

System copy: SAP Note 1768158 (SAP NW 7.0x) or 1738258 (SAP NW = 7.1x)

Dual-stack split: SAP Note 1797362

System rename: SAP Note 1619720

For more information on installation:

SAP Community Network: Software Logistics - - > Installation

Maintenance Planner: SAP Community Network at http://scn.sap.com/docs/DOC-65243

For more information on system copy and migration:

SAP Community Network: Software Logistics - - > System Copy and Migration

For more information on dual-stack split:

SAP Community Network: Software Logistics - - > Dual-Stack Split

For more information on system rename:

SAP Community Network: Software Logistics - - > System Rename

KUN export Preparation using SWPM 1.0 SP07 for Windows:

SAP Netweaver 7.0 including enhancement package 1

Software life cycle management option

System copy

Export

1. Export preparation

Profile

Export Location

Source system/target Database

Update statistic

Brconnect.log for checking the status of stats collection

After this phase complete the export location will create couple of folders and files. In our case /export/ABAP/DB

After export run report in SE38

SMIGR_CREATE_DDL:

Run the job and it will automatically create 2 files copy files accordingly

/export/ABAP/DB

/export/ABAP/DB/ORA

2. Table Splitting preparation

Export Location

Target Database

Table splitting /SWPM/table_split.txt

Give ABAP Schema (SAPSR3)/Password

Select table splitter (R3trans)

3. Database instance export

Profile Directory

Database SID and Host

Export Location and manually stop system.

Confirm the execution of report SMIGR_CREATE_DDL and its location

Confirm Source and target DB

Set splitting tool parameter and location

Update statistic

Stop the system and continue it will export the DB and create the file with .dump extension

KUN Import Preparation using SWPM 1.0 SP07 for Linux:

Setup environment for SWPM

Create file .sapinst as follows in directory /usr/sap/inst (any temp directory for installation)

Make sure permission set as 777 and owner as root:sapinst

export SAPINST_JRE_HOME=/usr/sap/KUN/SYS/exe/sapjvm_4

export JAVA_HOME=/usr/sap/KUN/SYS/exe/sapjvm_4

export PATH=$JAVA_HOME/bin:$PATH

export LIBPATH=/sapmnt/KUN/exe

export ORACLE_HOME=/oracle/KUN/112_64

Installation of KUN on Target system (HANA Appliance)

Installation of KUN on Target system (HANA Appliance)

SAP Netweaver 7.0 including enhancement package 2

Software life cycle management option

Prerequisite check

Check for required Prerequisite

Check central services instance

Database instance

Choose database instance as oracle

Choose Unicode

Provide UC Kernel

Confirm the summary

Execute installation Prerequisite

Main Import

Installation of KUN on Target system (HANA Appliance)

SAP Netweaver 7.0 including enhancement package 2

Software life cycle management option

System copy

Target system Installation

Oracle

Central system

Choose Custom

Define Parameter

Give SID KUN

Give mount point \sapmnt

Unicode tick

Set FQDN for SAP system uncheck

Give password for all user to this system (Don’t use @)

Give password for system administrator (sidadm)

Left other thing as usual

Choose installation method: standard system copy \ migration (load-based)

Enter the Database Parameter

DBSID: KUN

Oracle database installation for: Single Instance on file system

Install db with orasid user tick

Give password for database administrator (orasid)

Left other thing as usual

Give the required software Location

UC Kernel 7.21 location

Migration export

Enter the Parameter for Database system

Instance RAM: 516740

ABAP Schema: SAPSR3

Password for ABAP Schema: XXXXXXXX

ABAP SSFS: UNCHECK

DB Server version: 112

DB Client version: 112

DB Bit version: 64

Maxdatafile Size: 2000 MB

Left other thing as usual

Password for SYS

Password for System

Location of oracle RDBMS

Listener name: LISTENER

Listener Port:1521

Keep Listeren.ora yes

Keep Tnsnames.ora

Load Parameter

SAP Code Page: 4103

No Parallel job: 6

Migration Key

Expert option: keep as usual

Skip statistics creation (we can manually update stat after import)

Parameter for Central instance and ABAP central services instance (ASCS)

Central instance number: XX

ASCS instance number: XX

Uncheck the next option interrupt before SAP System starts

Provide password of DDIC 000 of exported system

Give SL Controller media 721

Give oracle client 112 media

Select all the option from next screen to unpack the archives

Confirm the summery and proceed further

Execute phases:

Create SAP User

Install common system files

Unpack SAP Archives

Create & Load Database

Install & Check Database

Evaluate Database Parameter

Provide Oracle RDBMS 112

Install Database Server Software

Set the DISPLAY variable

Change the directory to /oracle/stage/112_64/Database/SAP/

Run ./RUNINSTALLER

(We need to set env as per requirement)

Install Oracle Client software

Configure Oracle server network

This will create till above steps

Prepare database server configuration

Create Database

Create & Check Tablespace

Oracle Account installation

Check Oracle NLS_CHARECTORSET

Create Database Schema

Check Oracle Path

Install DBA Tools

Import ABAP

Post Load Activity

Perform ORA Post Load Activity

Create Database statistic

Install Central instance

Install instance basics of ASCS0

Start instance

ABAP Post installation Activity

Check DDIC password

Run ABAP Report

Post Linux Migration Steps

Start SGEN

Check webD configuration.

SMLG changes

RZ10

BDLS

Applied SAP license

HANA Migration using SAP DMO

DMO Concept:-

SUM creates shadow repository on the traditional database until downtime phase. In parallel the target database is being set up (such as client, schema)

The shadow repository is copied to the target database. Then the downtime starts.

After the migration of the application data (including data conversion), the update is finalized and the SAP system runs on the target database.

The Source database continues to run.

After the migration of KUN to HANA box using export and import we have to upgrade and migrate on HANA Database.

Pre-Steps

Run update Statistics

Configure SAP system in SAP Solution manager and download SAP Upgrade media using MOPZ. Don’t forgot to choose additional target kernel (SAP HANA + LINUX + OS on which SAP Application will run)

Download latest SUM (in our case it’s SUM 14)

Set ICM/hostname_full in instance profile and add host entry in /etc/hosts

Change log mode of SAP HANA database to overwrite during SoH migration. Once SoH migration is done, please set log mode to normal

Download migration key and SAP license key for HANA database

SAP BASIS, SAP BW has to be updated to meet SAP DMO pre-requisite. Please read SAP Note 1813548.

You must have sufficient free space

Password of root, sidadm, database user, ddic (000 Client)

Make sure DB is in noarchivelog mode

Increase em/initial_size_MB

Changing Oracle SGA parameter (Change parameter sga_max_size to 40 G & restart application)

Fix time zone – SAP HANA database and SAP application should have same time zone

Pre-Requisite of SAP DMO

SAP HANA appliance must be available

Stack.xml file has to be created (& SAP software files have to be downloaded: MOPZ)

Web Browser version might have to be updated. The user interface (UI) of the DMO procedure is based on SAPUI5 and requires a specific internet browser version

Changed permissions to 777 for root

./STARTUP confighostagent KUN it will give 3 url

JAVA https://hostname:1129/lmsl/sumjava/KUN/index.html

ABAP https://hostname:1129/lmsl/sumabap/KUN/doc/sluigui

DUAL https://hostname:1128/lmsl/sum/KUN/dual.html

In place of hostname put the ip address and run this url form chrome browser

JAVA https://10.xx.xxx.xxx:1129/lmsl/sumjava/KUN/index.html

ABAP https://10.xx.xxx.xxx:1129/lmsl/sumabap/KUN/doc/sluigui

DUAL https://10.xx.xxx.xxx:1128/lmsl/sum/KUN/dual.html

In our case its ABAP system so we are going with

https://10.xx.xxx.xxx:1129/lmsl/sumabap/KUN/doc/sluigui

it will ask for sidadm user and password mention the same and login to DMO. Make sure in browser setting popup allowed in case it’s not come up. Also also we can run these url from any machines.

The first option it will come for stack.xml file location. Provide the same with media that we downloaded after stack. in our case all media are in /usr/sap/trans/KUN.

SAP DMO Phase 1—Extraction

The first option it will come for stack.xml file location. Provide the same with media that we downloaded after stack. in our case all media are in /usr/sap/trans/KUN.

it will ask for ddic password in 000 client and SYSTEM password for database. Please don’t change ddic in between HANA migration that can cause SAP jobs cancel which are running as ddic user.

If your SPAM is not updated it will ask for spam update.

Enter the target database type:-

Here we have two options

No Migration

Hana Migration and provide the migration code

Choose Hana migration

Next screen we have to choose don’t compare table contents and provide the migration Key from marketplace.

Error:-

PREP_INIT/TOOLCHECKXML_UPG === List of tool Failing the check

Solution:-

We have got error for DBA tools (DB Independent resp. of Oracle) so we have downloaded the latest tools from Kernel in marketplace and extracted and kept in /usr/sap/SUM/abap/exe directory & continued.

In Last steps it will ask to apply SAP notes.

Next it will check for SPDD adjustment. Sent mail to Application team for adjustment of SPDD object when they completed their task keep the TR number and DATA and CO File in safe location.

Error:-

Could not open the ICU common library

The following files must be in the path described by

The environment variable "LD_LIBRARY_PATH":

libicuuc.so.50, libicudata.so.50, libicui18n.so.50 [/bas/742_REL/src/flat/nlsui0.c 1535] pid = 42935

LD_LIBRARY_PATH is currently set to /usr/sap/KUN/SYS/exe/run:/usr/sap/KUN/SYS/exe/uc/linuxx86_64:/oracle/client/11x_64/instantclient [/bas/742_REL/src/flat/nlsui0.c 1538] pid = 42935

Solution: Changed env variable rsdb_ssfs_connect from 0 to 1

rsecssfx put DB_CONNECT/DEFAULT_DB_USER SAPSR3 -plain

rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD admin123

chmod 600 <dir_global>/security/rsecssfs/data/SSFS_<sid>.DAT

Restart SAP SYSTEM

SAP DMO Phase 2— Configuration

Choose Advanced (Downtime Minimized option) and also choose keep archiving off during whole procedure

Check & configure WP according to the requirement & HW configuration

R3trans (import processes)

R3load (for migration export and import)

SQL processes for uptime and downtime activities.

In case of SAP DMO, these processes can be change any time. You can use below url to change those processes

http://IPAddressofthehost:1128/lmsl/sumabap/<SID>/set/procpar

SGEN can be run during UPTIME; it will save time in downtime. You can choose whether SGEN has to run on UPTIME or DOWNTIME in configuration phase. Choose SGEN processes based on system resources you have.

Note: Some time it’s took very long time so make sure you have informed to the client.

Next screen it will ask for hana client media path

Next it will ask SAP HANA details if not installed the Hana database then install it here.

Hana Database installation:

Extract the downloaded media and run ./hdblcm from the location whre media extracted for hana database.

It will give the console for installation and it will show installed hana database on server which is already running. In our case there is no database so choose option new installation and next screen it will ask for component. Choose All. Next provide installation path, it will suggest /hana/shared choose the same and then provide SID as KUD and instance number 00. Based on your requirement choose single/multi container. Then choose mode in our case its “Test”. Then chose data and log volume and memory restriction here choose “n” if you don’t want restriction on memory and it will also ask for some default option choose as per your need and finally database will be installed.

Now return to SUM screen

Target host IP address

Target SID

Instance number

Target system license, It will also ask for system databse user password. Please enter correct password. SAP HANA Licsens has to applied in this phase otherwise you will face errors. If you need to update SAP HANA reversion then It will be done before this phase.

Error:-

DMO screen prompted to apply some missing notes as we have missed in planning part as per DMO guide.

Next screen it will ask to choose addons which we want to modify as per below.

Next screen we going to see SPDD and SPAU, provide the SPDD and SPAU transport here which ABAP team usually provide.

SAP DMO Phase 3— Check

Here we are going to check the compatibility for our database version, os and S4hana ERP system.

The following actions are carried out:

Calculation of the space for the shadow system

System health checks (such as nametab, transport system)

Checks of relevant tool and system parameters

In next screen DMO will prompt to run variant check job. Which will run a job to save variant and later it will restore that variant.

Job name: JOB_RASUVAR , choose yes and next

After the upgrade, many of your variants can no longer be used because the relevant selection screens have changed. To save the variants, the SAP system offers two reports:

RASUVAR1 saves your variants on the source system.

RASUVAR2 restores the variants in the target system.

During phase SAVE_VAR_CHK you can decide whether you want the upgrade tool to run report RASUVAR1. The report is started in phase JOB_RASUVAR1. If you have decided to run report RASUVAR1, phase JOB_RASUVAR2 automatically starts report RASUVAR2 towards the end of the upgrade.

Next screen will be for ASU Upgrade

ASU Upgrade: It is application-specific update toolbox (ASU toolbox). its run using transaction /ASU/UPGRADE. The system loads the XML file (ASU.XML) contained in the SUM directory, generates a task list, and branches to the task list maintenance. SAP Note 1000009.

Error:

Update record still exist and space issue in tablespace.

Solution

update records are deleted from SM13

Executed commands

brspace -function tscreate -tablespace PSAPSR3740 -class none -data both -size 200 -incrsize 200 -maxsize 32000 -autoextend yes

brspace -function tsextend -tablespace PSAPSR3740 -size 200 -incrsize 200 -maxsize 32000 -autoextend yes

brspace -function tsextend -tablespace PSAPSR3740 -size 200 -incrsize 200 -maxsize 1032 -autoextend yes

brspace -function tsextend -tablespace PSAPSR3740 -size 200 -incrsize 200 -maxsize 25000 -autoextend yes

SAP DMO Phase 4— Preprocessing Phase

In this roadmap step, SUM creates the shadow system.

The shadow system is then used for various update activities while you can still use the original system in production operation. The SUM builds up the shadow system by cloning parts of the original system. All tables of the SAP NetWeaver Application Server are needed as shadow tables to operate the shadow system.

The shadow system is used to perform the modification adjustment of the ABAP Dictionary objects and the activation of new ABAP Dictionary objects that are part of the update. Finally, the Software Update Manager performs the shadow import and writes directly into the shadow tables.

Modifications to the contents of the original tables are indicated by triggers. These tables are copied and imported during downtime

The following actions are carried out:

Checks for locked objects

ABAP Workbench locking

Running the shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN)

DMO-specific actions:

Uptime migration: Repository

Execution of SMIGR_CREATE_DDL

Execution of phases related to SAP Business Warehouse

Error: - MAIN_INT/JOB_RSVBCHCK2 were negative

Solution

Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries.

1083709 - Error when you import Support Packages

Next screen development will be lock. Here we usually lock all user too except few

Error: - inactive and lock object found

We have got screen related to inactive object and lock object in TR, it was a miss as we haven’t checked before upgrade. Activate the object with the help of application team or use se38/se37 to activate these objects and release TR for locked object.

Next screen is for repository modification:

Login to shadow instance by unlocking it if not unlock. Create user with ddic copy and move the transport of SPDD into shadow from STMS_IMPORT. Before that make sure system is modifiable in se06 and TR is released.

Error MAIN_INT/ACT_UPG were negative

Check dumps job failed and tune memory but that did not helped. Finally reached to sap and as per them I have accepted the non-severe error and proceed further.

1387739 - Out of memory errors during shadow system operation

941735 - SAP memory management system for 64-bit Linux systems

Error:

SAPup broke during phase SUBMOD_SHD2_RUN/XPRAS_SHD_AIMMERGE in module MAIN_SHDIMP / Shadow Import

Error Message: Detected 35 errors summarized in 'XPRASSHD.ELG'

Calling '/usr/sap/SUM/abap/exe/tp' failed with return code 8, check /usr/sap/SUM/abap/log/SAPup.ECO for details

tp used shadow connect

Solution:130140 - ORA-4030 on NT, out of process memory

Also Accepted non-severe error and proceed further.

Next screen is for scale up: in Our case it was not there.

This section deals with the automated Landscape Reorganization feature for the SAP HANA scale out scenario that is available as of Software Update Manager version 1.0 SP10.

The scale out scenario means the deployment of multiple server nodes in case memory requirements exceed the available memory of a single server node after the migration to SAP HANA database. For this, several phases are carried out during the SUM with DMO run:

REQ_LANDSCAPE_REORG

In this phase, SUM prompts you in a dialogue to import an SQL-file from SAP Note 1958346 into the database.

REQ_LANDSCAPE_REORG_2

In this phase, SUM prompts you in a dialogue to import an SQL-file from one of the following notes into the database according to your product:

BW on SAP HANA: SAP Note 1908075

Suite on HANA: SAP Note 1899817

The next screen is to take full backup of system as well as SUM, this is the steps were we can reset our upgrade. After here we can’t reset upgrade/DMO migration.

SAP DMO Phase 5— Execution Phase

In this roadmap step, the switch to the target system takes place.

The SUM completes the copy import action during downtime for all tables with set triggers. The EU_SWITCH phase completes the switch to the new system. All tables prepared in the shadow system are copied to the target system. The KX_SWITCH_1 phase switches the SAP kernel. The PARCONV_UPG phase converts the application table, and the phase TABIM_UPG imports the remaining data. Finally, the XPRAS_UPG phase starts the XPRAs required by the system.

The following DMO-specific actions are carried out:

Migration of application data

Repository & kernel switch

Adoptions of structures to new release (phase PARCONV)

Main import (phase TABIM)

XPRAS

After Backup we proceeded and found below error:

Error:

Upgrade of the system will stop with error "Index SMSCMAID A01 could not be activated"

Solution:

Create index as per note and if fail run the report attached in snote.

1413569 - Index for SMSCMAID table for Performance and Upgrade