之前看了这篇文章 “坑爹”的绿盟数据库漏扫，求你专业一点 ,讲几点个人的看法。

因为近期国内勒索病毒问题频发，可以观测到QQ群内大量甲方人员提问关于绿盟扫描的问题。

文章的主旨是说 绿盟的ORACLE 数据库漏洞扫描的结果比较不靠谱，已经装了的补丁，扫描的结果仍是存在漏洞，让甲方的人员很苦恼。

 

绿盟号称是在企业安全市场占有率最高的公司，拥有自己的产品和服务，涉猎企业IT环境中的几乎所有的服务器、软件的安全问题，这几年由于安全问题越来越被重视，这类安全公司确实也跟着火了。

我曾经2013年在某省移动驻场负责维护几十套Oracle数据库，每季度都会收到绿盟发来的漏洞列表，第一次发来几千项，企信部领导“高度重视”，让我连夜排查并给出解决方案。当时大多数数据库版本是11203，且安装了较新的PSU，我发现漏洞里面居然还存在2009年的CVE高危漏洞，当时就纳闷Oracle自己在2009年公布的漏洞到现在咋还没修复呢？

通过原厂确认，首先Oracle不认可任何第三方软件的漏洞扫描结果，其次绿盟的漏洞扫描机制简单粗暴，基本上没有可信度，后来和甲方DBA达成共识：1、安装最新的PSU，2、通过技术手段屏蔽绿盟的扫描。

没想到现在都2019年了，这个问题依然存在，不知道产品经理是不是去岘港度假被抓了，看看苦逼DBA们被坑害的反馈吧：

首先说说绿盟漏扫的”业余“机制吧，通过数据库版本号直接去匹配Oracle官方的CVE漏洞列表，不会检测PSU。拜托，现在大多数科技公司都在应用AI、机器学习了，您还在通过几个数字匹配表格来定义企业的信息安全分数，真是太“LOW”，哪还有安全可言。

给出了一大堆漏洞，高危的红色，让领导瑟瑟发抖，我想绿盟可能还会觉得自己很牛X吧。然而却没有给出解决方案，最多丢一个Oracle 的CVE链接给你，自己去找补丁，各个补丁之间还可能冲突，对了这里是CPU，-_-||

无力吐槽！

给乙方DBA的建议：

1、不要浪费时间尝试根据不可信的漏洞列表一一去找单个的补丁，直接安装最新的PSU即可（不过最佳实践是次新，另外12.2改为RU）。

2、觉得不好交差，或者强迫症，可以通过防火墙、端口、数据库IP限制等方式限制绿盟机器的访问；

3、把“皮球”抛给现场的绿盟GG，让他们去跟甲方解释，承认这是绿盟漏扫软件的缺陷；

4、使用专业的数据库巡检平台检查数据库，从数据库的角度去排查安全问题。

给绿盟的建议：

1、希望绿盟专业一点，牢记“专功术业”的愿景，真正做到“成就所托”，不要学早期的360通过报大量高危漏洞吓唬用户来体现自身卑微的价值；

2、学习了解Oracle的补丁策略，弄清楚One of Patch、CPU、PSU、RU的区别以及大版本小版本的关系，分别修复了哪些CVE漏洞，如果真的存在漏洞，那么给出专家的方案，不要给个CVE链接草草了事，我相信这些需求相对来说比较容易，如果需要我们可以免费支持；

3、多听听业界的声音和用户的反馈，快速迭代改进产品，不然没有核心竞争力，分分钟被替代被超越。

最后还是诚恳的呼吁绿盟团队，尽快把自己产品的缺陷修复，完善各项功能，真正为国内企业信息安全建设贡献更多的力量，“专功术业，成就所托”。

 

 

结论是让绿盟在扫描上专业一点，改进产品。

评论里又绿盟的相关人员驳斥了文章观点，认为绿盟扫描结果不准确是因为 没有做登陆扫描。

 

@楼主，看你的描述，13年就接触数据库漏洞处理并接触了漏洞扫描器，不过看起来这么多年你也没有潜心研究漏洞扫描器原理、没有思考为啥这么多年误报问题一直无法解决、也没有尝试去找厂家研究扫描功能、也没有思考国内安全厂商的技术瓶颈与困境，给出可供参考的意见和建议，通篇只有闹骚满腹，无尽抱怨，看来你这么多年也没有进步，也没有看到别人的进步，希望你还是摆正心态，踏实做事。

