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

GV$OB_PROCESSLIST

Last Updated：2025-11-14 07:33:33 Updated

Note

This view is introduced since OceanBase Database V4.0.0.

Purpose

The GV$OB_PROCESSLIST view displays session information for all OBServer nodes in a tenant.

Columns

Column	Type	Nullable?	Description
SVR_IP	varchar(46)	NO	IP address of the server.
SVR_PORT	bigint(20)	NO	Port number of the server.
SQL_PORT	bigint(20)	NO	Port number of the SQL service.
ID	bigint(20) unsigned	NO	Session ID.
USER	varchar(32)	NO	Username.
HOST	varchar(128)	NO	Host name of the client. (For example, if you connect to the database through obproxy, this column displays the host name of obproxy.)
DB	varchar(128)	YES	Name of the database being accessed.
TENANT	varchar(128)	NO	Name of the tenant being accessed.
COMMAND	varchar(4096)	NO	Type of the current command.
TIME	bigint(20)	NO	Execution time of the current command in seconds. The value is reset to 0 when the command is retried.
TOTAL_TIME	bigint(20)	NO	Total execution time of the current command in seconds. The value is not reset when the command is retried.
STATE	varchar(128)	YES	Current session status.
INFO	varchar(262143)	YES	Displays the command being executed.
PROXY_SESSID	bigint(20) unsigned	YES	If the client is obproxy, this column displays the proxy session ID.
MASTER_SESSID	bigint(20) unsigned	YES	ID of the master session, which is used to link multiple subsessions of the same SQL statement.
USER_CLIENT_IP	varchar(46)	YES	IP address of the user client.
USER_HOST	varchar(128)	YES	Host name of the user client.
RETRY_CNT	bigint(20)	NO	Number of retries of the current command.
RETRY_INFO	bigint(20)	NO	Retry information of the current command, which is generally the error code of the last retry.
SQL_ID	varchar(32)	NO	SQL ID.
TRANS_ID	bigint(20) unsigned	NO	Transaction ID.
THREAD_ID	bigint(20) unsigned	NO	Thread ID.
SSL_CIPHER	varchar(4096)	YES	Name of the encryption cipher.
TRACE_ID	varchar(64)	YES	Trace ID.
TRANS_STATE	varchar(32)	YES	Transaction status. Valid values include: `IDLE`: idle state, indicating that the transaction has not started. `ACTIVE`: explicit transaction start. The transaction is explicitly started by using `START TRANSACTION`, `BEGIN`, and so on. `IMPLICIT_ACTIVE`: implicit transaction start. The transaction is implicitly started in the `autocommit = on` mode after a DML statement that modifies data is executed. `ROLLBACK_SAVEPOINT`: rollback to a savepoint. `IN_TERMINATE`: transaction termination, which can be caused by internal reasons or user-initiated termination (for example, by using the `COMMIT` or `ROLLBACK` statement). `ABORTED`: transaction internal termination or rollback due to an exception. `ROLLED_BACK`: transaction rollback. `COMMIT_TIMEOUT`: transaction commit timeout. `COMMIT_UNKNOWN`: unknown transaction commit result. `COMMITTED`: transaction commit success.
ACTION	varchar(4096)	YES	Name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.
MODULE	varchar(4096)	YES	Name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.
CLIENT_INFO	varchar(4096)	YES	Information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.
LEVEL	bigint(20)	NO	Indicates the full-link tracing monitoring level of the session. For example, 1 indicates level 1 diagnostic information. Note This field was introduced in V4.2.1.
SAMPLE_PERCENTAGE	bigint(20)	NO	Indicates the full-link tracing sampling frequency of the session. For example, 50 indicates that the sampling frequency is 50%. Note This field was introduced in V4.2.1.
RECORD_POLICY	varchar(32)	NO	Indicates the full-link tracing recording strategy of the session. Valid values include: ALL: Trace information of all traces that are traced and sampled is printed to the log file. The information is printed to the log file when each span is completed. ONLY_SLOW_QUERY: Only request traces that are traced and sampled and classified as slow queries are printed to the log file. Other traces are discarded. For this printing strategy, the trace logs are printed to the log file only after the request is determined to be a slow query. In obproxy, for a root span, which is a transaction-level span, the root span is printed to the log file when a slow query is detected. SAMPLE_AND_SLOW_QUERY: All traces that are traced and sampled are printed to the log file if the following conditions are met: When the `_print_sample_ppm` hidden parameter is used for 1% sampling, the trace is printed to the log file only if it is selected. The trace meets the printing conditions for the ONLY_SLOW_QUERY mode. In this mode, the trace logs are not printed to the log file when each span is completed. If condition 1 is met, the trace logs are forcibly marked for printing and the information is passed to the next link component. If condition 2 is met, the printing timing is the same as that for the ONLY_SLOW_QUERY mode. Note This field was introduced in V4.2.1.
LB_VID	bigint(20)	YES	If you directly connect to the database through load balancing in a public cloud environment, this column displays the VPC ID of the load balancing service. Otherwise, this column displays NULL. Note This field was introduced in V4.2.1.
LB_VIP	varchar(46)	YES	If you directly connect to the database through load balancing in a public cloud environment, this column displays the IP address of the client for connecting to the load balancing service. Otherwise, this column displays NULL. Note This field was introduced in V4.2.1.
LB_VPORT	bigint(20)	YES	If you directly connect to the database through load balancing in a public cloud environment, this column displays the port for connecting to the load balancing service. Otherwise, this column displays NULL. Note This field was introduced in V4.2.1.
IN_BYTES	bigint(20)	NO	Ingress traffic of the session in bytes. Note This field was introduced in V4.2.1.
OUT_BYTES	bigint(20)	NO	Egress traffic of the session in bytes. Note This field was introduced in V4.2.1.
USER_CLIENT_PORT	bigint(20)	NO	Client address information. Note In V4.3.x, this field was introduced in V4.3.0. In V4.2.x, this field was introduced in V4.2.3.
PROXY_USER	varchar(128)	YES	Displays the name of the proxy user in the proxy user login scenario. Displays an empty string in the non-proxy user login scenario. Note In V4.3.x, this field was introduced in V4.3.2. In V4.2.x, this field was introduced in V4.2.3.
SERVICE_NAME	varchar(64)	YES	Name of the service that created the session. The value is `NULL` if the session was not created by a service name. Note In V4.3.x, this field was introduced in V4.3.1. In V4.2.1, this field was introduced in V4.2.1 BP9. In V4.2.x (excluding V4.2.1), this field was introduced in V4.2.4.
TOTAL_CPU_TIME	bigint(21)	NO	CPU usage time of the current command in seconds. Note In V4.3.x, this field was introduced in V4.3.1. In V4.2.1, this field was introduced in V4.2.1 BP5.
TOP_INFO	varchar(262143)	YES	Displays the information of the top-level PL statement where the executing SQL statement is located. Note In V4.3.x, this field was introduced in V4.3.3. In V4.2.1, this field was introduced in V4.2.1 BP9.
MEMORY_USAGE	bigint(20)	YES	The memory occupied by a single SQL statement, in bytes. Note For V4.3.5, this field was introduced in V4.3.5 BP2.

