Registering a large number of database systems to monitor one by one can become a time consuming process. Instead of adding one system at a time, you can add multiple systems at once using an import file.

Note: This document was originally created by a former colleague of mine, Yuki Ji, in support of a customer engagement initiative regarding the SAP DB Control Center (DCC) product.  To preserve this knowledge, the document was migrated to this space.

1. Configure Monitored Systems - Make sure to setup the technical user for each system you wish to configure. You will need the credentials of the technical user for import registration.
2. Create an Import File - Create an import file according to the format indicated in the link. Save the import file as either a .csv or a .txt file.
   
   In the import file you are able to omit system login IDs or passwords. If you do so, SAP DCC prompts you during the import process for the missing information BUT it prompts you for only one user/password pair. The entered pair is then used for each system that is missing credentials for that import. If you are importing multiple systems with unique user/password combinations, it is simplest to import the systems in separate operations or to include all the login credentials in the import file.
   
3. Login to DCC and open System Directory. In the bottom right corner of System Directory select Import Systems.
   
   
   
   
4. Select your Import file from your local system and click Load File to continue to the next step.
   
   
   
   
5. Below you will see that one of the systems we entered, PM1, has already been registered so no further actions can be taken for that system. For the other systems, PM2 and YJI we can see that we are missing credentials for system YJI. The credentials will be addressed in the next step.
   
   In this step we choose which systems we wish to continue registering. For this example I am selecting both PM2 and YJI.
   
   Note: If DCC is unable to find or connect to the system, or there is a typo in the import file, you will see the related error messages on this page. Some things to check initially: monitored system configuration, Import file spelling and inputs.
   
   
   
   
6. On selecting Import, because we have credentials missing we are asked to supply them. The window also give a reminder that the credentials entered here will be applied to all systems that do not already credentials supplied. The credentials I enter will be applied to system YJI.
   
   
   
   
7. After clicking Login, if the credentials are correct the systems are registered! If after clicking Login the system is not registered, check the credentials you entered and whether they match the system.
   
   
   
   

Welcome to the SAP HANA Rules Framework (HRF) Community Site!

SAP HANA Rules Framework provides tools that enable application developers to build solutions with automated decisions and rules management services, implementers and administrators to set up a project/customer system, and business users to manage and automate business decisions and rules based on their organizations' data.

In daily business, strategic plans and mission critical tasks are implemented by a countless number of operational decisions, either manually or automated by business applications. These days - an organization's agility in decision-making becomes a critical need to keep up with dynamic changes in the market.

HRF Main Objectives are:

• To seize the opportunity of Big Data by helping developers to easily build automated decisioning solutions and\or solutions that require business rules management capabilities
• To unleash the power of SAP HANA by turning real time data into intelligent decisions and actions
• To empower business users to control, influence and personalize decisions/rules in highly dynamic scenarios

HRF Main Benefits are:

Rapid Application Development |Simple tools to quickly develop auto-decisioning applications

• Built-in editors in SAPHANA studio that allow easy modeling of the required resources for SAP HANA rules framework
• An easy to implement and configurable SAPUI5 control that exposes the framework’s capabilities to the business users and implementers

Business User Empowerment | Give control to the business user

• Simple, natural, and intuitive business condition language (Rule Expression Language)

• Simple and intuitive UI control that supports text rules and decision tables

• Simple and intuitive web application that enables business users to manage their own rules

Scalability and Performance |HRF as a native SAP HANA solution leverages all the capabilities and advantages of the SAPHANA platform.

For more information on HRF please contact shuki.idan@sap.com  and/or noam.gilady@sap.com

Interesting links:

• NEW!!! SAP HANA Rules Framework 1.00 SP07 is now available!
• SAP HANA Rules Framework's tutorials on SAP HANA Academy.
• Here is a link to SAP HANA Rules Framework's official documentation on SAP Service Marketplace
  
• Here is a link to an article that describes how to get started with HANA Rules Framework
  
• HRF Online Course:
  • 1. Lesson number-1: How to install SAP HANA Rules Framework?
  • 2. Lesson number-2: How to create a simple vocabulary on SAP HANA Rules Framework?
  • 3. Lesson number-3: How to create outputs and actions on SAP HANA Rules Framework?
  • 4. Lesson number-4: How to create dependent vocabularies on SAP HANA Rules Framework?
  • 5. Lesson number-5: How to create value lists on SAP HANA Rules Framework?
  • 6. Lesson number-6: How to create a text rule on SAP HANA Rules Framework?
  • 7. Lesson number-7: How to create a decision table on SAP HANA Rules Framework?
  • 8. Lesson number-8: How to create aliases on SAP HANA Rules Framework?
  • 9. Lesson number-9: How to create rule service on SAP HANA Rules Framework?
  • 10. Lesson number-10: How to create rule template on SAP HANA Rules Framework?
  • 11. Lesson number-11: How to write complex rules utilizing Rule Expression Language?

SAP solutions already utilizing HRF:

• SAP Operational Process Intelligence - link to SCN page
• SAP hybris Marketing (Customer Engagement Intelligence portfolio) - link to SCN page
• SAP Fraud Management - link to SCN page
• SAP Transportation Resource Planning - link to TRP help page

Use cases of SAP solutions already utilizing HRF:

SAP Transportation Resource Planning

SAP FraudManagement

SAP hybris Marketing (formerly SAP Customer Engagement Intelligence)

SAP Operational Process Intelligence

This document will deal with issues regarding analytical privileges with SAP HANA.

 

So what are Privileges some might ask?

 

System Privilege:

System privileges control general system activities. They are mainly used for administrative purposes, such as creating schemas, creating and changing users and roles, performing data backups, managing licenses, and so on.

Object Privilege:

Object privileges are used to allow access to and modification of database objects, such as tables and views. Depending on the object type, different actions can be authorized (for example, SELECT, CREATE ANY, ALTER, DROP, and so on).

Analytic Privilege:

Analytic privileges are used to allow read access to data in SAP HANA information models (that is, analytic views, attribute views, and calculation views) depending on certain values or combinations of values. Analytic privileges are evaluated during query processing.

In a multiple-container system, analytic privileges granted to users in a particular database authorize access to information models in that database only.

Package Privilege:

Package privileges are used to allow access to and the ability to work in packages in the repository of the SAP HANA database.

Packages contain design time versions of various objects, such as analytic views, attribute views, calculation views, and analytic privileges.

