SAP First Guidance
SAP NetWeaver BW 7.30 SAP NetWeaver BW 7.30
SAP HANA™ Appliance
Applicable Releases:
SAP HANA 1.0 SPS 03 (Rev. 23)
SAP NetWeaver BW SP06
and higher
Internal Use Only/Rampup usage This first Guidance should help to quickly implement either a fresh BW on HANA Installation or
an Export of an existing System with anyDB Export.
As the technical Installation Steps are the same the Guidance should make an own created
Customer specific Documentation obsolete and is the complementary Documentation to the
existing e2e Guide for migration BW on HANA.
The Document is still “work in progress”, so the Guide is not intended to be exhaustive so far,
and might never will. But it contains everything to successfully install the technical System
For more Information please contact [email protected]
Version 1.2
April 2012
First guidance... BW on HANA (ORANGE) Fresh Installation/Import - including unified Installer
© Copyright 2012 SAP AG. 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 AG. The
information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p,
System p5, System x, System z, System z10, System z9, z10, z9, iSeries,
pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,
OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power
Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,
HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and
Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other
countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either
trademarks or registered trademarks of Adobe Systems Incorporated in
the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open
Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,
and MultiWin are trademarks or registered trademarks of Citrix Systems,
Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks
of W3C®, World Wide Web Consortium, Massachusetts Institute of
Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used
under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, and other SAP products and
services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other
Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Business
Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,
and other Sybase products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Sybase, Inc.
Sybase is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this
document may be reproduced, copied, or transmitted in any form or for
any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license
agreement or any other agreement with SAP. This document contains
only intended strategies, developments, and functionalities of the SAP®
product and is not intended to be binding upon SAP to any particular
course of business, product strategy, and/or development. Please note
that this document is subject to change and may be changed by SAP at
any time without notice.
SAP assumes no responsibility for errors or omissions in this document.
SAP does not warrant the accuracy or completeness of the information,
text, graphics, links, or other items contained within this material. This
document is provided without a warranty of any kind, either express or
implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without
limitation direct, special, indirect, or consequential damages that may
result from the use of these materials. This limitation shall not apply in
cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not
affected. SAP has no control over the information that you may access
through the use of hot links contained in these materials and does not
endorse your use of third-party Web pages nor provide any warranty
whatsoever relating to third-party Web pages.
SAP “How-to” Guides are intended to simplify the product implement-
tation. While specific product features and procedures typically are
explained in a practical business context, it is not implied that those
features and procedures are the only approach in solving a specific
business problem using SAP NetWeaver. Should you wish to receive
additional information, clarification or support, please refer to SAP
Consulting.
Any software coding and/or code lines / strings (“Code”) included in this
documentation are only examples and are not intended to be used in a
productive system environment. The Code is only intended better explain
and visualize the syntax and phrasing rules of certain coding. SAP does
not warrant the correctness and completeness of the Code given herein,
and SAP shall not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java™. Any code change
in these components may cause unpredictable and severe malfunctions
and is therefore expressively prohibited, as is any decompilation of these
components.
Any Java™ Source Code delivered with this product is only to be used by
SAP’s Support Services and may not be modified or altered in any way.
Document History
Document Version Description
1.20 Update for BW 7.30 SP07 and HANA 1.0 Rev. 26
1.10 Update for BW 7.30 SP06 and HANA 1.0 Rev. 23
1.00 First official release of this guide
Typographic Conventions
Type Style Description
Example Text Words or characters quoted
from the screen. These
include field names, screen
titles, pushbuttons labels,
menu names, menu paths,
and menu options.
Cross-references to other
documentation
Example text Emphasized words or
phrases in body text, graphic
titles, and table titles
Example text File and directory names and
their paths, messages,
names of variables and
parameters, source text, and
names of installation,
upgrade and database tools.
Example text User entry texts. These are
words or characters that you
enter in the system exactly
as they appear in the
documentation.
<Example
text>
Variable user entry. Angle
brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
Icons
Icon Description
Caution
Note or Important
Example
Recommendation or Tip
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 1
Table of Contents
1. Installation of CIA System – BW on HANA (ORANGE) including unified Installer ............ 3
1.1 Prepare the HANA server before starting unified Installer........................................... 4
1.1.1 Prepare the filesystem for the default usage of HANA 1.0 SP03 and higher 6
1.1.2 starting/stopping HANA and sapstartsrv ......................................................... 6
1.1.3 create the default filesystem manually and reset install directory ................ 6
1.1.4 start the unified Installer ..................................................................................... 6
1.1.5 uninstall the unified Installer .............................................................................. 7
1.1.6 Adapt the file .sapenv.csh for the user <sid>adm ........................................... 7
1.1.7 Example output of the unified Installer ............................................................. 8
1.1.8 Check the Time Zones on the HANA server ................................................... 12
1.1.9 Check UUIID libraries on Linux based AppServers ........................................ 12
1.2 Starting the Import of the homogeneous System export of the CIA system ........... 13
1.2.1 IM Master on the backend (Linux) ................................................................... 14
1.2.2 SAPInst GUI on the Windows Frontend .......................................................... 14
1.2.3 Default location of the SAPInst directory ....................................................... 15
1.2.4 FQDN must be provided ................................................................................... 16
1.2.5 HANA client version for the HANA server Revision ....................................... 21
1.2.6 Exchange R3load and LibDBSL before import starts ....................................22
1.2.7 Check invalid_objects.txt ..................................................................................35
1.2.8 Setting the correct client DEFAULT.PFL and adapt the Instance Profile ... 40
1.2.9 Obsolete/wrong Parameters with NetWeaver 7.30 ABAP ........................... 41
1.2.10 Import new License and check secure storage after migration ................... 41
2. Apply the current SP stack (including corrections) ....................................................... 42
2.1 Apply the special SP06 stack for HANA based systems ........................................... 42
2.1.1 Apply corrections after SP06 for HANA based systems ............................. 44
2.1.2 Manual Processing of some SAP Notes .......................................................... 47
2.2 Apply SP07 for all BW 7.30 Systems ........................................................................... 49
2.2.1 Apply corrections after SP07 for HANA based systems .............................. 50
2.3 Apply the Business Content 7.36 (BI_CONT, BI_CONT_XT) ..................................... 51
2.4 Run transaction SGEN ...................................................................................................52
2.5 First run of BW technical content..................................................................................52
2.5.1 Check InfoObject 0IOBJNM .............................................................................53
3. Modifying the SAP Profiles (restart SAP) ...................................................................... 54
3.1 SAP Profile - DEFAULT.PFL ...........................................................................................54
3.2 SAP Profile - CIA_ASCS03_lt5006 ...............................................................................54
3.3 SAP Profile - CIA_DVEBMGS02_lt5006 ....................................................................... 55
3.4 Copy the Tickets from DVEBMGS02/sec to ASCS03/sec ....................................... 59
3.5 Check the HDB/ABAP settings for SP03 and SP05 .................................................. 59
3.5.1 Check /update the HDB ABAP settings ......................................................... 59
3.5.2 Check the HDB settings for SP03 ................................................................... 59
3.5.3 HANA 1.0 Rev. 21: Check Privileges TREXVIADBSL ...................................... 61
3.5.4 HANA 1.0 Rev. 22: unwanted big statistic data .............................................. 61
3.5.5 HANA 1.0 Rev. 23: Check Syntax Changes ..................................................... 61
3.5.6 HANA 1.0 Rev. 24: Temporary Switch join_red_parall ................................. 62
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 2
3.5.7 HANA 1.0 Rev. 25: several temporary switches ............................................ 62
3.5.8 HANA 1.0 Rev. 26: new version, several settings .......................................... 64
3.5.9 HANA 1.0 Rev. 27: special hotfix release........................................................ 64
4. Further tasks in the target system ................................................................................. 66
4.1.1 Check transaction SECSTORE after systemcopy......................................... 66
4.1.2 Reset the Logon Groups ................................................................................... 67
4.1.3 Check settings in Report RSCPINST ............................................................... 67
4.1.4 Check myself Connection after System migration ........................................ 67
4.1.5 Check DSO activation Parameters ................................................................. 68
4.1.6 Run the Post Steps after the Systemcopy ..................................................... 69
4.2 Check the settings for TMS after Systemcopy............................................................ 71
4.2.1 Check SE06 ........................................................................................................ 71
4.2.2 Check SE80 – Package ..................................................................................... 72
4.3 Check further BW Basis Settings .................................................................................. 73
4.4 Additional Tips for a fresh NetWeaver 7.30 Installation ............................................. 74
4.5 How to connect HANA to CSN (SAP access) .............................................................. 76
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 3
1. Installation of CIA System – BW on HANA (ORANGE) including unified Installer
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 4
1.1 Prepare the HANA server before starting unified Installer See the HANA Installation Guide and adapt the file setuphana.slmodel
https://service.sap.com/~sapidb/011000358700000604562011
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 5
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
************************************************************************
This is the template file for the HANA System Installation. setuphana.slmodel.HDB
Please check the manual for setting the required parameters.
************************************************************************
An entry is required for all fields marked with ${...}
-->
<DeclarativeModuleSerialization>
<ManagedObject class="com.sap.lm.hana.hana.HANAPlatformProduct" id="0">
<Child class="com.sap.lm.hana.hana.HANAPlatformSystem" id="4" name="hanaSystem">
<!-- Insert the path to the HDB data directory. Ensure that
this directory exists prior to invoking the installer.
The location of this directory depends on the hardware
setup as well as the location where the volume is
mounted. An example location might be "/data".
-->
<StringParameter name="dataPath" value="/usr/sap/HDB/data"/>
<!-- Insert the path to the HDB log directory. Ensure that this
directory exists prior to invoking the installer. The
location of this directory depends on the hardware setup as
well as the location where the volume is mounted. An example
location might be "/log".
-->
<StringParameter name="logPath" value="/usr/sap/HDB/log"/>
<!-- This is the path to the sapmnt volume. The setting below
is the default for a standard installation. The HDB
documentation provides additional details for setting up
distributed HANA installations.
-->
<StringParameter name="sapmntPath" value="/sapmnt"/>
<!-- Insert a valid instance number for the HDB Database. Examples
for valid instance numbers are 00, 04, and 50. -->
<StringParameter name="instanceNumber" value="01"/>
<!-- Insert a valid SID. Valid SIDs are for example HAN, H87, and GHJ. -->
<StringParameter name="sid" value="HDB"/>
<!-- Insert the host name of the HDB database. The host name must be
assigned to the local machine. -->
<StringParameter name="hdbHost" value="lt5006.wdf.sap.corp"/>
</Child>
<Reference name="centralComputerSystem" refid="1"/>
</ManagedObject>
<ManagedObject class="com.sap.lm.decl.os.ComputerSystem" id="1"/>
</DeclarativeModuleSerialization>
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 6
1.1.1 Prepare the filesystem for the default usage of HANA 1.0 SP03 and higher
cd /data
mkdir sap
chmod –R 777 sap
ln -s /data/sap /usr/sap
ln -s /data/sap /sapmnt
1.1.2 starting/stopping HANA and sapstartsrv
cd /usr/sap/HDB/HDB01/
HDB/HDB01> HDB start/stop/info/version/help
HDB/HDB01> cd /usr/sap/HDB/SYS/exe/hdb/
lt5006: exe/hdb> sapcontrol -nr 01 -prot NI_HTTP -function StopService
lt5006: exe/hdb> sapcontrol -nr 01 -prot NI_HTTP -function RestartService HDB
If the owner is not <sid>adm you could just delete it (as root) and perform a RestartService with the appropriate sapstartsrv.
In case the service is killed or the appropriate file .sapstreamXXXX is missing you can restart the sapservice daemon with
lt5006:HDB:hdbadm /usr/sap/HDB/SYS/profile 40 > sapstartsrv pf=<instance-profile> -D
Then the above commands will work again. This also works for the connected SAP Instances
1.1.3 create the default filesystem manually and reset install directory
lt5006:/usr/sap # dir
drwxr-xr-x 2 sapadm sapsys 4096 Oct 19 13:33 tmp
drwxrwxrwx 2 root root 4096 Oct 19 12:54 trans
lt5006:/usr/sap # mkdir HDB
lt5006:/usr/sap # mkdir HDB/log
lt5006:/usr/sap # mkdir HDB/data
lt5006:/usr/sap # chmod -R 777 HDB
lt5006:/usr/sap # cd /data/tmp/
lt5006:/data/tmp # rm -rf *
lt5006:/data/tmp # rm .eclipseproduct
1.1.4 start the unified Installer
lt5006:/usr/sap # cd
/data/software/HANA_SP03/DATA_UNITS/HANA_IM_LINUX__X86_64
./setup.sh /data/tmp setuphana.slmodel.HDB
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 7
1.1.5 uninstall the unified Installer
lt5006:/usr/sap # cd
/data/software/HANA_SP03/DATA_UNITS/HANA_IM_LINUX__X86_64
./uninstall.sh /data/tmp setuphana.slmodel.HDB
1.1.6 Adapt the file .sapenv.csh for the user <sid>adm
Add the line source ./HDBSettings.csh into the .sapenv.csh environment of <sid>adm after the run of the unified Installer. Furthermore adapt the .sapenv.csh with the correct timezone for SAP NetWeaver (CET instead of UTC)
# This is the SAP Environment
#set TZ to UTC, see SAP Note 1551454
setenv TZ CET
setenv LD_LIBRARY_PATH
setenv SAPSYSTEMNAME HDB
alias hostname 'hostname -s'
alias pd 'pushd'
alias pop 'popd'
alias dir 'ls -l'
alias l 'ls -abxCF'
alias h 'history'
alias Pwd '/bin/pwd'
setenv DIR_LIBRARY /usr/sap/HDB/SYS/exe/run
setenv LD_LIBRARY_PATH /usr/sap/HDB/SYS/exe/run
setenv PATH /usr/sap/HDB/SYS/exe/run:${PATH}
alias cdpro 'cd /usr/sap/HDB/SYS/profile'
alias cdexe 'cd /usr/sap/HDB/SYS/exe/run'
alias cdglo 'cd /usr/sap/HDB/SYS/global'
setenv PATH ${PATH}:/usr/sap/tools/bin
source ./HDBSettings.csh
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 8
1.1.7 Example output of the unified Installer ==========================================================================
SAP HANA unified installer
==========================================================================
Enter the master password. The master password must contain at least one
lower case characater, one uppper case character, and one number. It must
be at least eight characters long.
Master password:
Reenter master password:
Starting HANA Installer
DVD location: /data/software/HANA_SP03
Installer DATA: /data/software/HANA_SP03/DATA_UNITS/HANA_IM_LINUX__X86_64/com.sap.lm.hana.inst-
?.?.?-linux64.tar.gz
Working directory: /data/tmp
Model file: /data/software/HANA_SP03/DATA_UNITS/HANA_IM_LINUX__X86_64/setuphana.slmodel.HDB
Log file: /data/tmp/log/install.glf
Unzipping installer into dir: /data/tmp
Finished successfully.
User sapadm is member of group sapsys
SAP Host Agent seems not to be installed, trying to install it...
Checking DVD structure
Installing SAP Host Agent:
Preparing... ########################################### [100%]
1:SAPHostAgent ########################################### [100%]
saphostexec stopped
16:53:03 19.10.2011 LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
SAP Host Agent not running. Tyring to start it.
-> Start /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile <-
start hostcontrol using profile /usr/sap/hostctrl/exe/host_profile
Error: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (empty result: '')
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (wrong result: 4290215392 >
2048)
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (wrong result: 4290215424 >
2048)
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (wrong result: 4290215424 >
2048)
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (wrong result: 4290215424 >
2048)
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (wrong result: 4290215424 >
2048)
SAPOSCOL is not yet initialized. Waiting 10s to continue installation. (wrong result: 4290215424 >
2048)
SAPOSCOL successfully initialized. (64 < 2048)
Adapting cRef.xml (/data/tmp)
Done successfully.
Starting Installer in directory: /data/tmp
--> ./setuphana -f
/data/software/HANA_SP03/DATA_UNITS/HANA_IM_LINUX__X86_64/setuphana.slmodel.HDB -a execute
[20111019165418] [ 1% completed] Working on: 'HANAPlatformProduct' ... --> STARTED
[20111019165418] [ 1% completed] Working on: 'HANA Installation' ... --> STARTED
[20111019165418] [ 2% completed] Working on: 'Global Host (localhost)' ... --> STARTED
[20111019165418] [ 3% completed] Working on: 'SAPSystemAccounts' ... --> STARTED
[20111019165418] [ 4% completed] Working on: 'sapsys' ... --> STARTED
[20111019165418] [ 4% completed] Working on: 'sapsys' ... --> DONE (36 ms)
[20111019165418] [ 5% completed] Working on: 'hdbadm' ... --> STARTED
[20111019165418] [ 6% completed] Working on: 'hdbadm' ... --> DONE (64 ms)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 9
[20111019165418] [ 7% completed] Working on: '/usr/sap/HDB/home' ... --> STARTED
[20111019165419] [ 7% completed] Working on: '/usr/sap/HDB/home' ... --> DONE (104 ms)
[20111019165419] [ 8% completed] Working on: '.sapenv' ... --> STARTED
[20111019165420] [ 9% completed] Working on: '.sapenv' ... --> DONE (1420 ms)
[20111019165420] [ 10% completed] Working on: 'SAPSystemAccounts' ... --> DONE (1624 ms)
[20111019165420] [ 10% completed] Working on: '/sapmnt/HDB' ... --> STARTED
[20111019165420] [ 11% completed] Working on: 'global' ... --> STARTED
[20111019165420] [ 12% completed] Working on: 'security' ... --> STARTED
[20111019165420] [ 13% completed] Working on: 'data' ... --> STARTED
[20111019165421] [ 13% completed] Working on: 'data' ... --> DONE (118 ms)
[20111019165421] [ 14% completed] Working on: 'lib' ... --> STARTED
[20111019165421] [ 15% completed] Working on: 'tools' ... --> STARTED
[20111019165421] [ 16% completed] Working on: 'tools' ... --> DONE (117 ms)
[20111019165421] [ 16% completed] Working on: 'lib' ... --> DONE (234 ms)
[20111019165421] [ 17% completed] Working on: 'security' ... --> DONE (470 ms)
[20111019165421] [ 18% completed] Working on: 'global' ... --> DONE (711 ms)
[20111019165421] [ 19% completed] Working on: 'exe' ... --> STARTED
[20111019165421] [ 19% completed] Working on: 'exe' ... --> DONE (124 ms)
[20111019165421] [ 20% completed] Working on: 'profile' ... --> STARTED
[20111019165421] [ 21% completed] Working on: 'profile' ... --> DONE (122 ms)
[20111019165421] [ 21% completed] Working on: '/sapmnt/HDB' ... --> DONE (1087 ms)
[20111019165421] [ 22% completed] Working on: '/usr/sap/HDB' ... --> STARTED
[20111019165421] [ 23% completed] Working on: 'SYS' ... --> STARTED
[20111019165421] [ 24% completed] Working on: 'exe' ... --> STARTED
[20111019165421] [ 24% completed] Working on: '<NOT_RESOLVED>' ... --> STARTED
[20111019165421] [ 25% completed] Working on: '<NOT_RESOLVED>' ... --> DONE (4 ms)
[20111019165421] [ 26% completed] Working on: 'exe' ... --> DONE (148 ms)
[20111019165421] [ 27% completed] Working on: 'profile=>/sapmnt/HDB/profile' ... --> STARTED
[20111019165421] [ 27% completed] Working on: 'profile=>/sapmnt/HDB/profile' ... --> DONE
(52 ms)
[20111019165421] [ 28% completed] Working on: 'profile' ... --> STARTED
[20111019165422] [ 29% completed] Working on: 'profile' ... --> DONE (125 ms)
[20111019165422] [ 30% completed] Working on: 'global=>/sapmnt/HDB/global' ... --> STARTED
[20111019165422] [ 30% completed] Working on: 'global=>/sapmnt/HDB/global' ... --> DONE (57
ms)
[20111019165422] [ 31% completed] Working on: 'SYS' ... --> DONE (505 ms)
[20111019165422] [ 32% completed] Working on: '/usr/sap/HDB' ... --> DONE (583 ms)
[20111019165422] [ 33% completed] Working on: '/etc/services' ... --> STARTED
[20111019165422] [ 33% completed] Working on: '/etc/services' ... --> DONE (757 ms)
[20111019165422] [ 34% completed] Working on: 'Global Host (localhost)' ... --> DONE (4053 ms)
[20111019165422] [ 35% completed] Working on: 'SAPSystemAccounts' ... --> STARTED
[20111019165422] [ 36% completed] Working on: 'sapsys' ... --> STARTED
[20111019165422] [ 36% completed] Working on: 'sapsys' ... --> DONE (41 ms)
[20111019165422] [ 37% completed] Working on: 'hdbadm' ... --> STARTED
[20111019165422] [ 38% completed] Working on: 'hdbadm' ... --> DONE (64 ms)
[20111019165422] [ 39% completed] Working on: '/usr/sap/HDB/home' ... --> STARTED
|[20111019165423] [ 39% completed] Working on: '/usr/sap/HDB/home' ... --> DONE (84 ms)
[20111019165423] [ 40% completed] Working on: '.sapenv' ... --> STARTED
[20111019165424] [ 41% completed] Working on: '.sapenv' ... --> DONE (1547 ms)
[20111019165424] [ 41% completed] Working on: 'SAPSystemAccounts' ... --> DONE (1737 ms)
[20111019165424] [ 42% completed] Working on: 'HDB/HDB01' ... --> STARTED
[20111019165424] [ 43% completed] Working on: 'HDB/HDB01' ... --> DONE (1 ms)
[20111019165424] [ 44% completed] Working on: 'SystemProfile of System: HDB' ... --> STARTED
|[20111019165424] [ 44% completed] Working on: 'SAPSYSTEMNAME : HDB' ... --> STARTED
[20111019165424] [ 45% completed] Working on: 'SAPSYSTEMNAME : HDB' ... --> DONE (32 ms)
[20111019165424] [ 46% completed] Working on: 'SystemProfile of System: HDB' ... --> DONE (155
ms)
[20111019165424] [ 47% completed] Working on: '/usr/sap' ... --> STARTED
[20111019165424] [ 47% completed] Working on: 'hdbstudio_update' ... --> STARTED
[20111019165425] [ 48% completed] Working on: 'hdbstudio_update' ... --> DONE (134 ms)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 10
[20111019165425] [ 49% completed] Working on: 'HDB Studio Repository' ... --> STARTED
[20111019165425] [ 50% completed] Working on: 'HDB_SOFTWARE_STUDIO' ... --> STARTED
[20111019165429] [ 50% completed] Working on: 'HDB_SOFTWARE_STUDIO' ... --> DONE (4528 ms)
[20111019165429] [ 51% completed] Working on: 'HDB Studio Repository' ... --> DONE (4530 ms)
[20111019165429] [ 52% completed] Working on: 'SAP HANA DB lt5006' ... --> STARTED
[20111019165429] [ 53% completed] Working on: 'HDB_SOFTWARE_SERVER' ... --> STARTED
[20111019165744] [ 53% completed] Working on: 'HDB_SOFTWARE_SERVER' ... --> DONE (194546 ms)
[20111019165744] [ 54% completed] Working on: 'SAP HANA DB lt5006' ... --> DONE (194549 ms)
[20111019165744] [ 55% completed] Working on: 'HDB Client' ... --> STARTED
[20111019165744] [ 56% completed] Working on: 'HDB_SOFTWARE_CLIENT' ... --> STARTED
[20111019165752] [ 56% completed] Working on: 'HDB_SOFTWARE_CLIENT' ... --> DONE (7945 ms)
[20111019165752] [ 57% completed] Working on: 'hdbclient' ... --> STARTED
[20111019165752] [ 58% completed] Working on: 'hdbclient.lst' ... --> STARTED
[20111019165752] [ 59% completed] Working on: 'libSQLDBCHDB.so' ... --> STARTED
[20111019165752] [ 59% completed] Working on: 'libSQLDBCHDB.so' ... --> DONE (25 ms)
[20111019165752] [ 60% completed] Working on: 'hdbclient.lst' ... --> DONE (223 ms)
[20111019165752] [ 61% completed] Working on: 'HDB Client' ... --> DONE (400 ms)
[20111019165752] [ 61% completed] Working on: 'Sum4Hana Installer' ... --> STARTED
[20111019165752] [ 62% completed] Working on: 'HDB' ... --> STARTED
[20111019165752] [ 63% completed] Working on: 'SYS' ... --> STARTED
[20111019165752] [ 64% completed] Working on: 'SYS' ... --> DONE (126 ms)
[20111019165752] [ 64% completed] Working on: 'HDB' ... --> DONE (250 ms)
[20111019165752] [ 65% completed] Working on: 'SUM' ... --> STARTED
[20111019165752] [ 66% completed] Working on: 'SUM4HANA' ... --> STARTED
[20111019165759] [ 67% completed] Working on: 'SUM4HANA' ... --> DONE (6747 ms)
[20111019165759] [ 67% completed] Working on: 'HDB Studio HTTP Publisher' ... --> STARTED
[20111019165759] [ 68% completed] Working on: 'configuration' ... --> STARTED
[20111019165759] [ 69% completed] Working on: 'org.eclipse.equinox.simpleconfigurator' ...
--> STARTED
[20111019165800] [ 70% completed] Working on: 'bundles.info' ... --> STARTED
[20111019165800] [ 70% completed] Working on: 'studio_repository, 0.0.0,
file:/usr/sap/hdbstudio_update/repository,4,true' ... --> STARTED
[20111019165800] [ 71% completed] Working on: 'studio_repository, 0.0.0,
file:/usr/sap/hdbstudio_update/repository,4,true' ... --> DONE (53 ms)
[20111019165800] [ 72% completed] Working on: 'bundles.info' ... --> DONE (203 ms)
[20111019165800] [ 73% completed] Working on: 'org.eclipse.equinox.simpleconfigurator' ...
--> DONE (453 ms)
[20111019165800] [ 73% completed] Working on: 'configuration' ... --> DONE (588 ms)
[20111019165800] [ 74% completed] Working on: 'SUM' ... --> DONE (590 ms)
[20111019165800] [ 75% completed] Working on: 'Sum4HanaConfig' ... --> STARTED
[20111019165807] [ 76% completed] Working on: 'Sum4HanaConfig' ... --> DONE (7268 ms)
[20111019165807] [ 76% completed] Working on: 'Sum4Hana Installer' ... --> DONE (14794 ms)
[20111019165807] [ 77% completed] Working on: '/usr/sap/hdbstudio_update' ... --> STARTED
[20111019165807] [ 78% completed] Working on: 'repository' ... --> STARTED
[20111019165807] [ 79% completed] Working on: 'META-INF' ... --> STARTED
[20111019165807] [ 79% completed] Working on: 'MANIFEST.MF' ... --> STARTED
[20111019165807] [ 80% completed] Working on: 'MANIFEST.MF' ... --> DONE (26 ms)
[20111019165807] [ 81% completed] Working on: 'META-INF' ... --> DONE (134 ms)
[20111019165807] [ 81% completed] Working on: 'WEB-INF' ... --> STARTED
[20111019165807] [ 82% completed] Working on: 'web.xml' ... --> STARTED
[20111019165807] [ 83% completed] Working on: 'web.xml' ... --> DONE (21 ms)
[20111019165807] [ 84% completed] Working on: 'WEB-INF' ... --> DONE (128 ms)
[20111019165807] [ 84% completed] Working on: 'repository' ... --> DONE (374 ms)
[20111019165807] [ 85% completed] Working on: '/usr/sap/hdbstudio_update' ... --> DONE (462
ms)
[20111019165807] [ 86% completed] Working on: 'HDB Studio HTTP Publisher' ... --> DONE (15508
ms)
[20111019165807] [ 87% completed] Working on: 'trans' ... --> STARTED
[20111019165808] [ 87% completed] Working on: 'trans' ... --> DONE (182 ms)
[20111019165808] [ 88% completed] Working on: 'hdbclient' ... --> DONE (24037 ms)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 11
[20111019165808] [ 89% completed] Working on: 'tools' ... --> STARTED
[20111019165808] [ 90% completed] Working on: 'bin' ... --> STARTED
[20111019165808] [ 90% completed] Working on: 'SAPCAR' ... --> STARTED
[20111019165808] [ 91% completed] Working on: 'SAPCAR' ... --> DONE (175 ms)
[20111019165808] [ 92% completed] Working on: 'bin' ... --> DONE (371 ms)
[20111019165808] [ 93% completed] Working on: 'tools' ... --> DONE (549 ms)
[20111019165808] [ 93% completed] Working on: '/usr/sap' ... --> DONE (223948 ms)
[20111019165808] [ 94% completed] Working on: 'LM Structure Installer' ... --> STARTED
[20111019165808] [ 95% completed] Working on: 'LM_STRUCTURE_SOFTWARE' ... --> STARTED
[20111019165809] [ 96% completed] Working on: 'LM_STRUCTURE_SOFTWARE' ... --> DONE (876 ms)
[20111019165809] [ 96% completed] Working on: 'LM Structure Installer' ... --> DONE (877 ms)
[20111019165809] [ 97% completed] Working on: 'HANA Installation' ... --> DONE (230772 ms)
[20111019165809] [ 98% completed] Working on: 'Installation Host (localhost)' ... --> STARTED
[20111019165809] [ 99% completed] Working on: 'Linux' ... --> STARTED
[20111019165809] [ 99% completed] Working on: 'Linux' ... --> DONE (2 ms)
[20111019165809] [ 100% completed] Working on: 'HANAPlatformProduct' ... --> DONE (4 ms)
Installation of SAP HANA platform has completed successfully
Finished successfully.
lt5006:/data/software/HANA_SP03/DATA_UNITS/HANA_IM_LINUX__X86_64 #
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 12
1.1.8 Check the Time Zones on the HANA server After the Installation of the HANA database with/without the unified Installer it can happen that there are
time differences between the HANA box and the Application Server.
This Problem will occur in customer environments,
To solve the issue either change the time on the HANA box and restart the server before you start the
SAP Installation, otherwise you will have problems during the third Installation Step of sapinst when
creating the Central Instance
1.1.9 Check UUIID libraries on Linux based AppServers If you are using a 7.20 Kernel higher than 111 the update and usage of UUIID is mandatory. Please check
the correct function before you start the installation on Linux and Redhat based Application Servers
Note 1391070 - Linux UUID solutions
RHEL 5, RHEL 6, OL 5, and OL 6: In order to activate the UUID daemon you need to install the
uuidd RPM package. Additionally, it is required run the command 'chmod 6755 /usr/sbin/uuidd'
as root in order to activate the UUID daemon on-demand. (Alternatively, running the UUID
daemon permanently with 'service uuidd start', respective 'chkconfig uuidd on' is also possible.)
SLES 11 SP1: You simply need to install the sapconf RPM package (this is necessary for SAP
installations anyhow). The package sapconf incorporates the dependencies to uuid-runtime and
performs the README.SUSE.uuidd instructions above automatically. The sapconf package is
already installed if you install SLES 11 SP1 as described in note 1310037.
SLES 11 SP2: With SLES 11 SP2 no further uuidd activation is needed. The sapconf is not needed
for uuidd purposes, but still recommended for something different (refer note 1310037).
Additional hints:
Note 1054467 - Local host name refers to loopback address
Check for the correct format of the file /etc/hosts
Check for duplicated entries in the file /etc/services
http://www.sdn.sap.com/irj/sdn/edw-ops?rid=/library/uuid/5005c6c3-364b-2b10-fea9-
c476d0885458
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 13
1.2 Starting the Import of the homogeneous System export of the CIA system
This assumes that the heterogeneous Export is already available. This process is described in the
following Document: https://community.wdf.sap.corp/sbs/docs/DOC-94307 =>
The reading BW on HANA 1.0 e2e Guide http://help.sap.com/nw73bwhana#section2 is mandatory.
Note 1617021 - Inst. SAP NetWeaver 7.3: Windows / SAP HANA Database
Note 1617020 - Inst. SAP NetWeaver 7.3: UNIX / SAP HANA Database
If you are running a standard BW on HANA System Installation (either system import or fresh Installation)
you have to choose the distributed option in the sapinst. The three shown steps must be started
individually on after another, despite if it’s a fresh Installation or a system import from a copy.
If you are using a virtual hostname for you Application Server, you have to start the sapinst with the
option:
./sapinst SAPINST_USE_HOSTNAME=<virtual-servername> –nogui For all three offered steps of the distributed Installation.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 14
1.2.1 IM Master on the backend (Linux)
/data/software/BW730_SP05_04112011/BW730_IM_LINUX_X86_64_HDB
./sapinst –nogui
This option allows you to run the sapinstgui on your Fronted-PC without using the X-Windows
Implementation, or tools like VNC viewer are not available.
Of course you can use Putty (0.61) with the Xming Extension. For Details how to use it, visit the URL
http://www.straightrunning.com/XmingNotes/
Tip: don’t switch the user context when using Xming, this will also loses the DISPLAY variable.
1.2.2 SAPInst GUI on the Windows Frontend
D:\_install\ORANGE\BW730_SP05_04112011\NW730_IM_SAPINSTGUI_WIN_I386
sapinstgui.exe -host lt5006.wdf.sap.corp -port 21212
This is the option for the Installation of the created system export.
(See the Document SAP first Guidance - BW Systemexport V1.0.pdf)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 15
1.2.3 Default location of the SAPInst directory
/tmp/sapinst_instdir/NW73/HDB/COPY/HDB/SYSTEM/STD/AS-ABAP
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 16
1.2.4 FQDN must be provided
Please Note: a working FQDN is a pre-requisite for the NetWeaver 7.30 Installation (despite HANA or anyDB). Several System parameters are set during the Installation, to guarantee a working System. Ignoring the setting will lead into system inconsistencies.
If you cannot afford a FQDN for your Application Server, create a temporary entry in your /etc/hosts file on the HANA server, the Application server and the used Frontend- PC’s like
10.22.40.106 lt5006 lt5006.wdf.sap.corp
For the time being until the final FQDN name is available. Do not continue here without the flag set.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 17
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 18
The HANA database host is entered without the FQDN Name here, but must be available also for the HANA server as well.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 19
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 20
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 21
1.2.5 HANA client version for the HANA server Revision
For a newer client which fits to the HANA server Revision you can/must download the correspondending from the SWDC location.
Currently the client files are located on the HANA 1.0 DVD. You must have the medium available, even the HW partner installed the correct HANA version already in the factory. (SAP HANA PLATFORM EDIT. 1.0 - Number 51041779)
In the corresponding directory, e.g. /software/HANA_SP03_51041779/DATA_UNITS/HDB_CLIENT_LINUX_X86_64 you will find the file LABEL.ASC. Unpack the file IMDB_CLIENT100_23-10009663.SAR on the server. This will create a directory SAP_HANA_CLIENT. Place the file LABEL.ASC into this directory and choose the directory, when you will be asking for the RDBMS HANA client.
The other option is to replace the content of the directory /software/HANA_SP03_51041779/DATA_UNITS/HDB_CLIENT_LINUX_X86_64 with the content of the directory SAP_HANA_CLIENT and select the original source directory from the HANA 1.0 SP03 DVD
Location on the SAP Service Marketplace (SMP) http://service.sap.com/patches
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 22
1.2.6 Exchange R3load and LibDBSL before import starts Unfortunally the Versions of the files R3load and LibDBSL (<= PL112) are not meeting the requirements
for importing the load into HANA 1.0 Rev. 21 and higher. Please exchange the two files in the DIR_CT_RUN
directory, before the import starts. The files can be downloaded from Service Market Place, depending on
your Version of the SAP Application Server (see Example for Linux X86_64)
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/linuxx86_64
Location on the SAP Service Marketplace (SMP) http://service.sap.com/patches
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 23
With a fresh Installation you choose the Standard Export here
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 24
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 25
You might want to use the unsorted load order, see Note 954268
Please Note that improvements for Oracle or MS SQL not work for HDB. According to Note 936441, HANA DB is not supported for unsort option.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 26
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 27
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 28
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 29
Currently the HANA sapinst will not recognize, if a Diagnostic Agent is already installed. You will definitely be asked to install a Diagnostic Agent Instance.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 30
This is a manual step, which can be done at any time. The sapinst dialog can continue here.
Edit the file /usr/sap/hostctrl/exe/host_profile and add the line service/admin_users
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 31
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 32
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 33
Optional: if you encounter any Import Problems which are not critical, the quickest approach is to use the guidance of the following Note:
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 34
Note 885441 - Common Migration Errors
Error in file SAPAPPL1.TSK D BTCJSTAT I ign
I RSDANLREQ~002 C ign
Error in ZTZ_EIUSALES4__DTP.TSK ZTZ_EIUSALES4~P C ign
Nevertheless you should check the root cause of the problem.
This method is not intend to correct a large amount of table/indexes, therefore you have to check your export source, and if you missed some steps in preparation beforehand, the best approach is to restart the export process, rather than to spend too much time on solving some problems which can be prevented with a correct export source.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 35
1.2.7 Check invalid_objects.txt
Once the import Process is finished, you can check as stated in the SAPInst dialog the file invalid_objects.txt. You might see the same entries (the first ones) different entries or even an empty file
lt5006:/tmp/sapinst_instdir/NW73/HDB/COPY/HDB/SYSTEM/STD/AS-ABAP #
more invalid_objects.txt
checkObjects=
dbType=HDB
strDirs=/data/software/ORANGE4/ABAP/DATA
trace=all
tskDir=/tmp/sapinst_instdir/NW73/HDB/COPY/HDB/SYSTEM/STD/AS-ABAP
--------------------------
packages without TSK files
--------------------------
BALDAT
D010TAB
RSDSRUNTIMETRACE
…
_BIC_ATE11_SM100
_BIC_ATE11_SM300
_BIC_AXTE11_S300
_BIC_B0003603000
_BIC_B0003604000
_BIC_B0003613000
--------------------------
---------------------------------------------------
package object type action status
---------------------------------------------------
SAPAPPL1 BTCJSTAT table load ignore
SAPAPPL1 RSDANLREQ~002 index create ignore
SAPAPPL0_1 /BI0/XD_CUSTOMER table load ignore
---------------------------------------------------
lt5006:/tmp/sapinst_instdir/NW73/HDB/COPY/HDB/SYSTEM/STD/AS-ABAP #
With future Improvements of the SAPInst for HDB some of the above error will not occur anymore, the RU Version of the SAPInst stated from 3rd of November 2011 is the minimum sufficient Version for the anyDB export.
For the time being, it will create a file with at least the first entries, even they are processed successfully.
If an error occur about the file REPOSRC.TSK and the correspondending file REPOSRC.TSK.bck delete the *.bck file and choose retry in the sapinst dialog. See also Note 455195, if you have to merge *.bck files. /tmp/sapinst_instdir/NW73/INSTALL/SYSTEM/HDB/STD/AS/REPOSRC.TSK.bck
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 36
If under any circumstances there is no left space in the directories /sapmnt/<SID> or /usr/sap/<SID> during the kernel copy procedure, please make sure that the source kernel files in the directory DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/linuxx86_64 are identical with the files in /usr/sap/<SID>/DVEBMGS<nr>/exe and /usr/sap/<SID>/ASCS<nr>/exe and no files with length 0 are in the directories.
If any core dumps are written, please remove them as they can get up to 6GB big and with a small filesystem, it can prevent you from successful starting of the SAP instance.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 37
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 38
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 39
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 40
1.2.8 Setting the correct client DEFAULT.PFL and adapt the Instance Profile
To activate the correct client you have to restart the instance
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 41
1.2.9 Obsolete/wrong Parameters with NetWeaver 7.30 ABAP Note 1440880 - Parameter ms/standalone is obsolete
exe/saposcol = $(DIR_CT_RUN)/saposcol obsolete, replaced by Diagnostic Agent
check the Profiles for unnecessary JAVA parameter’s as well, e.g.
1.2.10 Import new License and check secure storage after migration
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 42
2. Apply the current SP stack (including corrections)
2.1 Apply the special SP06 stack for HANA based systems For Rampup customers which are in the process either to migrate from an existing anyDB to HANA or
with a fresh Installation to apply the Special SP06 which easies the migration Process. Furthermore it
includes the manual steps from certain Notes after SP05. You might have a look to Note 1640741, as
these steps cannot be included into a SAP Note.
Remark: Make sure that
Note 1632495 - Method GET_TABLES does not return any table names are applied BEFORE importing
SP06!
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 43
See the latest Corrections after SP06 on the following Wiki Page http://ims-bw:8080/wiki/index.php/Orange_notes
Additional Notes around patches and SP06 to consider:
• Note 1600929 - SAP BW powered by SAP inMemory DB – Information
• Note 1600066 - Available DBSL patches for NewDB
• Note 1639744 - heterogeneous systemcopy NetWeaver 7.30 to HANA target DB
• Note 1657994 - SAP BW 7.30 powered by HANA - Special SP06
Please find the passwords for the ABAP packages below:
• SAP_BASIS SAPKB73006 Password: 55ED27A285
• SAP_ABA SAPKA73006 Password: 55ED27A286
• PI_BASIS SAPK-73006INPIBASIS Password: 5DF03EB888
• SAP_BW SAPKW73006 Password: 55ED27A290
• Note 1662588 - Download: ABAP only SP06 for SAP BW powered by HANA DB
Note 1662588 - Download: ABAP only SP06 for SAP BW powered by HANA DB check the Note for the Passwords in transaction SPAM
HANA 1.0 Version: the usage of Rev.23 or higher is suggested together with BW 7.30 SP06 (only enabled for HANA)
This is an Example of a current BW on HANA System, based on HANA 1.0 Rev.24 and SP06 plus corrections
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 44
2.1.1 Apply corrections after SP06 for HANA based systems
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 45
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 46
See also the additional Notes which can be helpful with the Transaction SNOTE
Note 1627683 - SCWB/SNOTE/SPAU: Changed development package SP07 for 7.30
Note 1564508 - /SDF/RSORADLD_NEW: No statements during autom. download SP05 for ST-PI
Note 1557768 - Note Assistant: find the notes that modify an object Checkprogram
As reference from SP05 to SP06 this correction synchronizes any inconsistent deltas
Note 1649814 - Post corrections for BICS 7.30 SP5 and 7.31 SP1
You can always create a current list of correction when you use the following Keywords in the Note
Search http://service.sap.com/notes
For corrections after SP06 for BW 7.30 on HANA: SAPKW73007 HANA
You can download the target list as HTML and copy the column with the Note Number into a *.txt file
Such a file can be uploaded to the transaction SNOTE
And specify the created *.txt file. So all of the Notes will be read to the transaction at once.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 47
2.1.2 Manual Processing of some SAP Notes
Note 1649837 - Long runtime for queries with hierarchies
You may have to check additional Notes for the depended Notes. This might also affecting other Notes
Note 1673420 - X/Y Tabellen haben auf der Datenbank keinen Primary Key
Run the Report RSDRX_REPAIR_XYTAB_ON_HANA after you applied the Note to ensure that X/Y Tables are correct
Note 1631860 - Short Dump in FM 'SDOK_M_ENT_PROPS_SET'
(necessary for correct CTS on ORANGE before SP07 for 7.30)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 48
Note 1669250 - DBDIFF Einträge für HANA DB optimierte Changelog Tabellen
Make sure this Note is applied before RS_BW_POST_MIGRATION runs; otherwise the report SAP_UPDATE_DBDIFF deletes entries in table DBDIFF.
You can also check the consistency with transaction DB02
Note 1640741 - Different database user for DBA Cockpit for SAP HANA
We recommend activating the behavior from Support Package 6 already in Support Package 5, that is, to operate the DBA Cockpit with the dedicated database user DBACOCKPIT<SID>. To do this, the following action is required: Create a DBCON entry for the database user DBACOCKPIT<SID>. To do this, on the initial screen of transaction DBACOCKPIT, first choose the function "DB Connections" and then the "Add" icon. Here, make the following entries: Connection name: Enter the <SID> of the SAP system. Database System: SAP HANA database User name: DBACOCKPIT<SID> Password: Enter the password of DBACOCKPIT<SID> twice. Database Host: Enter the host on which the database is installed. SQL Port: 3xx15, where xx stands for the SAP HANA instance ID
With SP06 and onwards the correct setting should be created. If not, you can delete the automatic created entry in table DB6NAVSYST for the ABAP <SID> and remove the entry in transaction DBCO for the same <SID> before you reenter the transaction DBACOCKPIT again.
Please note that the entry for the DB host is created without any FQDN due to the fact that the hostname is generated directly from the SAP kernel.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 49
2.2 Apply SP07 for all BW 7.30 Systems Since the availability of SP07 you should apply this mayor Support Package Stack as soon as possible. Consider to use this SP also for Upgrade Projects as the next SP will not be released within the next six month.
Please Note that the latest available Version of HANA 1.0 (Rev. 26) is mandatory to be applied as well, as the import of support packages, Add-On’s, etc. can take longer on HANA based systems due to the location of tables still in the row store.
Applying SP’s takes a long time. This is owing to DOKIL table. It has been created as column store table, not row store. So, we needed to suspend applying SP, and converted it to row store. After that, import has been accelerated. Notes 1600929 which refer’s to the guidance in Notes 1660125 and 1660125.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 50
2.2.1 Apply corrections after SP07 for HANA based systems You can always create a current list of correction when you use the following Keywords in the Note
Search http://service.sap.com/notes
For corrections after SP07 for BW 7.30 on HANA: SAPKW73008 HANA
Note 1712334 - Important Notes for SAP BW powered by HANA on SP7
To upload a list of Note you can follow the procedure described in Chapter 2.1.1
In any case the complete list (a dynamic list depending on the issues) cannot be processed, the
corrections with high priority are mandatory.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 51
2.3 Apply the Business Content 7.36 (BI_CONT, BI_CONT_XT) Check the Note and download the SP as well. Please Note you will need BC and BC_XT
Note 1578396 - Installation or upgrade of BI_CONT / BI_CONT_XT 736/746
Installation Passwords:
Package: SAPK-736AHINBICONT Password: 142F674347
Package: SAPK-736AGINBICONTXT Password: 142F673B3C
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 52
2.4 Run transaction SGEN Currently transaction SGEN takes quite a while when selecting entries from table TADIR.
As a workaround you can select all components which skip the TADIR selection. Then the SGEN generation will start immeditially. A general Solution is available with HANA 1.0 Rev. 26
2.5 First run of BW technical content Check the InfoObject 0LANGU when you have a fresh Install of BW 7.30 SP05 and higher (despite of HANA). You have to activate the InfoObject prior to the activation of the technical content, especially you import Objects from other BW Releases/Systems (check with RSD5 and see Note 1387166). See also the following Notes for corrections/explanations:
Note 984021 - Changes to InfoObject 0LANGU
Note 1608322 - Technical Content Activation - Operational BI systems
Note 1597959 - Errors when activating time characteristics of Tech. Content
Note 1387166 - Master Data Read Class (actually a post activity after the Upgrade to NetWeaver 7.x)
The InfoObjects 0BCTCOMP, 0CALDAY (referring to 0DATE) needs special attention:
The problem is related to the fact, that InfoObject 0BCTCOMP references table RSOCOMPT as the text
table instead of an own generated text table. As the activation process now tries to create an attribute
view using field TXTSH, which is not in table RSOCOMPT, the process aborted. When you change table
RSOCOMPT by adding the field TXTSH and reactivated the InfoObject, then the activation process will be
successful.
The normal way to solve the problem would be to define a read class for the master data in RSD1.
However since there is no delivery version for this object and it has a long text field named TEXTLG in its
text table RSOCOMPT, the value help index activation problem may be solved here by modifying the
object definition in RSD1 to support only long texts.
To do this just deactivate the check box "Medium text exists" and activate the check box "Long text
exists" instead. Some of the mentioned Issues are collected in the following Note:
Note 1695112 - Activities in BW after migrating to the SAP HANA database
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 53
2.5.1 Check InfoObject 0IOBJNM Before you start any Transaction for the start of Business Content Installation (also true before starting
transaction RSA1 which triggers the Technical Content Installation) in new installed systems you must
take of the InfoObject 0IOBJNM first.
So go to transaction SNRO (Number Range Object Maintenance) and look for BIM9999991. Change the
NR Status from 0 to 2 and save the changes.
Details are described in Notes 586648 and 1331403 and in the following Note:
1637935 - Short Dump RAISE_EXCEPTION RSO_CONTENT_INSTALL_BATCH X_MESSAGE
After this the following transactions can be called to activate the necessary Business Content:
RS_PERS_ACTIVATE Activating Personalization in BEx
RSTCT_INST_BIAC Report RSTCT_ACTIVATEADMINCOCKPIT_NEW
RSTCO_ADMIN Installation SAP BW technical content
Note 1543092 - Upgrade of BP_BIADMIN 1.0 to BP_BIADMIN 3.0(BP BW ADMINISTRATION)
This additional Note contains a template for design rules required to create a user-defined expert routine, which can be useful for the BW on HANA use case:
Note 1227667 - Guidelines for expert routine: Design rules
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 54
3. Modifying the SAP Profiles (restart SAP)
3.1 SAP Profile - DEFAULT.PFL
SAPDBHOST = lt5006
SAPSYSTEMNAME = CIA
SAPGLOBALHOST = lt5006
SAPLOCALHOST = lt5006
SAPFQDN = wdf.sap.corp
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
system/type = ABAP
rdisp/mshost = lt5006
rdisp/msserv = sapmsCIA
rdisp/msserv_internal = 3903
ms/redirect_version = 1
ms/urlmap_secure = 1
ms/urlprefix_secure = 1
enque/process_location = REMOTESA
enque/serverhost = lt5006
enque/serverinst = 03
gw/acl_mode = 1
icf/user_recheck = 1
icm/HTTP/ASJava/disable_url_session_tracking = TRUE
is/HTTP/show_detailed_errors = FALSE
korr_protected = 00206583830421493132
login/system_client = 003
login/password_downwards_compatibility = 4
login/no_automatic_user_sapstar = 0
rdisp/TRACE = 1
service/protectedwebmethods = SDEFAULT
ssf/name = SAPSECULIB
3.2 SAP Profile - CIA_ASCS03_lt5006
SAPSYSTEMNAME = CIA
SAPSYSTEM = 03
INSTANCE_NAME = ASCS03
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/linuxx86_64
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/CIA_ASCS03_lt5006
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_CT_RUN)/scs.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 55
_CPARG1 = list:$(DIR_CT_RUN)/sapcrypto.lst
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1)
#-----------------------------------------------------------------------
# Start SAP message server
#-----------------------------------------------------------------------
_MS = ms.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_MS)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)
Restart_Program_00 = local $(_MS) pf=$(_PF)
#-----------------------------------------------------------------------
# Start SAP enqueue server
#-----------------------------------------------------------------------
_EN = en.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_04 = local rm -f $(_EN)
Execute_05 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN)
Restart_Program_01 = local $(_EN) pf=$(_PF)
#-----------------------------------------------------------------------
# SAP Enqueue Server
#-----------------------------------------------------------------------
enque/table_size = 64000
enque/snapshot_pck_ids = 1600
enque/server/max_query_requests = 5000
enque/server/max_requests = 5000
enque/async_req_max = 5000
enque/encni/threadcount = 4
rdisp/enqname = $(rdisp/myname)
SETENV_05 = SECUDIR=$(DIR_INSTANCE)/sec
ssl/ssl_lib = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)
sec/libsapsecu = $(ssl/ssl_lib)
ssf/ssfapi_lib = $(ssl/ssl_lib)
3.3 SAP Profile - CIA_DVEBMGS02_lt5006
SAPSYSTEMNAME = CIA
SAPSYSTEM = 02
INSTANCE_NAME = DVEBMGS02
DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/linuxx86_64
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/CIA_DVEBMGS02_lt5006
SETENV_00 = DIR_LIBRARY=$(DIR_LIBRARY)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_02 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_03 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF)
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF)
_CPARG0 = list:$(DIR_CT_RUN)/sapcrypto.lst
Execute_02 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 56
SAPJVM_VERSION = 6.1.032
DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6
jstartup/vm/home = $(DIR_SAPJVM)
#-----------------------------------------------------------------------
# Start ABAP database
#-----------------------------------------------------------------------
_DB = db.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_03 = immediate rm -f $(_DB)
Execute_04 = immediate ln -s -f $(DIR_CT_RUN)/startdb $(_DB)
Start_Program_00 = immediate $(_DB)
exe/icmbnd = $(DIR_CT_RUN)/icmbnd
rdisp/wp_no_btc = 32
rdisp/wp_no_dia = 64
#-----------------------------------------------------------------------
# Start SCSA administration
#-----------------------------------------------------------------------
Execute_05 = local $(DIR_EXECUTABLE)/sapmscsa pf=$(_PF) -n
#-----------------------------------------------------------------------
# Start application server
#-----------------------------------------------------------------------
_DW = dw.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_06 = local rm -f $(_DW)
Execute_07 = local ln -s -f $(DIR_EXECUTABLE)/disp+work$(FT_EXE) $(_DW)
Start_Program_01 = local $(_DW) pf=$(_PF)
#-----------------------------------------------------------------------
# Start internet graphics server
#-----------------------------------------------------------------------
_IG = ig.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_08 = local rm -f $(_IG)
Execute_09 = local ln -s -f $(DIR_EXECUTABLE)/igswd_mt $(_IG)
Start_Program_02 = local $(_IG) -mode=profile pf=$(_PF)
rdisp/wp_no_spo = 1
rdisp/wp_no_vb = 2
rdisp/wp_no_vb2 = 1
rdisp/max_wprun_time = 3600
# http://trexweb.wdf.sap.corp:1080/wiki/index.php/AppServer_profile_parameter
# rsdb/dbid = HDB
# dbs/hdb/sqlopt = -X SQL,PACKET
dbs/hdb/cmd_buffersize = 1048576
# dbs/hdb/dbsl_profile = 0
dbs/hdb/max_array = 100000
rsdb/max_blocking_factor = 50
rsdb/min_blocking_factor = 0
rsdb/max_in_blocking_factor = 1024
rsdb/min_in_blocking_factor = 0
ipc/shm_psize_10 = 220000000
ipc/shm_psize_40 = 508000000
abap/buffersize = 4000000
abap/heap_area_dia = 5726623060
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 57
abap/heap_area_nondia = 5726623060
abap/heap_area_total = 5726623060
abap/heaplimit = 40000000
abap/package_check = off
abap/pxa = develop
abap/shared_objects_size_MB = 200
em/blocksize_KB = 4096
em/global_area_MB = 2048
em/initial_size_MB = 32768
em/max_size_MB = 32768
# em/lock_method = sema
# em/use_sema_lock = TRUE
es/implementation = std
gw/max_conn = 4096
gw/max_conn_per_wp = 128
gw/max_sys = 4096
gw/max_wp = 4096
gw/stat = 1
rdisp/PG_MAXFS = 262144
rdisp/PG_SHM = 262144
rdisp/ROLL_MAXFS = 262144
rdisp/ROLL_SHM = 262144
rsdb/esm/buffersize_kb = 524288
rsdb/esm/large_object_size = 67108864
rsdb/esm/max_objects = 20000
rsdb/ntab/entrycount = 200000
rsdb/ntab/ftabsize = 160000
rsdb/ntab/irbdsize = 32000
rsdb/ntab/sntabsize = 40000
rsdb/obj/buffersize = 262144
rsdb/obj/large_obj_size = 32768
rsdb/obj/max_objects = 40000
rsdb/cua/buffersize = 15000
rtbb/buffer_length = 296608
rtbb/max_tables = 2000
sap/bufdir_entries = 20000
zcsa/db_max_buftab = 100000
zcsa/table_buffer_area = 350000000
ztta/max_memreq_MB = 4096
ztta/parameter_area = 64000
zcsa/installed_languages = DEFINK
zcsa/presentation_buffer_area = 78000000
zcsa/sync_reload = 5
zcsa/system_language = E
ztta/roll_area = 4194304
ztta/roll_extension = 3221225472
ztta/roll_extension_dia = 3221225472
ztta/roll_extension_nondia = 3221225472
ztta/roll_first = 1
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 58
#- ICM parameter (global part) ------------------------------------------
rdisp/start_icman = true
vmcj/enable = off
icm/min_threads = 24
icm/max_threads = 60
icm/max_conn = 2048
icm/max_sockets = 4096
icm/keep_alive_timeout = 120
icm/conn_timeout = 50000
icm/max_timeout_net = 20000
icm/min_timeout_mpi = 50000
icm/HTTP/logging_0 = PREFIX=/, LOGFILE=http_server_log, LOGFORMAT=%t %H %a -
%r %s %b %{Content-Length}i %L, MAXSIZEKB=102400, FILEWRAP=on
icm/HTTP/logging_client_0 = PREFIX=/, LOGFILE=http_client_log, LOGFORMAT=%t %H %a -
%r %s %b %{Content-Length}i %L, MAXSIZEKB=102400, FILEWRAP=on
icm/server_port_0 = PROT=HTTP , PORT=80$(SAPSYSTEM), PROCTIMEOUT=120, TIMEOUT=2000
icm/server_port_1 = PROT=HTTPS, PORT=81$(SAPSYSTEM), PROCTIMEOUT=120, TIMEOUT=2000
icm/server_port_2 = PROT=SMTP , PORT=25$(SAPSYSTEM), PROCTIMEOUT=120, TIMEOUT=2000
icm/HTTP/server_cache_0 = PREFIX=/, CACHEDIR=$(DIR_DATA)/cache
icm/HTTP/server_cache_0/size_MB = 100
icm/HTTP/max_request_size_KB = -1
icm/host_name_full = $(SAPGLOBALHOST).$(SAPFQDN)
is/SMTP/virt_host_0 = *:25$(SAPSYSTEM)
mpi/total_size_MB = 512
mpi/buffer_size = 32768
mpi/max_pipes = 4000
ms/redirect_version = 1
ms/urlmap_secure = 1
ms/urlprefix_secure = 1
ms/server_port_0 = PROT=HTTP,PORT=82$(SAPSYSTEM)
ms/server_port_1 = PROT=HTTPS,PORT=83$(SAPSYSTEM)
wdisp/HTTP/min_pooled_con = 128
wdisp/HTTP/max_pooled_con = 256
login/accept_sso2_ticket = 1
login/create_sso2_ticket = 2
SETENV_05 = SECUDIR=$(DIR_INSTANCE)/sec
ssl/ssl_lib = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)
sec/libsapsecu = $(ssl/ssl_lib)
ssf/ssfapi_lib = $(ssl/ssl_lib)
ssf/name = SAPSECULIB
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 59
3.4 Copy the Tickets from DVEBMGS02/sec to ASCS03/sec
As with NetWeaver 7.30 a fresh Installation needs the SAPCryptoLib mandatory. Currently the new enqueue server Instance together with the ICM Instance doesn’t contain the necessary tickets for the SSO/SSF initialization. Simply copy the tickets from DVEBMGS02/sec to ASCS03/sec before restart.
unalias cp
3.5 Check the HDB/ABAP settings for SP03 and SP05
3.5.1 Check /update the HDB ABAP settings
# http://trexweb.wdf.sap.corp:1080/wiki/index.php/AppServer_profile_parameter
rsdb/dbid = HDB
#dbs/hdb/sqlopt = -X SQL,PACKET
dbs/hdb/cmd_buffersize = 1048576
# dbs/hdb/dbsl_profile = 0
dbs/hdb/max_array = 100000
rsdb/max_blocking_factor = 50
rsdb/min_blocking_factor = 0
rsdb/max_in_blocking_factor = 1024
rsdb/min_in_blocking_factor = 0
3.5.2 Check the HDB settings for SP03
Check/change the settings either from transaction DBACOCKPIT or from the HANA studio
Note 1645183 - Changing log mode for SAP HANA DB after SPS2 to SPS3 upgrade
Note 1654455 - Upgrade News and Tips Hana Modeler from SP3 (Revision 20) onwards
With HANA you are forced to change the SAP<SID> (DBACOCKPIT<SID>) password regularly. If you
want to skip this feature, change this behavior by executing the following statement in the HANA studio
for the affected SAP Schema user:
'alter user SAP<SID> disable password lifetime;'
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 60
Configuration Changes Needed
Within SAP HANA Studio, open the Administration view of your system, navigate to the Configuration tab, and use the Filter field to search for occurrences of each parameter:
1. Adjust runlevel for services:
daemon.ini indexserver[] runlevel = “3”
daemon.ini indexserver.c[] runlevel = “3”
daemon.ini statisticsserver[] runlevel = “3”
daemon.ini scriptserver[] runlevel = “3” daemon.ini xsengine[] runlevel = “3”
2. Set log mode to normal:
global.ini persistence[] log_mode = “normal”
3. Enable backup of logs:
global.ini persistence[] enable_auto_log_backup=”yes”
4. Set log backup timeout to a value > 0 (e. g. 900 seconds):
global.ini persistence[] log_backup_timeout_s=”900”
5. OPTIONAL: Change the paths where data and log backups are saved to a separate location with enough disk space:
global.ini persistence[] basepath_databackup = <file system path> global.ini persistence[] basepath_logbackup = <file system path>
6. Restart your database! 7. Create a full data backup of your database!
Tip: you can also use the attached SQL file to change the parameters. Within SAP HANA Studio, open a SQL Editor for your system, paste the file content, change the data backup and log backup paths to your desired location, and hit F8.
Additional Notes and Explanations
A value of 900 for the log backup timeout ensures that in the event of a disaster (e.g. a hard disk failure), you will lose no more than 15 minutes of data.
When switching to log mode “normal”, log backups will be created on a continuous basis. This will require a steadily increasing amount of disk space that will eventually lead to a full disk if not handled properly. For this reason, we recommend that you change the paths where log and data backups are located to a separate storage medium with sufficient disk space. In addition to avoiding space issues, using a separate storage medium also leads to improved safety in case of disk failures and better performance.
To ensure that you can recover your database to the most recent point in time without needing to replay a large number of log backups, you should perform data backups at regular intervals.
Do not delete log backups unless you are absolutely sure that you no longer need them. Deleting log backups may make it impossible to do a recovery (this depends on where you want to recover to).
Do not rely on you most recent data backups only.
Archiving of log backups should be part of your overall backup and recovery strategy.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 61
3.5.3 HANA 1.0 Rev. 21: Check Privileges TREXVIADBSL
3.5.4 HANA 1.0 Rev. 22: unwanted big statistic data With Revision 22 the behavior of collecting information is fixed in the way the tables don't become too big.
Furthermore old data will be deleted automatically.
If you face this kind of crashes you should clean up the statisticsserver data manually by executing the
SQL statements below directly after the statisticsserver startup:
Note 1676348 - SAP HANA db: Statisticsserver runs out of memory
3.5.5 HANA 1.0 Rev. 23: Check Syntax Changes Note 1675260 - "invalidated view" error for monitoring views
Solution: Execute the following SQL statement as user SYSTEM:
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') SET ('metadata',
'force_auto_migration') = 'off'
Restart and change parameter back to 'off'. The Issue is fixed with Rev. 24
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 62
3.5.6 HANA 1.0 Rev. 24: Temporary Switch join_red_parall After updating the HANA database to Rev. 24 you must temporary consider the following Note:
Note 1681865 - SAP HANA DB (Rev24): Incorrect results in column table joins
Use the HANA studio and add the following parameter to the section joins in the indexserver.ini
The indexserver has to be reconfigured or restarted after saving new changes in indexserver.ini.
Reconfiguration in HDB Studio:
The error will be fixed with Revision 25. After implementing Revision 25 the parameter changes should be
reverted in order to take advantage of following performance improvements.
3.5.7 HANA 1.0 Rev. 25: several temporary switches Note 1686312 - SP08: Probl. paketierte Extraktion InfoCube / MultiProvider
Add the following Parameter with the program SAP_RSADMIN_MAINTAIN into table RSADMIN
The problem will be fixed with Revision 26 for Non In-Memory Cubes; with Rev. 25 it is already fine for In-
Memory optimized cubes.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 63
Note 1688029 - Possible deadlock during data load or merge in Rev24/25 Reconfi gura tio n in HDB Stu dio:
Go to Administration -> tab Configuration -> attributes.ini -> change index_create_threads = 0.
The error will be fixed with Revision 26. After implementing Revision 26 the parameter changes should be
reverted in order to take advantage of performance improvements.
Note 1687660 - HANADB: Full DataStore conversion only as of revision 26
Inconsistent data may have been created exclusively in the change log during the conversion in older
revisions. The active data is not affected by this error. Potentially affected DataStores can be identified as
follows:
Call transaction SE16 and select the table RSDRI_HDB_CNVDSO
Select the content and restrict the field CONV_MODE to "2§.
As a result, you receive all DataStore objects that were fully converted as well as their time of conversion
time stamp format.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 64
3.5.8 HANA 1.0 Rev. 26: new version, several settings A short recap:
Update DB/Client for HANA install/update
http://help.sap.com/hana_appliance#section2
Rev. 26 Hinweis: Please refer to SAP Note 1692981:
https://service.sap.com/sap/support/notes/1692981
All components must be patched: DB, Client and Studio
The processing order would be first the DB, and before the system is accessed via NetWeaver then the
HANA Client libraries. Finally, if the system is monitored through the HANA Studio, this component has to
be updated as well.
Please Note there is a known bug with the Rev. 26 of the Studio (all Versions). You have to uninstall the
old Version(s) and to a fresh install.
Furthermore the usage of the SAP Kernel/LibDBSL PL211 and higher is mandatory, otherwise the
transaction DBACOCKPIT will crash.
If you used any of the temporary settings from the previous Revisions or switches in the table RSADMIN
please make sure that they are resetted after the import of Rev. 26
More Notes to consider:
1703417 - SAP HANA database Revision 26: New version available
1702673 - SAP HANA DB (Rev26): Upgrade failed - Statistic Server
1701909 - SAP HANA DB (Rev26): Data compression setting before upgrade
1701216 - SAP HANA DB (Rev26): Shrink Data Volume does not work
1700651 - SAP HANA DB: history table not be retrieved for partioning
1694574 - Revision 26 Enhancements for Planning Functions
1691126 - SAP HANA Modeler - revision 26 - variables and parameters
1690552 - HANA DB:Fix for getting current user from a stored procedure
The full conversion of DSO objects into In-Memory is now possible
Note 1687660 - HANADB: Full DataStore conversion only as of revision 26
3.5.9 HANA 1.0 Rev. 27: special hotfix release Note 1711643 - SAP HANA appliance: Revision 27 of SAP HANA database
Please note! This is an unplanned revision regarding one specific hotfix (see details below). The following
Revision 28 will include this hotfix and all other fixes which were originally planned for Revision 27.
There is no need to upgrade to this hotfix Revision 27 unless you are facing the crashdump mentioned
below. (see full details in the mentioned Note)
----> Symbolic stack backtrace <----
0: AttributeEngine::Parallel::MultiValueExpander::preparePostAggExpansion() +
1: AttributeEngine::Parallel::ComputeKeysJobMVExpansion::run() + 0x27
TRexUtils::Parallel::Context::runJob(Container::SafePointerHolder< TRexUtils::Parallel::JobBase>&,
Execution::CPUTimeMeasurement&) + 0x64
3: TRexUtils::Parallel::Dispatcher::runJob(Container::SafePointerHolder<
TRexUtils::Parallel::JobBase>&,
Execution::CPUTimeMeasurement&) + 0x1a
4: TRexUtils::Parallel::WorkerThread::run(void*) + 0x210
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 65
Current settings in HANA 1.0 Rev. 25 for BW on HANA (ORANGE):
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 66
4. Further tasks in the target system
Depending on the scenario further follow up tasks are necessary now:
- Systemcopy post activities, if the <SID> has changed
- Processing of the connected source systems
- NetWeaver 7.30 BW – TQM
- Migration of DSO/InfoCubes after system migration
- tbd.
4.1.1 Check transaction SECSTORE after systemcopy After a systemcopy when either the server or the SID has changed the secure store of the ABAP server
has to be converted. This can be done with transaction SECSTORE.
The Procedure is explained in Note 816861 - Migrating entries in the secure storage
For further problem with the secure store you can also refer to the following Notes:
Note 1584228 - Internal error in secure store/Semaphore run out on a system
Note 502422 - Long texts for error messages SECSTORE021 to SECSTORE031
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 67
4.1.2 Reset the Logon Groups
4.1.3 Check settings in Report RSCPINST
4.1.4 Check myself Connection after System migration Especially after the Systemmigration the fields Target and Gateway Host might contain still the old server
details. This would prevent the DSO conversion in general.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 68
4.1.5 Check DSO activation Parameters Transaction RSCUSTV6
These are the suggested settings for the default data transfer. You might different values after a systemcopy or a fresh installation.
Especially the Value “Partition size” is moreless an “on/off Button” for the partitioning of the PSA tables that means a value below 1.000.000 is not suitable and a value higher than 1.000.000 is not applicable.
A higher value in the field the “FrequencyStatus-IDOC” will show less updates in the Monitor, a lower value will show a shorter frequency in the Monitor update.
Note 1646723 - BW on SAP HANA DB: IMO DSO Activation Parameters
Transaction SM30 V_RSODSOIMOSET
MCR stands for MemoryConsumptionReduced
The checkbox "Prevent MCR during Act." determines whether a procedure with reduced memory consumption is used for the activation. (MCR stands for MemoryConsumptionReduced.) This method significantly reduces the memory that is required by the activation but runs a little slower than the activation without this flag. In most cases it is recommended to use the MCR method. Only if you plan to activate small amounts of data and you are willing to invest more memory in order to gain maximum speed it makes sense not to use MCR activation. For large activations (>= 10 mio records) you should always use MCR. MCR package size is the package size used for the MCR activation. This parameter is ignored if MCR is not used. A larger package size causes higher memory consumption and a slightly lower runtime. The default value is 0 which means that the DataStore implementation determines the value by itself. Currently the package size used in this case is fixed: 100000. Enter a smaller value if you want to further reduce memory consumption. A value lower than about 20000 is not recommended because it causes too much overhead.
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 69
The last parameter determines the number of packages that are processed in parallel. It is used for both methods of activation. A higher value causes more parallel threads to be used for the activation. This implies a higher consumption of memory and CPU resources but speeds up the activation due to higher parallelization. The default value 0 means that the DataStore implementation determines the value by itself. Currently it uses num_cores/8 for the MCR activation and num_cores/4 for the non MCR activation. Num_cores is the number of cores that is supposed to be used by the HANA database. By default it is the number of cores the machine has. The upper limit for the number of packages processed in parallel is num_cores/3. If the value entered is higher than num_cores/3 num_cores/3 will be used.
4.1.6 Run the Post Steps after the Systemcopy With the GA of BW on HANA (expected end of May 2012) there will be a new tool available, to ease the Pre
and Post Steps of a BW systemcopy (initial systemcopy form Note 886102) called post copy automation
(PCA) with tasks lists for the specific steps for Export and Import.
See the overall Document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0b9ce6c-64d2-2e10-3b9f-
d6b2fdb281f3
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 70
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 71
4.2 Check the settings for TMS after Systemcopy
4.2.1 Check SE06
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 72
4.2.2 Check SE80 – Package
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 73
4.3 Check further BW Basis Settings Check with the SDN Page http://www.sdn.sap.com/irj/sdn/edw-ops#section18 for additional BW Basis
Settings which are not changed since 7.0x
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 74
4.4 Additional Tips for a fresh NetWeaver 7.30 Installation
With a fresh installation of any new NetWeaver System based on NetWeaver 7.02 or higher, the following
Notes must be applied to avoid errors with the SLT Replication which are NOTE related to the SLT
Product.
If you are not logon in EN, you get an error like this: "Kein Verbuchungs-Server für Kontext :D:
gefunden"
This is due the default UC Installation now, follow
Note 1037947 - Logon language is not yet activated
After installation and the creation of the first user run the RSADRCK2 for fixing the initial Address
Problem, in every client, e.g. 000, 001, etc.
Increase the upper value of the spool number range to 999,999 to make a spool overflow less likely.
See note 48284 for more details. This is a general recommendation by SAP.
Configure the SSO/SSF scenario for HTTPS for the correct logon procedure to the SLT Web Dynpro,
see the following SDN document:
http://www.sdn.sap.com/irj/sdn/edw-ops?rid=/library/uuid/70bd59d6-3a4b-2b10-bfab-
d0c3bd8abf15
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 75
The Transaction SNOTE for implementing ABAP corrections must be configured first. Therefore go to Transaction OSS1
and Choose in the Menu Parameter Technical settings and click on Change.
Now choose your location and press save.
With that the RFC connection OSS is automatically filled with user/password and Transaction SNOTE can connect to
the OSS/SMP to download ABAP notes.
Note 1484091 - CCMS Monitoring does not work
Transaction RZ21
SAP First Guidance - System migration/Fresh Install – BW on HANA
May 2012 76
4.5 How to connect HANA to CSN (SAP access)
This is an overview of the Note which describes the different possibilities to connect HANA to the SAP
Support System for various purposes.
Note 1635304 - Central note for HANA support connections Note 1634848 - SAP HANA database service connections (collective note)
Note 1058533 - TREX/BIA/HANA service connection to customer systems Note 1592925 - SAP HANA Studio service connection
Note 1610702 - HANA Support processed and procedures Note 1067044 - How to use the TREX/BIA connection
Note 1651638 - How to establish WTS remote support connections - Data Services Note 605795 - Windows Terminal Server connection in remote support
Note 35010 - Service connections: Composite note (overview)
www.sap.com/contactsap
www.sdn.sap.com/irj/sdn/edw-ops