Sample queries

Query the session information of all OBServer nodes where the tenant resides.

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

The query result is as follows:

*************************** 1. row ***************************
           SVR_IP: 172.xx.xxx.xxx
         SVR_PORT: 2882
         SQL_PORT: 2881
               ID: 3221735835
             USER: root
             HOST: 100.xx.xxx.xxx:28135
               DB: demo
           TENANT: mysql001
          COMMAND: Query
             TIME: 120.800875
       TOTAL_TIME: 0.000136
            STATE: ACTIVE
             INFO: INSERT INTO orders (
            user_id,
            product_name,
            order_amount,
            order_date,
            order_status
        ) VALUES (
            FLOOR(RAND() * 10000),
            CONCAT('Product ', FLOOR(RAND() * 1000)),
            ROUND(RAND() * 1000, 2),
            DATE_SUB(NOW(), INTERVAL FLOOR(RAND() * 1500) DAY),
            ELT(FLOOR(RAND() * 3 + 1), 'pending', 'completed', 'cancelled')
        )
     PROXY_SESSID: NULL
    MASTER_SESSID: NULL
   USER_CLIENT_IP: 100.xx.xxx.xxx
        USER_HOST: %
        RETRY_CNT: 0
       RETRY_INFO: 0
           SQL_ID: A2572E6AF77AEF27E893F08559A9FA67
         TRANS_ID: 1463901
        THREAD_ID: 2443
       SSL_CIPHER: NULL
         TRACE_ID: YB4***************************************-0-0
      TRANS_STATE: IN_TERMINATE
           ACTION:
           MODULE:
      CLIENT_INFO:
            LEVEL: 1
SAMPLE_PERCENTAGE: 50
    RECORD_POLICY: ALL
           LB_VID: NULL
           LB_VIP: NULL
         LB_VPORT: NULL
         IN_BYTES: 447
        OUT_BYTES: 0
 USER_CLIENT_PORT: 28135
       PROXY_USER:
     SERVICE_NAME: NULL
   TOTAL_CPU_TIME: 121
         TOP_INFO: CALL generate_test_orders()
     MEMORY_USAGE: NULL
1 row in set

GV$OB_PROCESSLIST

Note

Purpose

Columns

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Sample queries

References