OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Database

SQL - V4.3.5

    Download PDF

    OceanBase logo

    The Unified Distributed Database for the AI Era.

    Follow Us
    Products
    OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
    Resources
    DocsBlogLive DemosTraining & CertificationTicket
    Company
    About OceanBaseTrust CenterLegalPartnerContact Us
    Follow Us

    © OceanBase 2026. All rights reserved

    Cloud Service AgreementPrivacy PolicySecurity
    Contact Us
    Document Feedback
    1. Documentation Center
    2. OceanBase Database
    3. SQL
    4. V4.3.5
    iconOceanBase Database
    SQL - V 4.3.5
    SQL
    KV
    • V 4.6.0
    • V 4.4.2
    • V 4.3.5
    • V 4.3.3
    • V 4.3.1
    • V 4.3.0
    • V 4.2.5
    • V 4.2.2
    • V 4.2.1
    • V 4.2.0
    • V 4.1.0
    • V 4.0.0
    • V 3.1.4 and earlier

    V$OB_PROCESSLIST

    Last Updated:2026-04-15 06:09:08  Updated
    share
    What is on this page
    Purpose
    Columns
    Sample queries
    References

    folded

    share

    Note

    This view is introduced since OceanBase Database V4.0.0.

    Purpose

    The V$OB_PROCESSLIST view displays session information on this OBServer node.

    Columns

    Column
    Type
    Nullable?
    Description
    SVR_IP varchar(46) NO The IP address of the server.
    SVR_PORT bigint(20) NO The port of the server.
    SQL_PORT bigint(20) NO The port for SQL statements.
    ID bigint(20) unsigned NO The session ID.
    USER varchar(32) NO The username.
    HOST varchar(128) NO The host name of the client. (For connections through obproxy, this column displays the host address of obproxy.)
    DB varchar(128) NO The name of the database being accessed.
    TENANT varchar(128) NO The name of the tenant being accessed.
    COMMAND varchar(4096) NO The type of the current command.
    TIME bigint(20) NO The execution time of the current command in seconds. If the command is retried, the value is reset to 0.
    TOTAL_TIME bigint(20) NO The total execution time of the current command in seconds. If the command is retried, the value is not reset.
    STATE varchar(128) NO The current session status.
    INFO varchar(262143) NO The current command being executed.
    PROXY_SESSID bigint(20) unsigned NO The proxy session ID if the client is obproxy.
    MASTER_SESSID bigint(20) unsigned NO The master session ID, which is used to chain multiple subsessions of the same SQL statement.
    USER_CLIENT_IP varchar(46) NO The IP address of the user client.
    USER_HOST varchar(128) NO The host name of the user client.
    RETRY_CNT bigint(20) NO The number of retries of the current command.
    RETRY_INFO bigint(20) NO The retry information of the current command, which is generally 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) NO The name of the encryption cipher.
    TRACE_ID varchar(64) NO The trace ID.
    TRANS_STATE varchar(32) NO The transaction state.
    • IDLE: The transaction is idle, indicating that the transaction has not started.
    • ACTIVE: The transaction is explicitly started. It is started by using the START TRANSACTION or BEGIN statement.
    • IMPLICIT_ACTIVE: The transaction is implicitly started. It is started in the autocommit = on mode after a DML statement that modifies data is executed.
    • ROLLBACK_SAVEPOINT: The transaction is rolled back to a savepoint.
    • IN_TERMINATE: The transaction is being terminated, which can be caused by internal reasons or user-initiated termination (for example, the COMMIT or ROLLBACK statement).
    • ABORTED: The transaction is terminated due to an exception.
    • ROLLED_BACK: The transaction has been rolled back.
    • COMMIT_TIMEOUT: The transaction commit has timed out.
    • COMMIT_UNKNOWN: The commit result of the transaction is unknown.
    • COMMITTED: The transaction has been successfully committed.
    ACTION varchar(4096) NO The name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.
    MODULE varchar(4096) NO The name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.
    CLIENT_INFO varchar(4096) NO The information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.
    LEVEL bigint(20) NO The full-link trace 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 The full-link trace sampling frequency of the session. For example, 50 indicates that diagnostic information is sampled at a 50% frequency.

    Note

    This field was introduced in V4.2.1.

    RECORD_POLICY varchar(32) NO The full-link trace recording strategy of the session. It supports the following three strategies:
    • ALL: Trace points that are traced when sampling is enabled are printed to the log file. The log file is updated when a span ends.
    • ONLY_SLOW_QUERY: Only request traces that are traced when sampling is enabled and identified 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 after a request is identified as a slow query. In the obproxy mode, for root spans, which are transaction-level spans, the root spans are printed to the log file when a slow query is detected.
    • SAMPLE_AND_SLOW_QUERY: All traces that are traced when sampling is enabled and meet the following conditions are printed to the log file:
      1. When the probability of sampling is 1/1000 and the sampling result is selected, the trace is printed to the log file.
      2. The trace meets the conditions for printing in the ONLY_SLOW_QUERY mode.
      For this mode, the log is not updated when a span ends. If condition 1 is met, the trace is marked as a forced print trace and the information is passed to the subsequent link component. If condition 2 is met, the log is updated based on the ONLY_SLOW_QUERY mode.

    Note

    This field was introduced in V4.2.1.

    LB_VID bigint(20) NO 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, it displays NULL.

    Note

    This field was introduced in V4.2.1.

    LB_VIP varchar(46) NO If you directly connect to the database through load balancing in a public cloud environment, this column displays the IP address of the client connecting to the load balancing service. Otherwise, it displays NULL.

    Note

    This field was introduced in V4.2.1.

    LB_VPORT bigint(20) NO If you directly connect to the database through load balancing in a public cloud environment, this column displays the port of the client connecting to the load balancing service. Otherwise, it displays NULL.

    Note

    This field was introduced in V4.2.1.

    IN_BYTES bigint(20) NO The incoming traffic of the session in bytes.

    Note

    This field was introduced in V4.2.1.

    OUT_BYTES bigint(20) NO The outgoing traffic of the session in bytes.

    Note

    This field was introduced in V4.2.1.

    USER_CLIENT_PORT bigint(20) NO The 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) NO
    • The name of the proxy user if you log in as a proxy user.
    • NULL if you log in as a non-proxy user.

    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 The 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. For other V4.2.x versions, this field was introduced in V4.2.4.
    TOTAL_CPU_TIME bigint(21) NO The 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 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) NO The memory occupied by a single SQL statement, in bytes.

    Note

    For V4.3.5, this field was introduced in V4.3.5 BP2.

    TOP_TIME double NO The top_time column in the PL scenario indicates the entire PL execution time.

    Note

    In V4.3.x, this field was introduced in V4.3.5 BP5.

    TOP_TRACE_ID varchar(64) YES The traceid of the top-level statement.

    Note

    In V4.3.x, this field was introduced in V4.3.5 BP5.

    Sample queries

    Query the session information of this OBServer node.

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

    The query result is as follows:

    *************************** 1. row ***************************
    *************************** 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
    

    References

    • GV$OB_PROCESSLIST
    • Methods

    Previous topic

    V$OB_PLAN_CACHE_STAT
    Last

    Next topic

    V$OB_PS_ITEM_INFO
    Next
    What is on this page
    Purpose
    Columns
    Sample queries
    References