[Oralce][InMemory]如何确定一个表已经被Populate 到In Memory 中?

简介:
[Oralce][InMemory]如何确定一个表已经被Populate 到In Memory 中?

以如下方法来查看 POPULATE_STATUS 是不行的。

SQL> select inst_id,
 2  pool
 3  ,alloc_bytes/1024/1024 alloc_mb
 4  ,used_bytes/1024/1024 used_mb
 5  ,populate_status
 6  ,con_id
 7  from gv$inmemory_area;

  INST_ID POOL          ALLOC_MB     USED_MB POPULATE_STATUS     CON_ID
---------- ---------- ----------- ----------- --------------- ----------
        1 1MB POOL       1816903     1451021 DONE                     0
        1 64KB POOL       198075        2174 DONE                     0

        2 1MB POOL       1916903     1449851 DONE                     0
        2 64KB POOL       198075        2170 DONE                     0

最准确的方法,是查看 v$im_segments 的 bytes_not_populated 列:

SELECT
v.owner,
v.segment_name,
v.partition_name,
v.bytes orig_size,
v.inmemory_size in_mem_size,
v.bytes_not_populated not_pop_size,
v.bytes/v.inmemory_size comp_ratio

FROM v$im_segments v;







本文转自健哥的数据花园博客园博客,原文链接:http://www.cnblogs.com/gaojian/p/7625446.html,如需转载请自行联系原作者

目录
相关文章
|
5月前
GEE错误——Layer error: Image.connectedPixelCount: Segment size calculation on floating point bands is n
GEE错误——Layer error: Image.connectedPixelCount: Segment size calculation on floating point bands is n
67 0
|
10天前
|
SQL 关系型数据库 数据库
PostgreSQL数据库报错 ERROR: multiple default values specified for column "" of table "" 如何解决?
PostgreSQL数据库报错 ERROR: multiple default values specified for column "" of table "" 如何解决?
161 59
|
11天前
|
SQL 关系型数据库 MySQL
MySQL 8.0报错--1118-Row size too large. The maximum row size for the used table type, not counting BLOBs,is 8126,
MySQL 8.0报错--1118-Row size too large. The maximum row size for the used table type, not counting BLOBs,is 8126,
MySQL 8.0报错--1118-Row size too large. The maximum row size for the used table type, not counting BLOBs,is 8126,
|
5月前
Elasticsearch【问题记录 02】【不能以root运行es + max virtual memory areas vm.max_map_count [65530] is too low处理】
【4月更文挑战第12天】Elasticsearch【问题记录 02】【不能以root运行es + max virtual memory areas vm.max_map_count [65530] is too low处理】
48 3
|
关系型数据库 MySQL 数据库
MySQL新增字段报错:ERROR 1118 -- Row size too large. The maximum row size for the used table type
MySQL新增字段报错:ERROR 1118 -- Row size too large. The maximum row size for the used table type
1640 0
|
5月前
|
前端开发
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
33 0
|
5月前
|
关系型数据库 MySQL
mysql 5.5.62版本建表语句报错: Index column size too large. The maximum column size is 767 bytes
mysql 5.5.62版本建表语句报错: Index column size too large. The maximum column size is 767 bytes
131 0
|
5月前
|
关系型数据库 MySQL
MySQL【问题 02】报错 1709 - Index column size too large. The maximum column size is 767 bytes. 可能是最简单的方法
MySQL【问题 02】报错 1709 - Index column size too large. The maximum column size is 767 bytes. 可能是最简单的方法
171 0
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
174 0
|
存储 关系型数据库 MySQL
MySQL出现Data too long for column...(错误号1406)和 Data truncated for column...(错误号1265)
MySQL出现Data too long for column...(错误号1406)和 Data truncated for column...(错误号1265)
826 0
MySQL出现Data too long for column...(错误号1406)和 Data truncated for column...(错误号1265)