[20180730]exadata与行链接.txt
[20180730]exadata与行链接.txt
--//最近一段时间在看<expert oracle exadata>,智能扫描的三大优化方法是:字段投影,谓词过滤,存储索引.大多数智能扫描
--//优化方法的主要目标就是在执行扫描时减少需要传输回数据块服务端的数据量.
--//而智能扫描的先决条件,满足三个基本条件:
--//1.必须要是对象上的全扫描.
--//2.扫描必须要使用oracle直接路径读取机制.
--//3.对象必须存储在exadata存储中.
--//有几种情况转换为块传输模式:
--//1.一致性读取,
--//2,行链接(注意:不是行迁移)
--//3.存储服务器CPU太忙.
--//正好生产系统有1张大表存在大量行链接.自己测试看看.
1.环境:
xxxx> @ &r/ver1
PORT_STRING VERSION BANNER
------------------------------ -------------- --------------------------------------------------------------------------------
x86_64/Linux 2.4.xx 11.2.0.4.0 Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
2.测试:
xxxx> select bytes/1024/1024/1024 GB ,BLOCKS from dba_segments where owner='XXXX_YYY' and segment_name='BIG_TAB';
GB BLOCKS
---------- ----------
207.549805 27203968
--//表占用207G.
xxxx> set timing on
xxxx> @ &r/viewsess 'table fetch continued row'
NAME STATISTIC# VALUE SID
-------------------------- ---------- ---------- ----------
table fetch continued row 417 0 2323
Elapsed: 00:00:00.00
xxxx> select /*+ full(a) */ count(*) from xxxxxx_yyy.big_tab a;
COUNT(*)
----------
44669678
Elapsed: 00:01:38.73
xxxx> @ &r/viewsess 'table fetch continued row'
NAME STATISTIC# VALUE SID
------------------------- ---------- ---------- ----------
table fetch continued row 417 0 2323
Elapsed: 00:00:00.01
--//需要大约98秒完成查询.table fetch continued row的记数没有变化.
xxxx> @ &r/desc xxxxxx_yyy.big_tab;
Name Null? Type
------------- -------- ----------------------------
YZBXH NOT NULL NUMBER(18)
BRID NOT NULL NUMBER(18)
ZYH NOT NULL NUMBER(18)
YEPB NOT NULL NUMBER(1)
BRKS NOT NULL NUMBER(4)
BRBQ NUMBER(4)
BRCH VARCHAR2(20)
YDYZLB NOT NULL NUMBER(4)
XMLB NOT NULL NUMBER(8)
...
CAKEY VARCHAR2(2000)
YZCA VARCHAR2(3000)
TZ_CAKEY VARCHAR2(2000)
TZCA VARCHAR2(3000)
HSCAKEY VARCHAR2(2000)
HSCA VARCHAR2(3000)
TZ_HSCAKEY VARCHAR2(2000)
TZ_HSCA VARCHAR2(3000)
DYSJ DATE
YZZXSJ VARCHAR2(80)
ZXTZSJ DATE
ZYDY NUMBER(1)
FZLJ NUMBER(8)
BRZH NUMBER(8)
TZBRZH NUMBER(8)
TJSJ DATE
TQMXBZ NUMBER(1)
--//顺便找靠前的可以为NULL的字段BRBQ. 注意看那些XXkey的字段,正是这些字段导致了大量的行链接与行迁移.
xxxx> select sysdate from dual;
SYSDATE
-------------------
2018-07-30 08:49:54
Elapsed: 00:00:00.01
xxxx> select /*+ full(a) */ count(BRBQ) from xxxxxx_yyy.big_tab a;
select /*+ full(a) */ count(BRBQ) from xxxxxx_yyy.big_tab a
*
ERROR at line 1:
ORA-01013: user requested cancel of current operation
Elapsed: 00:03:09.84
xxxx> select sysdate from dual;
SYSDATE
-------------------
2018-07-30 08:53:37
Elapsed: 00:00:00.00
xxxx> @ &r/viewsess 'table fetch continued row'
NAME STATISTIC# VALUE SID
------------------------- ---------- ---------- ----------
table fetch continued row 417 53476 2323
Elapsed: 00:00:00.00
--//时间太长仅仅测试不到4分钟,放弃!!(注上个星期测试4个小时也没有出来报ora-01555错误,当时选择靠后的字段).说明可以大量的行
--//链接导致无法充分发挥exadata智能扫描的优势,转为块传输模式.
--//如果在服务器上观察可以发现:
# perf top -k /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
PerfTop: 5431 irqs/sec kernel:51.3% exact: 0.0% [1000Hz cycles], (all, 24 CPUs)
----------------------------------------------------------------------------------------------------------
samples pcnt function DSO
_______ _____ _______________________ _______________________________________________________
1125.00 5.3% kafger /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
763.00 3.6% qertbFetchByRowID /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
~~~~~~~~~~~~~~~~
740.00 3.5% kafgex1 /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
740.00 3.5% kcbgtcr /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
607.00 2.8% kdifxs1 /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
477.00 2.2% qerixtFetch /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
451.00 2.1% expepr /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
386.00 1.8% kdsgrp /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
--//出现许多qertbFetchByRowID函数调用.
3.顺便测试exadata的存储索引:
--//重新登录:
xxxx> @ &r/viewsess 'storage'
NAME STATISTIC# VALUE SID
---------------------------------------------------------------------- ---------- ---------- ----------
cell physical IO bytes saved by storage index 274 0 4821
xxxx> @ &r/viewsess 'table fetch continued row'
NAME STATISTIC# VALUE SID
---------------------------------------------------------------------- ---------- ---------- ----------
table fetch continued row 417 0 4821
xxxx> set timing on
xxxx> select /*+ full(a) */ count(*) from xxxxxx_yyy.big_tab a where ZXTZSJ between trunc(sysdate)-1 and trunc(sysdate)-1+1/86400;
COUNT(*)
----------
5
Elapsed: 00:47:05.16
--//仅仅取1秒的日期范围数据,竟然需要47分钟.
xxxx> @ &r/viewsess 'table fetch continued row'
NAME STATISTIC# VALUE SID
---------------------------------------------------------------------- ---------- ---------- ----------
table fetch continued row 417 3461046 4821
Elapsed: 00:00:00.00
xxxx> @ &r/viewsess 'storage'
NAME STATISTIC# VALUE SID
---------------------------------------------------------------------- ------------ ------------ ------------
cell physical IO bytes saved by storage index 274 15562743808 4821
--//15562743808/1024/1024/1024 = 14.49393463134765625
--//15562743808/1024/1024 = 14841.7890625
--//15562743808/8192 = 1899749块
--//竟然存储索引可以使用.我以为会失效.也许前面的部分数据是使用expdp导入的(我当时记忆5XG),可能发生行链接或者迁移的量很少.估计开始
--//实施也不规范,XXkey的字段都是NULL.我估计仅仅没有发生行迁移或者链接的存储单元1M的数据才有存储索引.(我的理解)
--//看看与cell相关的记数变化情况:
xxxx> @ &r/viewsess 'cell'
NAME STATISTIC# VALUE SID
---------------------------------------------------------------------- ------------ ------------ ------------
cell writes to flash cache 58 0 4821
cell overwrites in flash cache 59 0 4821
cell partial writes in flash cache 60 0 4821
cell physical IO interconnect bytes 64 33219425400 4821
cell physical IO bytes saved during optimized file creation 271 0 4821
cell physical IO bytes saved during optimized RMAN file restore 272 0 4821
cell physical IO bytes eligible for predicate offload 273 222633656320 4821
cell physical IO bytes saved by storage index 274 15562743808 4821
cell physical IO bytes sent directly to DB node to balance CPU 275 0 4821
cell smart IO session cache lookups 276 0 4821
cell smart IO session cache hits 277 0 4821
cell smart IO session cache soft misses 278 0 4821
cell smart IO session cache hard misses 279 0 4821
cell smart IO session cache hwm 280 0 4821
cell num smart IO sessions in rdbms block IO due to user 281 0 4821
cell num smart IO sessions in rdbms block IO due to open fail 282 0 4821
cell num smart IO sessions in rdbms block IO due to no cell mem 283 0 4821
cell num smart IO sessions in rdbms block IO due to big payload 284 0 4821
cell num smart IO sessions using passthru mode due to user 285 0 4821
cell num smart IO sessions using passthru mode due to cellsrv 286 0 4821
cell num smart IO sessions using passthru mode due to timezone 287 0 4821
cell num smart file creation sessions using rdbms block IO mode 288 0 4821
cell num block IOs due to a file instant restore in progress 289 0 4821
cell physical IO interconnect bytes returned by smart scan 290 6552450168 4821
cell num bytes in passthru during predicate offload 291 0 4821
cell num bytes in block IO during predicate offload 292 0 4821
cell num fast response sessions 293 0 4821
cell num fast response sessions continuing to smart scan 294 0 4821
cell num smartio automem buffer allocation attempts 295 1 4821
cell num smartio automem buffer allocation failures 296 0 4821
cell statistics spare1 297 0 4821
cell statistics spare2 298 0 4821
cell statistics spare3 299 0 4821
cell statistics spare4 300 0 4821
cell statistics spare5 301 0 4821
cell statistics spare6 302 0 4821
cell scans 421 1 4821
cell blocks processed by cache layer 422 25661755 4821
cell blocks processed by txn layer 423 25661095 4821
cell blocks processed by data layer 424 25282464 4821
cell blocks processed by index layer 425 0 4821
cell commit cache queries 426 0 4821
cell transactions found in commit cache 427 0 4821
cell blocks helped by commit cache 428 0 4821
cell blocks helped by minscn optimization 429 25647939 4821
chained rows skipped by cell 430 3467111 4821
chained rows processed by cell 431 1116529 4821
chained rows rejected by cell 432 3467111 4821
cell simulated physical IO bytes eligible for predicate offload 433 0 4821
cell simulated physical IO bytes returned by predicate offload 434 0 4821
cell CUs sent uncompressed 435 0 4821
cell CUs sent compressed 436 0 4821
cell CUs sent head piece 437 0 4821
cell CUs processed for uncompressed 438 0 4821
cell CUs processed for compressed 439 0 4821
cell IO uncompressed bytes 440 207119351808 4821
cell index scans 457 0 4821
cell flash cache read hits 646 3138149 4821
58 rows selected.
--//对于许多记数不是很熟悉,仅仅做一个记录.
--//附上viewsess.sql脚本:
set verify off
column name format a70
SELECT b.NAME, a.statistic#, a.VALUE,a.sid
FROM v$mystat a, v$statname b
WHERE lower(b.NAME) like lower('%&1%') AND a.statistic# = b.statistic# ;
--and a.value>0;
[20180730]exadata与行链接.txt的更多相关文章
- Oracle 行迁移和行链接
一.行迁移 1.1.行迁移概念 当一个行上的更新操作(原来的数据存在且没有减少)导致当前的数据不能在容纳在当前块,我们需要进行行迁移.一个行迁移意味着整行数据将会移动,仅仅保留的是一个转移地址.因此整 ...
- 参数化时按行读取txt文件，如何去掉换行符"\n"
参数化按行读取txt,每行默认自带了回车换行操作,导致脚本报错,故而按行读取时,需要去掉默认的'\n' #coding=utf-8 from selenium import webdriver imp ...
- 模拟Oracle行迁移和行链接
行链接消除方法创建大的block块------------------ 参考tom kyte的例子----------------------------------------------创建4k ...
- java指定编码的按行读写txt文件（几种读写方式的比较）
转: java指定编码的按行读写txt文件(几种读写方式的比较) 2018年10月16日 20:40:02 Handoking 阅读数:976 版权声明:本文为博主原创文章,未经博主允许不得转载. ...
- [20191010]bash行计算器.txt
[20191010]bash行计算器.txt --//写一个bash行计算器,为了避免冲突,函数命名为2个=,1个=感觉不是很好(心里上^_^).--//使用bc计算器,里面函数不能使用圆括号,使用中 ...
- C语言：按行读TXT文件
//搂行读取TXT #include <stdio.h> #include <stdlib.h> #include <string.h> #define MAX_L ...
- Python中将变量按行写入txt文本中
案例一: 讲数组a 循环写入名称为2.txt的文档中 # -*-coding:utf8-*- import requests from lxml import etree a=[1,2,3,4,5,6 ...
- 按行读取TXT文件中的内容
public Dictionary<int, string> GetDicFromLog() { try { StreamReader sr = new StreamReader(file ...
- java按行读取txt并按行写入
IO流想必大家都很熟悉了,本次实现的需求是按行读取文件内容并且按行写入,代码如下: try { String encoding="utf-8"; //设定自己需要的字符编码集 Fi ...
随机推荐
- Java语言访问Redis数据库之Set篇
如果想通过Java语言对Redis数据库进行访问. 首先,需要安装Redis数据库,可以是Windows系统,或者Linux系统.(本文以Windows系统的本地Redis数据库为例,代码说明如何操作 ...
- HP服务器设置iLO步凑
HP服务器设置iLO步凑 1.开机出现界面—按下F11进入Boot Menu: 2.选择Generic USB Boot回车: 3.选择System Configuration回车: 4.选择iLO ...
- 深入浅出分析MySQL MyISAM与INNODB索引原理、优缺点分析
本文浅显的分析了MySQL索引的原理及针对主程面试的一些问题,对各种资料进行了分析总结,分享给大家,希望祝大家早上走上属于自己的"成金之路". 学习知识最好的方式是带着问题去研究所 ...
- Visual Studio For MacOS 踩坑记(二)
Visual Studio For MacOS安装安卓SDK. 系统默认安装了安卓6.0 API23的SDK. 但是我需要安卓7.0的,API24. 遂安装. SDK可以下载成功,但是用Visu ...
- MariaDB 数据库
1. MariaDB 介绍 MariaDB数据库管理系统是 MySQL 的一个分支,主要由开源社区在维护,采用GPL授权许可 MariaDB的目的是完全兼容MySQL,包括API和命令行,使之能轻松成 ...
- docker 安全
由于容器运行在主机上,且与主机共用一套内核,因此在容器的安全使用上会涉及到容器本身以及主机的安全加固,如针对系统调用,系统资源,远程访问等都需要进行安全方面的考量. docker官网给出了简单的一些建 ...
- redis.properties
#### env:${env} redis.maxIdle= ##最小空闲数 redis.minIdle= ##最大连接数:能够同时建立的“最大链接个数” redis.maxTotal= #每次最大连 ...
- JavaWeb学习 (八)————HttpServletResponse对象(二)
一.HttpServletResponse常见应用——生成验证码 1.1.生成随机图片用作验证码 生成图片主要用到了一个BufferedImage类,
- 简要描述 JavaScript 中定义函数的几种方式
JavaScript 中,有三种定义函数的方式: 1.函数语句:即使用 function 关键字显式定义函数.如: function f(x){ return x+1; } 2.函数定义表达式:也称 ...
- 如何为你的树莓派安装一个WIN10系统？（非iot）
Windows10 ARM版,是的,这次并非IoT版,而是功能与PC一致的ARM版.需要注意的是,这个方法并非官方提供的,可用性上会有一些坑,热衷于尝试的玩家可以一试! 准备项目:树莓派3B以上型号, ...