MYSQL DATABASE SERVER
Hi All, The production server on which mysql database was running, get shutdown on one day. Then we have to manually start it. The server is hpdl585. What can be the reason of shutdown. What has gone wrong with the server. Is there is any to find the reason for shutdown. Thanks, Krishna
Re: MySQL 5.1.22 is out
Is there any kind of timetable for when 5.1 is actually expected to be released? - Original Message - From: "Kaj Arnö" <[EMAIL PROTECTED]> To: "MySQL List" Sent: Wednesday, October 17, 2007 3:07 AM Subject: BLOG: MySQL 5.1.22 is out MySQL users, Sorry for spamming mysql@lists.mysql.com, but you may be interested in my blog entry that complements our MySQL 5.1.22 announcement. The Real Thing in HTML is on http://www.planetmysql.org/kaj/?p=131 and pasted below for offline reading. MySQL 5.1.22 is out A good two weeks ago, MySQL 5.1.22 was released. MySQL 5.1 is a new release of MySQL Server, with new features like * partitioning (likely the top feature in 5.1) * events (”crontab” triggers in the database) * row-based replication * table logs * some XML functions and also with major bug fixes, such as the AUTO_INCREMENT table-lock contention in InnoDB (fixed now in 5.1.22), as well as early indications of performance improvements of up to 20 % - 40 % on dual cores in some scenarios. Jay Pipes has written an overview that compresses all of the pointers to 5.1 into one article, MySQL 5.1 Article Recap. I recommend you read it. I also recommend the manual section What’s New in MySQL 5.1. With 5.1.22, MySQL also changed the maturity state to “RC”, Release Candidate. Looking at our own Support Policies, Release Candidate (aka Gamma) release is defined as follows: Release Candidate binaries, also known as Gamma releases, are believed stable, having passed all of MySQL’s internal testing, and with all known fatal runtime bugs fixed. However this release has not been in widespread use long enough to know for sure that all bugs have been identified. However, we recognise that this particular RC does not fit the definition exactly. We still have some fatal runtime bugs left. We are producing an errata list of these, and expect to have the list ready and published on by 23 Oct 2007. We know that we should have published this list together with the RC itself, and we are now working as fast as we can to fix this. We know we have thus released our RC too early according to our own standards, and we are doing our best to fix it. We apologise for any inconvenience/miscommunication and are working on improving our internal guidelines to ensure it doesn’t happen again. That said, 5.1.22 is a great release, one that we’re proud of, and very likely worthy of your attention! Kaj -- Kaj Arnö <[EMAIL PROTECTED]> MySQL AB, VP Community Relations -- 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 archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: urgente
Hello David, On Tue, 2007-10-16 at 12:59 -0500, david chan cocom wrote: > estos son los errores que proporciona mysql cuando instalo el paquete o el > codigo fuente. > Espero que me puedan ayudar me urge mucho. > P.D hace 15 dias que tengo este problema por favor ayudenme de antemano se > los agradezco. Why you don't try to compile-it? ./configure \ "--prefix=/mysql5/bin-5.0.37" \ "--enable-thread-safe-client" \ "--with-pthread" \ "--with-tcp-port=3306" \ make make install PATH=$PATH:/mysql5/bin-5.0.37/bin export PATH groupadd mysql adduser -g mysql mysql mkdir /mysql5/bin-5.0.37/var chown -R mysql:mysql /mysql5/bin-5.0.37/var su - mysql mysql_install_db cp /mysql5/bin-5.0.37/share/mysql/mysql.server /etc/init.d/mysql5 /etc/init.d/mysql5 start mysqladmin -v password YOUR_PASSWORD PS: You does NOT need to change your "prefix"! -- Tiago Cruz http://everlinux.com Linux User #282636 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
urgente
buenas tardes espero que al recibir este mail se encuentre bien de salud todos . El motivo por el cual les envio este mail, es porque mysql que estoy instalando en solaris 10 marca errores cuando estoy instalando el paquete , el mysql lo obtuve de la pagina sunfreeware y cuando le doy un pkgadd mysql-5.0.41 empieza a instalarse y casi a la mitad de la instalacion sale este mensaje: installing MYSQL system tables... unknown suffix '@' used for variable 'port' (value '@mysql_TCP_PORT@') 071001 12:24:11 [ERROR] /usr/local/mysql-5.0.41/libexec/mysqld: error while setting value '@mysql_tcp_port' to 'port' installation of system tables failed! examine the log in /var/lib/mysql for more information. You can try to start the mysqld daemon with: /usr/local/mysql-5.0.41/libexec/mysqld --skip-grant & and use the command line tool /usr/local/mysql-5.0.41/bin/mysql to connect to the mysql database and look at the grant tables: bash# /usr/local/mysql-5.0.41/bin/mysql -u root mysql mysql>show tables try mysqld --help if you have problems with parths .using --log gives you a log in /var/lib/mysql that may be helpful. the latest information about mysql is available on the web at http://www.mysql.com please consult the mysql manual sections 'problems running mysql_install_db' and manual section that describes problems on your os. another information source is the mysql email archive please check all of the above before mailing us! and if you do mail, you must use the /usr/local/mysql-5.0.41/bin/mysqlbug script! despues que sale todo dice que fue un exito la instalacion. Cuando le doy bin/mysql_install_db --user=mysql vuelve a salir lo mismo que ya escribe arriba de este mail. Tambien ya baje el codigo fuente de mysql-5.0.41 pero en este tambien me marca errores cuando ejecuto el make me sale estos errores: make[2]: [all-recursive] error1 make[2]: leaving directory '/usr/local/mysql-5.0.41/server-tool' make[1]: [all-recursive] error 1 make[1]: leaving directory '/usr/local/mysql-5.0.41' make [all] error2 estos son los errores que proporciona mysql cuando instalo el paquete o el codigo fuente. Espero que me puedan ayudar me urge mucho. P.D hace 15 dias que tengo este problema por favor ayudenme de antemano se los agradezco. buen dia - ¡Sé un mejor ambientalista! Encuentra consejos para cuidar el lugar donde vivimos en: http://mx.yahoo.com/promos/mejorambientalista.html
[mysql] Text = Tinytext = MediumText = LongText?
Hello everyone, hopefully a quick question: is there a functional difference between the various text field sizes other than size? For example if I wanted to could I run a FULLTEXT index against a LongText field? The collary is of course how good of an idea is this, assuming that MOST of the data isn't even long enough to fill a text field. Thanks, Craig This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Bug?: "SELECT *, Field" vs. "SELECT Field, *"
Hi, When i try: "SELECT *, id FROM " all is fine. But if i want the "*" at the end (because the table is large) i try: "SELECT id, * FROM " and got: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '* FROM ' at line 1 I think this is a bug? It works when i try: "SELECT id, .* FROM " The Same thing is: "SELECT *, * FROM " (which possibly makes no sense) -Ralf -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: find real/valid name current db
ups, typo ... Sebastian Mendel schrieb: > Hi, > > how can i find the real/valid name for current active db? > > Windows, lower_case_table_names = 2 > > CREATE DATABASE `UPPERCASE`; > USE `UPPERCASE`; > SELECT DATABASE(); > // `UPPERCASE` should read // returns `uppercase` > but working with the returned lower case `UPPERCASE` results in an invlaid > db error should read: but working with the returned lower case `uppercase` results in an invalid db error > also see bug #31658 (http://bugs.mysql.com/31658) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
BLOG: MySQL 5.1.22 is out
MySQL users, Sorry for spamming mysql@lists.mysql.com, but you may be interested in my blog entry that complements our MySQL 5.1.22 announcement. The Real Thing in HTML is on http://www.planetmysql.org/kaj/?p=131 and pasted below for offline reading. MySQL 5.1.22 is out A good two weeks ago, MySQL 5.1.22 was released. MySQL 5.1 is a new release of MySQL Server, with new features like * partitioning (likely the top feature in 5.1) * events (”crontab” triggers in the database) * row-based replication * table logs * some XML functions and also with major bug fixes, such as the AUTO_INCREMENT table-lock contention in InnoDB (fixed now in 5.1.22), as well as early indications of performance improvements of up to 20 % - 40 % on dual cores in some scenarios. Jay Pipes has written an overview that compresses all of the pointers to 5.1 into one article, MySQL 5.1 Article Recap. I recommend you read it. I also recommend the manual section What’s New in MySQL 5.1. With 5.1.22, MySQL also changed the maturity state to “RC”, Release Candidate. Looking at our own Support Policies, Release Candidate (aka Gamma) release is defined as follows: Release Candidate binaries, also known as Gamma releases, are believed stable, having passed all of MySQL’s internal testing, and with all known fatal runtime bugs fixed. However this release has not been in widespread use long enough to know for sure that all bugs have been identified. However, we recognise that this particular RC does not fit the definition exactly. We still have some fatal runtime bugs left. We are producing an errata list of these, and expect to have the list ready and published on by 23 Oct 2007. We know that we should have published this list together with the RC itself, and we are now working as fast as we can to fix this. We know we have thus released our RC too early according to our own standards, and we are doing our best to fix it. We apologise for any inconvenience/miscommunication and are working on improving our internal guidelines to ensure it doesn’t happen again. That said, 5.1.22 is a great release, one that we’re proud of, and very likely worthy of your attention! Kaj -- Kaj Arnö <[EMAIL PROTECTED]> MySQL AB, VP Community Relations -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
find real/valid name current db
Hi, how can i find the real/valid name for current active db? Windows, lower_case_table_names = 2 CREATE DATABASE `UPPERCASE`; USE `UPPERCASE`; SELECT DATABASE(); // `UPPERCASE` but working with the returned lower case `UPPERCASE` results in an invlaid db error also see bug #31658 (http://bugs.mysql.com/31658) -- Sebastian -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
