Warning, this type of functionfacilitates, via a user interface that is homogenous with the software, the launch of procedures devolved to a database administrator. It is constructed to be launched by such an administrator (normally called DBA).
It therefore assumes a prior knowledge of database functioning and optimization in order to be used profitably.
However, an inappropriate usage of the function may pose serious performance problems and place the security of the software usage in peril.
This function is used to view the processes and the locks corresponding to these processes in the database.
These elements are presented in two tabs : the first provides a list of the processes, the second gives the list of locks.
The function is used to identify the blocking locks. After verification of the blocking and blocked processes, it will be possible to kill the blocking process.
Presentation
Used to identify the characteristics of the database used.
Close
Fields
The following fields are present on this tab :
| Nom de la base de données |
| Numéro de version de la base de données |
| Description de la version de la base de données |
Close
Presentation
On entry to this function, the processes connected to the current folder are displayed by default.
If the processes in all the solution folders are required, it is necessary to modify the Processes filter.
If the process display sort is to be modified, it is necessary to modify the Process sort and Direction.
It will then be necessary to refresh the display using the bottom of the screen.
This screen is made up of two sections :
This first section contains a grid that presents the processes running on the database.
This section is used to modify the filter options and the process sort.
The filter is used to restrict the processes display and as a result the display of the locks.
It will be necessary to refresh the display using the button at the bottom of the scree to take into account the new display options.
Close
Fields
The following fields are present on this tab :
| Identifier for the process in the database |
| Name of the database user |
| Nom de la base de données |
| Connection date |
| Connection time |
| Status of the connection |
| Program in the process of execution. |
| Command actually executed |
| Date of the last execution for an SQL instruction on the connection |
| Time of the last execution for an SQL instruction on the connection |
| Name or the computer or the machine (defined by the operating system) from which the user is connected. |
| Identifier for the process on the machine (defined by the operating system). |
| Total UC time for the execution of the process |
| Number of cache pages for the procedures actually allocated to the processes. A negative number indicates that the process liberates the memory allocated to another process. |
| Total number of write and read operations on the disk for the process. |
| Identifier for the blocking process |
Block number 2
| Used to restrict or not the list of processes. It is possible to display
|
|   |
| Used to sort the list of processes. There is the possibility to specify the sense of the sort. |
|   |
Close
Functions accessed by right click on the grid
Fields
The following fields are present in this window :
Block number 1
| Identifier for the process in the database |
| Nom de la base de données |
| Name of the database user |
| Date of the last execution for an SQL instruction on the connection |
| Time of the last execution for an SQL instruction on the connection |
| Name or the computer or the machine (defined by the operating system) from which the user is connected. |
Last SQL instruction
| Text for the last SQL instruction executed on the connection |
Close
Used to view the text for the last SQL instruction for the process.
Used to immediately kill the selected process.
Only a database user having the role sysadminor processadmincan carry out this action. It will therefore be necessary to give the name of the user having sufficient rights plus their password.
Fermer
Presentation
The second tab displays the list of locks in place and pending on the database that corresponds to the processes in the first tab.
This is used to distinguish in the case of blocking locks:
Close
Fields
The following fields are present on this tab :
| Identifier for the process in the database |
| Nom de la base de données |
| Name of the database user |
| Name or the computer or the machine (defined by the operating system) from which the user is connected. |
| Owner of the object currently being locked. |
| Name of the object or the transaction currently being locked. |
| Nom de l'index en cours de verrouillage. |
| Locked resource type. Possible values: 1. NUL = NULL resource (not used). |
| Textual description of a locking resource |
| Locking request method. This column corresponds to the locking method of the requestor and represents the method granted, the conversion method or the pending method. Possible values: 0 = NULL. No access is accorded to the resource. Serves as reserved space. |
| Status of the locking request. Possible values: 1 = Granted |
| Identifier for the blocking process |
Close
Functions accessed by right click on the grid
Fields
The following fields are present in this window :
Block number 1
| Identifier for the process in the database |
| Nom de la base de données |
| Name of the database user |
| Date of the last execution for an SQL instruction on the connection |
| Time of the last execution for an SQL instruction on the connection |
| Name or the computer or the machine (defined by the operating system) from which the user is connected. |
Last SQL instruction
| Text for the last SQL instruction executed on the connection |
Close
Used to view the text for the last SQL instruction for the process.
Fermer
This button, also accessible using the short cut, used to refresh the display of the tabs. |
In addition to the generic error messages, the following messages can appear during the entry :
Required information cannot be recovered from the solution.xml file. The parameterization of the solution is incomplete and it is necessary to complete it using the configuration console.