some myisam tables turned read only (MySQL Max 4.1.12)

Very odd problem. I do have a larger database, with many myisam tables. A couple days ago, some of them turned 'read only'. Symptom: delete from day_48392 where id=28398776259; ERROR 1036 (HY000): Table 'day_48392' is read only I checked: - table file permissions are right ('660

Re: [SOLUTION] some myisam tables turned read only (MySQL Max 4.1.12)

Well, I found the reason for these table becoming 'read only': These tables where part of a merge table, which included some read only tables (read only set in file system). Now even after the merge table was dropped, all member tables stayed 'read only' regardless of their individual file

random permission denied issues

I am having a very odd issue with one of my mysql 4.1.14 servers. Randomly, the server returns permission denied to queries even if identical queries succeeded within the same connection. To test the problem, I setup a script that connects to the database, and issues the same query 50,000 times.

Re: Very Strange command denied to user errors

156 Oud wrote: Hi, I've got a very strange problem with one of my MySQL servers. I've got 2 dedicated servers with MySQL 4.0.21, all is fine there. My new server with MySQL-4.1.14 give me some headakes ! Sometimes i've got errors like UPDATE command denied to user 'MyUser'@'192.168.0.4'

Re: random permission denied issues

sheeri kritzer wrote: What is max_connections set to (my.cnf?)? How many connections are there at a time? (show processlist) That would result in a too many connections error, but it's worth a shot. Max connections: 2000 typically 10-20 used (hardly ever 100). What is the thread cache set

auditing mysql logins

Is there any way to have MySQL generate a log of successful/failed login attempts? Or even better: have this information sent to syslog? (using mysql 4.1) signature.asc Description: OpenPGP digital signature

show slave status while load table from master

While doing a Load table from master, show slave status will hang (like it is locked, but processlist will not show it as locked) on MySQL 4.0.20... is this a bug or a feature? I don't remember earlier versions doing this. Also: I still experience mysql crashes after loading a few large tables

Re: Bug in 4.0.20

On Fri, 2004-06-11 at 08:50, Egor Egorov wrote: Wendell Dingus [EMAIL PROTECTED] wrote: RedHat Enterprise 3WS, fully up2date. MySQL binary RPMs for AMD64 won't even start for me, what were they built on?. I installed the .src.rpm and built one myself (-bb --target amd64). Installed that

Re: indexing text

I have a table that has a few short text fields [text(4000), text(1000)] I would like to index. Do you think it is a good idea to index them simply, or is it better if I create auxilary fields which hold the MD5 for the text fields and index those? Would that be faster? Try 'Fulltext'

Re: MySQL ARRAY

My requirement was 6 fields and 2nd guy need 12 filed. You should setup two tables. The first one will track common data for each user (e.g. name, address...) like: create table users ( name varchar(255), address varchar(255), ... userid integer unsigned auto_increment primary key

Re: mysql memory optimization - AMD 64 - odd crashes

First, what version are you using? 4.0.20? 4.0.18 as provided by Suse with 9.1 Professional. 64 bit 4.0.20 64bit crashes 'out of the box' (segfault as I start it). I just filed a bug report for that By key-cache, are you referring to the variable key_buffer_size? If so, keep in mind that

4.0.20 x86_64 on Suse 9.1

I am having problems installing 4.0.20 (64 bit version), on Suse 9.1 (64 bit as well). 'mysqld' and the mysql client segfault on start. 'mysql-max' appears to be running (but of course, the client still segfaults). 4.0.18, which is included with 9.1 works ok, but has issues with loading tables

mysql memory optimization - AMD 64 - odd crashes

I just started setting up a dual opteron system with Suse 9.1 (x86_64). At this point, I am sticking with the Suse provided rpms. I am having some odd mysql restarts (crashed with immediate restart by safe_mysqld). Odd part about it: not a single line in the error log. The connections just drop

mysql server crashes - high context switch rate - large 'merge' table

I am having problems with MySQL 4.0.12 on RedHat Advanced Server 2.1 using a dual Xeon with 8 GByte of RAM. I have a database collecting logs. Each day, a new table is created. In order to allow for queries across more than one day, I use 'MERGE' tables. Each individual table contains 10-30

Re: mysql crash during large insert from MYIASM to INNODB table.

which version of MySQL you are running? 3.23.39 :-(... sorry for not including this earlier. I will try and move to .47 Thanks! From http://www.innodb.com/bugfixes.html : November 17, 2001: The insert buffer tree can get into an inconsistent state, causing a crash,

mysql crash during large insert from MYIASM to INNODB table.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just started using innodb tables to help with some locking problems. The table I am trying to convert is large (100 Million rows, 23 GigByte). I setup 20 2Gig ibdata files. (I choose a size of 2 Gig as this is the maximum size I can easily

killing mysql query after Apache(PHP) stops.

For a web site with a relatively large database, I have a very anoying problem. At times, the response time is getting quite slow. As a result, the pages either time out, or even worse the user presses 'stop/reload'. However, the queries will continue to run even after the user pressed