Re: memory usage - mysql tuning!!

bruce a écrit : Hi.. Fairly new to mysql, in particular tuning. I have a test mysql db, on a test server. I've got a test app that runs on multiple servers, with each test app, firing/accessing data from the central db server. the central server is on a 2GHz, 1GMem, 100G system. MySQL is the b

memory usage - mysql tuning!!

Hi.. Fairly new to mysql, in particular tuning. I have a test mysql db, on a test server. I've got a test app that runs on multiple servers, with each test app, firing/accessing data from the central db server. the central server is on a 2GHz, 1GMem, 100G system. MySQL is the basic app. the remo

Re: innodb crash

Check the permission on mysql database realted files, it shoud be owned by mysql user. regards anandkl On Feb 13, 2008 4:42 PM, Saravanan <[EMAIL PROTECTED]> wrote: > Hi List, > > I got crash when i was creating procedure and it listed the following > error > > *** glibc detected *** /usr/local/

innodb crash

Hi List, I got crash when i was creating procedure and it listed the following error *** glibc detected *** /usr/local/mysql2/libexec/mysqld: corrupted double-linked list: 0x0b4ae810 *** === Backtrace: = /lib/libc.so.6[0x8949be] /lib/libc.so.6(cfree+0x90)[0x897fc0] /usr/lib/libstdc++

RE: [SPAM] - MS SQL emulator for MySQL in order to support MS Project Server, Sharepoint... - Email found in subject

http://blogs.ittoolbox.com/km/sharepoint/archives/sharepoint-and-mysql-2 2051 hmm.. but I think you might have problems getting support from sharepoint's vendor... IIRC they always push to use SQL server for this.. (we know the reason why.. :) ) >-Original Message- >From: Jacob,

MS SQL emulator for MySQL in order to support MS Project Server, Sharepoint...

I apologize for asking this question. I am somewhat confused by Microsoft's Licensing and I personally can not justify to senior management why MS SQL should be procured instead of procuring software more urgent requirements. I had the not so bright idea that maybe a MS SQL emulator or compatibili

MySQL 5.1.23-rc has been released (part 3)

Dear MySQL users, We are proud to present to you the MySQL Server 5.1.23-rc release, a new "release candidate" version of the popular open source database. Bear in mind that this is still a "candidate" release, and as with any other pre-production release, caution should be taken when installing

MySQL 5.1.23-rc has been released (part 2)

Dear MySQL users, We are proud to present to you the MySQL Server 5.1.23-rc release, a new "release candidate" version of the popular open source database. Bear in mind that this is still a "candidate" release, and as with any other pre-production release, caution should be taken when installing

MySQL 5.1.23-rc has been released (part 1)

Dear MySQL users, We are proud to present to you the MySQL Server 5.1.23-rc release, a new "release candidate" version of the popular open source database. Bear in mind that this is still a "candidate" release, and as with any other pre-production release, caution should be taken when installing

Re: Crashed InnoDB

Does it start up in a stable enough state to run a mysqldump of the tables? -Dan On 2/13/08 3:54 PM, "Bryan Cantwell" <[EMAIL PROTECTED]> wrote: > I can get mysql to start with that but still complains about corruptionŠ If I > try to do optimize table for instance, it crashes againŠ > I get th

RE: Crashed InnoDB

I can get mysql to start with that but still complains about corruption... If I try to do optimize table for instance, it crashes again... I get this now: 080213 14:32:16 InnoDB: Error: page 4246078 log sequence number 53 188440667 InnoDB: is in the future! Current system log sequence number 0

Re: Crashed InnoDB

Have you tried starting mysqld with innodb_force_recovery = x ? (where x = values defined below) http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html That might get you past the corruption that's killing startup. -Dan On 2/13/08 12:32 PM, "Bryan Cantwell" <[EMAIL PROTECTED]> wrote:

RE: Crashed InnoDB

No input on this one? -Original Message- From: Bryan Cantwell [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 11:51 AM To: mysql@lists.mysql.com Subject: Crashed InnoDB We had a power outage, now the mysql wont start at all. Here is the err file output... Any help on how to

Re: view irregularities

Lev Lvovsky wrote: I'm running into a difficult to reproduce problem with a view which is similar to the following: CREATE TABLE Common ( COMMON_ID INT UNSIGNED AUTO_INCREMENT PRIMARY KEY, COMMON_NAME VARCHAR(50), UNIQUE(COMMON_NAME) ) ENGINE = InnoDB; CREATE TABLE Parent

RE: crash

At 01:23 AM 2/13/2008, you wrote: Unfortuantely the server crashed and I had to manually boost it It happened before and I would like to know why so it doesn't again I don't have any innodb database on the system, only mysiam So why not disable InnoDb in my.cnf by uncommenting "skip-innodb"