Hello.
You can enable logging on the server. See: http://dev.mysql.com/doc/mysql/en/log-files.html You need the error log, query log, slow log. But be careful! Heavy loaded server can produce a lot of messages and your files will grow quickly. If you use InnoDB, you can enable the InnoDB monitors. See: http://dev.mysql.com/doc/mysql/en/innodb-monitor.html You can enable ODBC trace, but it very slows down the system. See: http://dev.mysql.com/doc/mysql/en/myodbc-trace.html The clues can be in one of the log files. matias Castilla <[EMAIL PROTECTED]> wrote: > I have a mysql server running on WIN-XP (in a critical > health area) and it started to give me that error. > At first, the problem ocurred in a machine and then > started to scatter all over the system. On Saturday I > reset the Server Machine and the problem disapeared. > But today applications started to fail again. > Sometimes showing this error messeges and sometimes > not showing the content of some tables. > mat?as. > > _________________________________________________________ > Do You Yahoo!? > Informaci?n de Estados Unidos y Am?rica Latina, en Yahoo! Noticias. > Vis?tanos en http://noticias.espanol.yahoo.com > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