In a multiple-container system, package privileges granted to users in a particular database authorize access to and the ability to work in packages in the repository of that database only.

 

For more information on SAP HANA privileges please see the SAP HANA Security Guide:

http://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdf

 

 

So, you are trying to access a view, a table or simply trying to add roles to users in HANA Studio and you are receiving errors such as:

• Error during Plan execution of model _SYS_BIC:onep.Queries.qnoverview/CV_QMT_OVERVIEW (-1), reason: user is not authorized
• pop1 (rc 2950, user is not authorized)
• insufficient privilege: search table error: [2950] user is not authorized
• Could not execute 'SELECT * FROM"_SYS_BIC"."<>"' SAP DBTech JDBC: [258]: insufficient privilege: Not authorized.SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

 

These errors are just examples of  some the different authorisation issues you can see in HANA Studio, and each one is pointing towards a missing analytical privilege.

 

Once you have created all your models, you then have the opportunity to define your specific authorization requirements on top of the views that you have created.

 

So for example, we have a model in HANA Studio Schema and its called "_SYS_BIC:Overview/SAP_OVERVIEW"

We have a user, lets just say its the "SYSTEM" user, and when you query this view you get the error:

 

Error during Plan execution of model _SYS_BIC:Overview/SAP_OVERVIEW (-1), reason: user is not authorized.

 

So if you are a DBA, and you get a message from a team member informing you that they getting a authorisation issue in HANA Studio. What are you to do?

How are you supposed to know the User ID? And most importantly, how are you to find out what the missing analytical privilege is?

 

So this is the perfect opportunity to run an authorisation trace through the means of the SQL console on HANA Studio.

So if you follow the below instructions it will walk you through executing the authorisation trace:

 

1) Please run the following statement in the HANA database to set the DB  trace:

alter system alter configuration ('indexserver.ini','SYSTEM') SET
('trace','authorization')='info' with reconfigure;

 

2) Reproduce the issue/execute the command again/

 

3)When the execution finishes please turn off the trace as follows in the Hana studio:

alter system alter configuration ('indexserver.ini','SYSTEM') unset
('trace','authorization') with reconfigure;

 

_____________________________________________________________________________________________________________________________

 

If you would like a more detailed trace on the privileges needed you could also execute the DEBUG level trace (Usually SAP Development would request this)

 

1) Please run the following statement in the HANA database to set the DB  trace:

alter system alter configuration ('indexserver.ini','SYSTEM') SET
('trace','authorization')='debug' with reconfigure;

 

2) Reproduce the issue/execute the command again

 

3)When the execution finishes please turn off the trace as follows in the Hana studio:

alter system alter configuration ('indexserver.ini','SYSTEM') unset
('trace','authorization') with reconfigure;

 

______________________________________________________________________________________________________________________________

 

So now that you have turned the trace on and reproduced the issue, now you must turn off the trace.

 

You should now see a new indexserver0000000trc file created in the Diagnosis Files Tab in HANA Studio

 

So once you open the trace files, scroll to the end of the file and you should see something familiar to this:

 

e cePlanExec      cePlanExecutor.cpp(06890) : Error during Plan execution of model _SYS_BIC:onep.Queries.qnoverview/CV_QMT_OVERVIEW (-1), reason: user is not authorized
i TraceContext    TraceContext.cpp(00718) : UserName=TABLEAU, ApplicationUserName=luben00d, ApplicationName=HDBStudio, ApplicationSource=csns.modeler.datapreview.providers.ResultSetDelegationDataProvider.<init>(ResultSetDelegationDataProvider.java:122);csns.modeler.actions.DataPreviewDelegationAction.getDataProvider(DataPreviewDelegationAction.java:310);csns.modeler.actions.DataPreviewDelegationAction.run(DataPreviewDelegationAction.java:270);csns.modeler.actions.DataPreviewDelegationAction.run(DataPreviewDelegationAction.java:130);csns.modeler.command.handlers.DataPreviewHandler.execute(DataPreviewHandler.java:70);org.eclipse.core.commands
i Authorization    XmlAnalyticalPrivilegeFacade.cpp(01250) : UserId(123456) is missing analytic privileges in order to access _SYS_BIC:onep.MasterData.qn/AT_QMT(ObjectId(15,0,oid=78787)). Current situation:
AP ObjectId(13,2,oid=3): Not granted.
i Authorization    TRexApiSearch.cpp(20566) : TRexApiSearch::analyticalPrivilegesCheck(): User TABLEAU is not authorized on _SYS_BIC:onep.MasterData.qn/AT_QMT (787878) due to XML APs
e CalcEngine      cePopDataSources.cpp(00488) : ceJoinSearchPop ($REQUEST$): Execution of search failed: user is not authorized(2950)
e Executor        PlanExecutor.cpp(00690) : plan plan558676@<> failed with rc 2950; user is not authorized
e Executor        PlanExecutor.cpp(00690) : -- returns for plan558676@<>
e Executor        PlanExecutor.cpp(00690) : user is not authorized(2950), plan: 1 pops: ceJoinSearchPop pop1(out a)
e Executor        PlanExecutor.cpp(00690) : pop1, 09:57:41.755  +0.000, cpu 139960197732232, <> ceJoinSearchPop, rc 2950, user is not authorized
e Executor        PlanExecutor.cpp(00690) : Comm total: 0.000
e Executor        PlanExecutor.cpp(00690) : Total: <Time- Stamp>, cpu 139960197732232
e Executor        PlanExecutor.cpp(00690) : sizes a 0
e Executor        PlanExecutor.cpp(00690) : -- end executor returns
e Executor        PlanExecutor.cpp(00690) : pop1 (rc 2950, user is not authorized)

 

So we can see from the trace file that User who is trying to query from the view is called TABLEAU. TABLEAU is also represented by the User ID (123456)

 

So by looking at the lines:

 

i Authorization    XmlAnalyticalPrivilegeFacade.cpp(01250) : UserId(123456) is missing analytic privileges in order to access _SYS_BIC:onep.MasterData.qn/AT_QMT(ObjectId(15,0,oid=78787)).

&

i Authorization    TRexApiSearch.cpp(20566) : TRexApiSearch::analyticalPrivilegesCheck(): User TABLEAU is not authorized on _SYS_BIC:onep.MasterData.qn/AT_QMT (787878) due to XML APs

 

We can clearly see that TABLEAU user is missing the correct analytical privileges to access the _SYS_BIC:onep.MasterData.qn/AT_QMT which is located on Object 78787.

 

