Cisco Cisco Process Orchestrator 3.1 User Guide

Use the HANA Memory Garbage Collection activity to perform garbage collection on the HANA 
system, and optionally force memory management garbage collection.

Force Memory Management Garbage Collection—Enter true or false to indicate whether to force a 
memory management garbage collection. If set to true, the force returns free memory fragments in 
big blocks.

Use the HANA Memory Management activity to retrieve memory allocation details.

Memory Allocator Name—Name of the memory allocator.

Use the HANA Performance Load activity to retrieve detailed information about the current HANA 
system workload, such as connections, memory, and swapping.

Host—Host server from which to retrieve workload metrics.

Use the HANA Performance Threads activity to retrieve detailed thread information for the specified 
HANA service, such as connection details, user details, and memory.

Thread Type—Enter the type of threads to request. The default is a ‘Request’ thread.

Host—Enter the host from which to retrieve the thread information.

Service—Enter a filter to retrieve thread information for selected services.

Use the HANA Start Instance activity to start HANA daemon instance wide or on a single host.

Host—Host (<Hostname> or “Instance”) on which to start HANA daemon.

System Number—Enter the system number assigned to HANA instance. Default value is 1.

Run Level—Enter the Unix run-level.

Priority Level—Enter the priority level to indicate up/down instance priority level which instances 
should be started.

Wait Timeout—Specify the timeout in seconds to wait for an instance to start. If the timeout expires 
during a start operation, remaining instances with a higher instance priority are not started since they 
rely on the other instances to be running.

Use the HANA Stop Instance activity to stop HANA daemon instance wide or on a single host.

Priority Levl—Enter the priority level to indicate up/down instance priority level which instances 
should be stopped.

Soft Timeout—Specify the timeout in seconds to wait for a soft shutdown via SIGQUIT. If the 
timeout expires, a hard shutdown is used for the remaining instances. All functions work 
asynchronously, just triggering the operation and returning immediately.