Scribd
Upload
8 views3 pages

Unit 1: Emergency Analysis and Troubleshooting

HA215-SAP HANA – Monitoring & Performance Tuning part 30

Uploaded by

kirandarekar24
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views3 pages

Unit 1: Emergency Analysis and Troubleshooting

HA215-SAP HANA – Monitoring & Performance Tuning part 30

Uploaded by

kirandarekar24
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

8/31/2021 SAP e-book

Unit 1: Emergency Analysis and Troubleshooting

Detail Description

Transaction ID Transaction ID
Update Transaction ID Update Transaction ID
Thread Status Thread State
Connection Transaction ID Transaction object ID
Connection Start Time Connected Time
Connection Idle Time (ms) Time that the connection is unused and idle
Connection Status Connection Status: 'RUNNING' or 'IDLE'
Client Host Host name of client machine
Client IP IP of client machine
Client PID Client Process ID
Connection Type Connection type: Remote, Local, History (re-
mote), History (local)
Own Connection Own connection: TRUE if own connection,
FALSE if not
Memory Size per Connection Allocated memory size per connection
Auto Commit Commit mode of the current transaction:
TRUE if the current connection is in auto-
commit mode, FALSE otherwise
Last Action The last action done by the current connec-
tion: ExecuteGroup, CommitTrans, Abort-
Trans, PrepareStatement, CloseStatement,
ExecutePrepared, ExecuteStatement, Fetch-
Cursor, CloseCursor, LobGetPiece, LogPut-
Piece, LobFind, Authenticate, Connect, Dis-
connect, ExecQidItab, CursorFetchItab, In-
sertIncompleteItab, AbapStream, TxStartXA,
TxJoinXA
Current Statement ID Current statement ID
Current Operator Name Current operator name
Fetched Record Count Sum of the record count fetched by select
statements
Sent Message Size (Bytes) Total size of messages sent by the current
connection
Sent Message Count Total message count sent by the current
connection
Received Message Size (Byte) Total size of messages/transactions re-
ceived by the current connection
Received Message Count Total message/transaction count received
by the current connection

© Copyright. All rights reserved. 52

1/3
8/31/2021 SAP e-book

Lesson: Analyzing a Suddenly Slow System

Detail Description

Creator Thread ID Thread ID who created the current connec-


tion
Created By Engine component that created the connec-
tions: Session, Planning, Repository, CalcEn-
gine, Authentication, Table Exporter, Loader,
LLVM, JSVM, IMS Search API, OLAP Engine,
Mergedog, Ping Status, Name Server, Queue
Server, SQL Stored Procedure, Authoriza-
tion, TrexViaDbsl from ABAP, HybridTable
Reorganizer, Session external
Is Encrypted Encrypted: TRUE if the secure communica-
tion is enabled (SSL enabled), FALSE, other-
wise
Connection End Time The time when the connection is closed for
history connections
Blocked Update Transaction ID Write transaction ID of the write transaction
waiting for the lock
Blocking Transaction ID Transaction object ID of the transaction hold-
ing the lock
Thread ID of Lock Owner Connection ID associated with the blocked
write transaction
Blocking Update Transaction ID Write transaction ID of the write transaction
holding the lock
Transactional Lock Type Transactional lock type
Transactional Lock Mode Transactional lock mode
Lock Wait Component Waiting for lock component
Lock Wait Name Waiting for lock ID
Timestamp of Blocked Transaction Timestamp of the blocked transaction
Waiting Record ID ID of the record on which the lock is currently
placed
Waiting Object Name Name of the object on which the lock is cur-
rently placed
Waiting Object Type Type of the object on which the lock is cur-
rently placed
Waiting Schema Name Name of the schema on which the lock is cur-
rently placed

Monitoring and Analyzing with the Top SQL Statements


Analyzing the current most critical statements running in the SAP HANA database can help
you identify the root cause of poor performance, CPU bottlenecks, or out-of-memory
scenarios. Enabling memory tracking allows you to monitor the amount of memory used by
single statement executions.

© Copyright. All rights reserved. 53

2/3
8/31/2021 SAP e-book

3/3

You might also like