Page tree
Skip to end of metadata
Go to start of metadata

The SAP HANA 2.0 cockpit introduced in SAP HANA 2.0 is significantly different to the SAP HANA 1.0 cockpit. This page aims to provide answers to frequently asked questions about the SAP HANA 2.0 cockpit. The page will be updated over time.

This page is intended as a convenience for users, and does not supersede product documentation, license agreements, or other formal statements by SAP about the product.

Where do I get the SAP HANA 2.0 cockpit software?

SAP HANA 2.0 cockpit is a software component released as part of SAP HANA Platform Edition 2.0. If you are an SAP customer with the rights to download SAP HANA Platform Edition 2.0 you can find SAP HANA 2.0 cockpit in the following location in the SAP Software Download Center:

Software Downloads >
  Support packages and patches tab> 
    By Alphabetical Index > 
      H > 
        SAP HANA Platform Edition > 
          SAP HANA Platform Edition 2.0 > 
             Downloads tab > 
                Browse to "HANA 2.0 Cockpit"

What are the system requirements for installing and running SAP HANA 2.0 cockpit?

Operating systems

SAP HANA 2.0 cockpit requires SUSE Linux Enterprise Server (SLES) for SAP Applications 12 or RedHat Enterprise Linux for SAP HANA 7.x.  For specific versions of those operating systems, please refer to the SAP Note 2380291 - SAP HANA 2.0 Cockpit Central Release Note.

If using SLES, please see SAP Note 2205917 - SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12.


SAP HANA 2.0 cockpit requires an Intel x64 processor or an IBM Power PC (Little Endian) processor. RedHat Enterprise Linux is not supported on Power PC. 

Memory requirements

SAP HANA 2.0 cockpit requires a minimum of 16 GB of RAM. 

Disk / storage requirements

SAP HANA 2.0 cockpit requires a minimum of 16 GB of disk space, plus additional space for the persistence storing the data generated as the cockpit runs.

Browser requirements

SAP HANA 2.0 cockpit is a browser-based application. To use it, use the latest version of Google Chrome, Mozilla Firefox, Microsoft Edge, or Apple Safari. Microsoft Internet Explorer 11 is also supported.

How do I install SAP HANA 2.0 cockpit?

SAP HANA 2.0 cockpit is installed as a single stack. Please see the install guide for complete details, available from the SAP Help Portal here. Be sure to view the documentation for the latest SP!

Do I need to run SAP HANA 2.0 cockpit on a dedicated machine?

For production use SAP recommends, but does not require, that you run SAP HANA 2.0 cockpit on a dedicated machine.

After I install SAP HANA 2.0 cockpit, what exactly do I get?

The main components of SAP HANA 2.0 cockpit are: (1) SAP HANA 2.0 cockpit application, (2) SAP HANA extended services, advanced model (XSA) runtime, and (3) SAP HANA express edition (HXE) for the persistence layer.

As previously mentioned, SAP HANA 2.0 cockpit is installed as a single stack, meaning that you must not separately install XSA or HXE. The SAP HANA 2.0 cockpit installation program takes care of installing and configuring all components for you.

Do I need to separately install XSA or HXE to operate the SAP HANA 2.0 cockpit?

No, both XSA and HXE are automatically installed and configured as part of the SAP HANA 2.0 installation.

Can I use an existing installation of XSA or HXE for the SAP HANA 2.0 cockpit?


Can I use an SAP HANA 2.0 Enterprise Edition tenant for the SAP HANA 2.0 cockpit persistence?

Yes, but it cannot be an existing tenant.  If you choose to deploy the cockpit using this method, the cockpit install program automatically creates and configures the tenant "COCKPITDB" for you.

Which versions of SAP HANA can I manage with SAP HANA 2.0 cockpit?

You can manage SAP HANA 1.0 SPS 12 databases and SAP HANA 2.0 (or later) databases with SAP HANA 2.0 cockpit.

How does the feature set of SAP HANA 2.0 cockpit compare to SAP HANA 1.0 cockpit?

SAP HANA 2.0 cockpit includes all the features of SAP HANA 1.0 cockpit. In addition, SAP HANA 2.0 cockpit allows you to manage and monitor multiple HANA systems from a single location.

How does the feature set of SAP HANA 2.0 cockpit compare to SAP HANA studio?

While SAP HANA 2.0 cockpit is a full-featured administration tool, there are a handful of SAP HANA studio Administration perspective that are not available from SAP HANA 2.0 cockpit.

How many databases can I manage with one SAP HANA 2.0 cockpit instance?

The answer depends on the SAP HANA 2.0 cockpit hardware and on activity levels of your databases, but a single SAP HANA 2.0 cockpit instance can manage thousands of resources.

How many users can use a single SAP HANA 2.0 cockpit instance?

