blocks|key|3115358|text|谁拥有/var/db/mysql，他们属于哪个组，应该是mysql:mysql。您还需要重新启动mysql以使更改生效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3115359|还要检查当前登录的用户是否具有更新的授权访问权限|3115360|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

who owns /var/db/mysql and what group are they in, should be mysql:mysql. you'll also need to restart mysql for changes to take affect

also check that the currently logged in user had GRANT access to update

blocks|key|233564|text|在我的例子中，mysql配置文件的innodb_force_recovery+=+1，注释掉就解决了这个问题。希望这能帮助到别人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|233565|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, mysql config file had innodb_force_recovery = 1. Commenting that out solved the issue. Hope it helps someone.

blocks|key|239165|text|(此答案与标题有关，但与原问题无关。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|239166|以防您(像我一样)尝试通过MySQL工作台接口临时更改数据：|239167|239168|如果表没有主键，则MySQL工作台无法识别您尝试更改的行，因此您无法更改它。在这种情况下，|unordered-list-item|239169|的解决方案是通过其他途径更改数据，或者直接向表中添加主键。|239170|239171|无论如何，我希望它能帮助某些人:)|239172|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|S|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

(This answer is related to the headline, but not to the original question.)

In case you (like me) are trying to temporarily alter data via the MySQL Workbench interface:

<ul>
<li>If the table does not have a primary key, MySQL Workbench has no way of identifying the row you are trying to alter, so therefore you cannot alter it.</li>
<li>Solution in that case is to either alter the data via another route, or simply to add a primary key to the table.</li>
</ul>

In any case, I hope it helps someone :)

blocks|key|3115372|text|您应该将所有者更改为MYSQL:MYSQL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3115373|使用以下命令：chown+-Rf+mysql:mysql+/var/lib/mysql/DBNAME|offset|length|style|CODE|3115374|entityMap^0|0|7|17|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You should change owner to MYSQL:MYSQL.

Use this command: <code>chown -Rf mysql:mysql /var/lib/mysql/DBNAME</code>

blocks|key|3115519|text|我的情况是每次需要在my.ini中编辑"innodb_force_recovery+=+1“来强制mysql启动时，错误日志显示如下错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3115520|尝试打开以前打开的表空间。以前的表空间mysql/innodb_stats在filepath：.\mysql\innodb_table_stats.ibd处使用空间ID:+1。无法打开表空间profile/profile_commentmeta，该表空间在文件路径.\profile\profile_commentmeta.ibd处使用空间ID:+1|3115521|我不知道为什么这个文件无法打开，它也给其他数据库造成了许多其他的“表只读”问题。|3115522|下面是我如何在不伤害其他文件的情况下，以一种简单的方式修复这个问题。|3115523|1首先，确保您在my.ini文件中的mysqld下面添加了innodb_force_recovery+=+1，并且它工作正常，路径为:+X:\xampp\mysql\bin\my.ini|3115524|2然后下一步，通过导出选项卡下的localhost/phpmyadmin导出所有数据库，并将其存储在某个位置，如下所示：|3115525|​|3115526|📷|atomic|3115527|3115528|3.将data文件夹注释掉到data-bak，然后新建一个data文件文件夹。|3115529|3115530|3115531|3115532|4下一步，将所有.sql数据库从phpmyadmin面板导入回请同时将phpmyadmin<代码>E229文件文件夹从旧的E231文件文件夹复制到新的data文件文件夹。如果需要任何文件，请返回到data-bak文件文件夹进行复制和粘贴。|3115533|3115534|3115535|3115536|现在所有的问题都解决了，不需要每次都强制mysql启动。希望这也适用于你。|3115537|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cfdb01fe31af5875d487a6b955255961.jpeg|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/7a8aa8f023f8e46c4103bb75638aeb3a.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/b9629cf374d8ec61c3c002fc2b8bd508.png^0|A|6|K|P|0|0|0|0|I|6|T|P|0|9|2|G|K|0|0|0|1|0|0|0|3|4|E|8|T|4|0|0|0|1|1|0|0|8|4|G|A|V|2G|0|0|1|0|0|1|0|1|2|0|0|1|0|0|11|0^^$0|@$1|2|3|4|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1P|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1R|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1S|8|@$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1X|8|@$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|22|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|23|8|@]|D|@$9|24|A|25|1|26]]|E|$]]|$1|U|3|Q|5|6|7|27|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|28|8|@$9|29|A|2A|B|C]|$9|2B|A|2C|B|C]|$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|X|3|Q|5|6|7|2F|8|@]|D|@]|E|$]]|$1|Y|3|S|5|T|7|2G|8|@]|D|@$9|2H|A|2I|1|2J]]|E|$]]|$1|Z|3|Q|5|6|7|2K|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|2L|8|@$9|2M|A|2N|B|C]|$9|2O|A|2P|B|C]|$9|2Q|A|2R|B|C]]|D|@]|E|$]]|$1|12|3|Q|5|6|7|2S|8|@$9|2T|A|2U|B|C]]|D|@]|E|$]]|$1|13|3|S|5|T|7|2V|8|@$9|2W|A|2X|B|C]]|D|@$9|2Y|A|2Z|1|30]]|E|$]]|$1|14|3|Q|5|6|7|31|8|@$9|32|A|33|B|C]]|D|@]|E|$]]|$1|15|3|16|5|6|7|34|8|@$9|35|A|36|B|C]]|D|@]|E|$]]|$1|17|3|-4|5|6|7|37|8|@]|D|@]|E|$]]]|18|$19|$5|1A|1B|1C|E|$1D|1E|1F|-4]]|1G|$5|1A|1B|1C|E|$1D|1H|1F|-4]]|1I|$5|1A|1B|1C|E|$1D|1J|1F|-4]]]]