So now we have to find out who owns the Object 78787. We can find out this information by querying the following:

 

select * from objects where object_oid = '<oid>';

Select * from objects where object_oid = '78787'

 

Once you have found out the owner for this object, you can get the owner to Grant the TABLEAU user the necessary privileges to query the object.

 

Please be aware that if you find that the owner of an object is _SYS_REPO, this is not as straight forward as logging in as _SYS_REPO as this is not possible because SYS_REPO is a technical database user used by the SAP HANA repository. The repository consists of packages that contain design time versions of various objects, such as attribute views, analytic views, calculation views, procedures, analytic privileges, and roles. _SYS_REPO is the owner of all objects in the repository, as well as their activated runtime versions.

You have to create a .hdbrole file which which gives the access ( Development type of role, giving select, execute, insert etc access) on this schema. You then assign this role to the user who is trying to access the object.

 

 

Another option that is available for analyzing privileges issues was introduced as of SP9. This comes in the form of the Authorization Dependency Viewer. Man-Ted Chan has prepared an excellent blog on this new feature:

 

http://scn.sap.com/community/hana-in-memory/blog/2015/07/07/authorization-dependency-viewer

 

 

 

For more useful information on Privileges can be seen in the following KBA's:

KBA #2220157 - Database error 258 at EXE insufficient

KBA #1735586 – Unable to grant privileges for SYS_REPO.-objects via SAP HANA Studio authorization management.

KBA #1966219 – HANA technical database user _SYS_REPO cannot be activated.

KBA #1897236 – HANA: Error&quot; insufficient privilege: Not authorized &quot; in SM21

KBA #2092748 – Failure to activate HANA roles in Design Time.

KBA #2126689 – Insufficient privilege. Not authorized

KBA #2250445 - SAP DBTech JDBC 485 - Invalid definition of structured privilege: Invalid filter condition

 

 

For more useful Troubleshooting documentation you can visit:

 

http://wiki.scn.sap.com/wiki/display/TechTSG/SAP+HANA+and+In-Memory+Computing

Purpose

The purpose of this document is to instruct SAP customers on how to analyse ABAP dumps.

Overview

How to troubleshoot ABAP Dumps

Troubleshooting

When looking at an ABAP system you can sometimes come across runtime errors in Transaction ST22:

Clicking into the "Today" or "Yesterday" tab will bring up all the ABAP Runtime errors you have encountered in the past 2 days.

You can also filter the dates for a particular dump by using the filter feature:

Here are some examples of runtime errors you might see in ST22:

So from looking at these dumps, you can see

1: Category

2: Runtime Errors

3: ABAP Program

4: Application Component

5: Data & Time.

The ST22 dumps do not not really give you much information here so more information will be needed.

For more information you will then look into the Dev_W files in the transaction ST11

ST11 allows you to look further into the Dev_w files relating to the dumps in ST22:

To find the work Dev_w file that corresponds with the dump, you can see this is ST22.

Go to ST22 > click on the Runtime Errors for "Today", "Yesterday" or a filter. This will being up the specific dump you wish to analyse.

Here you will see 11 columns like so:

Here you can see the columns I have mentioned. The Work Process Index number you need is in the column named WP Index.

Once you find the dev_w index number you can then go to ST11 and find further information:

In the ST11 Dev_w files you have to match the time of the dump in ST22 with the recorded times in the Dev_w process files.

If there no useable information in the Dev_W files, the next step would be to analyse the issue from the Database side.

To analyse from the Database side:

1: Open HANA Studio in SAP HANA Administration Console View

2: Check the diagnosis trace files in accordance with the time stamp of the dump you saw previously in ST22. To do this we have to go to the Diagnosis tab in HANA Studio:

3: Check the time stamp from the ST22 dump (Date and Time), and then match this accordingly with the time in either the Indexserver.trc or nameserver.trc.

Search for the corresponding time stamp mentioned above i.e. 18/11/2015 @ 10:55:43.

Or instead of searching you could use the below SQL:

select top 500 service_name, timestamp, trace_text from m_merged_traces where service_name in ('indexserver', 'nameserver') and timestamp between '2015-11-18 10:40:00' and '2015-11-18 10:59:00'

Searching the nameserver log files can be a good indication of whether your ST22 is related to network issues, you may see errors such as:

  TrexNet          Channel.cpp(00339) : ERROR: reading from channel 151 <127.0.0.1:<host>> failed with timeout error; timeout=10000 ms elapsed [73973]{-1}[-1/-1] 2015-01-28 01:58:55.208048 e TrexNetBuffer    BufferedIO.cpp(01092) : channel 151 from <127.0.0.1:<host>>: read from channel failed; resetting buffer

If you do find some errors similar to the above, firstly check which host the error is pointing to and check whether or not this service was available at the time of the dump.

If this does not yield any useful information, the next step is to ask someone from your network team to look into this. Checking the var/logs/messages is always a great place to start.

When searching through the indexserver.trc file, you could notice some irregularities recorded here. The next step is to search this error on the SAP Service Market Place for a known KBA or Note (Learn how to search more effectively 2081285 - How to enter good search terms to an SAP search? )

Related Documents

Did you know? You can find details of common issues, fixes, patches and much more by visiting SAP moderated forums on http://scn.sap.com/docs/DOC-18971

Documentation regarding HANA installation, upgrade, administration & development is available at http://help.sap.com/hana_appliance

SAP HANA Troubleshooting WIKI: http://wiki.scn.sap.com/wiki/display/TechTSG/SAP+HANA+and+In-Memory+Computing SAP Discussion HANA: http://scn.sap.com/community/hana-in-memory/ Learn how to search more effectively 2081285 - How to enter good search terms to an SAP search?
__________________________________________________________________________________________________________

With the release of SAP HANA SPS 05, SAP announced support for VMware hypervisor, as the first technology supported to partition a SAP HANA server into smaller partitions / VMs. Meanwhile SAP has further extended its support to run SAP HANA in a virtualized / partitioned (multi-tenant) environments, by adding additional scenarios and technologies supported.

See SAP Note 1788665 and attached SAP HANA technology roadmap for running on virtualized / partitioned platforms for more information on currently supported scenarios and where to find further information on best practices and constraints which may apply.

In short, current SAP HANA support covers:

