C_HANATEC_17 Questions and Answers

Admission control

Capture and replay

Thread throttling

Workload classes

To store connection information on the SAP HANA XS Advanced engine

To configure failover supporting a 3-tier scenario

To configure an SAP HANA Auto-Restart Fault Recovery Support

To store connection information on the SAP HANA database client

SYSTEM users replaced by standby host

The failed worker host no longer has access to write to files

The standby host has file access

The standby host has access to write to files

The source and target database system are of the same type

The Primary Application Server can be moved to a target system Landscape

The target database is SAP Adaptive Server Enterprise (ASE)

The source system is Application Server (AS) Java-base

The SAP HANA database is revision 90 or higher

The communication port 1329 is open

Internet Explorer - Version 8 or higher

The communication port 1129 is open

Reading from the /hana/log/ volume is NOT possible

Writing to the /hana/data/ volume is NOT possible

Runing out of free space on the /hana/shared volume

Exceeding system quota on the /usr/sap volume

Aborted transactions are rolled back. 2. Open transactions are recovered. 3. Row tables are loaded into memory. 4. Column tables are loaded.

Aborted transactions are rolled back.

Row tables are loaded into memory. 3. Open transactions are recovered. 4. Column tables are loaded.

Row tables are loaded into memory. 2. Column tables are loaded. 3. Open transactions are recovered. 4. Aborted transactions are rolled back.

Row tables are loaded into memory. 2. Open transactions are recovered. 3. Aborted transactions are rolled back. 4. Column tables are loaded.

SAP HANA tenant database replication

Internal communication channels with the system PKI

HTTPS client access using the SAP HANA Web Dispatcher

Client-server communication over JDBC

System replication

Automatic savepoint

Storage replication

Standby node

The privilege remains assigned to both USER A and USER C.

The privilege is revoked from USER A, but not USER C.

The privilege is revoked from both USER A and USER C.

The privilege is revoked from USER C, but not USER A.

DMO is an inplace procedure by default, keeping the application server host.

DMO allows an easy reset during the procedure.

DMO allows a lower target release on SAP HANA database.

DMO combines several steps into one procedure.

Columns can be partitioned

Only the columns required are actually loaded to memory

They are optimized for high-volume read /write transactional processing

Data footprint is automatically reduced through compression

Check database license

Check overall database status

Check session memory

Configure system properties

Standby node

Master node

SYSTEMDB

Run the benchmarking tool parallel to the DMO to automatically adjust the number of R3load processes

Use the benchmarking tool for a productive database migration with the DMO procedure

Provide the measured table migration duration for table sequencing during benchmarking

Adjust the number of R3load processes during benchmarking and the DMO procedure

Specify the name of the table/view.

Select INFO from the System Trace Level for the Indexserver component and then select AUTHORIZATION.

Specify the user as the database user.

Select INFO from the System Trace Level for the Preprocessor component and then select AUTHORIZATION.

Request Processing and Execution Control

Relational Engines

External Interfaces

Storage Engine and Disk Storage

Role collections

Scopes

Roles

Privileges

The R3LDCTL

The Process Bucket monitor

The Log viewer

The Observer Monitor

A native, lightweight application server

A data cleansing engine

An optional engine to handle excessive data loads

A user interface

A user with CATALOG READ privileges and SELECT on _SYS_STATISTICS schema

A user with DATA ADMIN privileges and SELECT on _SYS_TELEMETRY schema

A multitenant configuration with SYSTEMDB

The target database on SAP HANA 2.0 SPS00 or higher

Having the data and log volumes on the different disks.

Obtaining the hardware certification from SAP for the existing hardware you are going to use.

Obtaining C_HANATEC_XX Certification.

Having 10 GBit/s for storage zone and 1 GBit/s for internal zone for network connectivity.

Backup destination

Progress of a backup

Backup configuration

Backup ID

When you need to extend the scale-out memory

When you need to optimize the standby node memory.

When you need to measure total memory

When you need to actively free up memory.

One table is migrated per R3load pair.

TABART is considered for the creation of R3load control files.

SAP up decides which tables to split.

De-pooling of tables is done during the procedure.

$(DIR_INSTANCE)//trace

$(DIR_INSTANCE)/backup/data

$(DIR_INSTANCE)/../global/hdb/custom/config

$(DIR_INSTANCE)/backup/log

Procedures

Sequences

Tables

Views

Automatic round-robin statement routing

Explicit read and write on the secondary system

Explicit read only on the secondary system

Implicit hint-based statement routing

Takeover time is shorter

CPU load is reduced

Network traffic is reduced

Memory consumption is lower

The CPU architecture must be identical.

An explicit read-only connect on between both systems must be available

Both must have the same SAP HANA version.

Both systems are located in the same data center.

The same number of active hosts and standby hosts must be installed

Both must have the same SAP HANA version

An explicit read-only connection between both systems must be available

The CPU architecture must be identical

SAP HANA Infrastructure Services

SAP HANA Enterprise Cloud

SAP HANA AppServices

SAP HANA DBServices

LDAP identity provider

Scopes

User group

LDAP authorization mode

Keep all partitions on different hosts.

Keep the number of partitions per table high.

Keep the number of partitioned tables low.

Keep the number of key columns low.

SAP Adaptive Server Enterprise

SAP Business Intelligence

SAP Intelligent Query

SAP Analytics Cloud