Note
- For V4.3.x versions, this view was renamed to V$OB_ACTIVE_SESSION_HISTORY starting from V4.3.5. For V4.2.x versions, this view was renamed to V$OB_ACTIVE_SESSION_HISTORY starting from V4.2.2.
- This view is available starting with V4.0.0.
Purpose
The V$ACTIVE_SESSION_HISTORY view displays the active session history of the current OBServer node in the current tenant.
Columns
| Column | Type | Nullable | Description |
|---|---|---|---|
| SVR_IP | VARCHAR2(46) | NO | The IP address of the server to which the sample belongs. |
| SVR_PORT | NUMBER | NO | The port number of the server to which the sample belongs. |
| SAMPLE_ID | NUMBER | NO | The unique ID of the sample. |
| SAMPLE_TIME | TIMESTAMP(6) | NO | The time when the sample was taken. |
| CON_ID | NUMBER | NO | The tenant ID. |
| USER_ID | NUMBER | NO | The ID of the user who initiated the session being sampled. |
| SESSION_ID | NUMBER | NO | The ID of the session being sampled. For V4.3.x:
|
| SESSION_TYPE | VARCHAR2(10) | NO | The session type. Valid values:
|
| SESSION_STATE | VARCHAR2(7) | NO | The session state. Valid values:
|
| SQL_ID | VARCHAR2(32) | NO | The SQL ID. |
| PLAN_ID | NUMBER | NO | The plan ID of the sampled SQL in the plan cache. This ID is used to associate the sampling point with the plan. |
| TRACE_ID | VARCHAR2(64) | NO | The trace ID of the operator. |
| EVENT | VARCHAR2(64) | NO | The description of the wait event. |
| EVENT_NO | NUMBER | NO | The internal number of the wait event. This number is used for cross-table queries. |
| EVENT_ID | NUMBER | NO | The ID of the current wait event.
Note
|
| P1TEXT | VARCHAR2(64) | NO | The name of the first parameter of the wait event. The name varies with the value of the EVENT field. |
| P1 | NUMBER | NO | The value of the first parameter of the wait event. |
| P2TEXT | VARCHAR2(64) | NO | The name of the second parameter of the wait event. The name varies with the value of the EVENT field. |
| P2 | NUMBER | NO | The value of the second parameter of the wait event. |
| P3TEXT | VARCHAR2(64) | NO | The name of the third parameter of the wait event. The name varies with the value of the EVENT field. |
| P3 | NUMBER | NO | The value of the third parameter of the wait event. |
| WAIT_CLASS | VARCHAR2(64) | NO | The type of the wait event. |
| WAIT_CLASS_ID | NUMBER | NO | The ID of the type of the wait event. This ID is used for cross-table queries. |
| TIME_WAITED | NUMBER | NO | The total waiting time of the wait event, in microseconds (us). |
| SQL_PLAN_LINE_ID | NUMBER | NO | The number of the SQL operator in the SQL plan at the time when the sample was taken. |
| GROUP_ID | NUMBER | NO | The ID of the resource group to which the sample belongs. |
| PLAN_HASH | NUMBER | NO | The plan hash of the SQL statement being executed. |
| THREAD_ID | NUMBER | NO | The ID of the thread to which the active session belongs. |
| STMT_TYPE | NUMBER | NO | The SQL type of the active session. |
| TIME_MODEL | NUMBER | NO | time model information, which is a collection of data from all IN_XXX fields, such as IN_PARSE, IN_PL_PARSE, and so on. |
| IN_PARSE | VARCHAR2(1) | NO | Indicates whether the session is performing SQL parsing at the sampling point. |
| IN_PL_PARSE | VARCHAR2(1) | NO | Indicates whether the session is performing SQL PL parsing at the sampling point. |
| IN_PLAN_CACHE | VARCHAR2(1) | NO | Indicates whether the session is performing plan cache matching at the sampling point. |
| IN_SQL_OPTIMIZE | VARCHAR2(1) | NO | Indicates whether the session is performing SQL parsing optimization at the sampling point. |
| IN_SQL_EXECUTION | VARCHAR2(1) | NO | Indicates whether the session is performing SQL execution at the sampling point. |
| IN_PX_EXECUTION | VARCHAR2(1) | NO | Indicates whether the session is performing parallel execution of SQL at the sampling point. If the session is in this state, it must also be in the IN_SQL_EXECUTION state. |
| IN_SEQUENCE_LOAD | VARCHAR2(1) | NO | Indicates whether the session is performing value retrieval for an auto-increment column or a sequence at the sampling point. |
| IN_COMMITTING | VARCHAR2(1) | NO | Indicates whether the sampling point is in the transaction commit phase.
NoteThis column is available starting with V4.2.1. |
| IN_STORAGE_READ | VARCHAR2(1) | NO | Indicates whether the sampling point is in the storage read phase.
NoteThis column is available starting with V4.2.1. |
| IN_STORAGE_WRITE | VARCHAR2(1) | NO | Indicates whether the sampling point is in the storage write phase.
NoteThis column is available starting with V4.2.1. |
| IN_REMOTE_DAS_EXECUTION | VARCHAR2(1) | NO | Indicates whether the sampling point is in the DAS remote execution phase.
NoteThis column is available starting with V4.2.1. |
| IN_FILTER_ROWS | VARCHAR2(1) | NO | Indicates whether the sampling point is in the storage push-down execution phase. |
| IN_RPC_ENCODE | VARCHAR2(1) | NO | Indicates the serialization operation being performed by the current SQL statement. |
| IN_RPC_DECODE | VARCHAR2(1) | NO | Indicates the deserialization operation being performed by the current SQL statement. |
| IN_CONNECTION_MGR | VARCHAR2(1) | NO | Indicates the connection establishment operation being performed by the current SQL statement. |
| PROGRAM | VARCHAR2(64) | NO | The name of the program being executed at the sampling point:
|
| MODULE | VARCHAR2(64) | NO | The MODULE value recorded at the sampling point. This value is set by using the DBMS_APPLICATION_INFO.SET_MODULE package. |
| ACTION | VARCHAR2(64) | NO | The ACTION value recorded at the sampling point. This value is set by using the DBMS_APPLICATION_INFO.SET_ACTION package. |
| CLIENT_ID | VARCHAR2(64) | NO | The CLIENT_ID value recorded at the sampling point. This value is set by using the DBMS_SESSION.set_identifier package. |
| BACKTRACE | VARCHAR2(512) | NO | An auxiliary debugging column used to record the call stack at the time of the event. The value of this column is always NULL. |
| TM_DELTA_TIME | NUMBER | NO | The time interval for calculating the time model, in microseconds.
Note
|
| TM_DELTA_CPU_TIME | NUMBER | NO | The amount of time spent on the CPU during the TM_DELTA_TIME period.
Note
|
| TM_DELTA_DB_TIME | NUMBER | NO | The amount of time spent on database calls in the last TM_DELTA_TIME period.
Note
|
| TOP_LEVEL_SQL_ID | CHAR(32) | NO | The ID of the top-level SQL statement.
Note
|
| IN_PLSQL_COMPILATION | VARCHAR2(1) | NO | The PL compilation status: Y/N.
Note
|
| IN_PLSQL_EXECUTION | VARCHAR2(1) | NO | The PL execution status: Y/N.
Note
|
| PLSQL_ENTRY_OBJECT_ID | NUMBER | NO | The OBJECT ID of the top-level PL statement.
Note
|
| PLSQL_ENTRY_SUBPROGRAM_ID | NUMBER | NO | The subprogram ID of the top-level PL statement.
Note
|
| PLSQL_ENTRY_SUBPROGRAM_NAME | VARCHAR2(32) | NO | The subprogram name of the top-level PL statement.
Note
|
| PLSQL_OBJECT_ID | NUMBER | NO | The ID of the PL statement currently being executed.
Note
|
| PLSQL_SUBPROGRAM_ID | NUMBER | NO | The subprogram ID of the PL statement currently being executed.
Note
|
| PLSQL_SUBPROGRAM_NAME | VARCHAR2(32) | NO | The subprogram name of the PL statement currently being executed.
Note
|
| TX_ID | NUMBER | NO | The ID of the current transaction.
Note
|
| BLOCKING_SESSION_ID | NUMBER | NO | The ID of the session that is blocking the current session. This column is valid only in lock conflict scenarios, where it displays the ID of the session holding the lock.
Note
|
| TABLET_ID | NUMBER | NO | The ID of the tablet being processed by the current SQL statement.
Note
|
| PROXY_SID | NUMBER | NO | The ID of the proxy session.
Note
|
| DELTA_READ_IO_REQUESTS | NUMBER(38) | NO | The number of read I/O requests between two sampling intervals.
Note
|
| DELTA_READ_IO_BYTES | NUMBER(38) | NO | The total size of read files between two sampling intervals.
Note
|
| DELTA_WRITE_IO_REQUESTS | NUMBER(38) | NO | The number of write I/O requests between two sampling intervals.
Note
|
| DELTA_WRITE_IO_BYTES | NUMBER(38) | NO | The total size of write files between two sampling intervals.
Note
|
| WEIGHT | NUMBER | NO | The number of times the same tenant and action occur within the time range corresponding to this WR record.
NoteFor V4.4.x, this column is available starting with V4.4.2. |
| IS_WR_WEIGHT_SAMPLE | CHAR(1) | NO | Indicates whether this column is an aggregated column for queue backlog waiting events.
NoteFor V4.4.x, this column is available starting with V4.4.2. |
Sample query
Query the active session history (ASH) records of the current OBServer node in the current tenant.
obclient(SYS@oracle001)[SYS]> SELECT * FROM SYS.V$ACTIVE_SESSION_HISTORY WHERE ROWNUM <= 1\G
The query result is as follows:
*************************** 1. row ***************************
SVR_IP: xx.xx.xx.xx
SVR_PORT: 2882
SAMPLE_ID: 859127
SAMPLE_TIME: 09-JAN-26 11.21.51.056069 AM
CON_ID: 1004
USER_ID: 0
SESSION_ID: 2305843009213714606
SESSION_TYPE: BACKGROUND
SESSION_STATE: WAITING
SQL_ID: NULL
PLAN_ID: 0
TRACE_ID: NULL
EVENT: default condition wait
EVENT_NO: 41
EVENT_ID: 15101
P1TEXT: address
P1: 140696681705072
P2TEXT: NULL
P2: 0
P3TEXT: NULL
P3: 0
WAIT_CLASS: CONCURRENCY
WAIT_CLASS_ID: 104
TIME_WAITED: 99802
SQL_PLAN_LINE_ID: NULL
GROUP_ID: 0
PLAN_HASH: NULL
THREAD_ID: 95928
STMT_TYPE: NULL
TIME_MODEL: 0
IN_PARSE: N
IN_PL_PARSE: N
IN_PLAN_CACHE: N
IN_SQL_OPTIMIZE: N
IN_SQL_EXECUTION: N
IN_PX_EXECUTION: N
IN_SEQUENCE_LOAD: N
IN_COMMITTING: N
IN_STORAGE_READ: N
IN_STORAGE_WRITE: N
IN_REMOTE_DAS_EXECUTION: N
IN_FILTER_ROWS: N
IN_RPC_ENCODE: N
IN_RPC_DECODE: N
IN_CONNECTION_MGR: N
PROGRAM: T1004_LogService
MODULE: LogRestoreService
ACTION: RemoteLogWriter
CLIENT_ID: NULL
BACKTRACE: NULL
TM_DELTA_TIME: 997804
TM_DELTA_CPU_TIME: 279
TM_DELTA_DB_TIME: 997804
TOP_LEVEL_SQL_ID: NULL
IN_PLSQL_COMPILATION: N
IN_PLSQL_EXECUTION: N
PLSQL_ENTRY_OBJECT_ID: NULL
PLSQL_ENTRY_SUBPROGRAM_ID: NULL
PLSQL_ENTRY_SUBPROGRAM_NAME: NULL
PLSQL_OBJECT_ID: NULL
PLSQL_SUBPROGRAM_ID: NULL
PLSQL_SUBPROGRAM_NAME: NULL
TX_ID: NULL
BLOCKING_SESSION_ID: NULL
TABLET_ID: NULL
PROXY_SID: 2305843009213714606
DELTA_READ_IO_REQUESTS: 0
DELTA_READ_IO_BYTES: 0
DELTA_WRITE_IO_REQUESTS: 0
DELTA_WRITE_IO_BYTES: 0
WEIGHT: 1
IS_WR_WEIGHT_SAMPLE: N
1 row in set (0.035 sec)
References
After you obtain the ASH records, you can generate an ASH report as needed for analysis. For more information about ASH, see ASH report.