• General support for SAP HANA on VMware vSphere 5.1 in non-production
• General support for single SAP HANA VMs on VMware vSphere 5.5 in production and non-production
• Controlled General Availability for multi-VM and BW on HANA scale-out scenarios on VMware vSphere 5.5 in production
• Controlled Availability for Hitachi LPAR (single and multiple partitions) in production

On our roadmap for future support are:

• Support of larger VMs and 8-socket hardware with VMware vSphere 6

See above referenced SAP Note and slide deck for additional information and details.

HANATEC certificationhas in it's curricula the "HA100 - SAP HANA Introduction" and the "HA200 - SAP HANA Installation & Operations" training courses.

These courses are, in my opinion well structured and with enought exercises to get the exact understanding on the presented subjects. Perhaps the View concepts and creation in HA100 is to much stressed out than expected for the technical or BASIS consultant.

After a couple of weeks I was faced with the need to go thru all the course stuff again and I was searching for a HANA system to support my study and to do some or all the exercises .

The answer is in the HA100 course SPS7 though not anymore in SPS10. Creating a HANA Cloud free subscription for the "SAP HANA Developer Edition" it's enought for evaluations and  exploration covering the HA100 material at least.

Get access to a HANA system

To get a free account we can do it from http://developers.sap.com/hana and there sign up (only step 2 on next picture) to get started with a free SAP HANA developer edition in the cloud.

We should be aware these web pages are changing and continually evolving so one can find out diferent look on the pages.

After filling all the information to sign up we get the confirmation via e-mail:

From the confimation e-mail we get the URL to access our just created Hana cloud, where s000#######will be the S-user:

https://account.hanatrial.ondemand.com/cockpit#/acc/s000######trial/services

Get some tutorial

The data model available in the evaluation system is not the same as the one used in HA100 training course. The following document posted by Stoyan Manchev is as a very good alternative even if it doesn't go so deeper on the exercises about creating views .

8 Easy Steps to Develop an XS application on the SAP HANA Cloud Platform

When following steps 1 to 4 we begin preparing the environment and then connecting HANA studio do the Hana cloud and creating a view. Don't need to go thru step 5 and nexts since they are not related with our certification.

To run the step 2 we need a HANA Studio. We can download it to install from https://tools.hana.ondemand.com/#hanatools; I've done it with the Luna edition.

Take your time. It will take a while to get everything fitted together in order to create the views.

Updating HANA Studio to connect to a cloud system

To connect to a cloud system using HANA Studio we need to install additional tools:

https://help.hana.ondemand.com/help/frameset.htm?b0e351ada628458cb8906f55bcac4755.html

And as result we get a new option to Add cloud system:

Test your knowledge

After going thru these steps we'll master the HANA100 and to test our knowledge  before going to SAP to make the examen we can do a small assessment which we get choosing "Discovery Preview: SAP HANA Introduction" on https://performancemanager.successfactors.eu

This is a 12 hours e-learning free course based on HA100 with a web assessment included.

Limitations

Unfortunatelly this HANA Developpment Edition for wich we can have a freee access on the cloud is useless to cover almost all if not all the subjects of HA200 Because it has limitations in the adiministration parts. We are not able to define users, roles or even display any administration view.

Part of the SAP HANA Academy'sWhat's New with SAP HANA SPS11 series, Jamie Wiseman provides a tutorial video on using spatial functionality in HANA SQLScript. Specifically Jamie will detail how to use spatial data type ST_GEOMETRY and spatial methods to access and manipulate spatial data in HANA SQLScript. Note this feature is only applicable to SAP HANA SPS11 and it will not work for any prior iterations of SAP HANA.

Watch Jamie's quick tutorial below.

In SAP HANA SPS11 SQLScript now supports spatial data type ST_GEOMETRY and SQL spatial methods to access and manipulate spatial data. To demonstrate this Jamie is using a user defined function that uses spatial dimensions in a procedure. Then Jamie will call that procedure which contains a couple of ST_GEOMETRY inputs.

You must be logged into your SAP HANA system with a user who has the rights to create new functions and procedures. Please visit this GitHub page to access, for free, the script used in this tutorial.

Lines 1-9 of the script create a user defined function that has a pair of ST_GEOMETRY input parameters. Line 8 of the function uses the ST distance method to calculate the distance between the two inputs. The distance calculated is subjected to whatever SRID (spatial reference ID) is used.

Lines 11-27 create a procedure that not only references the user defined function, but also incorporates a pair of geometry type inputs. Also, two other spatial methods are used to create an additional display value. This display value consists of two different well-know text methods that will show spatial values in an easier to read text format. Currently at the time of this tutorial's creation only geometry spatial type values are allowed in SQLScript in SAP HANA SPS11.

If you were to uncomment line 13, which contains a point spatial type, then an error would be returned.

Lines 29-35 deal with the procedure call. The syntax for the two parameter inputs creates geometry spatial types. In Jamie's example both are points. The SRIDs of the two geometries are specified in the same input.

If you run all of the syntax at once you will get the results from the procedure's nested distance call and will also display the results from the two additional spatial methods.

For more tutorials videos on What's New with SAP HANA SPS11 please check out this playlist.

SAP HANA Academy - Over 1,300 free tutorials videos on SAP HANA, SAP Analytics and the SAP HANA Cloud Platform.

Follow us on Twitter @saphanaacademy and connect with us on LinkedIn to keep apprised of our latest free tutorials.

In a tutorial video the SAP HANA Academy's Jamie Wiseman shows how to create a user using the "NO_FORCE_FIRST_PASSWORD_CHANGE" option. This option enables a user to not have to change their password the very first time they log into SAP HANA. Note that your password's lifetime policy will still apply. The option is new in SAP HANA SPS11 but will not work in prior iterations of SAP HANA.

Check out Jamie's video below.

Lines 2-3 of the syntax shown below creates a user with the NO FORCE_FIRST_PASSWORD_CHANGE option. With this option the user's current and valid password is specified during the user creation. Therefore it is highly recommended to use a secure password at this point. The user you're logged into SAP HANA as must have the appropriate rights to create a user.

After all of the syntax is run navigate to the results from the SELECT * FROM USERS statement.

The newly created user's information is displayed on the last line of the table. Scrolling to the two Password columns (PASSWORD_CHANGE_TIME and PASSWORD_CHANGE_NEEDED) verifies that the user will not need to change their password until the password's lifetime expires.

If you're unsure regarding the system view name that contains your password policy it will be displayed in the results table from the SELECT * FROM M_PASSWORD_POLICY statement. Note that the password's lifetime policy in Jamie's demonstration in 182 days.

