mysql主从库执行计划不同
SQL:SELECT COUNT(l.`id_xx_cluster`) FROM app_xx_xx l where 1=1 AND l.id_xx_cluster IN (SELECT a.applicationName FROM axxxx_info a WHERE a.`axxxxStatus`!='02' GROUP BY a.applicationName);主库执行计划
聊一聊MySQL的直方图
前一段时间和一个客户在优化SQL,发现其实收集了直方图以后看起来对执行计划起不到多大影响。MySQL 8.0后开始支持直方图,我们可以通过analyze table时进行收集,ANALYZE TABLE t UPDATE HISTOGRAM ON c1, c2, c3 WITH 10 BUCKETS;ANALYZE TABLE t UPDATE HISTOGRAM ON c1, c3 WITH 1
利用HeatWave + MySQL实现高性能海量数据分析
原文:https://mp.weixin.qq.com/s/uCjkZTlBG647xHHOPfFddQ HeatWave云服务是Oracle新推出的与MySQL集成的、高性能的基于内存的查询加速器,普通用户可将分析和统计查询的性能提高几个数量级。HeatWave集群支持扩展到数千个内核,比Amazon Aurora快1100倍,比Amazon Redshift快2.7倍,而成本仅为其三分之一。带
MySQL null和''分析
INNODB:CREATE TABLE `test2` ( `col1` VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL , `col2` VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_ge
MYTFA(MYSQL 诊断信息收集工具)介绍
从事ORACLE数据库运维多年,发现ORACLE数据库上的很多方法都在影响着我们思维,进而在对其他类型数据库进行运维时,也会不自觉地学习ORACLE数据库很多方式。数据库运维经历发展,终将会步入智能化运维,不管身处什么时代,故障分析仍然是一项十分复杂的工作,在当下的情况,我们一般的路线是收集信息,分析信息,寻找根因,解决问题,在这个过程中,我们会积累
Mysql operator for Kubernetes介绍
MySQL Operator for Kubernetes是一个用于安装和管理一个或多个MySQL InnoDB Clusters 的操作工具。MySQL operator本身在Kubernetes集群中运行,并由Kubernetes Deployment控制,以确保 MySQL operator保持可用和运行。MySQL Operato
“alter database switchover to xx“过程不当导致的primary-primary 双主问题
关于切换时primary-primary 双主问题,看起来是因为使用“alter database switchover to xx” 执行切换时的流程上缺陷问题:首先在以往传统的switchover切换方式下,切换的流程是这样的:假如当前A库(primary),B库(standby)1. 在A库(primary)库上,执行切换语句"alter database commit to sw
pprof 分析mysqld 内存调用(笔记)
----???Install?TCMALLOC ??? 1.unpack tar?zxvf???gperftools-2.9.1.tar.gz ./configure???--enable-frame-pointers?--prefix=/u
mysql 5.7 vs 8.0默认值变化(笔记)
Changed Server DefaultsOption/ParameterOld DefaultNew DefaultServer changescharacter_set_serverlatin1utf8mb4collation_serverlatin1_swedish_ciutf8mb4_0900_ai_ciexplicit_defaults_for_timestampOFFONoptim
[ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds
InnoDB: ###### Diagnostic info printed to the standard error stream2021-11-19T14:52:21.671328+08:00 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally
[InnoDB] Assertion failure: ut0ut.cc:553 thread 140235111884544【笔记】
APPLIES TO:MySQL Server - Version 8.0 and laterInformation in this document applies to any platform.SYMPTOMSOn : 8.0 version, Server Crash ERROR----------------------- [InnoDB] Assertion fai
MYSQL The Server Shutdown Process(笔记)
The server shutdown process takes place as follows:The shutdown process is initiated.This can occur initiated several ways. For example, a user with the SHUTDOWN privilege can execute a 
MYSQL 8.0 Upgrade &Downgrade的几点注意
ImportantDowngrade from MySQL 8.0 to MySQL 5.7, or from a MySQL 8.0 release to a previous MySQL 8.0 release, is not supported. The only supported alternative is to restore a backup taken before upgrad
关于log file switch and checkpoint机制
转自同事周乙的研究总结,记录一下!关于ckpt的机制?何时发生check point?1.????? 每次redo file switch。2.????? 当达到参数LOG_CHECKPOINT_TIMEOUT设置值。3.????? 当有(
rac 正常关闭实例service不会自动漂移,只有在实例异常abort才会发生自动failover
关于正常计划性地shutdown 实例,服务不会自动漂移,只有在实例异常的情况下才会发生自动failover的情况。不过我们可以在srvctl stop instance时加上 “-f“ ,作用就是让服务自动failover到另外一个节点。-f?????? This option fails the running services ov
延迟块清除导致rac节点传输undo header块
节点11)创建表及索引,并插入数据:create table cwdtest.tab91 (id number,name varchar2(100),created date);create index cwdtest.idx_tab91_01 on cwdtest.tab91(id) pctfree 0;2)节点1 进行update:SYS@t1nnps1> update cwdtest.
ORA-15137: The ASM cluster is in rolling patch state
之前卸载12.1的GI再安装19.9的GI,在创建asmdisk的时候报错:ORA-15137: The ASM cluster is in rolling patch state.Case 1. Update the patch level on all nodes, As root user$ clscfg -patchExample:# <grid home>/bin/clscf
Cursor Cache Hit Ratio超过100%
这种Ratio超过100的是正常的吗?目前我们的监控对这种超过的处理有点问题11g到19c各个版本都有这个情况。 这是正常现象, Cursor Cache Hit Ratio指标的来源是:session cursor cache hits / (parse count (total) - parse count (hard))。其中session cursor ca
sqlplus as sysdb登录报ora-01017
1.报错信息:cnsh281177:t3fxqdb > sqlplus '/as sysdba' SQL*Plus: Release 12.1.0.2.0 Production on Wed Apr 14 09:28:15 2021 Copyright (c) 1982, 2014, Oracle. All rights reserved.&n
SQL的reload以及Invalidations
关于SQL的游标版本不高,但reload以及Invalidations次数相对比较多。基本上是每一次Invalidations便伴随着一次reload. 关于load以及Invalidations的说明如下, Invalidations - An invalidation is a measure of the number of times a cached cursor