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

Column	Type	Nullable	Description
SVR_IP	VARCHAR2(46)	NO	The IP address of the server.
SVR_PORT	NUMBER(38)	NO	The port number of the server.
SQL_PORT	NUMBER(38)	NO	The port number of SQL.
ID	NUMBER(38)	NO	The session ID.
USER	CHAR(193)	NO	The username.
HOST	VARCHAR2(128)	NO	The name of the client host. If the client is connected through an OBProxy, this column displays the IP address of the OBProxy.
DB	VARCHAR2(128)	NO	The name of the database being accessed.
TENANT	VARCHAR2(128)	NO	The name of the tenant being accessed.
COMMAND	VARCHAR2(4096)	NO	The type of the command being executed.
TIME	NUMBER(38)	NO	The time when the command is executed, in seconds. If the command is retried, this value is reset to 0 and recalculated.
TOTAL_TIME	NUMBER(38)	NO	The total time taken for the command to be executed, in seconds. If the command is being executed after a request is received and before a response is returned, this value represents the time interval from when the request was received to the current time. If the command is in a state that does not involve receiving a request, this value represents the duration of the current state. Note In versions earlier than V4.2.5, this field indicates the total time taken for the command to be executed, which is not reset when the command is retried.
STATE	VARCHAR2(128)	NO	The current session state.
INFO	VARCHAR2(262143)	NO	The command being executed.
PROXY_SESSID	NUMBER(38)	NO	If the client is an OBProxy, this column displays the proxy session ID.
MASTER_SESSID	NUMBER(38)	NO	The session ID of the master session, which is used to link multiple sub-sessions of the same SQL statement.
USER_CLIENT_IP	VARCHAR2(46)	NO	The IP address of the client.
USER_HOST	VARCHAR2(128)	NO	The name of the client host.
RETRY_CNT	NUMBER(38)	NO	The number of retries for the current command.
RETRY_INFO	NUMBER(38)	NO	The retry information for the current command. This value is generally the error code of the last retry.
SQL_ID	VARCHAR2(32)	NO	The SQL ID.
TRANS_ID	NUMBER(38)	NO	The transaction ID.
THREAD_ID	NUMBER(38)	NO	The thread ID.
SSL_CIPHER	VARCHAR2(4096)	NO	The name of the encryption cipher.
TRACE_ID	VARCHAR2(64)	NO	The trace ID.
TRANS_STATE	VARCHAR2(32)	NO	Transaction status: `IDLE`: idle state, indicating that the transaction has not been started. `ACTIVE`: the transaction is explicitly started by using the `START TRANSACTION` or `BEGIN` statement. `IMPLICIT_ACTIVE`: the transaction is implicitly started in the `autocommit = on` mode. After a DML statement is executed, the transaction is started. `ROLLBACK_SAVEPOINT`: the transaction is being rolled back to a savepoint. `IN_TERMINATE`: the transaction is being terminated. This includes termination caused by internal reasons and user-initiated termination (for example, by executing the `COMMIT` or `ROLLBACK` statement). `ABORTED`: the transaction is internally terminated 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	VARCHAR2(4096)	NO	The name of the current execution operation set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.
MODULE	VARCHAR2(4096)	NO	The name of the current execution operation set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.
CLIENT_INFO	VARCHAR2(4096)	NO	The information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.
LEVEL	NUMBER(38)	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	NUMBER(38)	NO	The end-to-end tracing sampling frequency of the session. For example, 50 indicates that diagnostic information is sampled with 50% probability. Note This column is available starting with V4.2.1.
RECORD_POLICY	VARCHAR2(32)	NO	The end-to-end tracing recording strategy of the session. The following three strategies are supported: ALL: All trace points that are sampled and enabled for tracing are printed to the log file. The trace points are printed to the log file at the end of each span. ONLY_SLOW_QUERY: All trace points that are sampled and enabled for tracing are printed to the log file. However, only trace points of slow queries are printed to the log file. For this recording strategy, trace logs are printed only after a request is determined to be a slow query. In a Proxy environment, the root span (transaction-level span) is printed only when a slow query is detected. SAMPLE_AND_SLOW_QUERY: All trace points that are sampled and enabled for tracing are printed to the log file if the trace points meet the following conditions: When the hidden configuration item `_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, trace logs are not printed at the end of a span. If condition 1 is met, the trace log is forcibly printed at the client and the 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	NUMBER(38)	NO	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 service. Otherwise, this column is NULL. Note This column is available starting with V4.2.1.
LB_VIP	VARCHAR2(46)	NO	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 service. Otherwise, this column is NULL. Note This column is available starting with V4.2.1.
LB_VPORT	NUMBER(38)	NO	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 service. Otherwise, this column is NULL. Note This column is available starting with V4.2.1.
IN_BYTES	NUMBER(38)	NO	The incoming traffic of the session, in bytes. Note This column is available starting with V4.2.1.
OUT_BYTES	NUMBER(38)	NO	The outgoing traffic of the session, in bytes. Note This column is available starting with V4.2.1.
USER_CLIENT_PORT	NUMBER(38))	NO	The client address information. Note This column is available starting with V4.2.3.
PROXY_USER	VARCHAR2(128)	NO	For proxy user login scenarios, the name of the proxy user is returned. For non-proxy user login scenarios, this column is empty. Note This column is available starting with V4.2.3.
TOTAL_CPU_TIME	VARCHAR2(38)	NO	The CPU usage time of the current command, in seconds. Note In V4.3.x, this column is available starting with V4.3.1. In V4.2.1, this column is available starting with V4.2.1 BP5. In other V4.2.x versions, this column is available starting with V4.2.5.
SERVICE_NAME	VARCHAR2(64)	NO	The service name that created the session. If the value is `NULL`, the session was not created by a service name. Note This column is available starting with V4.2.4.
TOP_INFO	VARCHAR2(262143)	NO	The information of the top PL statement of the executing SQL statement. Note In V4.3.x, this column is available starting with V4.3.3. In V4.2.1, this column is available starting with V4.2.1 BP9. In other V4.2.x versions, this column is available starting with V4.2.5.
MEMORY_USAGE	NUMBER(38)	NO	The size of memory used by the SQL statement, in bytes. Note In V4.2.5, this column is available starting with V4.2.5 BP2.

SVR_IP

VARCHAR2(46)

NO

The IP address of the server.

SVR_PORT

NUMBER(38)

NO

The port number of the server.

SQL_PORT

NUMBER(38)

NO

The port number of SQL.

ID

NUMBER(38)

NO

The session ID.

USER

CHAR(193)

NO

The username.

HOST

VARCHAR2(128)

NO

The name of the client host. If the client is connected through an OBProxy, this column displays the IP address of the OBProxy.

DB

VARCHAR2(128)

NO

The name of the database being accessed.

TENANT

VARCHAR2(128)

NO

The name of the tenant being accessed.

COMMAND

VARCHAR2(4096)

NO

The type of the command being executed.

TIME

NUMBER(38)

NO

The time when the command is executed, in seconds. If the command is retried, this value is reset to 0 and recalculated.

TOTAL_TIME

NUMBER(38)

NO

The total time taken for the command to be executed, in seconds.

If the command is being executed after a request is received and before a response is returned, this value represents the time interval from when the request was received to the current time.
If the command is in a state that does not involve receiving a request, this value represents the duration of the current state.

Note

In versions earlier than V4.2.5, this field indicates the total time taken for the command to be executed, which is not reset when the command is retried.

STATE

VARCHAR2(128)

NO

The current session state.

INFO

VARCHAR2(262143)

NO

The command being executed.

PROXY_SESSID

NUMBER(38)

NO

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

MASTER_SESSID

NUMBER(38)

NO

The session ID of the master session, which is used to link multiple sub-sessions of the same SQL statement.

USER_CLIENT_IP

VARCHAR2(46)

NO

The IP address of the client.

USER_HOST

VARCHAR2(128)

NO

The name of the client host.

RETRY_CNT

NUMBER(38)

NO

The number of retries for the current command.

RETRY_INFO

NUMBER(38)

NO

The retry information for the current command. This value is generally the error code of the last retry.

SQL_ID

VARCHAR2(32)

NO

The SQL ID.

TRANS_ID

NUMBER(38)

NO

The transaction ID.

THREAD_ID

NUMBER(38)

NO

The thread ID.

SSL_CIPHER

VARCHAR2(4096)

NO

The name of the encryption cipher.

TRACE_ID

VARCHAR2(64)

NO

The trace ID.

TRANS_STATE

VARCHAR2(32)

NO

Transaction status:

IDLE: idle state, indicating that the transaction has not been started.
ACTIVE: the transaction is explicitly started by using the START TRANSACTION or BEGIN statement.
IMPLICIT_ACTIVE: the transaction is implicitly started in the autocommit = on mode. After a DML statement is executed, the transaction is started.
ROLLBACK_SAVEPOINT: the transaction is being rolled back to a savepoint.
IN_TERMINATE: the transaction is being terminated. This includes termination caused by internal reasons and user-initiated termination (for example, by executing the COMMIT or ROLLBACK statement).
ABORTED: the transaction is internally terminated 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

VARCHAR2(4096)

NO

The name of the current execution operation set by calling the DBMS_APPLICATION_INFO.SET_ACTION procedure.

MODULE

VARCHAR2(4096)

NO

The name of the current execution operation set by calling the DBMS_APPLICATION_INFO.SET_MODULE procedure.

CLIENT_INFO

VARCHAR2(4096)

NO

The information set by calling the DBMS_APPLICATION_INFO.SET_CLIENT_INFO procedure.

LEVEL

NUMBER(38)

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

NUMBER(38)

NO

The end-to-end tracing sampling frequency of the session. For example, 50 indicates that diagnostic information is sampled with 50% probability.

Note

This column is available starting with V4.2.1.

RECORD_POLICY

VARCHAR2(32)

NO

The end-to-end tracing recording strategy of the session. The following three strategies are supported:

ALL: All trace points that are sampled and enabled for tracing are printed to the log file. The trace points are printed to the log file at the end of each span.
ONLY_SLOW_QUERY: All trace points that are sampled and enabled for tracing are printed to the log file. However, only trace points of slow queries are printed to the log file. For this recording strategy, trace logs are printed only after a request is determined to be a slow query. In a Proxy environment, the root span (transaction-level span) is printed only when a slow query is detected.
SAMPLE_AND_SLOW_QUERY: All trace points that are sampled and enabled for tracing are printed to the log file if the trace points meet the following conditions:
1. When the hidden configuration item _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.
2. The trace point meets the conditions for printing in the ONLY_SLOW_QUERY mode.
For this recording strategy, trace logs are not printed at the end of a span. If condition 1 is met, the trace log is forcibly printed at the client and the 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

In V4.3.x, this column is available starting with V4.3.3.
In V4.2.1, this column is available starting with V4.2.1 BP9. In other V4.2.x versions, this column is available starting with V4.2.5.

MEMORY_USAGE

NUMBER(38)

NO

The size of memory used by the SQL statement, in bytes.

Note

In V4.2.5, this column is available starting with V4.2.5 BP2.

V$OB_PROCESSLIST

Note

Purpose

Columns

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Note

Sample query

References