完全站在dba的角度去考虑安全，实话说挺无知的
1.先搞清楚基于网络的漏洞扫描原理，存活判别，应用识别，发包探测和回应到底能获取目标对象多少信息？
2.登录扫描原理，登录目标对象后到底能获取多少信息，是否会执行命令？什么情况下执行poc
3.想问问lz，哪个大厂的漏扫可以精准判断oracle漏洞？如果都不行，自己有思考过原因何在吗？光在这里瞎bb

楼主难道不知道登录扫描么？给建议，据说绿盟登录扫描很早就实现了，楼主没用过么？怪不得不知道，发文章

首先，远程扫描返回的banner不带patch，其次，还有登陆扫描的功能。
但，更多的情况是甲方不愿意把数据库的登陆方式交给除了数据库厂家外的其他乙方。吃得咸鱼抵得渴，不提供密码，扫描结果不准确那就自己受着。所以，涉密的东西还是甲方或者相关厂家自己做吧，别什么都赖给别人，自己不作为还怪别人呢。

太可怕了，lz 6年还没搞懂什么是登录扫描

 

 

上面陈述了一些问题，这里讲讲我的看法，一家之言

 

1. 没有做登陆扫描，主要原因一般是甲方人员并不放心把账户密码给来做扫描的技术人员；以人之常情而论，我相信90%的甲方同学并不愿意做登陆扫描
2. 因为 第一点的这个情况，导致绿盟的扫描结果，大多数情况下不准确和无价值
3. 打一个不恰当的比方，用户去医院看病，医生让验血/拍片，但用户都不愿意验血/拍片；因为不愿意验血/拍片，所以医生几乎没有可参考的信息
4. 在这种情况下，医生罗列了所有病人可能患的病症，列可能性嘛，多列一些总不会错
5. 用户面对医生罗列的一大堆病症可能性，无所适从

 

这里划分一下责任:

1. 这里可以看到，甲方的责任在于虽然有配合扫描漏洞的义务，但并不乐意真的提供账号密码来做登陆扫描。
2. 绿盟方面可能没有强调登陆扫描的重要性， 实际上 不做登陆扫描的话 ， 报告可以认为是没意义的，但这件事也就不用做了
3. 绿盟方面因为要在没有可能获得完整信息的情况下，给出报告。强行罗列了其可以确定的可能性，这导致维护方最后要么不处理，要么很吃瘪

 

最后说几点建议:

 

1. 如果甲方同意做漏洞扫描，就该开放账户密码给绿盟。绿盟在做扫描前应该确认这一点，如果甲方不愿意提供，那么强行去做这些事，可以说是走过场的形式主义
2. 国内大部分非外企或上市企业使用的要么是盗版ORACLE，要么从来不购买ORACLE标准服务；这种情况下做漏洞扫描，即便出了准确结果，甲方也并没有合法途径去获得相关的安全性补丁，从网上的非官方渠道下载一些补丁，岂不是更不安全？ 所以对于使用盗版ORACLE或者从不购买ORACLE标准服务的甲方，从法理上不建议去做这些漏洞扫描。这类甲方应当适当提高内网安全系数，避免ORACLE有暴露在外的可能性
3. ORACLE每季度都会出新的PSU/SPU(以前叫CPU 即安全补丁)，虽然重要度可能并不均匀（例如一年中只有一个季度发布了适应面很广，影响很大的漏洞）；但可以说永远可能会发现新的安全漏洞；如果是顶级的企业，无所谓人力成本，当然可能每年升级个几次，但一般来说是不可能的，成本不可控
4. 就Maclean的经验来看，中国和美国的顶级银行或企业都并不会如第三条这样做，打SPU的情况都是少数，除非特别需要
5. 目前阶段，国内的主要安全趋势还是做好内网安全，能把弱密码和低版本的Windows/Linux全干掉，把无密码的MongoDB/Redis干掉，已经功德无量了
6. 如果还有同学被绿盟的问题难住，可以耐心看下网上的许多评论，耐心和领导说明；毕竟我们纯技术人员，能做的事，或者说能做到的事并不多啊！

 

 

 

