The Kernel Threads user menu of the DBA Cockpit contains, among other things, a display of all tasks and their current status. You can end running SQL statements and tasks.
Open the DBA Cockpit (transaction DBACOCKPIT) and select .
The system displays an overview of the database tasks and information about the current state of each individual task. The following views are available:
Active Tasks
Executable Tasks
User Tasks (User task type)
System Tasks
All Tasks
You obtain the following data, among other things:
ID | Internal Task ID |
---|---|
Thread ID | Thread ID of the corresponding internal task |
Application PID | Process ID of the application program linked to the task A * before the PID indicates that the PID is on a separate server. |
Task State | Information about the current state of the database task. |
LCApps | liveCache Technology: Name of the DB Procedure |
You can refresh the display. To do so, choose
.You can automate this function by choosing
. The display for the function for the automatic refresh is above the header line of the table (green symbol: on, red symbol: off). In the field next to this, you can specify the time interval with which the automatic refresh should take place. The default value is 5 seconds.In the Task Manager, you can display detailed information about a task.
Select a task.
Choose
.Analyze the display of the task details.
liveCache Technology: The system displays the current name of the running DB procedure here, among other things.
In the Task Manager, you can activate or deactivate the internal time measurement for database activities.
You can use this function to, for example, calculate the average response times for an SQL command.
Choose
.Perform the desired time measurements.
Choose
.Evaluation of measurement data can be done via the analysis of bottlenecks using the Database Analyzer.
You can terminate an SQL statement (command) or an SQL session in the Task Manager.
Select a task.
Choose
. This terminates the SQL command currently being processed.or
Choose
. This terminates the task. If a work process of the SAP system was connected with the terminated task, the work process immediately logs on to a new task.If you want the affected SQL command to still be recorded in the performance trace after the termination, use one of these options to terminate a running action. If you terminate an action by terminating the corresponding work process (transaction code SM50), the SQL command is not recorded in the trace.
Task | State | Possible Causes | Possible Reactions |
---|---|---|---|
Log Writer | I/O wait | I/O bottleneck in the log area | |
User | I/O wait | Data cache too small Low performance of disk I/O | Monitoring Caches Monitoring I/O Operations Further analysis of Bottlenecks |
User | Vwait | SQL statements in the application cause SQL locks | Analyzing Wait Situations. |
Concepts of the Database System, Operating System Functions and Resources Used by Databases