Skip to end of metadata
Go to start of metadata

x_cons <database_name> show rte

Displays the information about the runtime environment, especially about the SAP MaxDB threads inside the SAP MaxDB kernel process. It shows information on all threads that belong to one operating system process.

Kernel Threads:
 Thread            UNIX  State         Sleep
 Name               Tid                Time
 Coordinator      17328  Sleeping
 StdIORedir       17329  Sleeping
 MemRemap         17330  Sleeping
 Clock            17357  Sleeping
 Timer            17358  Sleeping      1
 Console          17359  Sleeping
 ConsoleWork      17360  Running
 ConsoleWork      17361  Running
 Requestor        17362  Sleeping
 LegacyReque      17363  Sleeping
 TaskWorker       17364  Sleeping
 TaskWorker       17365  Sleeping
 TaskWorker       17366  Sleeping
 TaskWorker       17367  Sleeping
 TaskWorker       17368  Sleeping
 TaskWorker       17369  Sleeping
 TaskWorker       17370  Sleeping
 TaskWorker       17371  Sleeping
 MessageOutp      17389  Running


The status of special threads with thread ID is displayed. Each special thread is realized by a separate operating system thread. Special threads provide services for the user kernel threads. In special threads, the database system executes tasks whose duration cannot be predicted, such as operating system calls for reading, writing to volumes, or connection requests from clients. The database system processes special threads asynchronously to the user kernel threads. For more information on SAP MaxDB process structure and special threads, please refer to SAP MaxDB Console - Kernel Process Structure 7.8.

back to top

User Kernel Threads:
 Thread        UNIX  State       Dispatch  TaskSwitch Active Total Task
 Name           Tid               Counter     Counter  Tasks Tasks Cluster
 UKT1         17391  Sleeping          55           0      1     1 TW
 UKT2         17393  Sleeping     5467862           0      1     1 LW
 UKT3         17394  Sleeping           2           0      0     1 UT
 UKT4         17395  Sleeping    67599302    23197706     30    30 30*SV
 UKT5         17398  Sleeping    36849874           0      1     8 8*FS
 UKT6         17401  Sleeping      177521      119982     10    10 10*GC
 UKT7         17402  Sleeping     3804495     3561760     33    33 TI,32*PG
 UKT8         17403  Sleeping    84292206    10181085     16   126 125*US,IDL
 UKT9         17404  Sleeping    77546700     8546420     16   126 125*US,IDL
 UKT10        17405  Sleeping   122838736    20241545     16   126 125*US,IDL
 UKT11        17407  Sleeping    95012440     7971613     15   126 125*US,IDL


The status of user kernel threads (UKT) is also displayed. UKTs process client requests. They are the threads that use the most processor time. A database generally has several UKTs.
In general, a UKT consists of several tasks that perform various tasks. The database system controls the sequence in which the tasks run in a UKT, and can therefore avoid conflicts in access to resources. To distribute tasks optimally to the UKTs, the database system performs internal load balancing. For more information on the overview of important tasks, please refer to SAP MaxDB Console - Overview of Important Tasks.
Abbreviations of the Database Tasks in TASKCLUSTER:

  • LW: Log writer
  • PG: Pager. Task for cache monitoring and asynchronous cache displacement as well as savepoint I/O
  • EV: Event task
  • FS: Floating Service Task. FS cannot be found as a running task, it will be renamed to a db analyzer task or an event task.
  • GC: Garbage collector
  • SV: Server processes for backup I/O and special operations such as parallel index generation
  • TI: Task for timeout monitoring
  • TW: Trace writer, writes kernel traces and dumps
  • US: User tasks for executing SQL statements
  • UT: Utility task for administration tasks such as backup, recovery and so on

back to top

Processor information:
 Processors     : 4
 Processor cores: 4


The processor information is displayed ( on both Windows and Linux ).