putty                                        https://zcdn.askmac.cn/putty.exe
mobaxterm                              https://zcdn.askmac.cn/MobaXterm_Portable_v20.2.zip
teamviewer 14                        https://zcdn.askmac.cn/tv14.exe
xmanager 4                              https://zcdn.askmac.cn/Xme4.exe
xmanager 6                             https://zcdn.askmac.cn/Xme6.exe
cmder                                         https://zcdn.askmac.cn/cmder.zip
sqldeveloper                             https://zcdn.askmac.cn/sqldeveloper-19.1.0.094.2042-no-jre.zip
chrome win                                https://zcdn.askmac.cn/chrome-win.zip

bbed linux                              https://zcdn.askmac.cn/linux%20bbed.zip

bbed windows                          https://zcdn.askmac.cn/9ibbedfull.zip

everything                          https://zcdn.askmac.cn/Everything.exe

notepad++                        https://zcdn.askmac.cn/npp.7.3.1.Installer.exe

touch.exe                                https://zcdn.askmac.cn/touch.exe

winscp                                  https://zcdn.askmac.cn/winscp564setup.exe

vncviewer                         https://zcdn.askmac.cn/vncviewer.exe

hxd                                        https://zcdn.askmac.cn/HxD.exe

mysqlscan                            https://zcdn.askmac.cn/mysqlscan

xshell                                    https://zcdn.askmac.cn/Xshell-6.0.0197r.exe

 

PRM DUL  https://zcdn.parnassusdata.com/DUL5108.zip

PRM DUL latest: https://zcdn.parnassusdata.com/DUL5108rc12_java.zip

OpenJDK windows x86-64 : https://zcdn.parnassusdata.com/java-1.8.0-openjdk-1.8.0.232-1.b09.ojdkbuild.windows.x86_64.msi

Amazon JDK windows x86-64: https://zcdn.parnassusdata.com/amazon-corretto-8.232.09.1-windows-x64.msi

Windows X86-64: http://zcdn.parnassusdata.com/jdk-8u181-windows-x64.exe

LIUNX X86-64: http://zcdn.parnassusdata.com/jdk-8u91-linux-x64.rpm

 

 

 

JDK

 

JDK 1.8 DOWNLOAD URL:
AIX JAVA SDK: http://zcdn.parnassusdata.com/Java8_64.sdk.8.0.0.527.tar.gz
AIX JRE: http://zcdn.parnassusdata.com/Java8_64.jre.8.0.0.527.tar.gz
LINUX X86: http://zcdn.parnassusdata.com/jdk-8u201-linux-i586.rpm
LIUNX X86-64: http://zcdn.parnassusdata.com/jdk-8u91-linux-x64.rpm
Windows X86: http://zcdn.parnassusdata.com/jdk-8u201-windows-i586.exe
Windows X86-64: http://zcdn.parnassusdata.com/jdk-8u181-windows-x64.exe
HPUX Itanium: http://zcdn.parnassusdata.com/Itanium_JDK_8.0.16_December_2018_Z7550-63506_java8_18016_ia.depot


AIX JDK 6 https://zcdn.askmac.cn/Java6_64.sdk.6.0.0.655.tar

AIX JDK 8

https://zcdn.askmac.cn/Java8_64.jre.8.0.0.610.tar.gz
https://zcdn.askmac.cn/Java8_64.sdk.8.0.0.610.tar.gz

squirrel-sql-3.9.0: http://zcdn.parnassusdata.com/squirrel-sql-3.9.0-standard.jar
db-derby-10.14.2.0: http://zcdn.parnassusdata.com/db-derby-10.14.2.0-bin.zip

Derby IJ Connection setting:

Windows:
C:\> set DERBY_INSTALL=C:\Apache\db-derby-10.14.2.0-bin
C:\> set CLASSPATH=%DERBY_INSTALL%\lib\derby.jar;%DERBY_INSTALL%\lib\derbytools.jar;.
C:\> cd %DERBY_INSTALL%\bin
C:\Apache\db-derby-10.14.2.0-bin\bin> setEmbeddedCP.bat

LINUX/UNIX
$ export DERBY_INSTALL=/opt/Apache/db-derby-10.14.2.0-bin
$ export CLASSPATH=$DERBY_INSTALL/lib/derby.jar:$DERBY_INSTALL/lib/derbytools.jar:.
$ cd $DERBY_INSTALL/bin
$ . setEmbeddedCP


