Skip to main content

Connecting HANA Systems

HANA systems are connected via a secondary database connection of the master system. To create this connection transaction DBCO can be used. Starting from basis release 7.02, primarily transaction DBACOCKPIT can be used.

The SAP notes 2000003, 1597627 and 1640741 give detailed help for the preconditions which need to be fulfilled by the master system to be able to connect to a HANA system. A brief summary of the preconditions:

  • The SAP HANA Client needs to be installed

  • The SAP HANA DBSL needs to be installed

  • The SAP kernel must be at least of release 7.20

  • The system must be Unicode or on single code page 1100

For the secondary database connection, a privileged HANA database user is required. Users created as RESTRICTED users cannot be used. To use all features of the Snow Optimizers, the database user needs to have the system privileges LICENSE ADMIN and USER ADMIN.

If a dedicated new user is created in HANA for the database connection, please note that a password change is necessary before the first use. Alternatively, the SQL command

ALTER USER <USERNAME> DISABLE PASSWORD LIFETIME

can be used.

Starting from version 2.1 of the Snow Optimizer, instead of the system ID of the HANA system, the database name is used to build the display ID of the HANA system. This makes it possible to connect to the single tenants of a HANA database. Please note that this could result in the change of the display ID of an already connected HANA systems. To build the display ID, only the first seven characters of the database name in conjunction with the installation number of the HANA system are used. This combination must be unique in the system tree of the Snow Optimizer.