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 resides.

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 the SQL service.
ID	bigint(20) unsigned	NO	The session ID. In direct connection mode: This field indicates the server session ID. In ODP mode: If the `client_session_id_version` parameter is set to 2, this field indicates the client session ID. If the `client_session_id_version` parameter is set to 1, 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 be accessed.
TENANT	varchar(128)	NO	The name of the tenant to be accessed.
COMMAND	varchar(4096)	NO	The type of the command currently being executed.
TIME	bigint(20)	NO	The current execution time of the command, in seconds. If the command is retried, the value is reset to 0 and recalculated.
TOTAL_TIME	bigint(20)	NO	The total execution time of the command, in seconds. If the command is retried, the value is not reset.
STATE	varchar(128)	YES	The current session state.
INFO	varchar(262143)	YES	The command currently being executed.
PROXY_SESSID	bigint(20) unsigned	YES	If the client is an obproxy, this column displays the proxy session ID.
MASTER_SESSID	bigint(20) unsigned	YES	The ID of the master session, which 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 host name 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, which is usually 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 (empty if no transaction is active on the session): `IDLE`: idle state, indicating that no transaction is active. `ACTIVE`: the transaction is explicitly started by using statements such as `START TRANSACTION` or `BEGIN`. `IMPLICIT_ACTIVE`: the transaction is implicitly started in `autocommit = on` mode. After executing a DML statement, the transaction is started. `ROLLBACK_SAVEPOINT`: the transaction is being rolled back to a savepoint. `IN_TERMINATE`: the transaction is being ended, either due to internal reasons or initiated by the user (such as executing `COMMIT` or `ROLLBACK` statements). `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 timed 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 diagnostic information is sampled at 50% frequency. Note This column is available starting with V4.2.1.
RECORD_POLICY	varchar(32)	NO	The end-to-end tracing record policy of the session. The following three policies are supported: ALL: all trace points of trace sessions that are sampled are printed to the log file. Each span is printed to the log file when it ends. ONLY_SLOW_QUERY: trace points of trace sessions that are sampled and belong to slow queries are printed to the log file. Other trace points are discarded. For this printing strategy, trace logs are printed only after a request is determined to be a slow query. In the Proxy, for the root span, which is at the transaction level, the root span is printed only when a slow query is detected. SAMPLE_AND_SLOW_QUERY: trace points of trace sessions that are sampled and meet the following conditions are printed to the log file: When the hidden configuration item `_print_sample_ppm` is used for sampling at 0.0001% probability, the trace point is printed to the log only if the sampling result is selected. When the trace point meets the printing conditions of the ONLY_SLOW_QUERY mode. For this mode, trace logs are not printed when the span ends. If condition 1 is met, the trace log is marked for forced printing at the client and this information is passed to subsequent components in the chain. If condition 2 is met, 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, it is NULL. 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, it is NULL. 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, it is NULL. 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	For proxy user login scenarios, the name of the proxy user is returned. For non-proxy user login scenarios, 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 name of the service that created the session. If the value is `NULL`, the session was not created by a service. Note For V4.3.x versions, this column was introduced in V4.3.1. For V4.2.1 versions, 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 used by the current command, in seconds. Note For V4.3.x versions, this column was introduced in V4.3.1. For V4.2.1 versions, this column was introduced in V4.2.1 BP5.
TOP_INFO	varchar(262143)	YES	The information about the top-level PL statement of the executing SQL statement. Note For V4.3.x versions, this column was introduced in V4.3.3. For V4.2.1 versions, 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 versions, this column was introduced in V4.4.0, but it is not effective yet. The default value of this column is `NULL`.
TOP_TIME	double	NO	The top_time column in PL scenarios indicates the total execution time of the PL statement. Note For V4.4.x versions, this column was introduced in V4.4.1.
TOP_TRACE_ID	varchar(64)	YES	The trace ID of the top-level statement. Note For V4.4.x versions, 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: 3221557636
             USER: root
             HOST: 100.xx.xxx.xxx:17426
               DB: oceanbase
           TENANT: sys
          COMMAND: Query
             TIME: 0.003688
       TOTAL_TIME: 0.003285
            STATE: ACTIVE
             INFO: SELECT * FROM oceanbase.GV$OB_PROCESSLIST LIMIT 1
     PROXY_SESSID: NULL
    MASTER_SESSID: NULL
   USER_CLIENT_IP: 100.88.xxx.xxx
        USER_HOST: %
        RETRY_CNT: 0
       RETRY_INFO: 0
           SQL_ID: 536F00E9EFCC3725E2239429AB69C94D
         TRANS_ID: 0
        THREAD_ID: 3304100
       SSL_CIPHER: NULL
         TRACE_ID: YB42060CEB9F-00064360C9ED503B-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: 442
        OUT_BYTES: 0
 USER_CLIENT_PORT: 17426
       PROXY_USER:
     SERVICE_NAME: NULL
   TOTAL_CPU_TIME: 0
         TOP_INFO: NULL
     MEMORY_USAGE: 2834432
         TOP_TIME: 0
     TOP_TRACE_ID: YB42060CEB9F-00064360C9ED503B-0-0
1 row in set (0.038 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