java org.apache.derby.tools.sysinfo

java org.apache.derby.tools.ij

connect 'jdbc:derby:\dbinfo\parnassus_dbinfo_DB_20190127144050';
show schemas;
show tables;



clash for windows:   https://zcdn.askmac.cn/Clash.for.Windows-0.6.0-win.zip
surge :              https://zcdn.askmac.cn/Surge-latest.zip

prm dul恢复oracle数据库最简模式                                              http://zcdn.parnassusdata.com/prm%20dul%20recover%20oracle%20database%20easiest%20way.mp4
prm dul使用数据搭桥传输Oracle表数据                                          http://zcdn.parnassusdata.com/prm%20dul%20databridge%20transfer%20oracle%20table.mp4
prm dul在损坏数据库使用exportddl导出建表语句、索引、存储过程、函数等代码      http://zcdn.parnassusdata.com/prm%20dul%20export%20ddl%20from%20corrupted%20oracle%20database.mp4
prm dul恢复oracle中被delete的数据                                            http://zcdn.parnassusdata.com/prm%20dul%20recover%20oracle%20deleted%20rows.mp4
prm dul恢复oracle中被truncate的数据                                          http://zcdn.parnassusdata.com/prm%20dul%20recover%20oracle%20truncated%20table.mp4
prm dul用户级别的数据搭桥                                                    http://zcdn.parnassusdata.com/prm%20dul%20schema%20level%20databridge.mp4
prm dul在ASM存储情况下的最简模式                                             http://zcdn.parnassusdata.com/prm%20dul%20easiest%20way%20with%20ASM%20storage.mp4
prm dul恢复oracle中被drop掉的表                                              http://zcdn.parnassusdata.com/prm%20dul%20recover%20oracle%20dropped%20table.mp4
prm dul恢复oracle 12c以后可拔插数据库PDB/CDB中的数据                         http://zcdn.parnassusdata.com/prm%20dul%20work%20with%20oracle%2012c%20pdb%20pluggable%20database%20container%20database.mp4
prm dul恢复被恶意加密的Oracle数据文件                                        http://zcdn.parnassusdata.com/prm%20dul%20recover%20malware%20ransomware%20corrupted%20oracle%20datafile.mp4
prmscan oracle数据块重组恢复解决方案                                         http://zcdn.parnassusdata.com/prmscan.mp4

run {
allocate channel ch1 type 'sbt_tape'  PARMS="SBT_LIBRARY=/usr/local/commvault/Base64/libobk.so,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch4,ThreadCommandLine=-chg 2:2 -rac 21 -vm Instance001)";
restore archivelog sequence XX thread 2;
release channel ch1;
}

大致看了下mysql 的double write buffer概念 ：

So why doublewrite is needed ? It is needed to archive data safety in case of partial page writes. Innodb does not log full pages to the log files, but uses what is called “physiological” logging which means log records contain page number for the operation as well as operation data (ie update the row) and log sequence information. Such logging structure is geat as it require less data to be written to the log, however it requires pages to be internally consistent. It does not matter which page version it is – it could be “current” version in which case Innodb will skip page upate operation or “former” in which case Innodb will perform update. If page is inconsistent recovery can’t proceed.

Now lets talk a bit about partial page writes – what are they and why are they happening. Partial page writes is when page write request submited to OS completes only partially. For example out of 16K Innodb page only first 4KB are updated and other parts remain in their former state. Most typically partial page writes happen when power failure happens. It also can happen on OS crash – there is a chance operation system will split your 16K write into several writes and failure happens just between their execution. Reasons for splitting could be file fragmentation – most file systems use 4K block sizes by default so 16K could use more than one fragment. Also if software RAID is used page may come on the stripe border requiring multiple IO requests. Same happens with Hardware RAID on power failure if it does not have battery backed up cache. If there is single write issued to the disk itself it should be in theory completed even if power goes down as there should be enough power accomulated inside the drive to complete it. I honestly do not know if this is always the case – it is hard to check as it is not the only reason for partial page writes. I just know they tend to happen and before Innodb doublewirite was implemented I had couple of data corruptions due to it.