My situation is everytime I needed to edit &quot;innodb_force_recovery = 1&quot; in my.ini to force mysql to start, and the error log showed some error said:
Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace profile/profile_commentmeta which uses space ID: 1 at filepath: .\profile\profile_commentmeta.ibd
I didn't know why this file was not able to open and it caused so many other&quot;table read only&quot; problems to other databases too.
So here is how I fixed this problem in a simple way without hurting other files.
1
First of all, make sure if you add innodb_force_recovery = 1
below [mysqld] in my.ini file, and it is working, under path: X:\xampp\mysql\bin\my.ini
2
Then next step, export all the databases through localhost/phpmyadmin under the export tab, and store them somewhere, like this:
<a href="https://i.stack.imgur.com/xvWtg.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xvWtg.jpg" alt="export .sql databases somewhere" /></a>
3 comment out the data filefolder to data-bak, then create a new data filefolder,
<a href="https://i.stack.imgur.com/t9zxh.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/t9zxh.png" alt="enter image description here" /></a>
4 Next step, import all .sql database back from phpmyadmin panel, please also copy phpmyadmin filefolder from the old data-bak filefolder to the new data filefolder. If any file is necessary, go back to data-bak filefolder to copy and paste.
<a href="https://i.stack.imgur.com/DEKSM.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DEKSM.png" alt="enter image description here" /></a>
Now all fixed and done, don't need to force mysql to start everytime.
Hope this also works for you.

blocks|key|237300|text|MySQL对数据库文件没有写访问权限。检查文件的权限和所有者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|237301|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

MySQL doesn't have write access to the database file. Check the permissions and the owner of the file.

blocks|key|237375|text|在windows上，我使用Xampp服务器，我在my.ini+innodb_force_recovery+=+1中注释了这行代码来解决这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|237376|entityMap^0|O|6|V|P|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|N|8|@]|E|@]|F|$]]]|H|$]]

On windows I use Xampp server I comment the line in my.ini
<code>innodb_force_recovery = 1 </code> to <code>#innodb_force_recovery = 1</code> the problem resolved

blocks|key|3115553|text|我通过编辑app解决了同样的问题。装甲配置文件。在这里找到答案：https://stackoverflow.com/a/14563327/31755661|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3115554|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/14563327/3175566|1^0|W|18|0|24|1|1|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]|$A|Q|B|R|1|S]]|C|$]]|$1|D|3|-4|5|6|7|T|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|K]]]]

I solved the same issue by editing app. armour configuration file. Found the answer here: <a href="https://stackoverflow.com/a/14563327/3175566">https://stackoverflow.com/a/14563327/3175566</a><a href="https://stackoverflow.com/a/14563327/3175566">1</a>

blocks|key|237385|text|也许你会从你的表存储引擎中得到只读错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|237386|检查您的存储引擎，如果是MRG_MYISAM，请将其更改为MyISAM，然后重试。|237387|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

maybe you get read only error from your table storage engine. 
Check you Storage Engine, maybe if it is MRG_MYISAM change it to MyISAM and try again.

blocks|key|3115393|text|接收此错误的另一种方法是使用"Like“语句创建表，并将合并表用作源。这样，新创建的表是只读的，不能“接收”任何新记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3115394|所以|3115395|CREATE+TABLE+ic.icdrs_kw37+LIKE+ic.icdrs+...+#<-+a+merged+table.|code-block|syntax|javascript|3115396|然后：|3115397|REPLACE+INTO+ic.icdrs_kw37+...++#+->+"Table+is+read-only"|3115398|bug还是特性？|3115399|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

One other way to receive this error is to create your table with a "Like" statement and use as source a merged table. That way the newly create table is read-only and can't "receive" any new records.

so 

<pre><code>CREATE TABLE ic.icdrs_kw37 LIKE ic.icdrs ... #&lt;- a merged table.
</code></pre>

then:

<pre><code>REPLACE INTO ic.icdrs_kw37 ... # -&gt; "Table is read-only"
</code></pre>

bug or feature?

When I want to execute an <code>update</code> query on my table I got an error saying:

<blockquote>
 1036 - Table <code>data</code> is read only.
</blockquote>

How can I fix that?

Table attributes in <code>/var/db/mysql</code> are set to <code>777</code>.

'Repair Table' function doesnt seems to help.

Is there anything I can do with that?

Table is 'read only'

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当我想在我的表上执行一个update查询时，我得到了一个错误，说： 1036 -表data为只读。我怎么才能修复它呢？/var/db/mysql中的表属性设置为777。“'Repair”函数似乎没有帮助。有什么我能做的吗？

问表是“只读”的
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问表是“只读”的EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问表是“只读”的
EN