For more tutorials videos on What's New with SAP HANA SPS11 please check out this playlist.

SAP HANA Academy - Over 1,300 free tutorials videos on SAP HANA, SAP Analytics and the SAP HANA Cloud Platform.

Follow us on Twitter @saphanaacademy and connect with us on LinkedIn to keep apprised of our latest free tutorials.

In a tutorial video the SAP HANA Academy's Jamie Wiseman examines the Intersection Aggregate method, which is part of SAP HANA Spatial. This method is new to SAP HANA and available in SAP HANA SPS11. Watch Jamie's video below.

The Intersection Aggregate method returns the spatial intersection of all of the geometries in a group. The aggregate is logically computed by repeatedly applying the spatial type intersection method to combine two geometries at a time.

Jamie is using the .ST_AsText method so that the results are returned in a more readable format as opposed to the results coming back in a binary format. The syntax used in this video is available in the description of the video and also at the bottom of this post.

Lines 3-19 of the syntax will create a test schema and a test table. Next several geometries will be added to the shape column. The SRID will be 0 as Jamie will be looking at geometries in a Cartesian system.

If you run lines 4-25 you will return the data from your test table as shown below.

The table contains a pair of closed polygons, specifically a square and a triangle, and a line segment. The visual representation of these geometries are depicted below. The geometries were added in the following order: square, triangle, line.

Executing lines 28-29 will run the Intersection Aggregation on the shape column. The result is the single line segment that is shown below.

Note that this method will return a null if there is no common intersection between the complete set of geometries that are being compared. Also if the final set that the method looks at is a single geometry then that single geometry will be returned.

For more tutorials videos on What's New with SAP HANA SPS11 please check out this playlist.

SAP HANA Academy - Over 1,300 free tutorials videos on SAP HANA, SAP Analytics and the SAP HANA Cloud Platform.

Follow us on Twitter @saphanaacademy and connect with us on LinkedIn to keep apprised of our latest free tutorials.

Tutorial's Syntax:

-- create a test schema and add a test table

CREATE SCHEMA DEVTEST;

CREATE COLUMN TABLE DEVTEST.SPATIALTEST (

ID INTEGER PRIMARY KEY GENERATED ALWAYS AS IDENTITY,

SHAPE ST_GEOMETRY(0)

);

-- add several geometries to the test table

INSERT INTO DEVTEST.SPATIALTEST VALUES (

NEW ST_Polygon('Polygon ((0 0, 4 0, 4 4, 0 4, 0 0))')

);

INSERT INTO DEVTEST.SPATIALTEST VALUES (

NEW ST_Polygon('Polygon ((1 3, 3 1, 3 3, 1 3))')

);

INSERT INTO DEVTEST.SPATIALTEST VALUES (

NEW ST_LineString('LineString (0 0, 3 3)')

);

-- look at the data in the test table

SELECT

SHAPE.ST_AsWKT() AS SHAPE,

SHAPE.ST_GeometryType() AS SHAPE_TYPE

FROM DEVTEST.SPATIALTEST;

-- use ST_IntersectionAggr on the SHAPE column

SELECT  ST_IntersectionAggr ( SHAPE ).ST_AsText()

FROM DEVTEST.SPATIALTEST;

In a tutorial video the SAP HANA Academy's Jamie Wiseman examines two binary to hexadecimal conversion SQL Functions. Jamie details how to use the BinToHex () and the BinToNHex() functions. This pair of functions are new to SAP HANA SPS11. Watch Jamie's video below.

The difference between the two new SQL functions is the output type. The conversion of BinToHex is a VarChar output while the conversion of BinToNHex is a NVarChar output.

Jamie enters the syntax shown below and displayed at the bottom of this post into a SQL console in SAP HANA Studio.

Both functions require a single parameter (input value) and produce a hexadecimal value as the output. Running the syntax returns identical results for the two queries, except that the BinToNHex has a NVarChar output.

So the decision to use BinToHex or BinToNHex will largely depend on what your application is expecting.

Note that both the BinToHex and BinToNHex functions will automatically convert any input to binary. Therefore you won't need to use a To_BINARY conversion. A To_BINARY conversion is currently displayed in the second column of the result tables highlighted above.

For more tutorials videos on What's New with SAP HANA SPS11 please check out this playlist.

SAP HANA Academy - Over 1,300 free tutorials videos on SAP HANA, SAP Analytics and the SAP HANA Cloud Platform.

Follow us on Twitter @saphanaacademy and connect with us on LinkedIn to keep apprised of our latest free tutorials.

Tutorial's Syntax:

SELECT

BINTOHEX('ABC'),

BINTOHEX(TO_BINARY('ABC'))

FROM DUMMY;

-- Converts a binary value to a hexadecimal value as a VARCHAR data type.

-- The input value is converted to a binary value first if it is not a binary value.

--results:

--414243, 414243

SELECT

BINTONHEX('ABC'),

BINTONHEX(TO_BINARY('ABC'))

FROM DUMMY; 

-- Converts a binary value to a hexadecimal value as an NVARCHAR data type.

-- The input value is converted to a binary value first if it is not a binary value.

--results:

--414243, 414243

Standart Jobs function (transaction SM36) is obsolete in SAP S/4HANA for sap technical jobs. Instead of it, we have a new easy way: Technical Job Repository.

Technical Job Repository carries out the scheduling of periodic technical sap jobs in the client.

Also this mechanism is carried out automatically by the system. You do not need any interaction and scheduling, unlike the earlier Standard Jobs function in SM36.

New Job Repository function calls the transaction SJOBREPO.

SJOBREPO displays an overview of all job definitions delivered and scheduled by SAP in the technical job repository.

You can use SJOBREPO to change a job definition within certain limits or to completely deactivate it.

There is a hourly working trigger for technical background job generation. One kernel parameter is responsible for this mechanism (rdisp/job_repo_activate_time). These generations logs are stored in table BTCCTL for the last execution time.