So how does double write works ? You can think about it as about one more short term log file allocated inside Innodb tablespace – it contains space for 100 pages. When Innodb flushes pages from Innodb buffer pool it does so by multiple pages. So several pages will be written to double write buffer (sequentially), fsync() called to ensure they make it to the disk, then pages written to their real location and fsync() called the second time. Now on recovery Innodb checks doublewrite buffer contents and pages in their original location. If page is inconsistent in double write buffer it is simply discarded, if it is inconsistent in the tablespace it is recovered from double write buffer.

 

我是这样认为的 其实oracle中也有写 partial page(block)的可能，只不过 o的redo和controlfile 检查点比较严谨， 不在需要这样一个区域了。

对于 partial page(block) 的前滚，o也有这样的情况，例如 一个已经写好的块， 增量检查点 未必更新了控制文件， o认为 这个块不是最新的， 那么o也会同样的再写一次 ，即便这个块已经是最新的。 这种机制在oracle中称为resilver write 镀银写。

 

 

Most data blocks are changed via redo and written by DBWR. These writes are coordinated by cache locks that insure there is only one current dirty buffer for any given block. If DBWR dies for any reason, its instance will also die. It will be necessary to do some form of recovery applying redo to reconstruct the blocks that were in the cache at the time of the failure. This recovery will have to either read or write any block that is both modified by redo, and might have been in the middle of a write when DBWR died. Thus, these blocks are a superset of the blocks that Oracle must resilver if it is responsible for resilvering. Hence, during recovery, Oracle will rewrite every block it examines in files it is responsible for resilvering. Since media recovery may be used to recover changes lost when an instance dies, Oracle must also resilver when doing media recovery.
Data blocks used for sorting are modified without generating any redo. They are still written by DBWR. These blocks are never read by any process other than the one doing the sort, and if its DBWR dies then it too will die. Thus it is not important that these blocks become resilvered.

 

 

mysql里叫double write, o 里叫 resilver write。 目的应该是一样的，机制不同，mysql 里知名度很高 可能是因为其可以关闭。 o里面就没人研究能不能关这个了。

 

 

补充：  double write的核心意义在于减少partial page writes的可能性，特别是对于instance crash导致的partially written；其原理是依赖于两次先后的fsync()来保证实际的数据落盘。

 

对于Oracle而言，确实是可能存在partially written block的现象的，这种现象o中体现为fractured block块断裂 ： A fractured block is one that was partially written to disk, leaving a previous version on part of the block.

 

对于mysql中的double write，其也只能减少partial page writes的可能性，是并不能杜绝的，因为其还是依赖于fsync()。假设我们有一个调皮的存储子系统，对于第一次的fsync()尽职尽责地完成了，而对于第二次的fsync()只完成了一半就成功返回了。此时如果没有发生instance crash，那么也就没有对应的crash recovery发生。MySQL应当也不会去检查double write buffer和对应的page。那么还是会造成partially written。或者在MySQL Recovery情况下检测double write buffer和page内容是读取了文件系统或存储系统内被更新的缓存，那么还是会骗过这次检测。

double write更多的是为了保护crash recovery情况下可能发生的partially written；并不能完全杜绝存储子系统去“欺骗”它。

不管是Oracle还是MySQL，基本都基于现代存储子系统是基本可靠的这一点出来来设计。

对于Oracle而言，如果在crash recovery阶段发现了fractured block块断裂，那么确实它也是无法基于redo去恢复它的。用户也需要基于backup去恢复对应的数据块。

因为oracle的redo也是仅仅记录redo vector的，而不记录block的full image，仅仅在做hot backup是记录block full image。

oracle中引入了参数_db_writer_verify_writes ：Enable lost write detection mechanism

 

Parameter Type:string
Allowable Values: TRUE, LIOCHK, SCNCHK and FALSE.
Typical Values: User would use a value of either TRUE or FALSE.
Default Value: FALSE.
Dangerous Values: NA.
Description: This parameter will performs lost write detection.
Dynamic: No.
Syntax: _db_writer_verify_writes = <string value>

Algorithm: This parameter defaults to FALSE at startup. If set to LIOCHK we read the bunch of blocks, written by this DBWR process recently, into a PGA array and check the complete contents of the block with a memcmp. If set to SCNCHK we log the SCN of a block change into the simulated buffer header and check it back on read if the simulated buffer is still in the cache. If set to TRUE both SCNCHK and LIOCHK are performed. The performance overhead fromboth these changes is minimal.

 

