The SAP HANA database explorer is the primary tool within the SAP BTP cockpit used for in-depth database administration and development tasks. It provides direct access to the database's diagnostic files, allowing an administrator to view, download, and analyze various trace files (e.g., index server, compile server traces) to diagnose system-level errors.

The SQL trace analyzer is a specialized feature within the SAP HANA database explorer. It is specifically designed to parse and analyze SQL trace files (.sqltrace), providing detailed insights into the performance and execution plans of SQL statements, which is crucial for diagnosing application-level performance errors.

B. SAP HANA Cloud Central: This tool is used for the high-level lifecycle management of SAP HANA Cloud instances, such as provisioning, starting, stopping, and monitoring overall status, not for detailed file-level diagnostics.

D. Full system information dump: This is a collection of diagnostic files and system information (the data itself), which is generated for troubleshooting. It is not a tool used to perform the analysis.

1. SAP HANA Cloud Administration Guide

"Monitoring and Administration Tools": This guide explicitly lists the SAP HANA database explorer as a key tool for database administration. It states

"You can use the SAP HANA database explorer to... Access diagnosis files for troubleshooting purposes." This directly supports the use of the database explorer for analyzing trace files.

2. SAP HANA Cloud Administration Guide

"Analyzing Traces": This section details the process of trace analysis. It specifies

"You can analyze SQL traces... in the SQL trace analyzer

which is part of the SAP HANA database explorer." This confirms the SQL trace analyzer as a specific tool for this purpose.

3. SAP HANA Cloud Administration Guide

"SAP HANA Cloud Central": The documentation describes this tool's purpose as being the "central entry point for creating and managing SAP HANA Cloud instances

" confirming it is for lifecycle management

not in-depth analysis.

4. SAP HANA Cloud Administration Guide

"Collecting Diagnosis Information": This section describes how to "collect all diagnosis information and logs... into a single compressed file (full system information dump)." This clarifies that the dump is the output of a collection process

not an analysis tool.

The SAP HANA cockpit's "Manage Services" application, when connected to the SYSTEMDB, provides an interface to manage all services across the SAP HANA system, including those of tenant databases. An administrator can stop a tenant's index server (B) as a routine administrative task to take the tenant offline for maintenance. Similarly, the compile server (D) can be stopped for troubleshooting or configuration; its tasks are then temporarily handled by the index server. Both of these actions can be performed without disrupting the administrator's active session in the SAP HANA cockpit.

A. Web dispatcher: Stopping the web dispatcher service would terminate the user's HTTP(S) connection to the SAP HANA cockpit, as the cockpit itself is a web-based application served by this process.

C. XS engine: The classic XS engine (hdbxsengine) is a service for the deprecated SAP HANA XS Classic model. It is not a standard, default service in modern SAP HANA 2.0 systems and may not be present.

1. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section 6.3.3

"Managing Services in SAP HANA Cockpit". This section explicitly warns: "If you stop the system-internal web dispatcher

you will no longer be able to access SAP HANA cockpit and other HTTP-based tools." This supports why option A is incorrect in this context.

2. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section 2.2

"Server Components of the SAP HANA Database". The guide describes the compile server's role and notes: "If the compile server is not available

the index server takes over these tasks." This confirms that stopping the compile server is a non-critical operation

making option D a correct answer.

3. SAP HANA Tenant Databases Operations Guide 2.0 SPS07

Section 3.2

"Starting and Stopping Tenant Databases". This guide details that a tenant database is stopped by stopping its services. The primary service for a tenant is the index server

confirming that stopping an index server (of a tenant) is a standard administrative procedure (Option B).

To ensure a transactionally consistent state for a storage-level data snapshot, SAP HANA must first be prepared. This preparation involves the creation of an internal database snapshot. This internal snapshot freezes the database at a specific point in time, creating a consistent image. Once this internal snapshot is active, the external storage system can perform its snapshot operation. After the storage snapshot is complete, the internal database snapshot is removed, and normal database operations resume. This two-phase process guarantees that the external snapshot represents a valid and recoverable state of the database.

