Message -
From: "Baron Schwartz"
To: "Brent Baisley"
Cc: "Carl" ;
Sent: Tuesday, March 03, 2009 5:50 PM
Subject: Re: Select query locks tables in Innodb
On Tue, Mar 3, 2009 at 12:35 PM, Brent Baisley
wrote:
A SELECT will/can lock a table. It almost al
om: "Baron Schwartz"
To: "Brent Baisley"
Cc: "Carl" ;
Sent: Tuesday, March 03, 2009 5:50 PM
Subject: Re: Select query locks tables in Innodb
On Tue, Mar 3, 2009 at 12:35 PM, Brent Baisley
wrote:
A SELECT will/can lock a table. It almost always does in MyISAM (no
inse
On Tue, Mar 3, 2009 at 12:35 PM, Brent Baisley wrote:
> A SELECT will/can lock a table. It almost always does in MyISAM (no
> insert/updates), almost never does in InnoDB. There is an exception to
> every rule. The problem is most likely in the 107488 rows part of the
> query. Tha
have you
verified that each table you think is InnoDB really is? Do a SHOW
CREATE TABLE on them.
- Perrin
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
A SELECT will/can lock a table. It almost always does in MyISAM (no
insert/updates), almost never does in InnoDB. There is an exception to
every rule. The problem is most likely in the 107488 rows part of the
query. That's too many rows for InnoDB to keep a version history on so
it's l
I have been wrestling with this problem for a couple of weeks and have been
unable to find a solution.
The MySQL version is 5.0.37 and it is running on a Slackware Linux 11 box.
The problem:
A query that is selecting data for a report locks the files that it accesses
forcing users who are att
, Feb 19, 2009 at 2:14 PM, Claudio Nanni wrote:
I need to add an index on a table on a production server.
It is one 7Gb InnoDB table with single .ibd file (one_file_per_table),
the index creation on preprod server took 40 minutes but table was smaller.
I tried to add the index but was locking a
Hi!
On Thu, Feb 19, 2009 at 2:14 PM, Claudio Nanni wrote:
> I need to add an index on a table on a production server.
> It is one 7Gb InnoDB table with single .ibd file (one_file_per_table),
> the index creation on preprod server took 40 minutes but table was smaller.
> I tried to a
I need to add an index on a table on a production server.
It is one 7Gb InnoDB table with single .ibd file (one_file_per_table),
the index creation on preprod server took 40 minutes but table was smaller.
I tried to add the index but was locking all applications on production
and had to kill it
This is because you didn't copy innodb ibdata and ib_log files togeter. Or
you forgot to stop mysqld when you remove its ib_log files.
On Sat, Feb 7, 2009 at 7:21 AM, my sql wrote:
> WHY do I see this error when restoring my backup db :
> " InnoDB: Your database may be corrupt
necessarily endorse content contained within this
> transmission.
>
>
>
>
> > Date: Tue, 10 Feb 2009 11:03:46 -0600
> > To: mysql@lists.mysql.com
> > From: mo...@fastmail.fm
> > Subject: Re: InnoDB: Thousands of Tables or Hundreds of Databases?
> >
>
stmail.fm
> Subject: Re: InnoDB: Thousands of Tables or Hundreds of Databases?
>
> At 04:30 AM 2/10/2009, you wrote:
> >Thanks for your comments Mike.
> >
> >The largest table contains 48 columns (objects), the second largest 20
> >columns (users) and all the rest are l
At 04:30 AM 2/10/2009, you wrote:
Thanks for your comments Mike.
The largest table contains 48 columns (objects), the second largest 20
columns (users) and all the rest are less than 10 columns. The instance
sizes range from 10MB to 1GB.
Transactions and row locking are required. Most queries a
> > Dear Geniuses,
> >
> > I have an application requiring ~30 InnoDB tables, which needs to scale
> up
> > to at least 500 application instances (500 instances * ~30 tables =
> 15,000
> > tables).
> >
> > Discussions in the archives suggest I would be better o
Hi Michael,
On Mon, Feb 9, 2009 at 6:03 PM, Michael Addyman
wrote:
> Dear Geniuses,
>
> I have an application requiring ~30 InnoDB tables, which needs to scale up
> to at least 500 application instances (500 instances * ~30 tables = 15,000
> tables).
>
> Discussions in t
We'll continue to use many replication clusters of course. And yes, we use
bonded gigabit ethernet.
I stumbled across Dolphin Express today - if only there were a cheap
alternative!
Thanks for the reassurance!
On Tue, Feb 10, 2009 at 2:21 PM, Johan De Meersman wrote:
>
>
> On Tue, Feb 10, 2009
On Tue, Feb 10, 2009 at 2:57 PM, Michael Addyman <
michael.addy...@googlemail.com> wrote:
> Hooray! http://code.google.com/p/mysql-master-master/
>
> Am I crazy to be considering replicating 500+ databases? I think so...
>
I don't think the number of databases is an issue - the main point is the
ould also allow databases to be finely tuned to the table type, size,
>> > workload and writes : updates : reads ratio.
>> >
>> > However, re-developing the database layer to achieve this looks
>> incredibly
>> > difficult.
>> >
>> > An easy solution
Johan, we considered this approach but concluded it would require too much
re-development (more than just the database layer).
Thanks anyway.
On Tue, Feb 10, 2009 at 11:47 AM, Johan De Meersman wrote:
>
>
> On Tue, Feb 10, 2009 at 12:39 PM, Michael Addyman <
> michael.addy...@googlemail.com> wro
> > difficult.
> >
> > An easy solution would be to have ~100 instances per database, resulting
> in
> > ~3000 tables per database, and ~5 database clusters.
> >
> > I think my final suggestion is the most suitable.
> >
> > What would your recommendations be
t;
> Michael.
>
> On Tue, Feb 10, 2009 at 6:01 AM, mos wrote:
>
>> At 05:03 PM 2/9/2009, Michael Addyman wrote:
>>
>>> Dear Geniuses,
>>>
>>> I have an application requiring ~30 InnoDB tables, which needs to scale up
>>> to at least 500
On Tue, Feb 10, 2009 at 12:39 PM, Michael Addyman <
michael.addy...@googlemail.com> wrote:
>
> I have now thought of having 1 table type per database (i.e. ~30
> databases).
> This would be easier and cheaper to manage than hundreds of databases, and
> would also allow databases to be finely tuned
>>
>> I have an application requiring ~30 InnoDB tables, which needs to scale up
>> to at least 500 application instances (500 instances * ~30 tables = 15,000
>> tables).
>>
>
> Some of the questions people are going to ask are:
> How large are each of the 30
>> Dear Geniuses,
>>
>> I have an application requiring ~30 InnoDB tables, which needs to scale up
>> to at least 500 application instances (500 instances * ~30 tables = 15,000
>> tables).
>>
>
> Some of the questions people are going to ask are:
> How
an wrote:
>
>> Dear Geniuses,
>>
>> I have an application requiring ~30 InnoDB tables, which needs to scale up
>> to at least 500 application instances (500 instances * ~30 tables = 15,000
>> tables).
>>
>
> Some of the questions people are going to ask
At 05:03 PM 2/9/2009, Michael Addyman wrote:
Dear Geniuses,
I have an application requiring ~30 InnoDB tables, which needs to scale up
to at least 500 application instances (500 instances * ~30 tables = 15,000
tables).
Some of the questions people are going to ask are:
How large are each of
Dear Geniuses,
I have an application requiring ~30 InnoDB tables, which needs to scale up
to at least 500 application instances (500 instances * ~30 tables = 15,000
tables).
Discussions in the archives suggest I would be better off having independent
databases for each of the application
WHY do I see this error when restoring my backup db :
" InnoDB: Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. "
GOAL: Trying to restore mysql backup on different host
using InnoDB backup that copes the backed up files to a f
Gary,
I need to know a lot about your workload to say whether it will work
well on InnoDB with 4+ processors. You can check
http://www.mysqlperformanceblog.com/ for a lot of benchmarks in this
area. But in general, my opinion is that for most workloads, 4 total
processors (cores included) is
A few weeks back I was reading an article that said that INNODB doesn't take
adantage of servers using more than 4 processors. I think I also recieved this
as a reply some time ago as to the same thing.
I was wondering if this is indeed true. We are using 5.1.30 and wanted to
pickup
MySQL University: Scalability Challenges in an InnoDB-based Replication
Environment
This Thursday (January 29th), we're continuing our series of sessions on
MySQL performance measuring and improvements with David Lutz'
presentation titled Scalability Challenges in an InnoDB-based
R
MySQL University: Low-Level Locking in mysqld and InnoDB
Happy New Year!
MySQL University sessions are starting again after the winter break.
This Thursday, we're beginning with Tim Cook's presentation on low-level
locking in mysqld and InnoDB – the good, the bad, and the ugly. Tim
wo
Hi Nipuna,
InnoDB can be disabled with the skip-innodb option. MyISAM can't
really be disabled because it's required to read the grant tables.
-Eric
On Sat, Dec 27, 2008 at 4:21 AM, Nipuna Perera wrote:
> Hi All,
>
> I'm using mysql-cluster-gpl-6.2.15 for create
,
1. Is it possible to disable InnoDB and MyISAM engines while using the ndb
cluster in mysqld servers, if it is yes, can you tell me the way of doing
it?
2. Is there having any disterbance for ndb cluster by disabling the InnoDB
and MyISAM?
Thanks and Regards,
--
Nipuna Perera
නිපුණ පෙ
ebuilt)
7. Reload mysql sever from /root/MySQLData.sql
The only way ibdata1 will grow is with internal data dictionary information on
InnoDB tables. Data and Index Info will all reside in its own tablespace on a
per-table basis. When you run OPTIMIZE TABLE on an InnoDB table in its own
tablespace, that table
Hi jones,
Innodb does not release the space unless you optimize the tables. To dot
that you need to run dummy alter on all tables, by issuing "Alter table
engine=InnoDB"
but the space shall not regaing unless you start the table with
"innodb_file_per_table" option.
Then
Hi,
Since u have cancled the job, those in-complete temp files can be
deleted from the file system.
ok - but I'm using InnoDB. The IBdata file is bumped up. There are no
temp files on the database directory.
What's the problem with a larger ibdata-file? If the index is dropped
Hello Shachi,
> I thought you always have to go to the physical location and delete
> the tmp files manually. These are created in tmp folder.
>
> I am not sure if restarting helps...
since I am using InnoDB, there is no tmp folder.
The Ibdata file after killing alter table comm
Hi Ananda,
> So, now u dont have free space in your file system.
> Is this a production db.
> I think, restarting the db, should not cause any harm. Which version
> of mysql.
no free space it not my problem. I have only noticed that ibdata file
uses more space than before. Yes this is an producti
nt" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, December 04, 2008 4:09 PM
Subject: Re: Alter Table - InnoDB
So, now u dont have free space in your file system.
Is this a production db.
I think, restarting the db, should not cause any harm. Which version of
mysql.
regards
anandkl
O
ob, those in-complete temp files can be
> > deleted from the file system.
>
> ok - but I'm using InnoDB. The IBdata file is bumped up. There are no
> temp files on the database directory.
>
> Greets,
>Jonas
>
Hi Ananda,
> Since u have cancled the job, those in-complete temp files can be
> deleted from the file system.
ok - but I'm using InnoDB. The IBdata file is bumped up. There are no
temp files on the database directory.
Greets,
Jonas
--
MySQL General Mailing List
For li
TED]> wrote:
>
> Hello,
>
> we having an 60 GB InnoDB database. The table with the problem is about
> 12GB.
>
> On of our scripts has got a problem and run 60 times an alter table:
>
> ALTER TABLE `foo` ADD INDEX ( `bar` ) ;
>
> We had to kill the alter table
Hello,
we having an 60 GB InnoDB database. The table with the problem is about
12GB.
On of our scripts has got a problem and run 60 times an alter table:
ALTER TABLE `foo` ADD INDEX ( `bar` ) ;
We had to kill the alter table commands with kill on the mysql console.
Now we have one index on the
Hi All,I need tom combine two ndb cluster db and one MyISAM db and one
InnoDB db together using one mysqld demon,
can anyone help me to build the my.cnf?
ndb cluster details
ndb node1 = 172.18.18.1
ndb node2 = 172.18.18.2
ndb_mdmd1 = 172.18.18.3
ndb_mdmd2 = 172.18.18.4
myisam db details
only for nightly dumps.
There are 2245 databases, the majority of those (2240 or so) have 195
tables, of which about 190 are InnoDB (with "innodb_file_per_table"
set). That means that there is the default ibdata1 that is 1Gig, and
2 ib_logfile files, 128 Megs each, and then the ibd file
gt;query at 0x2aaae00bcd40 is invalid pointer
thd->thread_id=9694
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Number of processes running now: 0
081103 19:47:13 mysqld restarted
InnoD
t; I checked every table on all databases. All are using MYISAM.
>
> innodb section in my.cnf is commented out.
The innodb engine defaults to being enabled, so unless you have
"skip-innodb" in your my.cnf, the engine itself will start and generate
those three files, even if you do
I see the following log files
-rw-rw 1 mysql mysql 10485760 Sep 16 17:30 ibdata1
-rw-rw 1 mysql mysql5242880 Sep 16 17:30 ib_logfile0
-rw-rw 1 mysql mysql5242880 Jan 17 2006 ib_logfile1
I checked every table on all databases. All are using MYISAM.
innodb section in
ulate the total size of all InnoDB tables?
> --
> Ryan Schwartz
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
>
>
--
MySQL General Mailing List
For list
Hey Josh, I came in really late on this discussion. It's been my
experience that InnoDB is great until the size of the database/indexes
surpasses the amount of memory you can give to InnoDB for caching.
The performance drop off is pretty quick and dramatic. I've seen this
happ
chunks
>> disproportinate to what you immediately need, causing bursty performance.
>> * If your remaining MyISAM tables don't need it, take 2GB of the
>> key_buffer
>> alocation and put it towards the innodb buffer pool
>>
>> What are the system's s
x27;t need it, take 2GB of the key_buffer
alocation and put it towards the innodb buffer pool
What are the system's specs? What's it's underlying storage? What flags
were used when you created the filesystem(s)? What OS/Version of MySQL are
you running? Could you send us some io
2GB of the key_buffer
alocation and put it towards the innodb buffer pool
What are the system's specs? What's it's underlying storage? What flags
were used when you created the filesystem(s)? What OS/Version of MySQL are
you running? Could you send us some iostat output?
Thanks
On Thu, Sep 4, 2008 at 6:43 PM, Josh Miller <[EMAIL PROTECTED]> wrote:
> We'd like to prove InnoDB and move onto that storage engine for the
> transaction support, MVCC, etc.. but we're finding that performance is poor.
Well, thousands of large InnoDB database users prove
Perrin said it right.
If your app needs InnoDB (transaction, row level locks...) write it that
way.
Don't expect performance from a MyIsam compliant app when using InnoDB.
TomH
-Original Message-
From: Josh Miller [mailto:[EMAIL PROTECTED]
Sent: Friday, September 05, 2008 12:42
work on re-designing the queries and indexes. We
have a less than 50% index usage rate which is disastrous.
We'd like to prove InnoDB and move onto that storage engine for the
transaction support, MVCC, etc.. but we're finding that performance is poor.
Thanks!
Josh Miller, RHCE
--
M
Tom Horstmann wrote:
Addendum..
Please also try increasing your innodb_log_file_size to a much higher value
if you
have lots of writes/transactions. Maybe 250MB is a good first try.
You need to delete/move the InnoDB logs before restart.
Not sure about this, but please also set
est setting for your hardware. You might
want to go back to the default.
> Any ideas for what to check or modify to increase the performance here and
> let MyISAM and InnoDB play better together?
What you really need to do is look at which queries are slow and run
EXPLAIN plans for them. Mos
Addendum..
Please also try increasing your innodb_log_file_size to a much higher value
if you
have lots of writes/transactions. Maybe 250MB is a good first try.
You need to delete/move the InnoDB logs before restart.
Not sure about this, but please also set innodb_log_buffer_size. Try
something
ts
to the InnoDB table?
Is the table mostly read or more written?
You could set innodb_flush_log_at_trx_commit=2 if you may loose the latest
InnoDB
writes in case of a MySQL crash. It should give you much less IO for writes
on your
InnoDB tables.
Please see http://dev.mysql.com/doc/refman/4.1/
Tom Horstmann wrote:
Hello Josh,
why you moved your table to InnoDB? Your description doesn't sound like the
tables rows
are accessed concurrently and need to be locked? Are you sure you need
InnoDB for this table?
If you need InnoDB you probably need to redesign your queries and
Hello Josh,
why you moved your table to InnoDB? Your description doesn't sound like the
tables rows
are accessed concurrently and need to be locked? Are you sure you need
InnoDB for this table?
If you need InnoDB you probably need to redesign your queries and table
structure to get them
Good afternoon,
I have recently converted a large table from MyISAM to InnoDB and am
experiencing severe performance issues because of it. HTTP response
times have gone from avg .25 seconds to avg 2-3 seconds. Details follow:
PHP/MySQL website, no memcached, 3 web nodes that interact with
See Thread at: http://www.techienuggets.com/Detail?tx=48414 Posted on behalf of
a User
I have a MySQL 5.0 InnoDB database that's about 1 GB in size so it's still
pretty tiny. Is there any performance enhancement maintenance that should be
done on the tables? I do a weekly Optimize t
Good Morning Mike and Brent
Ive been following and implementing MYSQL tuning suggestions at
http://dev.mysql.com/doc/refman/5.1/en/innodb-tuning.html
I did'nt see any suggestions on converting the entire DB to INNODB
or converting the individual tables to INNODB
Suggestions?
M
transaction support, I use InnoDB.
What you did was not only switch the default table type, but you
disabled the InnoDB table type. As you may already know, MySQL's table
types are different engines that are really plug-ins. You can disable
those plug-ins if you like, which is what you did.
if you switch the default engine type any new tables would be created
with that new engine type. it does not convert existing tables to
your new format.
if you have existing innodb tables you need to have the innodb
settings active, in my.cnf
On 15 Aug 2008, at 06:01, [EMAIL PROTECTED
Hello mysql,
As I have previously mentioned, I installed WAMPSERVER 2.0 on my
Windows XP pro box recently. It installed INNODB as the Default
Engine.
All of my legacy Databases are MYISAM and after the installation, I
copied them all into the DATA folder and everything worked, even
adding new
I have a question about how InnoDB deals with fragmentation within
it's data files. Let me describe my usage scenario to you:
1.) Records are inserted into a InnoDB table. We'll call this table
"A". It contains several different kinds of columns including
VARCHARs.
hdparm -Tt /dev/sdX ?
Ian Simpson wrote:
That's pretty much what I've been doing to get that the drive is running
at 100% bandwidth.
What I'd like is something that just gives the bandwidth of the device
in terms of Mb/s: you can probably work it out using that iostat
command, seeing how mu
Hi Alex,
> >> >> >>
> >> >> >> Configurations are identical, other than the
> >> >> >> differences I initially
> >> >> >> mentioned. I've diffed both th
ces I initially
>> >> >> mentioned. I've diffed both the configuration
>> files
>> >> >> and the output of
>> >> >> SHOW VARIABLES on both servers.
>> &g
k about the
> >> >> RAID settings.
> >> >>
> >> >> Variable_name: innodb_flush_log_at_trx_commit
> >> >>Value: 1
> >> >> Variable_name: sy
able_name: innodb_flush_log_at_trx_commit
>> >>Value: 1
>> >> Variable_name: sync_binlog
>> >>Value: 0
>> >> Variable_name: in
Value: 0
> >> Variable_name: innodb_locks_unsafe_for_binlog
> >>Value: OFF
> >>
> >> Thanks
> >>
> >> --
> >>
innodb_locks_unsafe_for_binlog
>>Value: OFF
>>
>> Thanks
>>
>> --
>> Ian Simpson
>>
>> On Fri, 2008-06-13 at 17:43 +0530, Alex Arul Lurthu
>>
the data that needs to be modified by the slave sql
thread.
3. set innodb flush trx log commit to 2 or even 0.
4. Out of desperation sometimes disable innodb double write and also xa
support.
On Fri, Jun 13, 2008 at 7:33 PM, Ian Simpson <[EMAIL PROTECTED]> wrote:
>
>
> Hi g
> Please check if the my.cnf configurations to be the
> same.
> >
> > What are your configuration parameters in terms of
> innodh flush log
> > trx commit , bin logging, sync binlo
;> --
>> Ian Simpson
>>
>> On Fri, 2008-06-13 at 17:43 +0530, Alex Arul Lurthu wrote:
>> > Please check if the my.cnf configurations to be the same.
>> >
>> > What are your configuration parameters in terms of innodh flush log
>> > trx commit ,
Value: OFF
>
> Thanks
>
> --
> Ian Simpson
>
> On Fri, 2008-06-13 at 17:43 +0530, Alex Arul Lurthu wrote:
> > Please check if the my.cnf configurations to be the same.
> >
> > What are your configuration parameters in terms of innodh flush log
> > tr
> What are your configuration parameters in terms of innodh flush log
> trx commit , bin logging, sync binlog and innodb unsafe for binlog ?
>
> If the systems have raid, check if the BBWC is enabled on the new host
> and WB is enabled.
>
>
> On Fri, Jun 13, 2008 at 5:02 PM,
Please check if the my.cnf configurations to be the same.
What are your configuration parameters in terms of innodh flush log trx
commit , bin logging, sync binlog and innodb unsafe for binlog ?
If the systems have raid, check if the BBWC is enabled on the new host and
WB is enabled.
On Fri
ving a real struggle processing INSERT statements to InnoDB
tables; it's maxing out at around 100 inserts per second, even with very
simple two column tables (inserts into MyISAM tables run fine).
Meanwhile, the original server can happily process around 1000
inserts/sec into an id
Hi All,
I am converting some of the myisam tables to innodb.
What are the things i need to take care before doing this and also after
doing this.
regards
anandkl
I can see in MySQL Administrator that both tables are InnoDB.
Here is my table structure:
DROP TABLE IF EXISTS `members_orders`;
CREATE TABLE `members_orders` (
`id_order` int(10) unsigned NOT NULL auto_increment,
`paid_date` datetime default NULL,
`record_date` datetime NOT NULL,
`total` decimal(7,
You should keep it on in my opinion.
On Tue, May 13, 2008 at 6:04 PM, Nico Sabbi <[EMAIL PROTECTED]> wrote:
> Hi,
> I guess that when I'm using only Innodb and no replication I can
> safely disable mysql's (bin-) log files (that grow to no end) because
> Innodb
---+
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great
performance |
| MEMORY | YES | Hash based, stored in memory, useful for
temporary tables |
| InnoDB | YES | Supports transactions, row-level locking, and
foreign keys |
|
Hi,
I guess that when I'm using only Innodb and no replication I can
safely disable mysql's (bin-) log files (that grow to no end) because
Innodb has its own log files. Is it correct?
Thanks,
Nico
--
MySQL General Mailing List
For list archives: http://lists.mysql.co
On May 9, 2008, at 6:58 AM, Chris Pirazzi wrote:
Hello,
I _thought_ I knew how InnoDB worked, but due to a recent mysql doc
change, I am no longer sure--the change made the dox significantly
less clear, and potentially code-breaking.
Please can someone tell me the real behavior of InnoDB in
Hello,
I _thought_ I knew how InnoDB worked, but due to a recent mysql doc
change, I am no longer sure--the change made the dox significantly
less clear, and potentially code-breaking.
Please can someone tell me the real behavior of InnoDB in the
following case, and ideally clarify the dox too
Thanks for the idea. Unfortunately nothing I can easily use (for
instance in MySql Administrator) to log and monitor the lag in bytes
between log writes and row data writes. :)
Iñigo Medina García wrote:
Hi Ben,
Dear MySql,
I am trying to optimise InnoDB, and trying to find out how
Hi Ben,
>
> Dear MySql,
>
> I am trying to optimise InnoDB, and trying to find out how much of the
> innodb log file contains row data which has not been written to storage.
>
> Therefore I can optimize the size of the log, keeping it low to reduce
> crash recovery ti
Dear MySql,
I am trying to optimise InnoDB, and trying to find out how much of the
innodb log file contains row data which has not been written to storage.
Therefore I can optimize the size of the log, keeping it low to reduce
crash recovery time yet high enough to be useful.
I can see
try this back up the iblog and ibdata files and move it to some
>>> other location from /data/mysql
>>> and restart mysql to see if it shows innodb up on show engines, by doing
>>> this atleast u can isolate the
>>> problem is not with iblog or ibdata files
>&g
iblog and ibdata files and move it to some
other location from /data/mysql
and restart mysql to see if it shows innodb up on show engines, by doing
this atleast u can isolate the
problem is not with iblog or ibdata files
-srini
Krishna Chandra Prajapati wrote:
Hi,
What ever you have wri
ysql
> and restart mysql to see if it shows innodb up on show engines, by doing
> this atleast u can isolate the
> problem is not with iblog or ibdata files
>
> -srini
>
>
> Krishna Chandra Prajapati wrote:
>
> > Hi,
> >
> > What ever you have written i did
empty. What else can be the reason for
> > disable innodb.
>
> You mentioned that you're using Debian. The MySQL packages in Debian
> using syslog, check /var/log/syslog for errors.
>
>Norbert
>
>
> --
> MySQL General Mailing List
> For list ar
It could be the problem with permissions or sizes of iblog or ibdata files
Can you try this back up the iblog and ibdata files and move it to some
other location from /data/mysql
and restart mysql to see if it shows innodb up on show engines, by doing
this atleast u can isolate the
problem is
Am Mittwoch, den 07.05.2008, 01:30 schrieb Krishna Chandra Prajapati:
> Currently error log file is empty. What else can be the reason for
> disable innodb.
You mentioned that you're using Debian. The MySQL packages in Debian
using syslog, check /var/log/syslog for errors.
601 - 700 of 5315 matches
Mail list logo
