Sorry, should've sent an update last night. That was indeed the
problem. It's fixed now.
Thanks to everyone who helped.
-Stut
--
http://stut.net/
On 5 Jun 2008, at 09:04, Ben Clewett wrote:
It could be the size of your InnoDB log files. Or something else
which stops InnoDB running.
I o
It could be the size of your InnoDB log files. Or something else which
stops InnoDB running.
I once changed server and by mistake changed the size of the
innodb_log_file_size. The result was that InnoDB could not start and
instead dissabled its self. Therefore every table I created became M
On 5 Jun 2008, at 00:41, Phil wrote:
Just a very quick guess but is innobd engine running ?
SHOW STATUS like '%inno%'
Output shown below. I've just finished importing the backup file again
(into a different DB) and it's ignored the engine=innodb on each
create table and has used MyISAM ins
Just a very quick guess but is innobd engine running ?
SHOW STATUS like '%inno%'
On Wed, Jun 4, 2008 at 6:44 PM, Stut <[EMAIL PROTECTED]> wrote:
> On 4 Jun 2008, at 23:10, Stut wrote:
>
>> HELP!!
>>
>> Our database just died. SHOW TABLE STATUS shows the message in the status
>> line for every ta
On 4 Jun 2008, at 23:10, Stut wrote:
HELP!!
Our database just died. SHOW TABLE STATUS shows the message in the
status line for every table except the one that's MyISAM - the rest
are InnoDB.
Is there any way to rebuild the .frm files for the InnoDB tables?
Can anyone help? I know I haven
HELP!!
Our database just died. SHOW TABLE STATUS shows the message in the
status line for every table except the one that's MyISAM - the rest
are InnoDB.
Is there any way to rebuild the .frm files for the InnoDB tables?
-Stut
--
http://stut.net/
--
MySQL General Mailing List
For list arc
: Duane Hill [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 31, 2006 10:18 AM
> To: Mikhail Berman
> Cc: mysql@lists.mysql.com
> Subject: Re: Incorrect information in file...
> On Thursday, August 31, 2006 at 2:02:42 PM, Mikhail confabulated:
>> Hi Duane,
>> Have you t
To: Mikhail Berman
> Cc: mysql@lists.mysql.com
> Subject: Re: Incorrect information in file...
> On Thursday, August 31, 2006 at 2:02:42 PM, Mikhail confabulated:
>> Hi Duane,
>> Have you tried to repair "test" table using "REPAIR" to see if that
>>
TED]
Sent: Thursday, August 31, 2006 10:18 AM
To: Mikhail Berman
Cc: mysql@lists.mysql.com
Subject: Re: Incorrect information in file...
On Thursday, August 31, 2006 at 2:02:42 PM, Mikhail confabulated:
> Hi Duane,
> Have you tried to repair "test" table using "REPAIR"
t; From: Duane Hill [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 31, 2006 9:49 AM
> To: mysql@lists.mysql.com
> Subject: Incorrect information in file...
> MySQL v5.0.24 on FreeBSD v6.0-RELEASE
> I was attempting to do some tweaking in a my.cnf to increase
> perfor
yet. I will try that. Thanks.
> -Original Message-
> From: Duane Hill [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 31, 2006 9:49 AM
> To: mysql@lists.mysql.com
> Subject: Incorrect information in file...
> MySQL v5.0.24 on FreeBSD v6.0-RELEASE
> I was a
I
also changed the thread_concurrency option from 8 to 4. That was the
only changes I made in the configuration file. Upon restarting
MySQL, I could not select anything from any of the InnoDB tables
and received this error:
ERROR 1033 (HY000): Incorrect information in file:
'./testdb/
option from 8 to 4. That was the
only changes I made in the configuration file. Upon restarting
MySQL, I could not select anything from any of the InnoDB tables
and received this error:
ERROR 1033 (HY000): Incorrect information in file: './testdb/test.frm'
I did
>
>
> Brian J.S. Miller wrote:
>
>>
>>Walt,
>>
>>The tables are ISAM type. These are some seriously old tables
>> (originally
>>from version 3.21) and were never updated to type MyISAM. Despite
>>frequent updates to mysqld.
>>
>>There is a program isamchk which is similar to myisamchk, but it ret
Brian J.S. Miller wrote:
Walt,
The tables are ISAM type. These are some seriously old tables (originally
from version 3.21) and were never updated to type MyISAM. Despite
frequent updates to mysqld.
There is a program isamchk which is similar to myisamchk, but it returns
the error "___ is not a
ields
in table 'admin_privs'" (or whatever the table name is..that's just 1
exaple).
Here is what I have tried already:
1) backing down to Mysql 3.23
2) Running 2.6 kernel (read that ISAMs aren't binary compatible across
OS/platform)
3) CHECK TABLE admin_privs (says: &
t;>exaple).
>>
>>Here is what I have tried already:
>>1) backing down to Mysql 3.23
>>2) Running 2.6 kernel (read that ISAMs aren't binary compatible across
>>OS/platform)
>>3) CHECK TABLE admin_privs (says: "Incorrect information in file:
>>'
privs'" (or whatever the table name is..that's just 1
exaple).
Here is what I have tried already:
1) backing down to Mysql 3.23
2) Running 2.6 kernel (read that ISAMs aren't binary compatible across
OS/platform)
3) CHECK TABLE admin_privs (says: "Incorrect information in fi
whatever the table name is..that's just 1
exaple).
Here is what I have tried already:
1) backing down to Mysql 3.23
2) Running 2.6 kernel (read that ISAMs aren't binary compatible across
OS/platform)
3) CHECK TABLE admin_privs (says: "Incorrect information in file:
'./path/admin
. Its output is:
Preparing db table
Preparing host table
Preparing user table
Preparing func table
Preparing tables_priv table
Preparing columns_priv table
Installing all prepared tables
ERROR: 1033 Incorrect information in file: './
Silvio Picano writes:
> >> Might the NFS dependence be a problem?
>
>
> What does "some other processes access the files" mean? Are you thinking
> like automated system backup software, or my own database client
> accesses?
>
Both, as well as copying files, checking file system ...
>
>> Might the NFS dependence be a problem?
>Yes, it could , particularly if you do not have --skip-locking as
>mysqld startup or if some other processes access the files.
>Regards,
>Sinisa
Hi Sinisa,
What does "some other processes access the files" mean? Are you thinking
like automated system
gt; Query OK, 0 rows affected (0.02 sec)
>
> mysql> ALTER TABLE tbl_status_bac RENAME tbl_status;
> ERROR 1033: Incorrect information in file: './ts1/tbl_status_bac.frm'
>
>
> Hmmm, so I restored the above <>.frm file again.
> Then shutdown t
Starting mysqld daemon with databases from ...
010330 10:18:14 mysqld ended
$ less var/p
010330 10:18:14 mysqld started
010330 10:18:14 /fs5/b/spicano/dev/local/mysql/libexec/mysqld:
Incorrect information in file: './mysql/host.frm'
010330 10:18:14 /fs5/b/spicano/dev/local/
Silvio Picano writes:
> Hi,
>
> Been running mysql-3.22.32 / Solaris / Sun / dual-processor:
> Mysql.pm 1.2214 + DBI 1.14 + perl 5.004_04
> Database with 40 tables.
> Biggest table has 2,131,447 rows in it.
> No problems for 6 months.
>
>
> Recently ported to mysql-3.23.35 / Linux 2.2
Hi,
Been running mysql-3.22.32 / Solaris / Sun / dual-processor:
Mysql.pm 1.2214 + DBI 1.14 + perl 5.004_04
Database with 40 tables.
Biggest table has 2,131,447 rows in it.
No problems for 6 months.
Recently ported to mysql-3.23.35 / Linux 2.2.12-20smp / dual-processor.
Mysql.pm 1.2215 + DBI 1.
26 matches
Mail list logo