The answer will depend on the SAP HANA 2.0 cockpit hardware and on the user activity, but a single SAP HANA 2.0 cockpit instance supports tens of concurrent users in its initial release.

  • No labels


  1. thanks for such helpful wiki docs !

    starting new with HANA cockpit 2.0 SP11 e.g. with backup scheduling for a tenantDB (AS-Java) or backup scheduling for the systemDB,

    we struggle with the requirements for backup job scheduling.

    In every HANA database, xs-engine must be activated and xs-job scheduling must be activated - the documentation is poor and you waste a lot of valuable time checking:

    1) which XS engine is installed (XS-C or XS-A) and how can you can recognize, whether it is activated

        how check xs-engine for different tenantDB ? - must be enabled in each tenantDB + systemDB ?

    2) is the xs job scheduling activated? - how do you check this?

    3) what authorities must be assigned to a backup-user, especially the HANA cockpit security + authorizations is not easy

    4) create backup-user in each HanaDB - each tenant-DB ! 

    5) missing Hana-User authority is resulting in missing (not shown) options in HANA-Cockpit ! (e.g. "manage backup" is not shown when missing authority)

    6) does a managed HanaDB needs the XS-A additionally or is backup-scheduling possible with XS-C engine?

    7) (in cockpit view "resource directory")

         trying to change an initially maintained "user credentials" with "manage credentials" (edit an already created and authority-assigned backup-user)

         causing error "Unable to validate credentials"  ??


    additional info: 

    the error  "Unable to validate credentials"  is caused when creating Backup-User and mark/select the option "disable ODBC/JDBC access" (within User in TenantDB) 

    after deselect that option "disable ODBC/JDBC access" the usage of that user in HANA-Cockpit works fine.

  2. Hi Christoph - Thank you for your feedback.  I'll pass along the information to our User Assistance colleague to enhance the documentation.  Here are the answers to your questions:

    1) You can check the different services that are running by clicking the "Database Status" tile in the System Overview page.  It takes you to the "Manage Services" app.  You can do this for tenants and SYSTEMDB  and that's where you'd check which XS engine is running.  It needs to be enabled for each database.

    2) The "Manage Services" app will show you that.  If you need to enable it, you can issue a SQL statement as described here:

    3) Please refer to this document for the authorizations:

    4) I understand this to be a documentation error.

    5) That's the expected behaviour and it's a new feature in later versions of the HANA cockpit.  We had many requests to hide tiles where the cockpit user doesn't have the privilege to perform that operation.

    6) You need the XSC engine.

    7) As you noticed, you need ODBD/JDBC enabled for a database user.

    I hope this information helps you!

    José Ramos
    SAP HANA Product Management
    SAP Labs Canada

  3. Hi Jose, thanks for your reply, 

    to 1) + 2) 

    after executing that SQL-statements to systemDB and to tenantDB as described in the help-doc, (i did SQL-execution within HANA_studio in sql-console, and checked after that so the value was "true") 


    within HANA-Cockpit trying to setup a backup-jobscheduling => "Backup schedules", after configuring the jobschedule-setup for one job, it was shown in the header-lines "The schedule job is not enabled" 

    why ?

    after going => "Backup configuration" => in section "Data Backup Scheduler" there was shown a switch that shows "off" => so i do "edit" in "Data Backup Scheduler" and switch-on that function again. 

    is a different config needed (not only the mentioned sql-statement to setup XS-engine and to setup xs-scheduler) or was this a matter of delayed or not already finished reload of the HANA_configuration within the HANA-cockpit ? (i am able to deliver detailed hardcopys, if needed) 


  4. the HANA cockpit 2.0 itself has a HANA systemDB only,

    Trying to activate XS-engine and XS-Jobscheduling with SQL_Statements, did not succeed ?  ( 0 records affected )

    but trying to setup the backup-jobscheduling for HANA-Cockpit itself, -  a message comes up: 

    "This database is running without an XS Engine. Therefore it is not possible to schedule backups, and any already scheduled backups will not be executed.

    For more information, see the SAP HANA Database Administration Guide."  ( the docs are only according to XS-C engine ?)


    as i know, the HANA-cockpit comes with an XS-A engine,  How to activate XS-A engine for jobscheduling ? 

    1. Hi Christoph - you just need to enable the XS Classic engine.  Do you see it running in the Manage Services application?


  5. Hi Christoph, XSC is required for job scheduling, so activating it is required.

    1. i am talking about the HANA_Cockpit 2.0 itself, trying to schedule the systemDB backup of the HANA_Cockpit itself.

      this tool comes (as far as i know), with a HANA-Express DB ? and did not have a XS-C Engine ? 

  6. Hi Christoph,

    It depends. HANA Cockpit can be also installed as a tenant in an existing HANA system. In this case it can be scheduled and backed up like every other tenant database, provided XSC is activated. If you have cockpit installed standalone on HANA express, here is an article how to schedule backups for HANA express: .