简而言之，这个参数做的就是对DBWR写出的block，马上读取到PGA中做一个验证。这样能发现如下的情况：

• fractured block 即写了一部分，partially written
• Lost Write，写丢失

在Oracle中fractured block可以被算作physical corruption物理损坏，而Lost Write写丢失一般被认为是逻辑损坏。 写丢失是指这个该被写出更新的数据块一个字节都没更新，IO子系统欺骗上层DB引擎说已经写出了。

非instance crash情况下的partially written部分写块和lost write完全没写，其实是不多的；Mysql的double write机制保证了在crash recovery场景中存储子系统基本没问题的情况下，partially written和lost write不发生。

同时由于MySQL所处的存储子系统环境的复杂度往往没有oracle高，大部分采用本地磁盘或者没有复杂镜像基础的存储技术。而oracle中我们在采用大量存储镜像基础的用户哪里，是能明确遇到一些由于存储镜像技术问题造成的写丢失问题的：即Oracle写入到主镜像，存储成功返回；在后续的操作中Oracle读取到这些数据块，却没有被更新，因为读取到了没更新的存储镜像。这些故障的大量表象是ORA-08103,ORA-01410和一些ORA-00600报错。对于普通的存放ROW的block而言，lost write发生后甚至没有任何报错，也几乎无法让人察觉到，因为这个块本身内容是完全合法的。

在Oracle 11g中引入了db_lost_write_protect 参数来进一步防御写丢失，但该特性需要一般依赖于物理备库的存在。

 

 

目前 （2019年5月21日)似乎MOS上找不到 控制19c Automatic Indexing 自动建索引特性的Notes，大致可以通过 _optimizer_auto_index_allow 和 _optimizer_use_auto_indexes 2个参数关闭该新特性。

 col name format a40
 SELECT x.ksppinm NAME, y.ksppstvl VALUE
  FROM SYS.x$ksppi x, SYS.x$ksppcv y
  WHERE x.inst_id = USERENV ('Instance')
  AND y.inst_id = USERENV ('Instance')
  AND x.indx = y.indx
 AND x.ksppinm LIKE '%index%';
 
 NAME                                               VALUE
-------------------------------------------------- ------------------------------------------------------------
_optimizer_auto_index_allow                        AUTO
_gc_defer_ping_index_only                          TRUE
_kcl_index_split                                   TRUE
_gc_fast_index_split_wait                          0
_index_partition_large_extents                     FALSE
_index_partition_shrink_opt                        TRUE
_db_index_block_checking                           TRUE
_disable_index_block_prefetching                   FALSE
_index_scan_check_skip_corrupt                     FALSE
_index_scan_check_stopkey                          FALSE
_index_max_inc_trans_pct                           20
_index_split_chk_cancel                            5
_advanced_index_compression_trace                  0
db_index_compression_inheritance                   NONE
_index_alert_key_not_found                         FALSE
_reuse_index_loop                                  5
_reclaim_lob_index_scan_limit                      0
_ignore_desc_in_index                              FALSE
_index_load_buf_oltp_sacrifice_pct                 10
_index_load_buf_oltp_under_pct                     85
_index_load_buf_oltp_over_retry                    0
_index_load_last_leaf_comp                         85
_index_load_min_key_count                          10
_index_load_analysis_frequency                     4
_advanced_index_compression_umem_options           2147483647
_advanced_index_compression_options                0
_advanced_index_compression_cmp_options            0
_advanced_index_compression_tst_options            0
_advanced_index_compression_opt_options            0
_advanced_index_compression_options_value          0
_advanced_index_compression_recmp_cusz             90
_advanced_index_compression_recmp_crsz             10
_advanced_index_compression_recmp_nprg             10
_kdkv_index_lossy                                  TRUE
_kdkv_index_relocate                               FALSE
_kdkv_indexinvalid                                 FALSE
_domain_index_batch_size                           2000
_domain_index_dml_batch_size                       200
_odci_index_pmo_rebuild                            FALSE
_cell_index_scan_enabled                           TRUE
optimizer_index_cost_adj                           100
optimizer_index_caching                            0
_system_index_caching                              0
_index_prefetch_factor                             100
_index_join_enabled                                TRUE
_use_nosegment_indexes                             FALSE
_optimizer_compute_index_stats                     TRUE
skip_unusable_indexes                              TRUE
_delay_index_maintain                              TRUE
_disable_function_based_index                      FALSE
_globalindex_pnum_filter_enabled                   TRUE
_enable_online_index_without_s_locking             TRUE
_optimizer_fkr_index_cost_bias                     10
optimizer_use_invisible_indexes                    FALSE
_noseg_for_unusable_index_enabled                  TRUE
_px_index_sampling_objsize                         TRUE
_part_redef_global_index_update                    TRUE
_fast_index_maintenance                            TRUE
_modify_column_index_unusable                      FALSE
_indexable_con_id                                  TRUE
_optimizer_use_auto_indexes                        AUTO
_optimizer_gather_stats_on_load_index              TRUE

 
 
 
 
 
 _optimizer_auto_index_allow
 _optimizer_use_auto_indexes
 
 
 
 
 SQL> alter system set "_optimizer_auto_index_allow"=0 scope=spfile;
