>>>
Due to the method that the databases were copied over, I went into mysql used the grant option on all the databases to allow root access and ability to alter all the databases. Once this was done, I restarted mysql and I was able to run the example above.
>>>
I had already run the command:
grant all on tracerlock.test to bhaselto identified by "<password>"
and that didn't work when I did it, but I didn't restart mysql after running the command. Probably it was the restart of MySQL that made the difference.
By the way, if you're wondering what sort of ISP would have such good support that they would answer a question like this, it was RackSpace.com -- nothing but good things to say about their support process.
-Bennett
At 11:00 AM 8/17/2003 +0200, Petre Agenbag wrote:
Hi Bennett
I had a similar problem on my system a while back. With my particular case, the problem was the the default priv's on the new server for it's users did NOT include INSERT rights. Basically what I'm saying is: these are the reasons for a table to be (or appear to be) read-only: 1) Table files belong to someone other than mysql ( not the case here) 2) The permissions on the files are set read-only ( do a chmod to the correct permissions you require) 3)the user for that database has no insert, update, delete etc, rights.
For the last case you need to issue the correct grants, or you can edit the mysql user table directly and change the "N" to "Y" in the appropriate fields. Then you should probably restart the mysqld daemon.
On Sun, 2003-08-17 at 01:16, Bennett Haselton wrote:
> I'm trying to port my MySQL tables for a database called "tracerlock" from
> one server to another. On the old server, in the /var/lib/mysql/tracerlock
> directory, there was a ".MYD", ".MYI" and ".frm" file for every table in
> the database. So after creating a database called "tracerlock" on the new
> server, I copied these files over to the /var/lib/mysql/tracerlock
> directory on the new server. On both servers, all the table files are
> owned by user "mysql" in the "mysql" group.
>
> Now, when I connect to MySQL on the new machine and load the tracerlock
> database, "show tables" shows all the tables as expected, and I can perform
> SELECT statements on them and get the correct results. But when I try
> doing INSERT statements on one of the tables that was copied over, I get:
>
> mysql> INSERT INTO test VALUES(3);
> ERROR 1036: Table 'test' is read only
>
> However, if I create a new table called test2, I can perform INSERT
> statements on it with no error:
>
> mysql> insert into test2 values(3);
> Query OK, 1 row affected (0.00 sec)
>
> The files corresponding to test and test2 have the same permissions and
> ownership, so that's not it: > -rw-rw---- 1 mysql mysql 20 Aug 15 21:22 test.MYD > -rw-rw---- 1 mysql mysql 1024 Aug 15 21:22 test.MYI > -rw-rw---- 1 mysql mysql 8556 Aug 15 21:22 test.frm > -rw-rw---- 1 mysql mysql 5 Aug 16 19:13 test2.MYD > -rw-rw---- 1 mysql mysql 1024 Aug 16 19:13 test2.MYI > -rw-rw---- 1 mysql mysql 8556 Aug 16 19:13 test2.frm > > So how do I get rid of the error that "Table 'test' is read only"? > > -Bennett > > [EMAIL PROTECTED] http://www.peacefire.org > (425) 497 9002 >
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
[EMAIL PROTECTED] http://www.peacefire.org (425) 497 9002
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
