SAP HANA Studio

Home


1.  HANA Studio?

The SAP HANA Studio is both the central development environment and the main administration tool for SAP HANA.


2. Execute individual SQL statements with SAP HANA Studio?

You can execute individual SQL statements (e.g. taken from the SQL statement collection in SAP Note 1969700) using the SQL console of SAP HANA Studio.

It is possible to open multiple SQL consoles and run several SQL statements in parallel.


3. To stop an individual SQL statement started with SAP HANA Studio?

If you have started to execute a SQL statement with SAP HANA Studio and problems arise (e.g. high memory consumption), you can terminate this statement via the "Cancel operation" button in the Progress View (Windows -> Show View -> Progress).


4. How to SQL statements in the SQL editor be formatted automatically?

You can optimize the formatting of SQL statements using the keyboard combination CTRL - SHIFT - O, e.g.:

Original statement:

sqlOriginal.JPG

Formatted statement:

sqlFormatted.JPG


5. SAP HANA Studio delivered with version number 2.x as of SPS 09?

As of SAP HANA SPS 09 SAP HANA Studio is delivered with version number 2.x while the SAP HANA software still has version number 1.x. This change is caused by the intension of SAP to decouple the versions of SAP HANA Studio and the SAP HANA database. It doesn't impact the compatibility, so you can use SAP HANA Studio version 2.x in combination with SAP HANA databases 1.x.


6. How to resolve problems displaying the load graph?

The load graph ("Administration" -> "Performance" -> "Load") is a useful tool to check for historic database figures like CPU consumption, memory consumption or SQL throughput, but there can be situations where it's not working properly or the performance is slow. In this case you can access the underlying information differently (e.g. via DBACOCKPIT or SQL) or adjust the memory limit for SAP HANA Studio. See SAP Note 2222110 ("What can I do if displaying the SAP HANA Studio load graph doesn't work?") for more information.


7. What can we do if other memory-intensive activities in SAP HANA Studio don't work?

If other activities in SAP HANA Studio with a high memory requirement like a large PlanViz evaluation fail, the adjustment of the SAP HANA Studio memory configuration as described in SAP Note 2159510 can help.


8. What can we do if opening the overview tab in the administration console takes a long time?

Opening the overview tab in the administration console often suffers from a high amount of SAP HANA alerts. If it takes many seconds or even minutes to open the overview tab, you can check according to SAP Note 2147247 if the number of alerts in table STATISTICS_ALERTS_BASE is too high and perform a cleanup.

9. Which SAP HANA Studio version should be used for a certain SAP HANA database?

SAP HANA Studio is downward compatible, but not upward compatible. This means that you should always use at least the SAP HANA Studio Revision that was delivered together with the SAP HANA server software in order to perform monitoring and development tasks.

In some cases a SAP HANA Studio version higher than the SAP HANA server version can also result in errors, see e.g. SAP Note 2337716. To be on the save side, you should use identical versions for SAP HANA Studio and SAP HANA whenever possible.

10. How does the SAP HANA Studio version correspond to the SAP HANA Revisions?

The SAP HANA Studio version and the SAP HANA SPS level correspond in the following way:

SAP HANA Studio	SAP HANA
2.0.x	SPS 09
2.1.x	SPS 10
2.2.x	SPS 11
2.3.x	SPS 12

Install SAP license at OS level

Home


1) Sample warning message of license expired

B) Steps to renew the license from SAP marketplace
1) Ensure the installation number for the license renewal:  System -> Status

2) Login to SAP marketplace: Keys & Requests -> License Keys -> Click on the relevant installation
    number

3) Click on the "Change details" icon for system that required license renewal.

4) Click "Continue"

5) Select the Certificate that required renewal and click "Change selected entry".

6) Click "Save"

7) Once the "Valid Until" shown the new date, click "Continue".

8) Enter the email address to receive the certificate and click "Submit".

9) Click "OK".

10) Request is being process ...

11) Wait for the email from SAP containing the new certificate details

12) Sample content of the new certificate.

C) Steps to perform the renewal at OS level

1) Example of insufficient permission to perform license renewal from SAP GUI

2) By using WINSCP or FTP, transfer the certificate received into the "prdadm" folder

3) File transfer successfully.

4) With PUTTY, login to OS level with root permission and perform the steps below:
    With root permission:
    - cd /home/prdadm
    - chmod 777 CERTICATE_FILE (change mode of the file)
    - chown prdadm:sapsys CERTICATE_FILE (change owner for the file)
    - su - prdadm

