GV$OB_PROCESSLIST|V4.4.2| docs|Distributed Database

GV$OB_PROCESSLIST

Last Updated：2026-03-06 07:02:41 Updated

Note

This view is available starting with V4.0.0.

Purpose

The GV$OB_PROCESSLIST view displays the session information of all OBServer nodes where the tenant is located.

Columns

Column	Type	Nullable	Description
SVR_IP	varchar(46)	NO	The IP address of the server.
SVR_PORT	bigint(20)	NO	The port number of the server.
SQL_PORT	bigint(20)	NO	The port number of SQL.
ID	bigint(20) unsigned	NO	The session ID. In direct connection mode: This field indicates the server session ID. In ODP mode: When the configuration parameter `client_session_id_version = 2` is set in ODP, this field indicates the client session ID. When `client_session_id_version = 1` is set, this field indicates the server session ID.
USER	varchar(32)	NO	The username.
HOST	varchar(128)	NO	The IP address and port number of the client.
DB	varchar(128)	YES	The name of the database to which the session is connected.
TENANT	varchar(128)	NO	The name of the tenant to which the session is connected.
COMMAND	varchar(4096)	NO	The type of the command currently being executed.
TIME	bigint(20)	NO	The time when the current command is executed, in seconds. If the command is retried, this field is reset to 0 and recalculated.
TOTAL_TIME	bigint(20)	NO	The total time when the current command is executed, in seconds. If the command is retried, this field is not reset.
STATE	varchar(128)	YES	The state of the current session.
INFO	varchar(262143)	YES	The command currently being executed.
PROXY_SESSID	bigint(20) unsigned	YES	The proxy session ID. This field is displayed only when the client is an OBProxy.
MASTER_SESSID	bigint(20) unsigned	YES	The ID of the master session. This field is used to link multiple sub-sessions of the same SQL statement.
USER_CLIENT_IP	varchar(46)	YES	The IP address of the client.
USER_HOST	varchar(128)	YES	The hostname of the client.
RETRY_CNT	bigint(20)	NO	The number of retries for the current command.
RETRY_INFO	bigint(20)	NO	The retry information of the current command. This field usually contains the error code of the last retry.
SQL_ID	varchar(32)	NO	The SQL ID.
TRANS_ID	bigint(20) unsigned	NO	The transaction ID.
THREAD_ID	bigint(20) unsigned	NO	The thread ID.
SSL_CIPHER	varchar(4096)	YES	The name of the encryption cipher.
TRACE_ID	varchar(64)	YES	The trace ID.
TRANS_STATE	varchar(32)	YES	The transaction state. If no transaction is active for the session, this column is empty. `IDLE`: The transaction is idle. This indicates that no transaction is active. `ACTIVE`: The transaction is explicitly started. This state is set when you execute the `START TRANSACTION` or `BEGIN` statement. `IMPLICIT_ACTIVE`: The transaction is implicitly started. In `autocommit = on` mode, the transaction is started after you execute a DML statement. `ROLLBACK_SAVEPOINT`: The transaction is being rolled back to a savepoint. `IN_TERMINATE`: The transaction is being terminated. This state is set when the transaction is terminated by internal reasons or by user-initiated statements such as `COMMIT` or `ROLLBACK`. `ABORTED`: The transaction is internally aborted or rolled back due to an exception. `ROLLED_BACK`: The transaction has been rolled back. `COMMIT_TIMEOUT`: The transaction commit times out. `COMMIT_UNKNOWN`: The transaction commit result is unknown. `COMMITTED`: The transaction has been successfully committed.
ACTION	varchar(4096)	YES	The name of the current operation, set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.
MODULE	varchar(4096)	YES	The name of the current operation, set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.
CLIENT_INFO	varchar(4096)	YES	The information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.
LEVEL	bigint(20)	NO	The end-to-end tracing monitoring level of the session. For example, 1 indicates the diagnostic information of level 1. Note This column is available starting with V4.2.1.
SAMPLE_PERCENTAGE	bigint(20)	NO	The end-to-end tracing sampling frequency of the session. For example, 50 indicates that 50% of the diagnostic information is sampled. Note This column is available starting with V4.2.1.
RECORD_POLICY	varchar(32)	NO	The end-to-end tracing recording strategy of the session. The following three strategies are supported: ALL: All trace points generated when tracing is enabled are printed to the log file. The trace points are printed to the log file at the end of each span. ONLY_SLOW_QUERY: Only the trace points generated when tracing is enabled for slow queries are printed to the log file. Other trace points are discarded. For this recording strategy, the trace log is printed after the request is determined to be a slow query. In the Proxy, the root span (at the transaction level) is printed only when a slow query is detected. SAMPLE_AND_SLOW_QUERY: All trace points generated when tracing is enabled are printed to the log file if the trace points meet the following conditions: When the hidden parameter `_print_sample_ppm` is used for sampling at a 0.0001% probability, the trace point is printed to the log file only if the sampling result is selected. The trace point meets the conditions for printing in the ONLY_SLOW_QUERY mode. For this recording strategy, the trace log is not printed at the end of the span. If the trace point meets condition 1, the trace log is forcibly printed at the client and the information is passed to the subsequent components in the chain. If the trace point meets condition 2, the trace log is printed at the same time as in the ONLY_SLOW_QUERY mode. Note This column is available starting with V4.2.1.
LB_VID	bigint(20)	YES	If the database is directly connected to the load balancer in a public cloud environment, this column displays the VPC ID of the load balancer. Otherwise, this column is empty. Note This column is available starting with V4.2.1.
LB_VIP	varchar(46)	YES	If the database is directly connected to the load balancer in a public cloud environment, this column displays the IP address of the client connecting to the load balancer. Otherwise, this column is empty. Note This column is available starting with V4.2.1.
LB_VPORT	bigint(20)	YES	If the database is directly connected to the load balancer in a public cloud environment, this column displays the port of the client connecting to the load balancer. Otherwise, this column is empty. Note This column is available starting with V4.2.1.
IN_BYTES	bigint(20)	NO	The inflow traffic of the session, in bytes. Note This column is available starting with V4.2.1.
OUT_BYTES	bigint(20)	NO	The outflow traffic of the session, in bytes. Note This column is available starting with V4.2.1.
USER_CLIENT_PORT	bigint(20)	NO	The client address information. Note For V4.3.x, this column is available starting with V4.3.0. For V4.2.x, this column is available starting with V4.2.3.
PROXY_USER	varchar(128)	YES	When a proxy user logs in, the name of the proxy user is returned. When a non-proxy user logs in, this column is empty. Note For V4.3.x, this column is available starting with V4.3.2. For V4.2.x, this column is available starting with V4.2.3.
SERVICE_NAME	varchar(64)	YES	The service name of the session that created this session. If the value is `NULL`, the session was not created by a service name. Note For V4.3.x, this column was introduced in V4.3.1. For V4.2.1, this column was introduced in V4.2.1 BP9. For other V4.2.x versions, this column was introduced in V4.2.4.
TOTAL_CPU_TIME	bigint(21)	NO	The CPU time consumed by the current command, in seconds Note For V4.3.x, this column was introduced in V4.3.1. For V4.2.1, this column was introduced in V4.2.1 BP5.
TOP_INFO	varchar(262143)	YES	The information of the top PL statement of the executing SQL statement. Note For V4.3.x, this column was introduced in V4.3.3. For V4.2.1, this column was introduced in V4.2.1 BP9.
MEMORY_USAGE	bigint(20)	YES	The size of memory occupied by the current SQL statement, in bytes Note For V4.4.x, this column was introduced in V4.4.0. However, it is not effective at present, and the default value is `NULL`.
TOP_TIME	double	NO	The top_time column in the PL scenario indicates the total execution time of the PL statement. Note For V4.4.x, this column was introduced in V4.4.1.
TOP_TRACE_ID	varchar(64)	YES	The traceid of the top statement. Note For V4.4.x, this column was introduced in V4.4.1.

