全局索引的online重建要注意影响（Reconstruction of online global index should pay attention）.docVIP

下载本文档

5
0
约4.3千字
约 11页
2017-08-18 发布于河南
举报
版权申诉

全局索引的online重建要注意影响（Reconstruction of online global index should pay attention）.doc

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

全局索引的online重建要注意影响（Reconstruction of online global index should pay attention）

全局索引的online重建要注意影响（Reconstruction of online global index should pay attention） Oracle database: ONLINE reconstruction of global indexes should be paid attention to When I had a problem a few days ago, it took me more than 8 hours to rebuild the index of a table. Later, a closer look at the slow index was done to find that the basic global indexes are all ONLINE, and that each partition has the same reconstruction time, about 23 minutes or so. In fact, the cause of the problem is simple: because of the use of ONLINE, and the global index of each partition of the data from this table may be any one of the partitions, so ORACLE reconstruction for any global index partition will go full table scan. SQL SHOW USER USER is TEST SQL, CREATE, TABLE, T (ID, INT, NAME, VARCHAR2 (30)) 2, PARTITION, BY, RANGE (ID) (3 4, PARTITION, P1, VALUES, LESS, THAN (10000), 5, PARTITION, P2, VALUES, LESS, THAN (20000), 6, PARTITION, P3, VALUES, LESS, THAN (30000), 7, PARTITION, P4, VALUES, LESS, THAN (40000), 8, PARTITION, P5, VALUES, LESS, THAN (50000), 9, PARTITION, PMAX, VALUES, LESS, THAN (MAXVALUE) 10) 11 / Table created. SQL, CREATE, INDEX, T_ID_IDX, ON, T (ID) GLOBAL 2, PARTITION, BY, HASH (ID) 3 PARTITIONS 32 4 / Index created. SQL, COL, INDEX_NAME, FORMAT, A20 SQL, COL, PARTITION_NAME, FORMAT, A20 SQL, SELECT, INDEX_NAME, PARTITION_NAME, FROM, USER_IND_PARTITIONS, WHERE, INDEX_NAME=T_ID_IDX; INDEX_NAME PARTITION_NAME ---------------------------------------- T_ID_IDX SYS_P225 T_ID_IDX SYS_P226 T_ID_IDX SYS_P227 T_ID_IDX SYS_P228 T_ID_IDX SYS_P229 T_ID_IDX SYS_P230 T_ID_IDX SYS_P231 T_ID_IDX SYS_P232 T_ID_IDX SYS_P233 T_ID_IDX SYS_P234 T_ID_IDX SYS_P235 T_ID_IDX SYS_P236 T_ID_IDX SYS_P237 T_ID_IDX SYS_P238 T_ID_IDX SYS_P239 T_ID_IDX SYS_P240 T_ID_IDX SYS_P241 T_ID_IDX SYS_P242 T_ID_IDX SYS_P243 T_ID_IDX SYS_P244 T_ID_IDX SYS_P245 t _ id _ _ p246 idx. t _ id _ _ p247 idx. t _ id _ _ p248 idx. t _ id _ _ p249 idx. t _ id _ _ p250 idx. t _ id _ idx systems _ p251 t _ id _ _. p 252 idx.