5) Execute the command highlighted below with prdadm
    With prdadm permission
    - cdpro
    - ls (to get the correct DVEBMGS name)
    - pwd (to get the correct path name)
    - ls (to get the copied certificate filename)
    - saplikey pf=path name + "/" + DVEBMGS name -install certificate filename

6) Once license installed successfully, the warning message no longer appear

SAP Router Configuration File - SAPRouter tb

Home


1) SAP Support team having problem to remote access the Solution Manager page (HTTP Access)
for further remote support

2) Initial finding shown the connection is ok.

3) Further finding shown, additional port required to be configure on the SAP router for HTTP access.

4) Sample of the configuration settings required.

5) To perform any changes on the SAP router configuration file, stop the SAProuter service.

6) Locate the "saprouttab" file (ex: c:/usr/sap/saprouter) and add the required ports.

7) Once the "saprouttab" changes complete, restart the "SAProuter" services.

8) SAP Global team should be able to remote access the page by now.

SAP Router configuration and renew of the SAP router Certificate

Home


The first thing needs to do, is to send a customer message to SAP
Support (component XX-SER-NET-OSS-NEW) and tell them to register the
hostname and IP of your new SAProuter.

You have to register it with a official IP address (no internal IPs
allowed), but it’s allowed to use NAT in the firewall/router.

After you’ve received a confirmation from SAP that your SAProuter has
been registered, you are ready to configure your SAProuter.

If your SAProuter directory is C:\usr\sap\saprouter, these are the steps
to follow.


1. Set two environment variables: SECUDIR and SNC_LIB

C:\usr\sap\saprouter

The environment variable SNC_LIB needs to be set for the user account
   SAProuter is running under.

   variable Name : SNC_LIB
   Variable Value : D:\usr\sap\saprouter\ntintel\sapcrypto.dll


Set the environment SECUDIR = <directory_of_saprouter>

   variable Name : SECUDIR
   Variable Value : D:\usr\sap\saprouter

                         

2. Download the SAP Crypto Library  from service market place.

Create folder d:\usr\sap\saprouter   - on system where you are installing
unpack the downloaded softwere into folder

Copy these files to saprouter folder
saprouter.exe
niping.exe
sapgen.exe

Then copy these files to saprouter folder
LEGAL.TXT
Ticket
LICENSE.txt
Saprouttab

Copy ntintel this folder to saprouter folder



3. To generate a certificate request, run the command:

sapgenpse get_pse -v -r certreq -p local.pse "CN=SOLMAN, OU=0000491517, OU=SAProuter, O=SAP, C=DE"

Note: You will be asked for a PIN code. Just pick your own 4 numbers, but
you’ll have to use the same PIN every time you’re asked to enter one.

Please enter PIN:
Please reenter PIN:

Supplied distinguished name: "CN=SOLMAN, OU=0000491517, OU=SAProuter, O=SAP, C=DE"
Generating key (RSA, 1024-bits) ... succeeded.
certificate creation... ok
PSE update... ok
PKRoot... ok
Generating certificate request... ok.


4. Then you have to follow the guide and request the certificate from
http://service.sap.com/tcs -> Download Area -> SAProuter Certificate

Go to http://service.sap.com/saprouter-sncadd

Request certificate for SAP Router

which will give the certifcate like below.

SAP Solution Manager 7.1 installation

Home

Installation of SAP Solution Manager in Windows platform compatible with Amazon / Azure Cloud / Hyper-V / Standalone server
The SAP Solution Manager 7.1 installation steps below suitable on all Windows server environment including Amazon Web Services (AWS), Microsoft Azure, Microsoft Hyper-V or standalone server installation.

These configurations including:

A) Prerequisite
B) Oracle Database Installation
C) SAP Solution Manager 7.1 Installation with SWPM
D) SAP GUI Installation and login the SAP Solution Manager for the first time
E) Others


A) Prerequisite:
1) Windows server 2008 be ready

2) Minimum SAP Solution Manager 7.1 installation files

Download Object	Title
50118243_6	NW 7.0 Presentation - 7.30 Compilation 2 Present. ½
51041940	ORACLE Client 11.2.0.3
51042334_1 – 6	ORACLE RDBMS 11.2.0.3 Windows x64
51042607_1 - 12	SAP SOLMAN 7.1 SR1 Inst. Export (2)
51042609_1 – 5	SAP SOLMAN 7.1 SR1 Java Comp
51042616_9	SL CONTROLLER 700
51046511_6	720 UC Kernel for SWPM SP03 - Windows Server on x64 64bit
70SWPM10SP02_4-20009707.sar	Software Provisioning Manager 1.0 SP2 for NW 7.0x

3) Recommended server specifications:

