V$OB_PROCESSLIST|V4.3.5|OceanBase Database|docs|OceanBase Documentations

Column	Type	Nullable?	Description
SVR_IP	VARCHAR2(46)	NO	IP address of the server.
SVR_PORT	NUMBER(38)	NO	Port of the server.
SQL_PORT	NUMBER(38)	NO	Port for SQL statements.
ID	NUMBER(38)	NO	Session ID.
USER	CHAR(193)	NO	Username.
HOST	VARCHAR2(128)	NO	Host name of the client. (For example, if you connect to the database through obproxy, this column displays the host address of obproxy.)
DB	VARCHAR2(128)	YES	Name of the database being accessed.
TENANT	VARCHAR2(128)	NO	Name of the tenant being accessed.
COMMAND	VARCHAR2(4096)	NO	Type of the current command.
TIME	NUMBER(38)	NO	Execution time of the current command in seconds. If the command is retried, the value is reset to 0.
TOTAL_TIME	NUMBER(38)	NO	Total execution time of the current command in seconds. If the command is retried, the value is not reset.
STATE	VARCHAR2(128)	YES	Current session status.
INFO	VARCHAR2(262143)	YES	This view displays the current command being executed.
PROXY_SESSID	NUMBER(38)	YES	If the client is obproxy, this column displays the proxy session ID.
MASTER_SESSID	NUMBER(38)	YES	ID of the master session, which is used to chain multiple subsessions of the same SQL statement.
USER_CLIENT_IP	VARCHAR2(46)	YES	IP address of the user client.
USER_HOST	VARCHAR2(128)	YES	Host name of the user client.
RETRY_CNT	NUMBER(38)	NO	Number of retries of the current command.
RETRY_INFO	NUMBER(38)	NO	Retry information of the current command, which is generally the error code of the last retry.
SQL_ID	VARCHAR2(32)	NO	SQL ID.
TRANS_ID	NUMBER(38)	NO	Transaction ID.
THREAD_ID	NUMBER(38)	NO	Thread ID.
SSL_CIPHER	VARCHAR2(4096)	YES	Name of the encryption cipher.
TRACE_ID	VARCHAR2(64)	YES	Trace ID.
TRANS_STATE	VARCHAR2(32)	YES	Transaction status. Valid values include: `IDLE`: the transaction is idle, indicating that the transaction has not started. `ACTIVE`: the transaction is explicitly started. You can start a transaction by using the `START TRANSACTION` or `BEGIN` statement. `IMPLICIT_ACTIVE`: the transaction is implicitly started. In the `autocommit = on` mode, a transaction is started after you execute a data modification statement. `ROLLBACK_SAVEPOINT`: the transaction is rolling back to a savepoint. `IN_TERMINATE`: the transaction is being terminated, which can be caused by internal reasons or user-initiated transactions (for example, when you execute 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 result of the transaction commit is unknown. `COMMITTED`: the transaction has been committed.
ACTION	VARCHAR2(4096)	YES	Name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.
MODULE	VARCHAR2(4096)	YES	Name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.
CLIENT_INFO	VARCHAR2(4096)	YES	Information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.
LEVEL	NUMBER(38)	NO	Level of full-link tracing and monitoring for the session. For example, 1 indicates level 1 diagnostic information. Note This field was introduced in V4.2.1.
SAMPLE_PERCENTAGE	NUMBER(38)	NO	Sampling frequency for full-link tracing and monitoring for 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	VARCHAR2(32)	NO	Recording strategy for full-link tracing and monitoring for the session. Valid values include: ALL: Trace data points of all traces that are sampled and traced are printed to the log file, and are printed to the log file at the end of each span. ONLY_SLOW_QUERY: Trace data points of all traces that are sampled and traced are printed to the log file only if the trace is a slow query. Otherwise, the trace data points are discarded. For this printing strategy, the trace logs are printed to the log file after the request is determined to be a slow query. In obproxy, for the root span, which is the span at the transaction level, the root span is printed to the log file when a slow query is detected. SAMPLE_AND_SLOW_QUERY: Trace data points of all traces that are sampled and traced are printed to the log file if they meet the following conditions: If you use the hidden parameter `_print_sample_ppm` to perform sampling at a 1/10,000 probability, the trace data points are printed to the log file only if the sampling result is selected. The trace data points meet the printing conditions for the ONLY_SLOW_QUERY mode. In this mode, the trace logs are not printed to the log file at the end of the span. If condition 1 is met, the trace logs are marked as mandatory for printing and are passed to the following link components. If condition 2 is met, the trace logs are printed to the log file at the end of the span. Note This field was introduced in V4.2.1.
LB_VID	NUMBER(38)	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	VARCHAR2(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	NUMBER(38)	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	NUMBER(38)	NO	Incoming traffic of the session in bytes. Note This field was introduced in V4.2.1.
OUT_BYTES	NUMBER(38)	NO	Outgoing traffic of the session in bytes. Note This field was introduced in V4.2.1.
USER_CLIENT_PORT	NUMBER(38)	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	VARCHAR2(128)	YES	If you log in as a proxy user, the name of the proxy user is returned. If you log in as a non-proxy user, this column displays an empty string. 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	VARCHAR2(64)	YES	Service name for which the session is created. If the session is not created by a service name, this column displays NULL. 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	NUMBER(38)	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	VARCHAR2(262143)	YES	This view 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 column displays NULL.
MEMORY_USAGE	NUMBER(38)	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	NUMBER(38)	NO	This column displays the total execution time of the PL statement. Note In V4.3.x, this column was introduced in V4.3.5 BP5.
TOP_TRACE_ID	VARCHAR2(64)	YES	This column displays the trace ID of the top-level statement. Note In V4.3.x, this column was introduced in V4.3.5 BP5.

SVR_IP

VARCHAR2(46)

NO

IP address of the server.

SVR_PORT

NUMBER(38)

NO

Port of the server.

SQL_PORT

NUMBER(38)

NO

Port for SQL statements.

ID

NUMBER(38)

NO

Session ID.

USER

CHAR(193)

NO

Username.

HOST

VARCHAR2(128)

NO

Host name of the client. (For example, if you connect to the database through obproxy, this column displays the host address of obproxy.)

DB

VARCHAR2(128)

YES

Name of the database being accessed.

TENANT

VARCHAR2(128)

NO

Name of the tenant being accessed.

COMMAND

VARCHAR2(4096)

NO

Type of the current command.

TIME

NUMBER(38)

NO

Execution time of the current command in seconds. If the command is retried, the value is reset to 0.

TOTAL_TIME

NUMBER(38)

NO

Total execution time of the current command in seconds. If the command is retried, the value is not reset.

STATE

VARCHAR2(128)

YES

Current session status.

INFO

VARCHAR2(262143)

YES

This view displays the current command being executed.

PROXY_SESSID

NUMBER(38)

YES

If the client is obproxy, this column displays the proxy session ID.

MASTER_SESSID

NUMBER(38)

YES

ID of the master session, which is used to chain multiple subsessions of the same SQL statement.

USER_CLIENT_IP

VARCHAR2(46)

YES

IP address of the user client.

USER_HOST

VARCHAR2(128)

YES

Host name of the user client.

RETRY_CNT

NUMBER(38)

NO

Number of retries of the current command.

RETRY_INFO

NUMBER(38)

NO

Retry information of the current command, which is generally the error code of the last retry.

SQL_ID

VARCHAR2(32)

NO

SQL ID.

TRANS_ID

NUMBER(38)

NO

Transaction ID.

THREAD_ID

NUMBER(38)

NO

Thread ID.

SSL_CIPHER

VARCHAR2(4096)

YES

Name of the encryption cipher.

TRACE_ID

VARCHAR2(64)

YES

Trace ID.

TRANS_STATE

VARCHAR2(32)

YES

Transaction status. Valid values include:

IDLE: the transaction is idle, indicating that the transaction has not started.
ACTIVE: the transaction is explicitly started. You can start a transaction by using the START TRANSACTION or BEGIN statement.
IMPLICIT_ACTIVE: the transaction is implicitly started. In the autocommit = on mode, a transaction is started after you execute a data modification statement.
ROLLBACK_SAVEPOINT: the transaction is rolling back to a savepoint.
IN_TERMINATE: the transaction is being terminated, which can be caused by internal reasons or user-initiated transactions (for example, when you execute 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 result of the transaction commit is unknown.
COMMITTED: the transaction has been committed.

ACTION

VARCHAR2(4096)

YES

Name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.

MODULE

VARCHAR2(4096)

YES

Name of the current operation set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.

CLIENT_INFO

VARCHAR2(4096)

YES

Information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.

LEVEL

NUMBER(38)

NO

Level of full-link tracing and monitoring for the session. For example, 1 indicates level 1 diagnostic information.

Note

This field was introduced in V4.2.1.

SAMPLE_PERCENTAGE

NUMBER(38)

NO

Sampling frequency for full-link tracing and monitoring for 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

VARCHAR2(32)

NO

Recording strategy for full-link tracing and monitoring for the session. Valid values include:

ALL: Trace data points of all traces that are sampled and traced are printed to the log file, and are printed to the log file at the end of each span.
ONLY_SLOW_QUERY: Trace data points of all traces that are sampled and traced are printed to the log file only if the trace is a slow query. Otherwise, the trace data points are discarded. For this printing strategy, the trace logs are printed to the log file after the request is determined to be a slow query. In obproxy, for the root span, which is the span at the transaction level, the root span is printed to the log file when a slow query is detected.
SAMPLE_AND_SLOW_QUERY: Trace data points of all traces that are sampled and traced are printed to the log file if they meet the following conditions:
1. If you use the hidden parameter _print_sample_ppm to perform sampling at a 1/10,000 probability, the trace data points are printed to the log file only if the sampling result is selected.
2. The trace data points meet the printing conditions for the ONLY_SLOW_QUERY mode.
In this mode, the trace logs are not printed to the log file at the end of the span. If condition 1 is met, the trace logs are marked as mandatory for printing and are passed to the following link components. If condition 2 is met, the trace logs are printed to the log file at the end of the span.

Note

This field was introduced in V4.2.1.

LB_VID

NUMBER(38)

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

VARCHAR2(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

NUMBER(38)

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

NUMBER(38)

NO

Incoming traffic of the session in bytes.

Note

This field was introduced in V4.2.1.

OUT_BYTES

NUMBER(38)

NO

Outgoing traffic of the session in bytes.

Note

This field was introduced in V4.2.1.

USER_CLIENT_PORT

NUMBER(38)

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

VARCHAR2(128)

YES

If you log in as a proxy user, the name of the proxy user is returned.
If you log in as a non-proxy user, this column displays an empty string.

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

VARCHAR2(64)

YES

Service name for which the session is created. If the session is not created by a service name, this column displays NULL.

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

NUMBER(38)

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

VARCHAR2(262143)

YES

This view 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 column displays NULL.

MEMORY_USAGE

NUMBER(38)

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

NUMBER(38)

NO

This column displays the total execution time of the PL statement.

Note

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

TOP_TRACE_ID

VARCHAR2(64)

YES

This column displays the trace ID of the top-level statement.

Note

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

V$OB_PROCESSLIST

Note

Purpose

Columns

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Sample queries

References