Sample query

Query the session information of all OBServer nodes where the tenant is located.

obclient [oceanbase]> SELECT * FROM oceanbase.GV$OB_PROCESSLIST LIMIT 1\G

The query result is as follows:

*************************** 1. row ***************************
           SVR_IP: 6.12.xxx.xxx
         SVR_PORT: 2882
         SQL_PORT: 2881
               ID: 3221596574
             USER: root
             HOST: 100.xx.xxx.xxx:27210
               DB: oceanbase
           TENANT: mysql001
          COMMAND: Query
             TIME: 0.002131
       TOTAL_TIME: 0.002055
            STATE: ACTIVE
             INFO: SELECT * FROM oceanbase.GV$OB_PROCESSLIST LIMIT 1
     PROXY_SESSID: NULL
    MASTER_SESSID: NULL
   USER_CLIENT_IP: 100.xx.xxx.xxx
        USER_HOST: %
        RETRY_CNT: 0
       RETRY_INFO: 0
           SQL_ID: 536F00E9EFCC3725E2239429AB69C94D
         TRANS_ID: 0
        THREAD_ID: 3447775
       SSL_CIPHER: NULL
         TRACE_ID: YB42060CEB9F-000643606BCD508F-0-0
      TRANS_STATE:
           ACTION:
           MODULE:
      CLIENT_INFO:
            LEVEL: 1
SAMPLE_PERCENTAGE: 10
    RECORD_POLICY: SAMPLE_AND_SLOW_QUERY
           LB_VID: NULL
           LB_VIP: NULL
         LB_VPORT: NULL
         IN_BYTES: 448
        OUT_BYTES: 0
 USER_CLIENT_PORT: 27210
       PROXY_USER:
     SERVICE_NAME: NULL
   TOTAL_CPU_TIME: 0
         TOP_INFO: NULL
     MEMORY_USAGE: 2834432
         TOP_TIME: 0
     TOP_TRACE_ID: YB42060CEB9F-000643606BCD508F-0-0
1 row in set (0.048 sec)

GV$OB_PROCESSLIST

Note

Purpose

Columns

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Sample query

References