Type	Descriptions
OS	Windows Server 2012 Data Center
RAM	12GB
Hard disk	400GB (c:\ 100GB d:\300GB)

4) Reference for OS environment setup on AWS Cloud and Microsoft Hyper-V 

- AWS Cloud:  Section: AWS AMI Setup and Configurations (SAP IDES Installation)

- Microsoft Hyper-V: Section: A) Creating new VM in Hyper-V (setup Red Hat Enterprise Linux Server in Microsoft Hyper-V Server 2012)

5) Assumption:

     - The Windows OS will be configure as workgroup instead of joining a domain / active directory.

     - All the installation are mostly with default settings and further configurations or fine tune will be perform

        after the installation.

     - Windows OS been patched to latest update and some prerequisite steps as in SAP IDES Installation

     - The installation time estimation was based on a installation on Microsoft Hyper-V 2012 environment

        with the above mentioned hardware. In fact, the actual installation time might vary.

B) Oracle Database Installation:

1) Run the Oracle setup batch file "sapserver,cmd" to begin the database installation

 2) Enter the installation drive and SID

 3) Installation splash screen

 4) Click "Next"

 5) Click "Next" ignore the warning

 6) Select "Skip the software updates"

 7) Select " Install database software only"

 8) Select "single instance database installation"

 9) Click "Next"

 10) Select "Enterprise Edition"

 11) Choose the installation drive

 12) Wait for the verification process

 13) The verification process

 14) Click "Install" to begin the installation

 15) Click "Details" button to shown the installation progress

 16) The additional installation progress screen

 17) Wait until the installation complete and the click "Close" button

 18) Confirm the database been installed

B) SAP Solution Manager 7.1 Installation with SWPM

The installation process estimate will take about ~5 hours to complete with the above mentioned hardware specifications

1) Double click the "sapinst" extracted from SWPM - Section E) Others below shown how to extract the installation file with sapcar program

 2) Select "SAP Solution Manager 7.1 Support Release 1"

 3) Select "typical"

 4) The installation splash screen

 5) Select the SWPM kernel

 6) Enter the SAPSID and installation drive

 7) Configure the FQDN or it can be configure after the installation

 8) Enter the master password

 9) Enter the Oracle database ID created during the database installation

 10) Select the installation export package

 11) Select the other installation export package

 12) Click  "Next" with all the default settings

 13) Select the Java component package

 14) Ensure the installation drive are correct

 15) Click "Next" to accept the default listener configuration or change the port according to existing firewall

        policy

 16) Select the kernel package

 17) Select the Oracle client package

 18) Select "Configure a local SLD" in this example

 19) Enter the computer name in "Object Server Name"

 20) Click the "Next" button

 21) Click "Yes" button

 22) Click "No SLD destination" in this example

 23) Verify the selected options and click "Next" to accept all the settings

 24) The installation begin

 25) Example of the installation process

 26) Example of the installation process

 27) Example of the installation process

 28) Around ~5 hours for the installation to complete

 29) SAP management console and listener status command showing the SAP services are up and running

D) SAP GUI Installation and login the SAP Solution Manager for the first time

1) Perform the SAP GUI installation from the media kit: 50118243_6

2) The settings for the SAP logon

3) Login with user: "sap*"

4) The information screen

5) The relevant SAP system information

6) Login to the portal (http: port: 5<SID>00, https: port: 5<SID>01)

7) Main Menu of the portal

8) Use the default login: "j2ee_admin" and master password entered during installation

9) Sample of information screen

10) Again using the "j2ee_admin" for access

11) Sample of information screen

12) That's all on the basic steps to perform a new SAP Solution Manager installation.

13) Please refer to the common troubleshooting on SOLMAN_WORKCENTER post for further configurations or common errors troubleshooting

E) Others

How to extract the SWPM installation file with SAPCAR

1) Download the "Software Provisioning Manager 1.0 SP2 for NW 7.0x" from SAP marketplace

 2) Extract the sar file with SAPCAR -xvf <swpm filename.sar>

 3) The "sapinst" program use for the SAP Solution Manager installation

How to clear SWPM cache or resolve the SAP Solution Manager 7.1 selection node was not available for installation

After running the "sapinst", the "SAP Solution Manager 7.1 Support Release 1" option was not available and it seem appearing with different option ex: SAP Solution Manager 7.1 for HANA.

This happen due to the other SWPM was executed before and the files were cache and causing the other SWPM relevant selection node not updated.

1) Locate to "c:\users\Administrator\AppData\Local\Temp\2", delete all the files and folders contains in it

 2) Re-run the correct SWPM "sapinst" and the correct node would appear