Oracle 视图 V$INSTANCE_PING 官方解释，作用，如何使用详细说明
本站中文解释
Oracle视图V$INSTANCE_PING是一个动态视图，用于查看当前的Oracle实例是否正在运行。通过它，用户可以得知Oracle实例是否正常运行，以及是否有任何故障。
在运行SQL命令“SELECT * FROM V$INSTANCE_PING;”时，以下信息可以被显示：
• INSTANCE_NAME：向用户显示当前 Oracle 实例的名称。
• SERVER_VERSION：显示当前 Oracle实例的版本号。
• PING_TIME：显示当前 Oracle实例的响应时间。
• PING_USER：显示上次 ping 发出的用户的用户名。
• PING_STATUS：向用户显示 Oracle实例是正常启动还是损坏，此列可显示以下值：
NORMAL：表示Oracle实例正常启动。
DAMAGED：表示Oracle实例损坏。
官方英文解释
V$INSTANCE_PING provides information about measured latency of the interconnect for all instances in an Oracle Real Application Clusters (Oracle RAC) environment.
In an Oracle RAC environment, every few seconds the PING process of each instance checks the response of the interconnect to all instances of the same database.
It sends two messages. One message is 500 bytes in size (referred to in the column descriptions as 500B), and the other is 8 kilobytes in size (referred to in column descriptions as 8K).
For each message sent to each instance, the amount of time it took to get a response back is measured (in microseconds). The view records the latest measurements as well as cumulative data since instance startup.
| Column | Datatype | Description |
|---|---|---|
|
|
|
The instance communicated with. In the V$ view for each instance, there is one row for that instance, and in the GV$ view for each instance, there is also one row for that instance, so there are n2 rows for n instances. |
|
|
|
The latest response time for the 500B message (in microseconds) |
|
|
|
The average response time for the 500B messages since instance startup (in microseconds). Note that |
|
|
|
The maximal response time for the 500B messages since instance startup (in microseconds) |
|
|
|
The number of measurements for the 500B messages since instance startup |
|
|
|
The sum of all response times for the 500B messages since instance startup (in microseconds) |
|
|
|
The sum of the response time squared for 500B messages since instance startup. The unit is in microseconds squared and divided by 1000. |
|
|
|
The latest response time for the 8K message (in microseconds) |
|
|
|
The average response time for the 8K messages since instance startup (in microseconds). Note that |
|
|
|
The maximal response time for the 8K messages since instance startup (in microseconds) |
|
|
|
The number of measurements for the 8K messages since instance startup |
|
|
|
The sum of all response times for the 8K messages since instance startup (in microseconds) |
|
|
|
The sum of the response time squared for 8K messages since instance startup. The unit is in microseconds squared and divided by 16. |
|
|
|
The ID of the container to which the data pertains. For this view, the possible values include:
|