There is good one SAP note (#2190119) and it has an attached PDF document that explains the functionality and customizing possibilities of the technical job repository in SAP S/4HANA.

Have fun!

Registering a large number of database systems to monitor one by one can become a time consuming process. Instead of adding one system at a time, you can add multiple systems at once using an import file.

Note: This document was originally created by a former colleague of mine, Yuki Ji, in support of a customer engagement initiative regarding the SAP DB Control Center (DCC) product.  To preserve this knowledge, the document was migrated to this space.

1. Configure Monitored Systems - Make sure to setup the technical user for each system you wish to configure. You will need the credentials of the technical user for import registration.
2. Create an Import File - Create an import file according to the format indicated in the link. Save the import file as either a .csv or a .txt file.
   
   In the import file you are able to omit system login IDs or passwords. If you do so, SAP DCC prompts you during the import process for the missing information BUT it prompts you for only one user/password pair. The entered pair is then used for each system that is missing credentials for that import. If you are importing multiple systems with unique user/password combinations, it is simplest to import the systems in separate operations or to include all the login credentials in the import file.
   
3. Login to DCC and open System Directory. In the bottom right corner of System Directory select Import Systems.
   
   
   
   
4. Select your Import file from your local system and click Load File to continue to the next step.
   
   
   
   
5. Below you will see that one of the systems we entered, PM1, has already been registered so no further actions can be taken for that system. For the other systems, PM2 and YJI we can see that we are missing credentials for system YJI. The credentials will be addressed in the next step.
   
   In this step we choose which systems we wish to continue registering. For this example I am selecting both PM2 and YJI.
   
   Note: If DCC is unable to find or connect to the system, or there is a typo in the import file, you will see the related error messages on this page. Some things to check initially: monitored system configuration, Import file spelling and inputs.
   
   
   
   
6. On selecting Import, because we have credentials missing we are asked to supply them. The window also give a reminder that the credentials entered here will be applied to all systems that do not already credentials supplied. The credentials I enter will be applied to system YJI.
   
   
   
   
7. After clicking Login, if the credentials are correct the systems are registered! If after clicking Login the system is not registered, check the credentials you entered and whether they match the system.
   
   
   
   

Welcome to the SAP HANA Rules Framework (HRF) Community Site!

SAP HANA Rules Framework provides tools that enable application developers to build solutions with automated decisions and rules management services, implementers and administrators to set up a project/customer system, and business users to manage and automate business decisions and rules based on their organizations' data.

In daily business, strategic plans and mission critical tasks are implemented by a countless number of operational decisions, either manually or automated by business applications. These days - an organization's agility in decision-making becomes a critical need to keep up with dynamic changes in the market.

HRF Main Objectives are:

• To seize the opportunity of Big Data by helping developers to easily build automated decisioning solutions and\or solutions that require business rules management capabilities
• To unleash the power of SAP HANA by turning real time data into intelligent decisions and actions
• To empower business users to control, influence and personalize decisions/rules in highly dynamic scenarios

HRF Main Benefits are:

Rapid Application Development |Simple tools to quickly develop auto-decisioning applications

• Built-in editors in SAPHANA studio that allow easy modeling of the required resources for SAP HANA rules framework
• An easy to implement and configurable SAPUI5 control that exposes the framework’s capabilities to the business users and implementers

Business User Empowerment | Give control to the business user

• Simple, natural, and intuitive business condition language (Rule Expression Language)

• Simple and intuitive UI control that supports text rules and decision tables

• Simple and intuitive web application that enables business users to manage their own rules

Scalability and Performance |HRF as a native SAP HANA solution leverages all the capabilities and advantages of the SAPHANA platform.

For more information on HRF please contact shuki.idan@sap.com  and/or noam.gilady@sap.com

Interesting links:

• NEW!!! SAP HANA Rules Framework 1.00 SP07 is now available!
• SAP HANA Rules Framework's tutorials on SAP HANA Academy.
• Here is a link to SAP HANA Rules Framework's official documentation on SAP Service Marketplace
  
• Here is a link to an article that describes how to get started with HANA Rules Framework
  
• HRF Online Course:
  • 1. Lesson number-1: How to install SAP HANA Rules Framework?
  • 2. Lesson number-2: How to create a simple vocabulary on SAP HANA Rules Framework?
  • 3. Lesson number-3: How to create outputs and actions on SAP HANA Rules Framework?
  • 4. Lesson number-4: How to create dependent vocabularies on SAP HANA Rules Framework?
  • 5. Lesson number-5: How to create value lists on SAP HANA Rules Framework?
  • 6. Lesson number-6: How to create a text rule on SAP HANA Rules Framework?
  • 7. Lesson number-7: How to create a decision table on SAP HANA Rules Framework?
  • 8. Lesson number-8: How to create aliases on SAP HANA Rules Framework?
  • 9. Lesson number-9: How to create rule service on SAP HANA Rules Framework?
  • 10. Lesson number-10: How to create rule template on SAP HANA Rules Framework?
  • 11. Lesson number-11: How to write complex rules utilizing Rule Expression Language?

SAP solutions already utilizing HRF:

• SAP Operational Process Intelligence - link to SCN page
• SAP hybris Marketing (Customer Engagement Intelligence portfolio) - link to SCN page
• SAP Fraud Management - link to SCN page
• SAP Transportation Resource Planning - link to TRP help page

Use cases of SAP solutions already utilizing HRF:

SAP Transportation Resource Planning

SAP FraudManagement

SAP hybris Marketing (formerly SAP Customer Engagement Intelligence)

SAP Operational Process Intelligence

This document will deal with issues regarding analytical privileges with SAP HANA.

 

So what are Privileges some might ask?

 

System Privilege:

System privileges control general system activities. They are mainly used for administrative purposes, such as creating schemas, creating and changing users and roles, performing data backups, managing licenses, and so on.

Object Privilege:

Object privileges are used to allow access to and modification of database objects, such as tables and views. Depending on the object type, different actions can be authorized (for example, SELECT, CREATE ANY, ALTER, DROP, and so on).

Analytic Privilege:

Analytic privileges are used to allow read access to data in SAP HANA information models (that is, analytic views, attribute views, and calculation views) depending on certain values or combinations of values. Analytic privileges are evaluated during query processing.

In a multiple-container system, analytic privileges granted to users in a particular database authorize access to information models in that database only.

Package Privilege:

Package privileges are used to allow access to and the ability to work in packages in the repository of the SAP HANA database.

Packages contain design time versions of various objects, such as analytic views, attribute views, calculation views, and analytic privileges.

In a multiple-container system, package privileges granted to users in a particular database authorize access to and the ability to work in packages in the repository of that database only.

 

For more information on SAP HANA privileges please see the SAP HANA Security Guide:

http://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdf

 

 

So, you are trying to access a view, a table or simply trying to add roles to users in HANA Studio and you are receiving errors such as:

• Error during Plan execution of model _SYS_BIC:onep.Queries.qnoverview/CV_QMT_OVERVIEW (-1), reason: user is not authorized
• pop1 (rc 2950, user is not authorized)
• insufficient privilege: search table error: [2950] user is not authorized
• Could not execute 'SELECT * FROM"_SYS_BIC"."<>"' SAP DBTech JDBC: [258]: insufficient privilege: Not authorized.SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

 

These errors are just examples of  some the different authorisation issues you can see in HANA Studio, and each one is pointing towards a missing analytical privilege.

 

Once you have created all your models, you then have the opportunity to define your specific authorization requirements on top of the views that you have created.

 

So for example, we have a model in HANA Studio Schema and its called "_SYS_BIC:Overview/SAP_OVERVIEW"

We have a user, lets just say its the "SYSTEM" user, and when you query this view you get the error:

 

Error during Plan execution of model _SYS_BIC:Overview/SAP_OVERVIEW (-1), reason: user is not authorized.

 

So if you are a DBA, and you get a message from a team member informing you that they getting a authorisation issue in HANA Studio. What are you to do?

How are you supposed to know the User ID? And most importantly, how are you to find out what the missing analytical privilege is?

 

So this is the perfect opportunity to run an authorisation trace through the means of the SQL console on HANA Studio.

So if you follow the below instructions it will walk you through executing the authorisation trace:

 

1) Please run the following statement in the HANA database to set the DB  trace:

alter system alter configuration ('indexserver.ini','SYSTEM') SET
('trace','authorization')='info' with reconfigure;

 

2) Reproduce the issue/execute the command again/

 

3)When the execution finishes please turn off the trace as follows in the Hana studio:

alter system alter configuration ('indexserver.ini','SYSTEM') unset
('trace','authorization') with reconfigure;

 

_____________________________________________________________________________________________________________________________

 

If you would like a more detailed trace on the privileges needed you could also execute the DEBUG level trace (Usually SAP Development would request this)

 

1) Please run the following statement in the HANA database to set the DB  trace:

alter system alter configuration ('indexserver.ini','SYSTEM') SET
('trace','authorization')='debug' with reconfigure;

 

2) Reproduce the issue/execute the command again

 

3)When the execution finishes please turn off the trace as follows in the Hana studio:

alter system alter configuration ('indexserver.ini','SYSTEM') unset
('trace','authorization') with reconfigure;

 

______________________________________________________________________________________________________________________________

 

So now that you have turned the trace on and reproduced the issue, now you must turn off the trace.

 

You should now see a new indexserver0000000trc file created in the Diagnosis Files Tab in HANA Studio

 

So once you open the trace files, scroll to the end of the file and you should see something familiar to this:

 

e cePlanExec      cePlanExecutor.cpp(06890) : Error during Plan execution of model _SYS_BIC:onep.Queries.qnoverview/CV_QMT_OVERVIEW (-1), reason: user is not authorized
i TraceContext    TraceContext.cpp(00718) : UserName=TABLEAU, ApplicationUserName=luben00d, ApplicationName=HDBStudio, ApplicationSource=csns.modeler.datapreview.providers.ResultSetDelegationDataProvider.<init>(ResultSetDelegationDataProvider.java:122);csns.modeler.actions.DataPreviewDelegationAction.getDataProvider(DataPreviewDelegationAction.java:310);csns.modeler.actions.DataPreviewDelegationAction.run(DataPreviewDelegationAction.java:270);csns.modeler.actions.DataPreviewDelegationAction.run(DataPreviewDelegationAction.java:130);csns.modeler.command.handlers.DataPreviewHandler.execute(DataPreviewHandler.java:70);org.eclipse.core.commands
i Authorization    XmlAnalyticalPrivilegeFacade.cpp(01250) : UserId(123456) is missing analytic privileges in order to access _SYS_BIC:onep.MasterData.qn/AT_QMT(ObjectId(15,0,oid=78787)). Current situation:
AP ObjectId(13,2,oid=3): Not granted.
i Authorization    TRexApiSearch.cpp(20566) : TRexApiSearch::analyticalPrivilegesCheck(): User TABLEAU is not authorized on _SYS_BIC:onep.MasterData.qn/AT_QMT (787878) due to XML APs
e CalcEngine      cePopDataSources.cpp(00488) : ceJoinSearchPop ($REQUEST$): Execution of search failed: user is not authorized(2950)
e Executor        PlanExecutor.cpp(00690) : plan plan558676@<> failed with rc 2950; user is not authorized
e Executor        PlanExecutor.cpp(00690) : -- returns for plan558676@<>
e Executor        PlanExecutor.cpp(00690) : user is not authorized(2950), plan: 1 pops: ceJoinSearchPop pop1(out a)
e Executor        PlanExecutor.cpp(00690) : pop1, 09:57:41.755  +0.000, cpu 139960197732232, <> ceJoinSearchPop, rc 2950, user is not authorized
e Executor        PlanExecutor.cpp(00690) : Comm total: 0.000
e Executor        PlanExecutor.cpp(00690) : Total: <Time- Stamp>, cpu 139960197732232
e Executor        PlanExecutor.cpp(00690) : sizes a 0
e Executor        PlanExecutor.cpp(00690) : -- end executor returns
e Executor        PlanExecutor.cpp(00690) : pop1 (rc 2950, user is not authorized)

 

So we can see from the trace file that User who is trying to query from the view is called TABLEAU. TABLEAU is also represented by the User ID (123456)

 

So by looking at the lines:

 

i Authorization    XmlAnalyticalPrivilegeFacade.cpp(01250) : UserId(123456) is missing analytic privileges in order to access _SYS_BIC:onep.MasterData.qn/AT_QMT(ObjectId(15,0,oid=78787)).

&

i Authorization    TRexApiSearch.cpp(20566) : TRexApiSearch::analyticalPrivilegesCheck(): User TABLEAU is not authorized on _SYS_BIC:onep.MasterData.qn/AT_QMT (787878) due to XML APs

 

We can clearly see that TABLEAU user is missing the correct analytical privileges to access the _SYS_BIC:onep.MasterData.qn/AT_QMT which is located on Object 78787.

 

So now we have to find out who owns the Object 78787. We can find out this information by querying the following:

 

select * from objects where object_oid = '<oid>';

Select * from objects where object_oid = '78787'

 

Once you have found out the owner for this object, you can get the owner to Grant the TABLEAU user the necessary privileges to query the object.

 

