show variables like '%explicit_defaults_for_timestamp%'; +---------------------------------+-------+ | Variable_name...值变为当前时间,并没有被NOT NULL所限制 且该值是无法动态修改的,必须重启库才可以变更 mysql> set global explicit_defaults_for_timestamp=0; ERROR...1238 (HY000): Variable 'explicit_defaults_for_timestamp' is a read only variable 我们在my.cnf修改该参数后并重启库后...11:45:46 | +---------------------+ 2 rows in set (0.00 sec) mysql> insert into helei values(null); ERROR...1048 (23000): Column 'a' cannot be null mysql> insert into helei values(NULL); ERROR 1048 (23000): Column
01 错误信息无法显示 问题描述: ERROR 1238 (HY000): Unknown error 1238 我们知道,当我们在MySQL中执行一个SQL命令的时候,如果我们的命令写错了,MySQL...[ERROR] Can't read from messagefile '/usr/local/mysql-5.5.19-linux2.6-x86_64/share/english/errmsg.sys...--------------------------------------+---------------------------------------------------------+ | Variable_name...(HY000): Unknown error 很明显,不让直接修改,而且报错信息依旧只有个Unknow error 1238,于是我在配置文件中添加了一个记录: lc-messages-dir...(HY000): Variable 'lc_messages_dir' is a read only variable 02 字符串截取的一个小方法 上面是错误信息的问题,再来看第二个问题,
这使得 PERSIST_ONLY 适合配置只能在服务器启动时设置的只读系统变量。...mysql> SET PERSIST innodb_log_file_size=50331648*2; ERROR 1238 (HY000): Variable 'innodb_log_file_size...' is a read-only variable mysql> set persist_only innodb_log_file_size=50331648*2; Query OK, 0 rows affected...max_connections; Query OK, 0 rows affected (0.00 sec) mysql> RESET PERSIST innodb_max_dirty_pages_pct; ERROR...3615 (HY000): Variable innodb_max_dirty_pages_pct does not exist in persisted config file mysql> mysql
begin -> ; Query OK, 0 rows affected (0.00 sec) mysql> insert into a select 100000; ERROR...1665 (HY000): Cannotexecute statement: impossible to write to binary log since BINLOG_FORMAT =STATEMENT...ERROR 1665 (HY000): Cannotexecute statement: impossible to write to binary log since BINLOG_FORMAT =STATEMENT...----------------+ 1 row in set (0.00 sec) mysql> set global innodb_locks_unsafe_for_binlog=1; ERROR...1238 (HY000): Variable 'innodb_locks_unsafe_for_binlog' is a readonly variable mysql> 此参数是只读模式
mysql> show variables like '%case%'; +------------------------+-------+ | Variable_name | Value...mysql> select id,name from TEST_TAB; ERROR 1146 (42S02): Table 'test.TEST_TAB' doesn't exist 而在列级别,MySQL...mysql> set global lower_case_table_names=on; ERROR 1238 (HY000): Variable 'lower_case_table_names' is...a read only variable 重启后,test_TAB和原来的test_tab就是一个意思了。
Master_Port: 6054 Connect_Retry: 60 Master_Log_File: mysql-bin.021323 Read_Master_Log_Pos.../MLoiYLtT' (Errcode: 28 - No space left on device), Error_code: 3; Error writing file '/dev/shm/MLoiYLtT...' (errno: 28 - No space left on device), Error_code: 1026; handler error HA_ERR_RBR_LOGGING_FAILED;...(none)>show variables like "%tmp%"; +----------------------------------+-----------+ | Variable_name...(none)>set global tmpdir='/tmp'; ERROR 1238 (HY000): Variable 'tmpdir' is a read only variable 手工修改配置文件
Variable_name | Value | +---------------+-------+ | read_only | ON | +---------------+-------+...sec) # 使用普通权限用户 mysql> create table tb_b (b int); ERROR 1290 (HY000): The MySQL server is running with...'super_read_only'; +-----------------+-------+ | Variable_name | Value | +-----------------+------...-+ | super_read_only | ON | +-----------------+-------+ mysql> create table tb_c (c int); ERROR...mysql> insert into tb_a values (1); ERROR 1223 (HY000): Can't execute the query because you have a conflicting
[Note] InnoDB: Highest supported file format is Barracuda. 2017-09-13 16:05:14 7f73450a97e0 InnoDB: Error...mysql> set global innodb_force_recovery=2; ERROR 1238 (HY000): Variable 'innodb_force_recovery' is a...read only variable 在此假设我们设置为2,再次复现这个问题问题,你就会发现,数据库暂时是可以启动的,但是数据只能查询,DML操作都会抛错。...mysql> select *from test; Empty set (0.00 sec) mysql> mysql> insert into test values(1,'a'); ERROR 1030...(HY000): Got error -1 from storage engine 按照这个影响的范围来评估force_recovery的值,我们就可以做相应的取舍了。
怎么设 show global status like 'key_read%'; +------------------------+-------------+ | Variable_name |...这个值不用分配太大,通常设置16M够用了,默认8M,如果设置的内存大小不够,InnoDB 会自动申请更多的内存,并在 MySQL 的 Error Log 中记录警告信息。...{要改的key} = {值}; (立即生效重启后失效) 试验 mysql> set @@global.innodb_buffer_pool_size=4294967296; ERROR 1238 (HY000...): Variable 'innodb_buffer_pool_size' is a read only variable mysql> set @@global.thread_stack=262144...; ERROR 1238 (HY000): Variable 'thread_stack' is a read only variable mysql> set @@global.binlog_cache_size
MYSQL产生临时表目录,线上怎么设置的: mysql> show variables like 'tmpdir'; +---------------+----------------------+ | Variable_name...nock@app-ali-prod-db1 ~]# sudo mkdir -pv /data/tmp/mysqlmysql> set global tmpdir='/data/tmp/mysql'; ERROR...1238 (HY000): Variable 'tmpdir' is a read only variable 通过提示可知tmpdir参数只是一个只读变量不能动态修改指定,那看来只能通过在配置文件my.cnf...mysqld reload 查看效果: mysql> show variables like 'tmpdir'; +---------------+----------------------+ | Variable_name
mysql> set GLOBAL version=10; ERROR 1238 (HY000): Variable 'version' is a read only variable 作用域问题 在上面的设置语法中...0 rows affected (0.00 sec) mysql> show variables like '%autocommit%'; +---------------+-------+ | Variable_name...mysql> show GLOBAL variables like '%autocommit%'; +---------------+-------+ | Variable_name | Value |...row in set (0.00 sec) mysql> show SESSION variables like '%autocommit%'; +---------------+-------+ | Variable_name...mysql> SHOW STATUS LIKE '%thread%'; +------------------------------------------+-------+ | Variable_name
show variables like '%read_only%'; 2+-----------------------+-------+ 3| Variable_name | Value...-----+ 17| Variable_name | Value | 18+-----------------------+-------+ 19| innodb_read_only...1mysql> show variables like '%read_only%'; 2+-----------------------+-------+ 3| Variable_name...set (0.00 sec) 11 12mysql> 13mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so'; 14ERROR...1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this
mysql> set global gtid_executed='411693c9-d512-11ec-9e11-525400d51a16:1-10369';ERROR 1238 (HY000): Variable... 'gtid_executed' is a read only variable如果我们要修改它,必须通过修改 GTID_PURGED 来间接修改它。...mysql> set global gtid_purged='411693c9-d512-11ec-9e11-525400d51a16:1-10369';ERROR 1840 (HY000): @@GLOBAL.GTID_PURGED... can only be set when @@GLOBAL.GTID_EXECUTED is empty.而要 GTID_EXECUTED 为空,只能执行 RESET MASTER 操作。...50718 SET TRANSACTION ISOLATION LEVEL READ COMMITTED*//*!
日志报错 ERROR 1786 (HY000): Statement violates GTID consistency: CREATE TABLE … SELECT....(2)create table select语句拆成create table t like t1;insert into t select * from t1; ERROR 1197 (HY000):...Multi-statement transaction required more than ‘max_binlog_cache_size’ bytes of storage; increase this mysqld variable...如果是rc模式,mixed的话也会记录成row,原因是和gap lock有关,如果innodb_locks_unsafe_for_binlog参数设置为1就不会了(关闭gap lock,但是是read...only属性,即要重启mysqld) ERROR 1118 (42000): Row size too large (> 4030).
slow_log和general_log主要特点 日志表只能是CSV和MYISAM存储引擎 更改日志表的存储引擎必须先停止使用该日志表 日志表中的数据不记录binlog 锁表语句FTWRL和lock tables、read_only...1194 (HY000): Table 'slow_log' is marked as crashed and should be repaired mysql> mysql> check table...------------------------------------------------------------------------------------------------+ | Variable_name...-------------------------------------------------------------------------------------+ | sql_mode | ONLY_FULL_GROUP_BY...------------------------------------------------------------------------------------------------+ | Variable_name
information_schema.USER_VARIABLES; +---------------+----------------+---------------+--------------------+ | VARIABLE_NAME...| VARIABLE_VALUE | VARIABLE_TYPE | CHARACTER_SET_NAME | +---------------+----------------+----------...如: set @@innodb_undo_tablespaces=3; ERROR 1238 (HY000): Variable 'innodb_undo_tablespaces' is a read...only variable 系统变量除了可以在运行中的环境下设置,还可以在配置文件中或者mysqld/mysqld_safe这样的命令行中设置,甚至mysql客户端命令行也可以传递。
(ER_ERROR_ON_READ) 消息:读取文件'%s'时出错 (errno: %d) · 错误:1025 SQLSTATE: HY000 (ER_ERROR_ON_RENAME) 消息...· 错误:1207 SQLSTATE: 25000 (ER_READ_ONLY_TRANSACTION) 消息:在READ UNCOMMITTED事务期间,无法获得更新锁定。...· 错误:1238 SQLSTATE: HY000 (ER_INCORRECT_GLOBAL_LOCAL_VAR) 消息:变量'%s'是一种%s变量。...· 错误:1272 SQLSTATE: HY000 (ER_VARIABLE_IS_NOT_STRUCT) 消息:变量'%s'不是变量组分(不能用作XXXX.variable_name)。...· 错误:1463 SQLSTATE: HY000 (ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR) 消息:仅在KEY分区中允许使用字段列表。
在使用MySQL数据库时,有时会出现ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction 这样的报错。...into test1 values(2,'2edft6');Query OK, 1 row affected (0.00 sec)mysql> delete from test1 where id=1;ERROR...global variables like 'transaction_isolation';+-----------------------+----------------+| Variable_name...into test1 values(3,'3eft6');Query OK, 1 row affected (0.00 sec)mysql> delete from test1 where id=1;ERROR...-----------------+----------------+| Variable_name | Value |+-----------------------
Master_Port: Connect_Retry: Master_Log_File: mysqlbin.000123 Read_Master_Log_Pos...查看了一眼从库上参数的具体值,结果如下: (从库端) mysql:(none) ::>>show variables like '%report%'; +-----------------+-------+ | Variable_name...解决问题过程: 1、直接手动修改该参数: mysql:(none) ::>>set global report_host='10.21.130.62'; ERROR (HY000): Variable...'report_host' is a read only variable mysql:(none) ::>> 可以发现,这个参数是不允许直接修改的,会报错。...结果如下: (从库端) mysql:(none) ::>>show variables like '%report%'; +-----------------+----------------+ | Variable_name
1290 (HY000) at line 1: The MySQL server is running with the --super-read-only option so it cannot execute...this statement ERROR 1290 (HY000) at line 1: The MySQL server is running with the --super-read-only...with the --super-read-only option so it cannot execute this statement ERROR 1290 (HY000) at line 1: The...MySQL server is running with the --super-read-only option so it cannot execute this statement ERROR...1290 (HY000) at line 1: The MySQL server is running with the --super-read-only option so it cannot execute
领取专属 10元无门槛券
手把手带您无忧上云