alter system set "_optimizer_auto_index_allow"=0 scope=spfile
*
ERROR at line 1:
ORA-00096: invalid value 0 for parameter _optimizer_auto_index_allow, must be from among ALWAYS, AUTO, NEVER



alter system set "_optimizer_auto_index_allow"=NEVER scope=spfile;


alter system set "_optimizer_use_auto_indexes"=NEVER scope=spfile;
ERROR at line 1:
ORA-00096: invalid value NEVER for parameter _optimizer_use_auto_indexes, must be from among ON, AUTO, OFF


alter system set "_optimizer_use_auto_indexes"=OFF scope=spfile;

19C has a new feature database 19c is automatic indexing. How does it work?

QUESTIONS AND ANSWERS

How does automatic indexing work?
This is fully automated process. Oracle will identify candidate indexes,
verify their effectiveness, perform online validations and then implement the indexes where appropriate.

DBA does not need to do anything. Oracle internally picks the candidate indexes and validates the index or indexes.

Does any parameters need to be set for the automatic indexing to work?
Per documentation:
21.7.3 Enabling Automatic Indexing
Automatic indexing is disabled by default in an Oracle database. To enable
automatic indexing, set the AUTO_IMPLEMENT_INDEXES initialization parameter
to the Oracle database release number, for example, 19.1. You can disable
automatic indexing by setting the AUTO_IMPLEMENT_INDEXES initialization
parameter to NONE.

Database Oracle
Oracle Database Release 19
Database Administrator’s Guide

https://docs-stage.oracle.com/en/database/oracle/oracle-database/19/admin/managing-indexes.html#GUID-6E31777C-3BE3-4510-90D5-C715644E00CB

However, the parameter does not seem to exist though and cannot be used in 19.1

The parameter to control/enable automatic indexing is available in the next
refresh of the RDBMS, 19.2. per following internal bug:

Bug 29001016 – 19CBETA CANNOT USE AUTOMATIC INDEXING FUNCTIONALITY – PARAMETER MISSING

https://github.com/macleanliu/ora-easy-deploy

 

 

ora-easy-deploy  WORKS ON (CENTOS REDHAT ORACLE) LINUX 7


国外主机

su - root 
yum -y install git 
git clone https://github.com/macleanliu/ora-easy-deploy
wget https://www.dropbox.com/s/8097ds292gabpk9/oracle-database-ee-19c-1.0-1.x86_64.rpm
wget https://www.dropbox.com/s/x14jlgnj062nef2/oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm
yum -y localinstall oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm
rpm -ivh oracle-database-ee-19c-1.0-1.x86_64.rpm
bash ora-easy-deploy/create_db.sh

国内主机


wget --no-check-certificate https://zcdn.askmac.cn/oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm
wget --no-check-certificate https://zcdn.askmac.cn/oracle-database-ee-19c-1.0-1.x86_64.rpm


su - root 
yum -y install git 
git clone https://github.com/macleanliu/ora-easy-deploy
yum -y localinstall oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm
rpm -ivh oracle-database-ee-19c-1.0-1.x86_64.rpm
bash ora-easy-deploy/create_db.sh


安装完成后#设置ORACLE OS账户密码

su - root
passwd oracle                     
su - oracle

lsnrctl start 
sql
alter system register;


[oracle@vultr ~]$ sql

SQL*Plus: Release 19.0.0.0.0 - Production on Wed May 15 07:09:52 2019
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0