A. Execute the hdbbackupdiag tool.

This tool is used for checking the integrity and availability of existing backups after they have been created, not for ensuring consistency during the snapshot creation process.

B. Create a fallback snapshot.

A fallback snapshot is a specific use case for a snapshot, created before a system update to enable a quick rollback. It does not describe the underlying mechanism for ensuring consistency.

D. Trigger a savepoint.

While a savepoint is a critical part of the process to flush changed data to disk, the creation of an internal database snapshot is the specific, overarching mechanism that coordinates the entire procedure.

1. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS 07

Section: 11.3.3.1 Database Snapshots

Content: "To ensure data consistency

before a storage snapshot is created

the SAP HANA database must be prepared. Preparing the SAP HANA database for a storage snapshot involves creating an internal database snapshot. The internal database snapshot represents a consistent state of the database at a single point in time." This section explicitly states that an internal database snapshot is the mechanism for ensuring consistency.

2. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS 07

Section: 11.3.3.1.1 Creating a Storage Snapshot

Content: The guide details the workflow: "1. An SQL statement BACKUP DATA CREATE SNAPSHOT prepares SAP HANA for the storage snapshot... 2. SAP HANA creates an internal database snapshot... 3. SAP HANA freezes all write I/O operations... 4. The storage snapshot is created... 5. The storage snapshot is confirmed... 6. SAP HANA discards the internal database snapshot and resumes normal operation." This confirms that the internal snapshot (Option C) is the central mechanism.

3. SAP Note 2039883 - FAQ: SAP HANA database backup & recovery

Section: 10. Storage Snapshots

Content: The note clarifies the process: "In order to create a consistent storage snapshot

the database has to be prepared. This is done by creating a database snapshot... The database snapshot is a transactionally consistent state of the database." This reinforces that the internal database snapshot is the method to achieve consistency for the external storage snapshot.

The multidb.ini configuration file, located in the system database, is used to manage the multitenant database environment. It contains a specific section, [tenantinifilesblocklist], where a system administrator can list configuration parameters. Any parameter added to this blocklist cannot be modified by a tenant database administrator. This mechanism is crucial for preventing changes to critical system properties that could affect the stability, security, or performance of the overall SAP HANA system.

B. attributes.ini: This file is used for internal system attributes and is not the designated location for managing tenant configuration restrictions.

C. global.ini: This file sets system-wide default values for all services, but tenants can typically override these settings unless explicitly blocked via multidb.ini.

D. indexserver.ini: This file contains configuration parameters specific to the indexserver service; it does not control system-level restrictions imposed on tenants.

1. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS 07: In the section "Tenant-Specific Configuration"

it is detailed that the system administrator can restrict tenant administrators from changing certain parameters. The guide states

"You do this by adding the parameters to the tenantinifilesblocklist section of the multidb.ini file in the system database." (Found in Chapter 10: "Administering Multitenant Database Containers").

2. SAP HANA Security Guide for SAP HANA Platform 2.0 SPS 07: The guide discusses securing multitenant environments. It references the ability of the system administrator to enforce configuration settings on tenants

which is implemented through the blocklist mechanism in the multidb.ini file to maintain a secure and stable landscape. (Found in Chapter 6: "Securing Multitenant Database Containers").

When a tenant database is renamed in SAP HANA, the operation requires the database to be temporarily taken offline and then brought back online. The system automatically stops and then restarts the tenant database to apply the name change. As part of this process, the physical directory paths on the file system corresponding to the tenant's data, log, and trace files are renamed to reflect the new database name, ensuring consistency between the logical database name and its physical storage structure.

B. The tenant database backups are renamed.

This is incorrect. The backup catalog is updated to associate existing backups with the new database name, but the physical backup files themselves are not renamed.

D. The tenant database is unloaded from memory.

While stopping the database does unload it from memory, this option is less precise. The official process is a full stop and restart, making "stopped" the more accurate and direct description of the action.

1. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS 07

Section 3.3.5 Rename a Tenant Database.

Page 121: "The tenant database is stopped and restarted as part of the renaming process." (Supports Answer A).

Page 121: "The physical paths to the tenant's data and log volumes are renamed." (Supports Answer C

as trace directories are part of the physical volume structure).

Page 121: "The backup catalog is updated so that you can still use old backups of the database for recovery." (Explains why Answer B is incorrect).

The SAP HANA cockpit provides a backup scheduler that allows administrators to define and automate backup policies. This scheduler is specifically designed for creating file-based data backups. The types of data backups that can be scheduled as part of a recurring backup policy are Complete Data Backups (full), Incremental Data Backups, and Differential Data Backups. These options enable administrators to implement a comprehensive and efficient backup strategy directly from the central administration tool.

A. Data snapshot: While data snapshots can be created using the SAP HANA cockpit, they are not a schedulable backup type within the standard backup policy scheduler, which focuses on file-based backups.

D. Log backup: Log backups are not scheduled in the same manner as data backups. They are configured to run automatically and are triggered by events, such as a log segment becoming full or a configurable timeout, rather than being scheduled for a specific time.

1. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section: "Scheduling Backups with the SAP HANA Cockpit". This section details the process of creating a backup policy and explicitly lists "Complete Data Backup"

"Differential Data Backup"

and "Incremental Data Backup" as the schedulable backup types.

2. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section: "Log Backups". This section explains

"Log backups are written automatically... You cannot schedule log backups. You can only enable or disable automatic log backups." This confirms that log backups are not managed by the backup scheduler.

3. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section: "Data Snapshots". This part of the documentation describes the manual creation of data snapshots on the storage level. It does not mention them as an option within the cockpit's recurring backup policy scheduler.

The recoverSys.py script is the designated SAP HANA tool for reinitializing the system database (SYSTEMDB) in a multi-tenant environment. This tool is used in a critical recovery scenario where the SYSTEMDB's data and log volumes are lost or corrupted, and a recovery from a backup is not feasible. Executing this script effectively creates a new, clean system database, allowing the administrator to subsequently recover or re-register the tenant databases.

A. hdbrecovercheck: This command-line tool is used exclusively to verify the integrity and usability of existing SAP HANA data backups before attempting a recovery; it does not perform any recovery or reinitialization actions.

C. hdbmdcutil: This utility is used for administrative tasks on tenant databases within a functioning multi-tenant system, such as creating, dropping, or altering tenants. It does not operate on or reinitialize the system database itself.

D. RecoverUtil.py: This is not a recognized or standard SAP HANA command-line tool. The correct and officially documented script for reinitializing the system database is recoverSys.py.

1. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section: 11.5.1.3 Recovering the System Database with recoverSys.py. The guide states

"If the data and log areas of the system database are lost and can't be recovered from a backup

you can re-create the system database using the Python script recoverSys.py." This directly confirms its use for a non-recoverable system database.

2. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section: 11.5.2.1 Checking Recoverability of Data Backups with hdbrecovercheck. This section details the function of hdbrecovercheck

confirming it is a verification tool: "You can use the tool hdbrecovercheck to check whether a data backup can be used for a recovery."

3. SAP HANA Administration Guide for SAP HANA Platform 2.0 SPS07

Section: 3.3.2.2 Administration of Tenant Databases with hdbmdcutil. This section describes the purpose of hdbmdcutil: "You can use the command line tool hdbmdcutil to perform administrative tasks on tenant databases." This clarifies it is for tenant management

not SYSTEMDB recovery.

According to the official SAP HANA Cloud documentation, the default retention period for complete data backups is 14 days. This policy ensures that recent recovery points are available for restoration while managing storage consumption. This setting applies to both automatic and manual backups unless explicitly changed by an administrator. The system automatically deletes backups older than this 14-day period to free up storage space.

A. 3 weeks: This is not the default retention period; it would require manual configuration to extend the duration to 21 days.