I/O via UKTs and I/O Threads:
 Thread        UNIX  Volume               Devs.      Read     Write    Queue
 Name           Tid  Name                   No.     Count     Count  Len. Max.
 I/O0             0  knltrace                 1         0         1    0  ( 1)
 I/O0             0  /sapdb/A....ISKD0001     2         2        72    0  ( 1)
 I/O1             0  /sapdb/A....ISKD0001     2   6469721     35633    0  ( 2)
 I/O2             0  /sapdb/A....ISKD0001     2    379100     21535    0  ( 2)
 I/O3             0  /sapdb/A....ISKD0001     2     57212     14389    0  ( 2)
 I/O4             0  /sapdb/A....ISKD0001     2     14505      8992    0  ( 2)
 I/O5             0  /sapdb/A....ISKD0001     2      4110      5695    0  ( 2)
 I/O6             0  /sapdb/A....ISKD0001     2       758      2800    0  ( 1)
 I/O7             0  /sapdb/A....ISKD0001     2       177       980    0  ( 1)
 I/O8             0  /sapdb/A....ISKD0001     2       921       372    0  ( 1)
 I/O9             0  /sapdb/A....ISKD0001     2     36577       155    0  ( 1)
 I/O0             0  /sapdb/A....ISKD0002     3       777     18990    0  (144)
 I/O1             0  /sapdb/A....ISKD0002     3  13134468    118088    0  (145)
 I/O2             0  /sapdb/A....ISKD0002     3   2104806     92860    0  (145)
 I/O3             0  /sapdb/A....ISKD0002     3    686518     73169    0  (145)
 I/O4             0  /sapdb/A....ISKD0002     3    258582     54704    0  (145)
 I/O5             0  /sapdb/A....ISKD0002     3     83649     45449    0  (144)
 I/O6             0  /sapdb/A....ISKD0002     3     24992     38491    0  (144)
 I/O7             0  /sapdb/A....ISKD0002     3      8021     31822    0  (144)
 I/O8             0  /sapdb/A....ISKD0002     3      8488     26439    0  (144)
 I/O9             0  /sapdb/A....ISKD0002     3    107594     22076    0  (144)
:
 I/O0             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O1             0  /sapdb/A....DISKL001     9    192333      1008    0  ( 1)
 I/O2             0  /sapdb/A....DISKL001     9       190         3    0  ( 1)
 I/O3             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O4             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O5             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O6             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O7             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O8             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)
 I/O9             0  /sapdb/A....DISKL001     9         0         0    0  ( 0)


For each UKT and for each worker thread, it shows I/O counters.

  • Thread Name : This column displays whether this I/O is executed via UKT or I/O thread.
  • Win Tid/Unix tid: Process ID of the thread.
  • Volume Name : Name of the media which the thread is currently accessing.
  • Devs. No. : Internal volume identifier assigned in the attach order.
  • Read Count : Read count
  • Write Count : Write count
  • Queue Len. : Current length of the queue
  • Queue Max. : Maximum length of the queue

 

IO Worker Threads:
 Thread              UNIX  State        IO
 Name                 Tid               Counter
 IO001/0            17351  Sleeping     29113
 IO002/1            17352  Sleeping     2787291
 IO003/1            18083  Sleeping     2936965
 IO004/1            18084  Sleeping     3255002
 IO005/1            18085  Sleeping     2716174
 IO006/1            18086  Sleeping     2532642
 IO007/1            18087  Sleeping     3534254
 IO008/1            18088  Sleeping     2273460
 :
 IO040/1            19397  Sleeping     2968834
 IO041/1            19398  Sleeping     2960968
 IO042/1            19399  Sleeping     3307356
 IO043/1            19400  Sleeping     3414856
 IO044/1            19401  Sleeping     2585291
 IO045/1            19402  Sleeping     2993468
 IO046/1            19403  Sleeping     3113091

 37 IO Worker threads executing concurrently


The status of each concurrently active I/O worker threads and number of I/O oeprations are displayed with the name and priority. Each I/O worker can server any queue of same or higher priority jobs. Workers are picking the next queue to process frrom ticket queue.
back to top

  • No labels