7.126 V$CIRCUIT
V$CIRCUIT
contains information about virtual circuits, which are user connections to the database through dispatchers and servers.
Column | Datatype | Description |
---|---|---|
|
|
Circuit address |
|
|
Current dispatcher process address |
|
|
Current server process address |
|
|
Address of the server process that is waiting for the (currently busy) circuit to become available |
|
|
Address of the session bound to the circuit |
|
|
Status of the circuit:
|
|
|
Queue the circuit is currently on:
|
|
|
Size in bytes of the messages in the first message buffer |
|
|
Size in bytes of the messages in the second message buffer |
|
|
Size in bytes of the messages in the third message buffer |
|
|
Size in bytes of the messages in the fourth message buffer |
|
|
Total number of messages that have gone through this circuit |
|
|
Total number of bytes that have gone through this circuit |
|
|
Total number of breaks (interruptions) for this circuit |
|
|
Presentation protocol used by the client and server |
|
|
Address of the parent circuit |
|
|
Time that a circuit and shared server have been bound (in centiseconds) |
|
|
Provides a reason (a short explanation) for why a shared server and circuit could not be unbound. This column is empty when a circuit is not bound to a server. When the server starts serving a circuit, When this column is not empty, it will be cleared once the server and circuit are unbound (that is, once the resources preventing the session migration to another shared server are released). |
|
|
The ID of the container to which the data pertains. Possible values include:
|
Footnote 1 This column is available starting with Oracle Database release 19c, version 19.1.