C. 1 week: This is shorter than the standard default retention period of 14 days set for SAP HANA Cloud backups.

D. 4 weeks: This is a longer retention period than the default and would need to be explicitly configured by an administrator.

1. SAP Help Portal

SAP HANA Cloud

SAP HANA Database Administration Guide: In the section "Managing Backups in SAP HANA Cloud

" the documentation states

"By default

complete data backups are retained for 14 days." (Source: SAP HANA Cloud

SAP HANA Database Administration Guide > Managing Backups in SAP HANA Cloud)

2. SAP Help Portal

SAP HANA Cloud Backup and Recovery: This guide reinforces the default policy. In the "Backup Retention" section

it specifies

"The default retention period for backups is 14 days. Backups older than 14 days are automatically deleted." (Source: SAP HANA Cloud Backup and Recovery > Backup Retention)

The "Troubleshoot Unresponsive System" application within the SAP HANA cockpit is the designated tool for investigating a system that is offline, hung, or otherwise unresponsive to normal SQL connections. This application provides functionality to connect to the sapstartsrv service on the host, even when the database itself is not responding. It allows an administrator to trigger the creation of critical diagnostic files, such as runtime dumps (RTE dumps), which are essential for performing a root cause analysis of the unresponsive state. This makes it the primary tool for this specific emergency scenario.

A. Alert Monitor: This application requires an active connection to a running database to retrieve and display alerts, making it unsuitable for an offline system.

B. Full System Information Dumps: While this collects comprehensive diagnostic data, the "Troubleshoot Unresponsive System" app is the specific tool designed to initiate diagnostics when the system is inaccessible.

D. Performance Monitor: This tool is used to analyze performance metrics (CPU, memory, etc.) of an online and operational system and cannot function if the system is offline.

1. SAP HANA Cockpit Administration Guide

section "Troubleshooting an Unresponsive System". The documentation states

"If an SAP HANA system is unresponsive

you can use the Troubleshoot Unresponsive System app in the SAP HANA cockpit to investigate the situation. For example

you can create runtime dumps to analyze the current state of all server processes." (SAP Help Portal

SAP HANA Platform 2.0 SPS 07).

2. SAP HANA Administration Guide for SAP HANA Platform

section "Troubleshooting Unresponsive Systems". This guide details the process

noting that tools like the hdbcons command line or the SAP HANA cockpit's "Troubleshoot Unresponsive System" app are used to trigger runtime dumps when a system is hung. (SAP Help Portal

SAP HANA Platform 2.0 SPS 07).

In the SAP HANA Cloud administration tools, such as the SAP HANA cockpit or SAP HANA Cloud Central, the "Manage Services" application displays the services for a database instance. This view distinguishes between services dedicated to the tenant database and services that are shared across the landscape. The Data Provisioning (DP) server, which enables Smart Data Integration (SDI), and the Deployment Infrastructure (DI) server, which manages SAP HANA Deployment Infrastructure (HDI) containers, are explicitly listed as shared services. These services provide centralized functionalities that can be utilized by multiple applications or tenants.

A. Compile server: The compile server is not a standalone service in the SAP HANA Cloud architecture; its functionality for compiling SQL and procedures has been integrated into the index server.

B. Name server: The name server is a fundamental system-level service that manages the overall landscape topology, but it is not categorized as a "shared" service within a specific tenant's service view.

1. SAP Help Portal

SAP HANA Cloud

SAP HANA Database Administration Guide: Monitoring Services. This official guide explicitly states

"The SAP HANA deployment infrastructure (DI) server and the Data Provisioning Server are shared services. All other services run on the database." This directly confirms that the DI server and DP server are the shared services displayed.

2. SAP Help Portal

SAP HANA Cloud

SAP HANA Database Administration Guide: SAP HANA Service Types. This section details the various services. It describes the dpserver for data provisioning and the diserver for the SAP HANA Deployment Infrastructure

while noting that the compileserver is not present in SAP HANA Cloud.