SQL> alter system register;

System altered.

SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0


[oracle@vultr ~]$ lsnrctl status

LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 15-MAY-2019 07:28:31

Copyright (c) 1991, 2019, Oracle.  All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date                15-MAY-2019 07:27:06
Uptime                    0 days 0 hr. 1 min. 24 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Log File         /opt/oracle/diag/tnslsnr/vultr/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=vultr.guest)(PORT=1521)))
Services Summary...
Service "PROD" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...
Service "PRODXDB" has 1 instance(s).
  Instance "PROD", status READY, has 1 handler(s) for this service...
The command completed successfully






关闭部分19c特性sql


alter system set "_optimizer_aggr_groupby_elim"=false;
alter system set "_drop_stat_segment"=1;
alter system set "_common_data_view_enabled"=false;
alter system set optimizer_adaptive_features=false;
alter system set "_optimizer_dsdir_usage_control"=0; 
alter system set "_enable_automatic_sqltune"=false scope=both; 
alter system set "_serial_direct_read"=false;
alter system set "_nlj_batching_enabled" = 0; 
alter system set "_optimizer_undo_cost_change" = '10.2.0.4';
alter system set "_optimizer_null_aware_antijoin" = false;
alter system set "_optimizer_extend_jppd_view_types" = false;
alter system set "_replace_virtual_columns" = false;
alter system set "_first_k_rows_dynamic_proration" = false;
alter system set "_bloom_pruning_enabled" = false;
alter system set "_optimizer_multi_level_push_pred" = false;
alter system set "_optim_peek_user_binds"=false; 
alter system set client_result_cache_size=0 scope=spfile;
alter system set result_cache_mode=MANUAL;
alter system set "_diag_hm_rc_enabled"=false; 
alter system set audit_trail=none scope=spfile;
alter system set "_memory_imm_mode_without_autosga"=false scope=both; 
alter system set "_enable_shared_pool_durations"=false scope=spfile;
alter system set deferred_segment_creation=false; 
alter system set "_datafile_write_errors_crash_instance"=false ;
alter system set "_fairness_threshold"=6 scope=spfile;
alter system set "_gc_read_mostly_locking"=false scope=spfile;
alter system set "_gc_policy_time"=0 scope=spfile;
alter system set "_gc_defer_time"=3  scope=spfile;
alter system set "parallel_force_local"=false;
alter system set "_gc_bypass_readers"=false;
alter system set "_row_cr"=false;
alter system set ddl_lock_timeout=0;
alter system set "_gby_hash_aggregation_enabled"=False scope=spfile;
alter system set "_cleanup_rollback_entries"=400 scope=spfile;
alter system set "_dbms_sql_security_level"=0                          scope=spfile;
alter system set "_bloom_pruning_enabled"=False                        scope=spfile;
alter system set "_simple_view_merging"=True                           scope=spfile;
alter system set "_enable_NUMA_optimization"=FALSE                     scope=spfile;
alter system set "_fix_control"='9344709:OFF'                           scope=spfile;
alter system set "_px_use_large_pool"=True                              scope=spfile;
alter system set "_mv_refresh_use_hash_sj"=FALSE                      scope=spfile;
alter system set "_mv_refresh_use_stats"=True                          scope=spfile;
alter system set "_like_with_bind_as_equality"=TRUE                    scope=spfile;
alter system set optimizer_secure_view_merging=false                   scope=spfile;
alter system set optimizer_capture_sql_plan_baselines=False            scope=spfile;
alter system set event="10949 TRACE NAME CONTEXT FOREVER:28401 trace name context forever, level 1"  scope=spfile;
exec  DBMS_AUTO_TASK_ADMIN.DISABLE( client_name =>  'auto optimizer stats collection', operation => NULL,window_name => NULL);
exec  DBMS_AUTO_TASK_ADMIN.DISABLE( client_name =>  'auto space advisor', operation => NULL,window_name => NULL);
exec  DBMS_AUTO_TASK_ADMIN.DISABLE( client_name => 'sql tuning advisor', operation => NULL,window_name => NULL);
commit;
exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');
exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');
exec DBMS_STATS.SET_PARAM( 'method_opt','FOR ALL COLUMNS SIZE 1' );
commit;



shutdown immediate;
startup ;