Instance Administration: Parameters, Memory & Workload

What does a HANA workload class let you control, and which SQL statement creates one?

What is the role of a HANA workload mapping (`CREATE WORKLOAD MAPPING`)?

What are SAP HANA log segments?

During full-log recovery, why must you create a symbolic link after moving a HANA log volume to a temporary location?

What does the SAP HANA log segment state `Writing` indicate?

How often does SAP HANA switch to a new log segment even when activity is low, and which parameter controls it?

When the SAP HANA redo log file system fills up, what is the visible symptom?

What is the default log segment size for the indexserver (tenant transactions) in SAP HANA?

In SAP HANA's INI configuration files, what is the precedence order of the configuration layers (highest to lowest)?

What does the SAP HANA `statement_memory_limit` parameter do, and in what unit is it expressed?

How do you limit the memory consumption of an individual SAP HANA tenant database?

Which SAP HANA monitoring view shows host-level memory, CPU, and swap utilization?

When you change a HANA parameter with `ALTER SYSTEM ALTER CONFIGURATION`, what does the `WITH RECONFIGURE` clause do?

After re-enabling logging with `ALTER SYSTEM LOGGING ON` in SAP HANA, what must you do to restore recoverability?

What is the default value of the SAP HANA `lock_wait_timeout` parameter?

What two purposes do SAP HANA redo logs serve?

What is the purpose of admission control in SAP HANA?

Which SQL statement disables logging entirely in SAP HANA, and what is the main risk?

Which two SAP HANA monitoring views distinguish object (metadata) locks from row-level locks?

Which OS user owns an SAP HANA instance, and which group does it belong to?

If you manually switch SAP HANA from overwrite log mode back to normal, what must you do immediately, and why?

In SAP HANA, what does the log segment state `Free` mean (per `M_LOG_SEGMENTS`)?

Why does a newly installed SAP HANA database initially run in overwrite log mode rather than normal?

Which SAP HANA monitoring view is the primary source of information about the state of the redo log?

In SAP HANA overwrite log mode, what is the consequence for recovery?

Which SQL command reclaims (frees) backed-up log space in SAP HANA after a full-log situation, and which command must you NOT use to manage logs?

In SAP HANA, what is the difference between heap memory and shared memory?

Which SAP HANA monitoring view lists the currently open database sessions/connections?

Why does SAP HANA normal log mode permit point-in-time recovery?

Which SAP HANA log segment state appears only in replicated systems, and what does it mean?

In SAP HANA, what distinguishes the `Closed` log segment state from the `Truncated` state?

Which SQL layer keyword sets a parameter system-wide, and which sets it for a single tenant database?

What are the two SAP HANA log modes, and which parameter sets them?

What is the core idea of the procedure to recover from a full-log situation in SAP HANA?

How do you remove a customized HANA parameter so it reverts to its default value?

What is the default value of the SAP HANA `global_allocation_limit` parameter, and what does it control?

Why does the SAP HANA cockpit / DBACOCKPIT report 100% used size for log segments even when they are nearly empty?