Please be aware that if you find that the owner of an object is _SYS_REPO, this is not as straight forward as logging in as _SYS_REPO as this is not possible because SYS_REPO is a technical database user used by the SAP HANA repository. The repository consists of packages that contain design time versions of various objects, such as attribute views, analytic views, calculation views, procedures, analytic privileges, and roles. _SYS_REPO is the owner of all objects in the repository, as well as their activated runtime versions.

You have to create a .hdbrole file which which gives the access ( Development type of role, giving select, execute, insert etc access) on this schema. You then assign this role to the user who is trying to access the object.

 

 

Another option that is available for analyzing privileges issues was introduced as of SP9. This comes in the form of the Authorization Dependency Viewer. Man-Ted Chan has prepared an excellent blog on this new feature:

 

http://scn.sap.com/community/hana-in-memory/blog/2015/07/07/authorization-dependency-viewer

 

 

 

For more useful information on Privileges can be seen in the following KBA's:

KBA #2220157 - Database error 258 at EXE insufficient

KBA #1735586 – Unable to grant privileges for SYS_REPO.-objects via SAP HANA Studio authorization management.

KBA #1966219 – HANA technical database user _SYS_REPO cannot be activated.

KBA #1897236 – HANA: Error&quot; insufficient privilege: Not authorized &quot; in SM21

KBA #2092748 – Failure to activate HANA roles in Design Time.

KBA #2126689 – Insufficient privilege. Not authorized

KBA #2250445 - SAP DBTech JDBC 485 - Invalid definition of structured privilege: Invalid filter condition

 

 

For more useful Troubleshooting documentation you can visit:

 

http://wiki.scn.sap.com/wiki/display/TechTSG/SAP+HANA+and+In-Memory+Computing

Purpose

The purpose of this document is to instruct SAP customers on how to analyse ABAP dumps.

Overview

How to troubleshoot ABAP Dumps

Troubleshooting

When looking at an ABAP system you can sometimes come across runtime errors in Transaction ST22:

Clicking into the "Today" or "Yesterday" tab will bring up all the ABAP Runtime errors you have encountered in the past 2 days.

You can also filter the dates for a particular dump by using the filter feature:

Here are some examples of runtime errors you might see in ST22:

So from looking at these dumps, you can see

1: Category

2: Runtime Errors

3: ABAP Program

4: Application Component

5: Data & Time.

The ST22 dumps do not not really give you much information here so more information will be needed.

For more information you will then look into the Dev_W files in the transaction ST11

ST11 allows you to look further into the Dev_w files relating to the dumps in ST22:

To find the work Dev_w file that corresponds with the dump, you can see this is ST22.

Go to ST22 > click on the Runtime Errors for "Today", "Yesterday" or a filter. This will being up the specific dump you wish to analyse.

Here you will see 11 columns like so:

Here you can see the columns I have mentioned. The Work Process Index number you need is in the column named WP Index.

Once you find the dev_w index number you can then go to ST11 and find further information:

In the ST11 Dev_w files you have to match the time of the dump in ST22 with the recorded times in the Dev_w process files.

If there no useable information in the Dev_W files, the next step would be to analyse the issue from the Database side.

To analyse from the Database side:

1: Open HANA Studio in SAP HANA Administration Console View

2: Check the diagnosis trace files in accordance with the time stamp of the dump you saw previously in ST22. To do this we have to go to the Diagnosis tab in HANA Studio:

3: Check the time stamp from the ST22 dump (Date and Time), and then match this accordingly with the time in either the Indexserver.trc or nameserver.trc.

Search for the corresponding time stamp mentioned above i.e. 18/11/2015 @ 10:55:43.

Or instead of searching you could use the below SQL:

select top 500 service_name, timestamp, trace_text from m_merged_traces where service_name in ('indexserver', 'nameserver') and timestamp between '2015-11-18 10:40:00' and '2015-11-18 10:59:00'

Searching the nameserver log files can be a good indication of whether your ST22 is related to network issues, you may see errors such as:

  TrexNet          Channel.cpp(00339) : ERROR: reading from channel 151 <127.0.0.1:<host>> failed with timeout error; timeout=10000 ms elapsed [73973]{-1}[-1/-1] 2015-01-28 01:58:55.208048 e TrexNetBuffer    BufferedIO.cpp(01092) : channel 151 from <127.0.0.1:<host>>: read from channel failed; resetting buffer

If you do find some errors similar to the above, firstly check which host the error is pointing to and check whether or not this service was available at the time of the dump.

If this does not yield any useful information, the next step is to ask someone from your network team to look into this. Checking the var/logs/messages is always a great place to start.

When searching through the indexserver.trc file, you could notice some irregularities recorded here. The next step is to search this error on the SAP Service Market Place for a known KBA or Note (Learn how to search more effectively 2081285 - How to enter good search terms to an SAP search? )

Related Documents

Did you know? You can find details of common issues, fixes, patches and much more by visiting SAP moderated forums on http://scn.sap.com/docs/DOC-18971

Documentation regarding HANA installation, upgrade, administration & development is available at http://help.sap.com/hana_appliance

SAP HANA Troubleshooting WIKI: http://wiki.scn.sap.com/wiki/display/TechTSG/SAP+HANA+and+In-Memory+Computing SAP Discussion HANA: http://scn.sap.com/community/hana-in-memory/ Learn how to search more effectively 2081285 - How to enter good search terms to an SAP search?
__________________________________________________________________________________________________________

With the release of SAP HANA SPS 05, SAP announced support for VMware hypervisor, as the first technology supported to partition a SAP HANA server into smaller partitions / VMs. Meanwhile SAP has further extended its support to run SAP HANA in a virtualized / partitioned (multi-tenant) environments, by adding additional scenarios and technologies supported.

See SAP Note 1788665 and attached SAP HANA technology roadmap for running on virtualized / partitioned platforms for more information on currently supported scenarios and where to find further information on best practices and constraints which may apply.

In short, current SAP HANA support covers:

• General support for SAP HANA on VMware vSphere 5.1 in non-production
• General support for single SAP HANA VMs on VMware vSphere 5.5 in production and non-production
• Controlled General Availability for multi-VM and BW on HANA scale-out scenarios on VMware vSphere 5.5 in production
• Controlled Availability for Hitachi LPAR (single and multiple partitions) in production

On our roadmap for future support are:

• Support of larger VMs and 8-socket hardware with VMware vSphere 6

See above referenced SAP Note and slide deck for additional information and details.